In the product development process, we understand that design is important. The next question becomes, who owns design in the product development process?
1. No one team should have
all that power
Understanding who owns design in the
product development process
Monet Spells
2. A Little About Me
Professional Background
- Computer Science + Web Development
- Product Manager at a NYC start up
- User Experience Designer
- Studying Human-Computer Interaction
Hi, I’m Monet! I live in Atlanta. I do UX, with a smile.
3. Who Owns Design?
So...how do teams share ownership of design?
Developers? Designers? Marketing? Stakeholders? Product?
Everyone owns design.
4. Traditional Design Approach
A traditional design approach focuses on users and design as
important, but distinct, entities.
“No one [team] should have all that power.” - Kanye West
Users
- Begins with users or design - Bridges, like product managers
QA
Developers
Support
Product
Design
Designers
Stakeholders
Marketing
5. Design-Driven Approach
A design-driven approach focuses simultaneously on users and
design, understanding that they balance and guide one another.
- Begins with users and design - All teams are guided by design
Designers
MarketingDevelopers
QA
Support
Product
Stakeholders
Users
Design
6. Lessons Learned
Align on a
vision, mission,
and goals
Eliminate
bottlenecks for
efficiency sake
(More time for champagne!)
Always consider
the user’s
experience
Empower everyone
to contribute to
design