Why do so few product development programs make that connection between the product specification document content and the released product? It seems to be such a common thing that these two don’t connect that organizations don’t even bother to review or analyze this after release.
The mindset at that point seems to be:
- We did the best we could with the resources we had
- All product change from their original specifications
- It transformed into a product that better fits our updated understanding of what could be made to satisfy the market
These are all just comfort statements so the project can be tidily closed out without any hanging questions. Everyone wants to move on to the next program; and we may also 
But doesn’t this seem a bit crazy from a farther vantage point?
Why was so much effort put into:
- Studying the product market and customers then defining a product niche
- Studying current technology
- Capability of new technology
- Risk of capital investment & business goals
- Brand alignment and goals
Something became disconnected. No one created all those specifications based on such a large multi-department initiative thinking it wouldn’t direct the development program through to completion. Maybe we should push to have our team, or just those willing to invest a bit of time. Evaluate together how well the product matched the spec and highlight what was off and why. It could create a few realizations that could drive some strong improvement in the next product development cycle.
Comment on this post or simply contact me directly by email or phone. I am very interested in hearing your story.
abahret@apexridge.com
978 879 8617
Thanks -Adam
Leave a Reply