this might seem like semantic pedantry to folk more familiar with delivery contexts, yet for product oriented people it's a completely different way of thinking and working - a different frame of reference
once again: the things that digital product teams output aren't 'value' and a stream of such things isn't 'flow of value'
they're certainly working on value creation, but the actual things aren't the value - the value comes from user interaction
#Product#ProductManagement
viewing the outputs as 'the value' is imo rooted in the (stuff) 'delivery' mindset that still pervades software development, which regularly results in wrongly incentivised people focusing on the wrong thing
the work level incentive of someone at the boundary of a team constrains the work level of that team
eg. if the boundary individual is operating at an output level, then the team is constrained to output or below (ie. activity)
the work level incentive of someone at the boundary of a team constrains the work level of that team
eg. if the boundary individual is operating at an output level, then the team is constrained to output or below (ie. activity)
"...product managers, product designers and engineers..."
I think at this point it's OK to slip 'product' in front of 'engineers' too - the idea of a homogeneous blob of 'engineers' is getting pretty stale (and it's not about FE vs BE vs FS)
#Product#ProductManagement
In the past, we've never doubted that we were going to ship the product. In a continuous world the product is now the variable. https://t.co/ORc8da1J5e
🎶 Back in stock! 🚀
Samorost 3 Soundtrack 2LP by Floex is back and available again on this hard-to-resist marble blue vinyl! Comes with a FLAC download code and 6 art prints.
Grab one in our shop: https://t.co/XddGWJr4ft
you then introduce Dish C, which also uses carrots, and these are prepared differently from both A and B - instead of 'refactoring' the carrot prep, you add a third carrot station to the kitchen to get the dish live
🥕🥕🥕
a better restaurant metaphor for software development:
what you're doing is creating new dishes to evolve the existing menu - and you might trial a bunch of dishes first, before refining and going live with the one that got the best feedback
#SoftwareDevelopment
the tech debt metaphor maybe goes like this:
you have an established Dish A which uses carrots
you introduce Dish B, which also uses carrots, however the carrots are prepared slightly differently, so you just add a new carrot chopping station to the kitchen for now
What’s the most effective way to write OKRs?
Make sure the “KR” part is an outcome. To do that, you have to understand what an outcome actually is, how to work with that understanding, and how to deliver it.