This article is really some of the common mistakes I see people and teams make when they create and work with story maps.
1. Losing the story
2. Getting lost in the details
3. Worrying too much about flow, branches, and what-abouts
4. Mapping the whole product when you’re trying to add a single feature
5. Not anchoring releases on an outcome
Organizations and the people in them irrationally and addictively build and release products that often have no real value. This article gives my best explanation why.
This article describes my beliefs on what product vision is and isn’t.
This article describes the simple language I use to describe product development: opportunity, output, outcome, and impact. But more importantly it describes the tensions and unexpected implications in the model:
Beam me up We all understand how a star trek transporter works. Which is surprising since it’s not real and I don’t even understand how my toaster oven works. But,…
The service provider antipattern baked into our thinking, processes, and culture. Here’s how it hurts us.
More info coming soon… But, here’s the link to download the pdf
tl;dr: Your product team will need to keep its work visible to stakeholders outside the team. If your product team is doing both discovery and delivery, you’ll need to review…
tl;dr: If you’re using a typical Agile process like Scrum or XP you’ll work in short 1-3 week Sprints or Iterations. You’ll finish each Sprint by reviewing the work you’ve…
tl;dr: If you’re a team working together on a product you’ll need a quick review and planning meeting every day. If you’re a team doing both discovery and delivery, that…
