Weeknotes 538

I did:

Momentum

Three day week so I was super-focused on moving the important stuff forward.

  • Discussed conversion rate forecasting as we get ready to scale an MVP.
  • Chatted about agile governance and why stakeholder engagement (and education) is so important.
  • Ran a team expectations workshop.
  • Chatted to content designers about automated communications.
  • Updated our roadmap.
  • Talked through a really good example of a data-driven product process that identifies user needs and validates whether we can solve them.
  • Reviewed a product requirements document.
  • Started figuring out how to approach bringing lots of analytics data together in a way that make sense.
  • Briefed myself on some new work. Writing stuff down helps make things clearer.

I read:

Roadmapping exemplar

Josh Hunt and the team at DHCW set a new standard in roadmapping. If you’re thinking about how to improve your roadmap, you should read their blog post and take a look at their public roadmap. Jealous much?

Product management resources

Seyifunmi Olafioye put together this super useful resource list.

AI product system

Rian van der Merwe describes his AI product system. Two things really interested me about how this works. First, the loop of updating context keeps information fresh, second, the commits graph is an indicator of how quickly the work is progressing. It’s basically flow rate, because every time someone from the team does something (has a meeting, diagrams some thoughts, writes some code) it’s put into context and shows in the commit graph. Very cool.

I thought:

Theory of product management

I’ve been working on some theory building for product management. My core claim is that product management is the organisational function that runs the scientific method on the value chain. It operates by forming hypotheses about where value comes from explicit, testing them cheaply, and reallocating resources based on the evidence. The value of product management comes from fewer wrong bets and faster learning for course correction, not the usage of the shipped product (it should generate value too but that’s separate from the value the product function provides).

It means that the success of the product function is down to the intensity to which an organisation applies the scientific method. The more consistently value hypotheses are explicitly stated, evidence that would falsify them is defined, proportionate tests are run, and decisions are changed when evidence disconfirms, then the more value an organisation will get from product management.

If I had the time, I’d love to research this and create a proper theory for product management.

Observe / change / measure

In my ongoing attempts to understand product management, and communicate what we do and why it matters (and why it isn’t project management), my latest thing is that what we do is observe, change, measure. It’s about as simple a version of the scientific method as I can get.

Observe and measure can be hard enough, but it’s the change part that is most challenging. It’s the hard bit because organisations are built to maintain the status quo. If that’s what most product managers spend most their time on, and we don’t make the observe and measure parts visible and important enough, then is it a surprise that we are seen as project managers?

Defining value

The MBA module I’m studying at the moment is about value so it’s got me thinking about how to define value.

Value is a surplus that has been co-created through exchange, most often where the things being exchanged are of different types and the surplus of the types isn’t clearly distinguishable, but continues to exists after the exchange is complete, and diminishes over time.

For example, you and Netflix co-create value through exchanging things you have that they want for things they have that you want. You have money, time and attention which you give to Netflix and they have videos, games and mobile apps which they give to you.

Get weeknotes in your inbox