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
"Frequent, bite-sized training is crucial so staff actually remember how to support customers with disabilities."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
"Our evaluation tool is a Google Sheet so we can quickly make adjustments without being bogged down by unnecessary features."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"Embedding designers gave them deep expertise but siloed goals prevented consistent cross-product experiences."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"Design is often framed as problem solving, but conversation is a better framework to respect users as active experts."
Daniel GloydWarming the User Experience: Lessons from America's first and most radical human-centered designers
May 9, 2024
"The careful application of structured queries can reveal deeper insights than traditional research alone."
Patrick BoehlerFishing for Real Needs: Reimagining Journalism Needs with AI
June 10, 2025
"Many customers struggle to get anyone to listen to actual insights because of the volume and complexity of raw video data."
Andy Barraclough Betsy NelsonFrom Costly Complexity to Efficient Insights: Why UX Teams Are Switching To Voxpopme
September 23, 2024
"I’m totally freaked out by facial recognition and wonder why we don’t get together as consumers to push back on bad designs."
Alexandra SchmidtWhy Ethics Can't Save Tech
November 18, 2022
"In government, the motivation is reduction of misery: why are we up at 3 AM fixing something avoidable?"
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"Sketch made it possible to build a scalable library that millions of customers rely on with just a couple clicks."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
Latest Books All books
Dig deeper with the Rosenbot
How does Mary Lynn view the impact of data-driven design practices on end users and designers?
What is democratization in UX research, and how is it influencing who performs research tasks?
How can designers identify which parts of a system they can influence or should monitor using affordance mapping?