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.
All Posts
Product Vision is Science Fiction
This article describes my beliefs on what product vision is and isn’t.
Tension: why product development requires balancing conflicting goals
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:
- Customer problems aren’t business problems
- We can’t directly solve business problems
- On time delivery doesn’t lead to customer or business success
- Focusing on business success alone is harmful
- Focusing customer success alone is harmful
- Aligning your purpose with your organization’s purpose is really what motivates us.
Keep actual effort and outcome visible
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 Mindset That Kills Product Thinking
The service provider antipattern baked into our thinking, processes, and culture. Here’s how it hurts us.
Product Discovery Recipes
More info coming soon… But, here’s the link to download the pdf
Dual-track Stakeholder Review
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…
Dual-track Team Review and Retrospective
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…
Dual-track Daily Standup
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…
Dual-track Sprint/Iteration Planning Recipe
tl;dr: If you’re using a typical agile process like Scrum, you’ll break your work into Sprints or Iterations that usually range from 1-3 weeks. You’ll start each Sprint with a…