We celebrate product launches.
We stage elaborate meetings at customers for product training.
We hold focus groups and beta summits.
But do we get the team together at the start of a development process to share the "why" of a release?
Do we bring in customers who really need what it is that we're planning to build, so developers and production teams can see them and hear how their work will change based on what we're building?
Do we highlight those aspects of a release that sprang from internal innovation, as opposed to the fertile mind of the product manager?
Do we leave the door open for continued innovation during development through an explicit change management process?
Let me suggest that how we finish is directly proportional to how well we begin.
No comments:
Post a Comment