This one was mentioned in a great talk about product management by Neha Datt. Product inceptions are a tool to reduce risk of a product as early as possible. Ideally this happens even before an MVP is built. Besides a de-risking effect an inception should also foster alignment, build trust and outline next steps.
Here is a summary directly from the playbook of what an inception can deliver (should you decide to continue):
- Goals and scope: What we will do and why
- Solution approach: What the solution will ‘look like’ and how we will deliver, covering functional and technological aspects, as well as processes and ways of working
- Risks and dependencies: Where to be careful
- Plan and cost: An overview of when to expect what, and the required capabilities and resources
- Playback deck: A summary of findings and recommendations
The 129 pages playbook on product inceptions covers the Why, What and How. The outcome of an inception should be answer to the questions if you continue and what needs to happen next.
DIBB Framework: Data – Insights – Belief – Bet
The DIBB framework was made popular by Spotify, although I did not find much of its true origins.
The first step is to analyse your data. From there on you generate insights. Your insights then form a belief. Lastly you make a bet.
An example to make this less abstract:
- Data: More and more users access your shop from mobile phones
- Insight: Our shop is not optimised for mobile, we’re losing money!
- Belief: We need to become mobile-first!
- Bet: Hire mobile developers who will build a shopping app and optimise the online shop for mobile browsers.
Audio editing basics
This week I recorded a conversation between my friend and awesome agilista Mel Lang. We used Zencastr to capture the audio and automatically post-process. Now I am working with Audacity to edit out the awkward breaks and ums.