The Designer is the most misunderstood role in Product.
And yet, their work is crucial for a team's success.
Over the years, I've observed 2 toxic patterns: 🧵
#productmanagement #uxdesign
And yet, their work is crucial for a team's success.
Over the years, I've observed 2 toxic patterns: 🧵
#productmanagement #uxdesign
1. There is no Designer on the team.
Sometimes there might be some UI guy who takes care of selecting stock photos or modifying the CSS styles. But in reality, the usability of the product is not taken seriously by anyone.
So the usability sucks.
Sometimes there might be some UI guy who takes care of selecting stock photos or modifying the CSS styles. But in reality, the usability of the product is not taken seriously by anyone.
So the usability sucks.
2. The Designer is engaged too late.
The Designer is asked for help when low-fidelity prototypes are ready, or worse, once the application is built. Their only job is to "make it prettier."
No matter how much they try, it's like lipsticking a pig.
How can we solve this?
The Designer is asked for help when low-fidelity prototypes are ready, or worse, once the application is built. Their only job is to "make it prettier."
No matter how much they try, it's like lipsticking a pig.
How can we solve this?
Every product has 5 key risk areas:
- Value. Will it create value for the customers?
- Usability. Will users know how to use it?
- Viability. Can our business support it?
- Feasibility. Can it be done?
- Ethic: Should we do it?
Usability is the responsibility of the Designer.
- Value. Will it create value for the customers?
- Usability. Will users know how to use it?
- Viability. Can our business support it?
- Feasibility. Can it be done?
- Ethic: Should we do it?
Usability is the responsibility of the Designer.
One of the goals of Product Discovery it to address those risks before selecting ideas for implementation. If one of the risks materializes, e.g., usability is not there, your product idea is useless - neither the customers nor the business can benefit from it.
In the Continuous Discovery Habits, @ttorres introduced the term "Product Trio" - a group of people who make Product Discovery collectively:
- Product Manager
- Designer
- Engineer
- Product Manager
- Designer
- Engineer
Instead of building silos with stage gates, I highly recommend that you embrace a collaborative approach. Ensure the Designer, and at least one Engineer is included.
In particular:
- It's a Designer's job, not the PM's, to create user prototypes.
- Prototypes are created, and ideas are tested before developers start the work.
- It's a Designer's job, not the PM's, to create user prototypes.
- Prototypes are created, and ideas are tested before developers start the work.
Appreciate your Designers and let them do what they do best. It's the best way to create great products customers love.
Do you have a similar experience?
Do you have a similar experience?
If you like threads like this, follow me on Twitter and check out my biweekly newsletter:
huryn.substack.com/?src=t
huryn.substack.com/?src=t
• • •
Missing some Tweet in this thread? You can try to
force a refresh
