Teams have been running some flavor of Agile for years. Sprint after sprint, month after month teams rush to get features out the door.
Adjusting course — i.e., the agility that they seek—means adding stories onto an already impossibly long backlog and the idea of managing to outcomes—meaningful changes in customer behavior — seems to have been lost in the shuffle.
Give teams a problem to solve, not a solution to implement
You may also like
How Loom grew from 0-500K users, and beyond: [Part 1 of 2]First, some context: – Loom was founded in 2015 by @yoyo_thomas, @vhmth, and myself – Fascinated by video in the workplace and wanted to build use cases against it. – We built a user testing marketplace (failed) → pivoted...
It’s all about communities. Great products, businesses, creators are all building their communities – and having built some of the active startup/product communities, all I can say is that we are so done with Slack channels and even Discourse forums. The text-y conversations are...
Why product management is hard (and why good product management matters) 1/15 👇🏾1/ Sometimes, you should imitate competitors. Other times, watch them closely. And sometimes, largely ignore them.2/ Sometimes, you should build what users say they want. Other times, you shouldn’t.3/ Sometimes, you...