People usually want features. They come to me with a specific thing they'd like me to build. No matter where someone is in their process, I ask them to walk through the same methodology I use for every client I work with.
It's okay if someone asks you for a feature. It's part of your job as a product manager to translate feature requests into measurable goals. So rather than just "build the thing" we use a process that can translate the request into a set of goals that will facilitate a conversation with developers to use the specific function they provide at the strategy stage: pricing stuff
The 3 Amigos: Business, Product & Dev
The 4 Horsemen: Business, Product, Dev & QA
The Fabulous 5: Business, Product, Dev, QA & Dev Ops
You get the point.
The Almighty Yield
Everything has a (COST) (RISK) (EXPECTED RETURN AGAINST GOALS) (OTHER FACTORS?)
- Business Goals & Measures of Success
- What is the business goal? (e.g. "
Here's a picture of a client who just realized he doesn't need me: