Organizations and decision makers have depended on analytics – or analysis – for making better, fact-based decisions. With an explosion of data, available both publicly and within organizational confines, coupled with sophistication of computational technology creating analytics is not as onerous as it once was. The great thing about analytics is that they are never dead-ends. They are not what I refer to as “terminal” (this is where a lot of data vendors have a problem because they have always seen – and called – their offerings as “terminals”). In order to glean true insights from analytics one must further the analysis. Furtherance happens either by extension (“this is fine, but how about a further analysis of all our lost businesses”) or collaboration (“hey Steve, I think there is something funny with our sales trend. Can we take a look at it together and try make sense of it?”). Thus, analytics almost always casts an eye to the future. When we stand at the cross roads of a situation and we want to take the turn towards understanding the future, what question do we ask?
“Then” sets us out on a path of inquiry that hurls us into the future. “Then, once I have the current price of a security, I look up what the price trend has been in the past”. “Then?”. “Then I try to figure out if there is a price level from where it has bounced back so I could buy at that price”. “Then?”. “Then I place an order with my broker to buy at that price”. Theoretically we can go on but you get the drift. If you are building a product or service that has to do with user workflows, the word “then” is the best friend you can hope to have. Leave the “Why?” to the policemen.
Post Script 1: Of particular interest will be for interaction designers is this “then?” concept. Anyone has examples in action will post in comments, no?