You'll never get buy-in for prototyping or MVPs if your org thinks that development is the hard part, and deciding what to build is easy.
When org culture is engineer-led, this happens a lot.
This may be the only time that knowing how to code meaningfully helps designers.
When org culture is engineer-led, this happens a lot.
This may be the only time that knowing how to code meaningfully helps designers.
This goes hand-in-hand with "flat" orgs that are nevertheless heavily siloed, and lack good outcome-based principles. Engineering is not responsible for product outcomes, but always wants to control product decisions.
A prototype proves that its design is possible & desirable.
A prototype proves that its design is possible & desirable.
Designers know that a prototype doesn't have to be hi-fi. Making your team watch a user struggle through some wireframes can be enough.
But if your org struggles to execute, you can't wait for production releases to go hi-fi. You need to speed up the feedback loop yourself.
But if your org struggles to execute, you can't wait for production releases to go hi-fi. You need to speed up the feedback loop yourself.
