Summary
In many companies, Design is viewed as a tactical resource; in fact, it’s often a subsidiary of Product, there to support the Engineering team. Basically, Design is viewed as “the wire frame people.” This results in a lot of frustration and feeling like the design team doesn’t have a seat at the table, and creates resentment between Design and their Product and Engineering partners. It also results in the organization not realizing the full value of its investment in the design team. The solution to this problem is to transition Design from being a tactical resource to a strategic partner. The question is, how? This session will cover ways that Design can make this transition, exponentially increase their influence, and become a key strategic resource/partner for everyone in the organization.
Key Insights
-
•
Design is often viewed as a tactical resource rather than a strategic partner, leading to exclusion from planning and decision making.
-
•
Measuring design impact requires aligning granular design metrics with higher-level business metrics like OKRs or North Star metrics.
-
•
Organizing teams in a fractal structure with product, engineering, and design as equal roles fosters better partnerships.
-
•
Design systems should include not only components but also guidance on when and how to use them to support self-service design.
-
•
Adopting a business mindset means designers act pragmatically, focusing on solving business problems rather than insisting on perfect design.
-
•
Saying no in design risks being seen as a roadblock; instead, asking why and clarifying problems builds partnership.
-
•
Designers should understand their product and engineering partners’ pressures and goals, treating partnership as a design challenge itself.
-
•
At Procore, redefining metrics with product and engineering through workshops aligned user success moments with business goals and shifted design’s role.
-
•
Small iterative measurement efforts build momentum and buy-in within organizations rather than monolithic projects.
-
•
Even when design leadership isn’t at the same level as product and engineering, staff designers can still 'punch above their weight' to influence strategy.
Notable Quotes
"Design is often a subsidiary of product, really there to serve engineering—wireframe people."
"If design is not viewed as a player moving the needle on business strategy, designers feel disempowered and frustrated."
"Turning the company’s view of design from tactical to strategic is like turning a super tanker—it takes a long, wide arc."
"If you don’t measure, it’s like a tree falling in the forest with no one around to hear it."
"Design systems typically lack content on when and how to use components—adding this makes design more self-service."
"Try to approach your work like a business person with design skills rather than a designer in a business."
"Instead of saying no, try asking why and focus on the problems to be solved rather than specific stakeholder solutions."
"Look at your partnership with product and engineering as a design task—understand their pressures and needs."
"We were allowed to taste the cake, not bake the cake; this process got UX into the kitchen."
"Usability testing is the gateway drug for research; similarly, small measurements are the gateway for strategic design impact."
Or choose a question:
More Videos
"A good story that people can retell is key for global communication, even if it distorts a bit."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"We don’t get upset when users say one thing and do another, but we freak out when our leadership behaves that way."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Digital is a system, not a project. It’s there all the time and you have to keep iterating on it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The time for action is now, and it must be collaborative."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"OKRs are a tool for each of us to tidy our house and focus on what’s important."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Thick data is the opposite of big data; it’s stories, qualitative, and crucial during moments of rapid change."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Delivering research in small, lean increments allowed us to iterate fast and reduce bias."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Our brains are terrible at operating only on one type of information, whether object-oriented or context-oriented."
Designing Systems at Scale
November 7, 2018
"Most product teams work linearly, but systems thinking captures the real-world complexity of moving forward and sometimes stepping back."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024