MVPD-Day

One problem occurs quite often when a transformation is working against the clock: failure to identify what will constitute the Minimum Viable Product (MVP).  If you have not identified this bottom-line of your transformation, you are unlikely to deliver very well against your objective and will be very vulnerable to mission creep and crop.

In high speed transformations, typically what happens is that deadlines are so tight that your team will be working on developing and delivering simultaneously with identifying your MVP. You’re in learning-by-doing mode. You’re identifying what you can do whilst still not having identified what you should do.  

This will cause the purpose and the output of the Programme to be poorly defined – which invariably results in an expensive free-for-all, with he-who-shouts-loudest being the only satisfied customer.

Stop. Draw a breath. Choose to make identification of the MVP a priority.

Set a date by which you will agree the MVP – or at least, the headline content of the MVP. This date marks the end of the beginning. Discussion of “potential” output is replaced on this day with discussion of “planned” output. We are committed.

This method has a very interesting side-effect. It drives engagement.

That’s because those people who want to have their area of operation included in the transformation suddenly recognise they need to get involved. Instead of telling you they’re too busy to talk to you until at least the middle of next April, they will find time to ensure you are aware of their requirements before the MVP is agreed … on MVPD-Day.