Summary
DevOps has spent a decade focused on tooling that allows developers to code, deploy, monitor, and optimize quickly and efficiently. Along the way, many within that community forget that the people within that community and the developers that they serve are, first and foremost, people. Hear what happens when a Design Ops professional finds herself embedded in a DevOps team, helps them see each other as people, and applies a bit of design thinking, tools and techniques to help them learn the skills necessary as the people they serve move from the information age to the conceptual age.
Key Insights
-
•
The meaning of 'design' and 'We' can be highly ambiguous in companies like WeWork, requiring explicit grammar and syntax to clarify communication.
-
•
WeWork operates at a rapid pace where a single day equals the typical volume of challenges faced in a week elsewhere, termed 'WeWork time'.
-
•
Program managers at WeWork were often misunderstood, labeled as "expensive routers," missing the emotional intelligence and 'how' behind their work.
-
•
Understanding people’s origin stories reveals their motivations and values, building deeper connections beyond what they do to why they do it.
-
•
The Red Tech mission consisted of three waves of teams with differing backgrounds causing challenges in cohesion and emotional divides like fear and shame.
-
•
A concise, fundamentals-first agile scrum training helped level up teams who were 'faking it,' leading to the emergence of #sharedunderstanding across disciplines.
-
•
Quarterly retrospectives with defined ground rules and an emphasis on what improved over time enabled honest dialogue and team growth while maintaining privacy.
-
•
Mapping individual user stories to OKRs and broader company goals enabled visibility into how multiple teams contribute in different ways, sparking inter-team collaboration.
-
•
Small cultural rituals like Silver Heart Hat Awards build emotional connections and internal recognition crucial for team morale during rapid scaling.
-
•
Finding or building a tribe, whether real or imagined, is critical for personal resilience and effective collaboration in environments of constant change.
Notable Quotes
"When you work for a company called WeWork, the word We can get really confusing and really, really muddy."
"WeWork time means the volume that others see in a week I confronted in a single day."
"One of our VPs said program managers are just expensive routers — that’s the what but they missed the how."
"Learning someone’s origin story lets you understand what means the most to them, not just the what but the why."
"Teams were faking it until they made it with scrum; they were using the right words but not the right practices."
"The quarterly retro’s last question—what started off poorly but improved—is where all the magic happened."
"What happens in retro stays in retro, creating a safe space for honest conversation and healthier teams."
"Adding OKRs to stories helped teams see how their work contributed to WeWork’s goals and discover overlaps with other teams."
"Silver Heart Hat Awards were a small thing, but everyone was so excited to celebrate their colleagues without question."
"Find the people with whom you can lock eyes—those are the people you need, your tribe."
Or choose a question:
More Videos
"Organizations don’t always need external training; they can facilitate internal learning and mentorship."
Shaping design, designers and teams
November 8, 2018
"You cannot sleep on your job; the design operating model must continuously evolve and be communicated."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"If you think IE identity verification is necessary, ask why and if you really have to do it."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"Design, product, engineering, legal, and leadership all need to be involved; it should never be just one group’s responsibility."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility (Videoconference)
May 26, 2022
"We decided to let it rip with clarity about who we were as a team and what we wanted to achieve."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"You need strong regional players with negotiation skills to navigate the split loyalties in global teams."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"I’m hoping that once we figure this out, I can kind of go back to my old goal and break those rules."
Operationalizing DesignOps
November 7, 2018
"When in doubt, make pictures. Drawing takes control of the conversation and makes it concrete."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"Strategy should be continuous, circular, and evolve with every action the organization takes."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020