BatchBook Blog

Archive for Tag

The Secret Sauce: Post Vacation Ketchup

IMG00010

I recently spent a few weeks vacationing with my husband, 3 kids and a rotating stream of relatives and friends at our family retreat on a tiny island north of Portland, Maine. Each day wondering if we should sail, climb the rocks, play on the beach, boogie board, collect starfish, hunt crabs, fish, play tennis, eat mussels, clams or lobsters, or all of the above. At BatchBlue we put a high premium on family time. We talk a bit about mandatory vacations in our Virtual Office Blue Paper, but a customer wrote in recently with the comment, “it is great that you know how to disengaged, but do you find it hard to re-engage?” It’s hard to benefit from the personal time if you are worried about the mounting workload, so I thought I would share a few of my tips on quickly catching up on the waiting backlog.

Here are a few of the things I did to quickly get back up to BatchBlue speed::

  1. Read staff meeting agendas – ok, alright, I did this one while on vacation. Not to prove I work harder than anyone else, but just because leaving your business for a few weeks is like leaving your kids for a few weeks. You can’t not check in once in a while. So on staff meeting days I would check our company wiki and read through the notes that the team had taken during the meeting. Great way to peek in without being noticed.
  2. Search of the daily staff updates – at BatchBlue each staff person sends around a daily report on what they are working on. I set up a filter in Gmail to collect these in a folder while I was gone, so it was pretty easy to quickly read through them chronologically and get a sense of what progress was made while I was out.
  3. Click back through the history of my Twitter feed on the BatchBook dashboard to get a sense of what the Twitterverse was saying about BatchBlue, SBBuzz, or me.
  4. I already have a “BatchBlue” folder in my Google Reader where I subscribe to a number of company related RSS feeds. So all in one place I get a quick glimpse of the following:
    • BatchBlue Blog posts written by the staff while I was gone.
    • BatchBook comments or notes added to contact records in BatchBook. For the most part these were silly remarks by staff about each other, but there is something comforting about catching up on some of the inside company jokes, as well.
    • BatchBlue communications including all e-mails, phone calls, Twitter messages or other communications sent out or received by BatchBlue staff. I admit I would flip back into BatchBook reading most of these – such a great way to remind myself who some of the e-mails recipients are (thank you social media SuperTag!).
    • Forum posts showed me all of the BatchBook questions and suggestions our customers posted in our online forums as well as the BatchBlue responses. I always learn something new in there.
    • Hubspot Feeds are the nice messages our friends at Hubspot send telling us about anyone in the wonderful world of the Web talking about us. A little self-indulgent, but in a good way.

    (more…)

Facebook Twitter Linkedin Email

2 comments so far. Leave a comment of your own.

Our Users Are So Smart: Simple prompt to create a follow-up To-Do

Sometimes the best solutions are really the most simple.

A couple weeks ago, there was a great forum discussion on how to assign follow up tasks immediately after logging communications. This wasn’t just a back-and-forth, this was a full fledged discussion with forum users Bradley, Kenny, HansD, and Stewart taking part.

We have always had the ability to log a communication and to create a To-Do that was assigned to a user and linked back to a communication. But the forum users were looking for a way to “remind” the other users on their account to create a To-Do after logging a communication, if one was necessary. Many approaches were discussed, but the following messages made it clear what we needed to do:

From Bradley:

From a business-process stand point, logging a communication and generating the resulting task are a single action. Yes, you could log the communication, then open it, then start a to-do action. However, you’ve now undertaken three actions as opposed to one, any one of which a staff person could forget or be interrupted before completing.

(more…)

Facebook Twitter Linkedin Email

Leave a comment