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 ambiguity of the word 'We' at WeWork necessitated developing a unique internal syntax for clarity.
-
•
WeWork operates at an exceptionally rapid pace, experiencing a week’s worth of challenges daily.
-
•
Program managers were initially misunderstood as 'expense of routers,' highlighting a gap in understanding their unique skills.
-
•
Learning people’s origin stories reveals their motivations and helps build deeper connections beyond just knowing roles.
-
•
The Red Tech mission was formed from three distinct waves of teams with very different cultures and histories.
-
•
Introducing simple, fundamental agile scrum training helped unify teams with varying levels of scrum knowledge.
-
•
Quarterly retrospectives with strict ground rules and three focused questions unlocked honest dialogue and revealed emotional undercurrents.
-
•
Mapping agile stories directly to OKRs connected team efforts to company goals and surfaced cross-team collaborations.
-
•
Implementing peer recognition through the Silver Heart Hat Awards boosted morale and peer appreciation visibly and inclusively.
-
•
Building or finding a 'tribe' of trusted collaborators is essential for emotional support and navigating rapid organizational change.
Notable Quotes
"When I talk about We, am I talking about You and Me, or the company itself? The word We can get really confusing."
"The volume coming at me every day was like a week’s worth of work compressed into one day."
"Program managers are just expense of routers—what they missed was the how, that secret sauce of EQ."
"Asking someone’s origin story gets you their why, not just the what."
"There are at least six definitions for desks at WeWork—context matters."
"Many team members were faking scrum until they made it; they used the words but didn’t know the practice."
"What started off poorly but improved during the quarter is where all of the magic happened in retrospectives."
"Quarterly retros are sacred; what happens in retro stays in retro to create trust and honest conversations."
"Multiple teams were supporting the same goals in different ways, and that led to meaningful cross-team conversations."
"Find the people with whom you can lock eyes—those are your tribe, your support system."
Or choose a question:
More Videos
"What is design’s relationship to power and privilege? Which humans do we center when we say human-centered design?"
George AyeThat Quiet Little Voice: When Design and Ethics Collide
November 16, 2022
"We fundraised to cover Tatiana’s salary for three months so she could launch this project very quickly after the war started."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"When you get a best in class tool, you are able to execute more rigorous research and show clearer ROI."
Benjamin Wiedmaier Annie MayfieldRedefining Toolkits: Unbundling to Create a Perfect Match
March 11, 2025
"You can’t iterate on everything at once; you have to pick areas to improve based on business criticality and performance."
John DevanneyThe Design Management Office
November 6, 2017
"You have to ask yourself, what's the least amount of work you need to do to get the learning you want from a prototype."
Steve Sanderson Alissa Briggs Jeff Gothelf Bill ScottDiscussion
May 14, 2015
"How do they grow and organize their teams to keep up? How do they scale their processes? How do they maximize efficiency and quality?"
Jemma AhmedTheme 2 Intro
January 8, 2024
"The only person who gets to decide what it means to be badass is you."
Megan KiersteadYou Are a Badass at UX: Overcoming Imposter Syndrome
March 10, 2021
"We moved from versioning the entire system quarterly to individually versioning components, so changes are easier to track and prioritize."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Extractive, commercially-driven communities aren’t really communities in the pure sense."
James LangIf you can design an app, you can design a community
May 22, 2025
