Strategic product thinking for the scrappy entrepreneur in all of us.
Strategic product thinking for the scrappy entrepreneur in all of us.
Everyone wants innovation, especially if we can plan and schedule into each sprint.
But innovation is uncertain. Can we shift the discussion to planning and scheduling and funding of discovery that can (often) lead to innovation?
ProductFocus’s Ian Lunn and I will talk through how software product companies make money, and how that’s in direct contrast with how software outsourcing and custom development companies make money. Then we’ll apply that to B2B/enterprise software vendors who may have conflicting business models.
Most agile conversations are about morale, velocity (aka throughput), quality, predictability, and team dynamics. But we rarely address actual customer/user vale or business outcomes — instead hiding behind story points or vanity internal value metrics. This discussion will be about how strong product management bridges the outward customer/market view and inward development view.
After years of struggle, I’m advising all of my clients and product leader coachees to stop using the term “MVP”. Not to stop doing validation, discovery, prototyping or experiments they may associate that that acronym, but to remove the label from all of their docs and presentations and talks. To delete the letters MVP from roadmaps and product charters…
I’ve seen some patterns in how companies recruit their Heads of Product (aka Chief Product Officer, VP Product, Director of Product Management, or Group Product Lead). This post unpacks some fundamental misconceptions — and how to get the strong product leadership we need.
Before we start crunching business case numbers, we should think about the underlying money story: who it’s for, how it generates money, and what similar money stories we are considering.
a podcast about product management, real-world validation, executive teams, and highlighting the contributions of product folks on our teams,data-aware decisions
Most agile conversations are about morale, velocity (aka throughput), quality, predictability, and team dynamics. But we rarely address actual customer/user vale or business outcomes — instead hiding behind story points or vanity internal value metrics. This discussion will be about how strong product management bridges the outward customer/market view and inward development view.
In this podcast with Jay Stansell, we note that company executives often have very different perceptions of customer needs than the product management team. How do we understand this, sympathize, yet still bring balance evidence into C-level conversations?
There are no generic or universal KPIs, since every business has unique aspects. So if we want KPIs for a B2B/enterprise company, where would we start? And how do we avoid committing to improvements in metrics/KPIs before understanding our current scores (or situation)?
