
Stop asking what to measure & start asking what to care about. Then measure that. #measureoutcomes #outcomedriven

Product development & operations. Antifragility, cynefin, flow, continuous learning. (ex- Spotify)

Stop asking what to measure & start asking what to care about. Then measure that. #measureoutcomes #outcomedriven

There is no perfection. There is only the right thing at the right time. And time moves on.

Push = emergent need for predictability Pull = emergent ability to predict

If you have two teams dependent on each other to deliver value, you actually have ONE team. Treat WIP & queues accordingly.

If you're not doing TDD, you're so missing out on continuous dopamine hits


“Protect Value” is work to ensure validated user value continues. It is NOT tech debt. PV-work is maybe not as fancy as “Create New Value”, but it’s validated and valued, unlike “New Value”. Should be easy to prio most of the time.

If you care about predictability, you should care about product quality first. Bugs, incidents & tech debt will ruin any attempt at increasing predictability of product delivery.

Beware: “Align” might sometimes mean “make sure everyone understands all project requirements before we get started”.

Agile folks seem to have forgotten it's original Intent: “Working software is the primary measure of progress”

It's irresponsible to load teams to 100% capacity. Increased workload creates longer delays, lower quality, and higher costs. #agile #leadership

There’s a lot you need to get “right” building product; right timing, right user, right tech, right skills, etc… Good strategy positions us to get more things right than wrong, but never all of it right. That’s just luck.

"If you only have one road, do you really need a map?" #Roadmap

You already know what WIP is and when it’s a problem. But if someone asks and you’re tired of explaining, I’ve got you covered: medium.com/@hamrinmarcus/wha…

I wrote some thoughts on "Batching" and how it relates to predictability: medium.com/@hamrinmarcus/str…

Product development is messy, nonlinear, unpredictable, nebulous. If our processes don’t embrace that, we’ll probably end up often building the wrong things the wrong way with the wrong results, but in a neat and orderly fashion.