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
"If I don’t trust you, how can I feel safe with you?"
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"Ownership means belonging to the person who anticipates, observes, or monitors the prioritization process—not distributed ownership."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars) (Videoconference)
June 13, 2024
"Every time somebody purchased a domain name, I earned a commission. Over three to four years, I earned over $100,000 as a high school student."
Nick CochranGrowing in Enterprise Design through Making Connections
June 3, 2019
"Not everything that is faced can be changed, but nothing can be changed until it is faced. - James Baldwin"
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Show, don’t tell—that’s a principle we learned from the UK Government Digital Service."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"I’ve never done this before. I’m going to be learning as I go and I’m going to share everything I learn with you."
Nova Wehman-BrownWe've Never Done This Before
June 4, 2019
"We need to learn the domain, the technology, the algorithm, and the data—not enough to code, but enough for meaningful discussions."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"The arrival of workers during COVID lockdown meant coordinating across government ministries, airport authority, federal border services and public health – this was a design problem."
Gordon Ross12 Months of COVID-19 Design and Digital Response with the British Columbia Government
December 8, 2021
"People will forget what you said, people will forget what you did, but people will never forget how you made them feel."
Tutti TaygerlyMake Space to Lead
June 12, 2021
