No one team should have all that power: Understanding who owns design in the product development process
Download as PPTX, PDF0 likes318 views
The document discusses different approaches to ownership of design in product development teams. A traditional approach sees design and users as separate entities, with designers owning the design process. A design-driven approach sees users and design as mutually guiding and balancing, with all teams guided by design. Some lessons are to align teams on shared goals, eliminate bottlenecks for efficiency, always consider the user experience, and empower everyone to contribute to design.
![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
Designer
s
Stakeholder
s
Marketing](https://image.slidesharecdn.com/9xsvmsdistepqcczxalh-signature-34b3b84b9b3ee3091aed5f8cb54a9b8a6d41e79026d0c65b20c263ea15be63fb-poli-150210120710-conversion-gate02/85/No-one-team-should-have-all-that-power-Understanding-who-owns-design-in-the-product-development-process-4-320.jpg)
No one team should have all that power: Understanding 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 Designer s Stakeholder s 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 Designer s MarketingDevelopers QA Support Product Stakeholder s 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
- 8. Thank you! monet.spells@gmail.com | @OhMonet
Editor's Notes
- #3: KW:don’t read from the slides
- #4: K: "better collaborate on design" K: could ask more questions here...
- #5: K: Start with your experience, not the definition...this is your definition, so it’s based on you rexperience K: Bridges are technically a good thing...but they COULD create a bottleneck, IF a company relies too heavily on any one team (e.g. product) K: Your story isn’t weaving in well enough...when you mentioned “...from here we grew” i forget who “we” are
- #6: K: Not sure I agree with the HR example...
- #7: K: either mention mission/vision/goals on slide 4 when you speak to it, or tell a story here about how PP incorporated these concepts to become design driven