Lessons in business analysis from MS Courier

I'm just as excited as the next IT gadget geek to see what Microsoft releases with its upcoming dual screen Courier Digital Journal. But rather than speculate on what features it may or may not have, I want to pause to observe something about the preliminary videos we're seeing pop up--particularly the ones found on engadget.

Watch the videos, and even without sound you get it. You know what this device should do. You have a good idea of who it's for. How many pages of written requirements would it take to convey all the information you just received from this short video?

Watch Joe Levine's TED talk on a proposed mission to Mars and you come to the same conclusion: in a few minutes of video you find yourself saying that's possible. You are previewing the future. It's a simulation, but somehow tangible at the same time. How many words would it take to convey the same information? And how long would that take to digest?

I've spent a lot of years writing requirements documents for software and technology projects. They still have their place. But what is the single most important skill for business analysts of today and tomorrow? Film making.

Thinking with your hands

I was listening to a TED podcast this morning from a gentleman from IDEO. He described a design session where an IDEO team was meeting with surgeon's to discuss a new surgical instrument they would like developed. Someone from the design team left the room and in a few minutes returned with a dry erase marker taped to an empty film canister that was taped to a clothes pin in the rough shape of a gun. The designer gave it to the surgeon's who passed it around and begin offering very constructive feedback on how the device should sit in the hand, how it should be shaped, what it should do, etc. IDEO calls this behavior "thinking with your hands" (and this eventually turned into a real device).

It typically involves making many low-resolution prototypes very quickly. Often by bringing many found elements together in order to get to a solution...And so this behavior is all about quickly getting something into the real world and having your thinking advanced as a result.

This dovetails precisely with the Getting Real approach advocated by 37Signals. Tom Peters has been an advocate of this for years. And it explains why the Back of the Napkin approach of visual thinking works so well.

IDEO takes this idea seriously and has "protyping carts" around filled with Play-doh, tape, Legos, colored paper, markers, etc. ("the stuff we all had in pre-school") so desingers can begin prototyping objects whenever they want. They also apply this approach to designing a service experience through rapidly jumping into role-playing various scenarios.

Is the teacher learning?

I just listened to a captivating TED talk from a gentleman who voluntarily did not speak for 17 years. As one would imagine, he has some interesting things to say about listening. During his silence, he was a college professor where he would write and use a make-shift sign language to communicate. He said many times as he would make signs and gestures the students would play a kind of guessing game trying to make out what he was trying to say. Many times they got it right. Sometimes they would not. Frequently, he would think to himself, "That's not what I was trying to say!" And then he'd catch himself and think, "...but it probably should have been..." as he realized the students had struck upon a critical angle or point he was overlooking. His point was that if you are not learning while you're teaching, you're probably not really teaching.

Creativity

Creativity begins when a zero is cut from your project budget.

- Maverick designer and urban planner, Jaime Lerner in a 2007 TED speech.

Agile and Spaghetti Sauce

I recently discovered TED. I have no idea how it's not hit my radar until now, but I can't listen to and watch the talks fast enough. I was watching Malcolm Gladwell talk about a personal hero of his, Howard Moskowitz, and the role he had in discovering the value of providing calculated varieties of a product versus trying to find the one, "perfect" product that will meet the needs of the majority of the market. With Seth Godin's work and The Long Tail we tend to take this idea for granted today, but Malcolm does a wonderful job of taking us back in time to a point where this paradigm was uncommon and even revolutionary.

One of the many anecdotes that impressed me was when Mr. Moskowitz concocted nearly endless varieties of spaghetti sauce using variations on sauce thickness, amounts of various spices, introducing bits of vegetable chunks, etc. and then fed 10 bowls of various varieties to a number of subjects. When he worked through the data of people's preferences he found they fell into three groups: plain, spicy, and chunky. He concluded this latter category represented the preferences of about a third of the population--and there was no sauce on the shelves with chunks of juicy vegetables at that time. Prego went on to release such a product and make a fortune, but the lesson I want to focus on is one observation Malcolm makes in his narrative: no one had mentioned they would like a chunky spaghetti sauce in any prior focus groups. The lesson Malcolm draws from this is that people don't really know what they want until you give it to them.

This conclusion is reinforced in protracted software development projects that follow a rigid waterfall approach. The requirements analyst asks the business users what they want and their answers are often within an implicit and many times unconscious context or menu of what they've already got in an existing system or think would be possible based upon a limited understanding of possible system features. In other words, they say they want a good tasting sauce.

In Agile or more iterative, prototype-rich methodologies, the user would be presented with rough drawings of user interfaces, story boards, and HTML and/or PowerPoint mock-ups, over and over again throughout the very initial stages of the process. In other words, the developers spend a fair amount of time up front cooking up a ton of varieties and keeping the business users taste-testing. Now the possibilities are open and we're getting several quick cycles of real-time, visceral feedback. Now we can get from the 40-50% approval ratings Malcolm mentioned are the usual result of a homogenized solution to the 75%+ delight ratings of people who get what they didn't know they really wanted.

Tom Peters mentions how Ritz Carlton aims to "fulfill the unexpressed wishes of its guests" in a few of his books. The Japanese have a common practice of insisting on finding seven viable solutions to a problem or challenge before they select their approach.

It is incumbent upon those of us in the IT solutions field to translate what is really a collection of abstract ideas in the beginning of a project into tangible value and options in the minds and senses of end users as quickly as we can.