Skip to main content

Lead and Lag Measures


Outcome based product management seems to be taking off.

Along with Hypothesis based development, this has turned around product development from detailed product roadmaps that we used to have to more customer and user focussed product development.

However, We seem to fall under the trap of Build-Measure-Learn and not measure the right things.

A lot of times, we measure lag indicators that do not help us learn faster. Lag indicators are history, they tell us what we did right and wrong post-facto after the event has happened.

We need a way to understand and measure how features can go into a product roadmap as we are building it or as we are considering it.

Lead measures help us with that.




Comments

Popular posts from this blog

Apple Watch - Managing "Out of stock"

Apple is credited for a lot of things - the least of which is managing retail operations. However, that seems to be a key element of product launches with apple these days.

From Idea to reality - The progress of an Idea

 I have been thinking of writing a simple app for locating trash cans at Chennai. The first thing anyone would do was to see if the idea has been already implemented. Sure enough, it has been. This is the app - Check it out. http://trashithere.herokuapp.com/ When I tried using the app, I found out that there were only few trash cans. This was a crowd sourced application. I guess this app was not used much. The Spark This led me to questioning myself - What problem led me to this application. I yearned to live in a place that was clean. My assumption was that if people found places to throw thrash, they would not litter. Going ahead with your idea

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It i...