Also, Highrise has yet to get the printing right. I tried to print a contact I knew I had to call and the "Tasks" section shows bullets but no text.
Monday, March 26, 2007
Two Quick Tips
Also, Highrise has yet to get the printing right. I tried to print a contact I knew I had to call and the "Tasks" section shows bullets but no text.
Highrise and GTD
Just a quick post to reinforce a great feature of Highrise--the new light weight CRM system from 37Signals. If you're into David Allen's Getting Things Done (GTD) approach to time and life management and are familiar with how he suggests you categorize your tasks by context, you'll love the Tasks feature in Highrise.
First off, you get a drop box of intuitive time frames to choose from that make it super quick to determine the "When it's due" part of the task. Then you get a second drop box of commonly used categories and the ability to create your own (I've added "After Work" and "During Lunch" among others in my list). These categories or context cues are then placed in small black boxes in front of each task making it easy to scan very quickly.
Labels:
37Signals,
David Allen,
Getting Things Done,
GTD,
Highrise,
Time Management
Friday, March 23, 2007
Six Sigma Net Promoter Metric and Tom Peters TGR/TGW
I was listening to episode six of the Six Sigma Pointers podcast by Thomas Pyzdek, this morning, (which I highly recommend, btw) and he was talking about the Net Promoter metric. Essentially, you ask a customer if they would recommend your product or service to a friend or colleague--asking them to respond on a scale from zero to 10. If the customer marks a nine or 10 they are considered "promoters." If they mark a seven or eight they are considered neutral. And if they mark a six or less they are considered "detractors." The metric is derived by subtracting the detractors from the promoters.
The podcast elaborates on how closely this metric correlates with business performance and on how many of the Fortune 500 have adopted it. But what I found most interesting was when Mr. Pyzdek mentioned how one goes about improving this metric. Obviously from a pure math perspective one can either increase the number of promoters or decrease the number of detractors. But each group seems to respond to a different driver. Detractors seem to respond to just getting the basics right and not doing things wrong. Promoters tend to respond to providing a "Wow!" level of service and doing things right.
I think Tom Peters has the clearest description of this distinction in chapter eight (Beyond TQM Toward Wow!) of his book The Tom Peters Seminar. He gives some great examples and insights which I won't attempt to recite here (it's really worth picking up the book!) but his thesis is basically that we need both sides of the equation and when Americans began really looking at quality as a competitive driver we were almost entirely focused on eliminating the "things gone wrong" (TGW) from our systems and processes. And that's important. He makes the point you shouldn't have crumbs on the floor and missing towels when you walk into the hotel room. But that's not enough. We also need to look at "things gone right" (TGR) and find ways to "delight and provide even the unexpressed needs of the customer" (e.g., such as Tom walking into a hotel room where he would be giving a speech the next morning to find a projector and screen set with cables carefully taped down so he could practice his presentation.)
Dr. Goldratt mentions a similar paradigm in Beyond the Goal when he says there are really only two things to worry about:
The podcast elaborates on how closely this metric correlates with business performance and on how many of the Fortune 500 have adopted it. But what I found most interesting was when Mr. Pyzdek mentioned how one goes about improving this metric. Obviously from a pure math perspective one can either increase the number of promoters or decrease the number of detractors. But each group seems to respond to a different driver. Detractors seem to respond to just getting the basics right and not doing things wrong. Promoters tend to respond to providing a "Wow!" level of service and doing things right.
I think Tom Peters has the clearest description of this distinction in chapter eight (Beyond TQM Toward Wow!) of his book The Tom Peters Seminar. He gives some great examples and insights which I won't attempt to recite here (it's really worth picking up the book!) but his thesis is basically that we need both sides of the equation and when Americans began really looking at quality as a competitive driver we were almost entirely focused on eliminating the "things gone wrong" (TGW) from our systems and processes. And that's important. He makes the point you shouldn't have crumbs on the floor and missing towels when you walk into the hotel room. But that's not enough. We also need to look at "things gone right" (TGR) and find ways to "delight and provide even the unexpressed needs of the customer" (e.g., such as Tom walking into a hotel room where he would be giving a speech the next morning to find a projector and screen set with cables carefully taped down so he could practice his presentation.)
Dr. Goldratt mentions a similar paradigm in Beyond the Goal when he says there are really only two things to worry about:
- Things that shouldn't have happened but did; and
- Things that should have happened but did not.
Labels:
Net Promoter Metric,
Six Sigma,
TGR,
TGW,
Theory of Constraints,
Thomas Pyzdek,
TomPeters
Thursday, March 22, 2007
Three Days: Product Overhaul or Just a Meeting?

I've been posting about the new CRM solution from 37Signals called Highrise and complained how the "Cases" feature was only available to premium accounts. Apparently a lot of others didn't like it either. So today, three days after launch, Signals sends out an email informing everyone they're giving cases to everyone, dramatically increased storage limits, even created a new user category and corresponding pricing structure. Their ability to take the pulse of the community and respond quickly and iterate is impressive. Imagine a "big" company doing that...naw, I can't conjure that up either. I'm willing to bet in most companies it would take three days just to find an open slot on everyone's calendar to have a meeting about if we should consider modifying the product.
It reminds me of Tom Peters' example of Paul Paliska's Professional Parking Service, Inc. in The Tom Peters Seminar (page 139). Essentially, Tom showed up to speak at a luncheon at a very busy Orange County Marriott and despite all the traffic and people he noticed everyone was parked in very short order. He complimented Marriott on it during his speech only to learn afterwards that Marriott hadn't parked the cars--Paul's subcontracted parking service had. Tom mused that since Paul and his crew were so focused on and good at event parking they probably got better insurance rates than "giant" Marriott. So he posed the question, "Who's really the big fish in this picture?"
Seth's saying about the same things these days. And I expect we'll get more of that with his new book The Dip coming out in May. Excellence comes from focus. The question is how big can one get before you're no longer nimble? Maybe when you can't pass the rework and relaunch your whole product in 36 hours test?
Labels:
37Signals,
Cases Feature,
Highrise,
Seth Godin,
Small is the new Big,
Tom Peters
Wednesday, March 21, 2007
Follow-up on Highrise: Emailing Notes--Where Have You Been All My Life?
Highrise has this feature where every account is given a unique "drop box" email address. Simply include this address in the Cc or Bcc fields and the email text is sent to the appropriate contact as a new note. It then shows up as a mail icon in the contact's overview.I mentioned in yesterday's post about Highrise that I'd had some exposure to evaluating enterprise CRM systems. When I was investigating various options and interviewed a number of existing users and their managers about the adoption rate of whatever system they had installed, one issue kept coming up over and over again: integration with Outlook.
"My people just live inside of Outlook. They already have to have one or two other windows up for silo systems that allow them to view or perform transactions, when we gave them another CRM window--they just didn't use it."
Even if you try to use Outlook Contacts to keep notes on and set flags for every significant contact you have with a person, it was always double entry: send the email, log that you sent it in their contact notes pane. Even if you use the MS CRM product you still have to toggle the "save this email" off and on. So once again, 37Signals has embraced constraints and found a simple solution where others wrap lots and lots of features and code around it. And I haven't even tried emailing tasks yet...
Now as a caveat I will say this feature is not "perfect." On my first attempt it missed the body of the email and only included text from my auto signature down. After consulting the Help screens I realized the feature was optimized for Plain Text emails (and I insist on using HTML). I switched the format to Plain Text, forwarded it to my drop box, and that did work perfectly.
Tuesday, March 20, 2007
37Signals Launches Highrise, I experience "just right"
It's here! We can finally give Highrise a spin. After doing a fair amount of analysis on commercial CRM packages for past employers I was really anxious to see how 37Signals would approach this. I wasn't disappointed (except for the price [more on that in a second]).
I logged in and started pulling business and 3x5 cards out of various pockets where I'd been keeping notes and reminders about my upcoming move and had it all into Highrise in about five minutes. Then I looked around a bit and experienced something I rarely get to experience with software: I was done. There were no more pull-downs to explore, no features I'd yet to uncover, no stubborn formatting hacks I had to research on Google to learn how to work around, I came in, did precisely what I needed to do, and that was all there was to do. I was done. Beautiful.
Now, I really wish I didn't have to shell out fifty bucks a months to get access to Cases. But I've run the budgets on other systems and know this is literally pennies compared to most CRM systems. It's just that I'm using it to keep track of our family's move so it's not like I had to compare this with installing a Siebel system. Seems like they should want individuals to use all the functionality so they'll want it at work.
Also, I wish I had the same formatting options in notes that I have in Basecamp.
And finally, I'm going to be really interested to see if Highrise was necessary or if the new features could have been rolled into Basecamp as optional settings.
But overall, good job guys!
Thursday, March 15, 2007
Using Basecamp for Requirements Analysis
I'm working on a project now where we're moving from System A to System B and 17 groups within the company will be affected. We naturally set up meetings with each group to explain the motivation for the changes, outline the proposed architecture, and more importantly analyze their current processes and requirements so we can foresee their needs in the new environment and the impact the intended system would have on their workflow and systems. Usually at each meeting we'd have representatives from the stakeholder as well as from the sponsoring business unit who are responsible for the new system--all taking notes.
I wanted the requirements to reflect all of our notes so I set up a Basecamp site for the project and created a Writeboard for each of the 17 groups. I then posted my notes as Version One of the Writeboard and invited the members of the business unit who attended to review/edit them by a deadline (which I posted as a Milestone). This worked remarkably well. Some went in and edited the text while others just added comments at the bottom, but it saved us from having 17 Word files with track changes turned on bouncing around several people's inboxes.
When the deadline came, I simply exported each Writeboard to a network drive and summarized the notes into a requirements document (which I posted in the Files section).
I used this same approach with the project charter.
I wanted the requirements to reflect all of our notes so I set up a Basecamp site for the project and created a Writeboard for each of the 17 groups. I then posted my notes as Version One of the Writeboard and invited the members of the business unit who attended to review/edit them by a deadline (which I posted as a Milestone). This worked remarkably well. Some went in and edited the text while others just added comments at the bottom, but it saved us from having 17 Word files with track changes turned on bouncing around several people's inboxes.
When the deadline came, I simply exported each Writeboard to a network drive and summarized the notes into a requirements document (which I posted in the Files section).
I used this same approach with the project charter.
Wednesday, March 14, 2007
Email Inbox Hack
I've found the GTD principle of keeping your email inbox clean does help me focus on the task at hand. I'm finding that when I have a pile of emails in my view I have the tendency to always be in what David calls the "emergency scan" mode or surfing back and forth over this list instead of just buckling down and getting one thing done.
I always try to use the two minute and touch it once rules but despite my best efforts, after a few days of cleaning my inbox down to empty I've got 15-20 just sitting there again. Usually I've looked at them and know what project they pertain to but they would have taken longer than two minutes to complete and so they sit.
What I've been doing lately is to set up a "1.0 Need to File" folder under each project folder. I then stick emails from my inbox into the appropriate need to file subfolder. I know when I block off time to work on Project A one of the Next Actions is to tackle that folder.
Personal Productivity, Time Management, Effectiveness, Email Hack, GTD, Getting Things Done
I always try to use the two minute and touch it once rules but despite my best efforts, after a few days of cleaning my inbox down to empty I've got 15-20 just sitting there again. Usually I've looked at them and know what project they pertain to but they would have taken longer than two minutes to complete and so they sit.
What I've been doing lately is to set up a "1.0 Need to File" folder under each project folder. I then stick emails from my inbox into the appropriate need to file subfolder. I know when I block off time to work on Project A one of the Next Actions is to tackle that folder.
Thursday, February 15, 2007
Free Conference Calls
Tuesday, February 06, 2007
Cool Online Collaboration Tool for Graphics
This looks like a really promising site dedicated what appears to be real-time, online collaboration around graphic files. Love the concept and the approach. Monday, January 29, 2007
Online Mind Mapping Tool
Mind mapping is super valuable tool for brainstorming or just capturing ideas and connections between concepts in an organic, free-flowing manner. I use a few client applications (one on my PC at work and a different one on my Mac at home) but I've been looking for a web-based solution. I've just come across bubbl.us and although it's still a bit clumsy in parts it's simple and shows promise.Tuesday, October 31, 2006
What's the Big Deal?
I tried to take a fresh look at this and other similar blogs that I follow to see what someone without an organization/productivity otaku must think about them. I mean, what's the big deal with all the little tips and hacks and ways to shave three minutes here and seven minutes there?
To answer that I'd like to share a passage from the beginning of a book I'm reading (via DailyLit.com) entitled How to Live on Twenty-Four Hours a Day by Arnold Bennett. He's talking about the discipline of getting up earlier:
It's the last line here that contains the profundity. Sometimes the difference between getting your exercise in for the day or not boils down to if you left your running shoes in front of the bathroom door so you'd trip on them when you woke up in the morning. The difference between getting the new client account or not may come down to remembering some detail about the client relationship that was on the index card you had with you to read in the waiting room before the meeting.
To paraphrase a quote from Dr. Covey's 7 Habits book,
Or to put it another (albeit a bit more obscure) way, in many Eastern traditions they believe the hidden path to enlightenment is found through the mundane.
If you're so overwhelmed that you can't relate to the above then read what David Allen and Covey have to say to learn how to block and tackle. But after that, the big "aha's" and breakthroughs are hard to come by and our hunger for more must be satisfied with a crumb here and there. But that's okay because often it's the strategically placed straw that breaks the camel's back or can make the difference to put us over the edge or to reach the tipping point.
Personal Productivity, Time Management, Organization, Effectiveness, GTD, Getting Things Done
To answer that I'd like to share a passage from the beginning of a book I'm reading (via DailyLit.com) entitled How to Live on Twenty-Four Hours a Day by Arnold Bennett. He's talking about the discipline of getting up earlier:
Rise an hour, an hour and a half, or even two hours earlier; and--if you must--retire earlier when you can. In the matter of exceeding programmes, you will accomplish as much in one morning hour as in two evening hours. "But," you say, "I couldn't begin without some food, and servants." Surely, my dear sir, in an age when an excellent spirit-lamp (including a saucepan) can be bought for less than a shilling, you are not going to allow your highest welfare to depend upon the precarious immediate co-operation of a fellow creature! Instruct the fellow creature, whoever she may be, at night. Tell her to put a tray in a suitable position over night. On that tray two biscuits, a cup and saucer, a box of matches and a spirit-lamp; on the lamp, the saucepan; on the saucepan, the lid-- but turned the wrong way up; on the reversed lid, the small teapot, containing a minute quantity of tea leaves. You will then have to strike a match--that is all.
In three minutes the water boils, and you pour it into the teapot (which is already warm). In three more minutes the tea is infused. You can begin your day while drinking it. These details may seem trivial to the foolish, but to the thoughtful they will not seem trivial. The proper, wise balancing of one's whole life may depend upon the feasibility of a cup of tea at an unusual hour.
It's the last line here that contains the profundity. Sometimes the difference between getting your exercise in for the day or not boils down to if you left your running shoes in front of the bathroom door so you'd trip on them when you woke up in the morning. The difference between getting the new client account or not may come down to remembering some detail about the client relationship that was on the index card you had with you to read in the waiting room before the meeting.
To paraphrase a quote from Dr. Covey's 7 Habits book,
"I see so many big results coming from such little things I'm persuaded there are no little things."
Or to put it another (albeit a bit more obscure) way, in many Eastern traditions they believe the hidden path to enlightenment is found through the mundane.
If you're so overwhelmed that you can't relate to the above then read what David Allen and Covey have to say to learn how to block and tackle. But after that, the big "aha's" and breakthroughs are hard to come by and our hunger for more must be satisfied with a crumb here and there. But that's okay because often it's the strategically placed straw that breaks the camel's back or can make the difference to put us over the edge or to reach the tipping point.
Thursday, October 26, 2006
User Story Cards and Traceability
In Agile practice it's customary to use user story or task cards as a quick and easy organization tool. On the face of said cards it's also customary to include a concise description of the story or task, some kind of estimate of how long it will take to complete, and perhaps some initials of who is responsible.
I keep a stack of blank cards and a Sharpie at my desk so that if I'm talking to the client or a member of the project team and a new story/feature/enhancement/task/whatever begins to surface I grab a card and start writing. I fill out all of the above, but I also like to flip the card over and jot down the current date and time as well as the person I'm talking to. That way I have traceability for each requirement.
Incidentally, I'm hesitant to add any "required fields" to cards as folks tend to get carried way (as in this example) and over time what was supposed to be a light weight, easy system takes on so much complexity and beuracracy and card police that it misses the point. Mike Cohn put it well when he said (and I'm paraphrasing) that story cards are not full blown use cases--they're reminders to have a conversation with the needed subject matter experts on a given topic.
Personal Productivity, Time Management, Organization, Effectiveness, GTD, Getting Things Done, Agile, Scrum, User Stories, Business Analysis
I keep a stack of blank cards and a Sharpie at my desk so that if I'm talking to the client or a member of the project team and a new story/feature/enhancement/task/whatever begins to surface I grab a card and start writing. I fill out all of the above, but I also like to flip the card over and jot down the current date and time as well as the person I'm talking to. That way I have traceability for each requirement.
Incidentally, I'm hesitant to add any "required fields" to cards as folks tend to get carried way (as in this example) and over time what was supposed to be a light weight, easy system takes on so much complexity and beuracracy and card police that it misses the point. Mike Cohn put it well when he said (and I'm paraphrasing) that story cards are not full blown use cases--they're reminders to have a conversation with the needed subject matter experts on a given topic.
Tuesday, October 24, 2006
Quick Lifehack for Dry Cleaning
Keep a pack of sticker dots next to where you collect your clothes to take to the dry cleaners. The next time you get a spot of spaghetti sauce on your tie or your toddler son comes up to give you a hug and smears mashed potatoes on your suit pants place a sticker dot on the spot before tossing into the pile. When you get to the dry cleaners you'll be able to quickly tell them which clothes you've brought in for standard cleaning and which need special attention (and where).Monday, October 23, 2006
Reduce Junk Mail and Plant Some Trees
I first got wind of this cool service from a recent post on The Trend Junkie blog. I've posted before about effective ways to deal with the continuous river of junk mail that shows up in our mailboxes. This service is designed to eliminate much of it and plant trees in the process--all for a dime a day. I've just signed up and will post in the future on if I can tell a noticeable difference or not.I've noticed on some other blogs questions re: if it's worth paying anything to eliminate some junk mail from our lives. Let's say you spend three minutes a day, six days a week, 50 weeks a year on junk mail. That adds up to 15 hours a year! Any time spent handling junk mail is a waste so if I could even reduce this to 14 hours annually it's certainly worth $36.
Promising Online/Offline Organizer
I'm looking forward to taking a test drive with this tool; if it lives up to the the preview movie it looks like the AJAX features alone will put it in a class of its own (at least until someone else catches up [which in Internet time is probably less than a week after launch]). It also looks like it may put PocketMod (see prior post) out of business with its "PaperSync" feature.
Friday, October 20, 2006
Promising online collaboration tool

Just heard about this tool from the Agile Toolkit Podcast and tried it out as soon as I got to my desk. The idea is that there are times when we just can't get everyone on the project/Agile team together in the same room to sort through, add, and edit a pile of index cards with user stories or brainstorming ideas on them. Sometimes, team members are remote. This tool is designed to create a virtual space where everyone can deal with the same set of cards.
The interface is super simple and well done and it was quick to set up. But I couldn't save my cards from session to session and it seems the security permissions of my workplace prevented any collaboration with colleagues...which was obvioulsy the point of the whole exercise.
The developers readily acknowledge this is in early beta testing so I'd give it a bit more time to mature before using it as a serious tool but it's promising in that it's the best tool I've seen thus far to do what it's designed to do.
Tuesday, October 17, 2006
Meeting Tip
I just got back from a meeting where one of the key participants was late and I didn't have his number memorized or with me. Duh! So, today's tip is to make gathering the phone numbers of the meeting participants and placing them with your agenda and meeting materials part of your regular meeting preparation so that if you arrive on time and others don't, you can make a call to get things going without having to get back to your desk.
Personal Productivity, Time Management, Organization, Effectiveness, Meetings
This Guy Gives New Meaning to "Moving the Fulcrum"
If you've ever wondered about how some of the large engineering feats of ancient times might have been accomplished check out this YouTube clip on "The Man That Can Move Anything."
Monday, October 16, 2006
Basecamp To-Do Hack

Ever have a list of To-Do items in Basecamp that have varying priorities? At times I've used naming conventions (e.g., "a_Task 1, b_Task 2") or simply placed an "[A], [B], or [C]" in front of each item and both options work fine when that's the only dimension you need to display.
But I have a case right now where I'm already distinguishing whether a list of requirements are more format or appearance-related (which I mark with an "[A]") or if they are what I like to call "plumbing"-related meaning they deal with getting data from Point A to Point B (which I mark with a "[B]").
So now I want to designate two dimensions for each To-Do item: priority, and type (and obviously the name of who the To-Do item is assigned to is a third dimension).
I simply created a To-Do item that I called "***TOP PRIORITY TASKS***" and another called "***MEDIUM PRIORITY TASKS***, etc." and assigned each to "Anyone" so no name appears in front of each item. As the priorities change on a given item I simply go into the "Reorder" function and move the tasks to fall under the appropriate heading.
Subscribe to:
Posts (Atom)
