A Design Ops Girl in a Dev Ops World
Summary
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
"Everyone goes through quite an extensive application process, but it was stress-free and informal."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"You have to make the hard thing easier to do. Behavioral change must be lower friction."
Dem Gerolemou Alexis Oh Neef RehmanClimate technology fundamentals
May 15, 2024
"Our benchmarking survey includes free exploration of the entire website or app, not just the homepage."
Daniela Magaña Flores Ariane Rahn Jeff Ephraim BanderAhead of Competition: Learn What UX Benchmarking Can Do for Your Business Today
March 10, 2022
"We focused on consolidating frameworks and landed on Canvas, which now supports 45 teams and growing."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"We automated everything — now we click a button weekly to produce updated staffing and priority alignment scores."
Patrick CommarfordDesign Staffing for Impact
January 8, 2024
"We mapped every individual journey on Google Earth attaching quotations and photographs to each location to represent human experiences."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"If you’re not paying for the product, you are the product."
Craig VillamorDesign Systems for Ethical Design
January 26, 2023
"The missing hub is the design planning and management tool."
Jon Fukuda Ellie KryslDesign Planning and Management Support
October 3, 2023
"Designers tend to work behind closed doors because the design process is messy and chaotic, and they don’t want people to see that."
Iain McMaster IHan ChengDesign and Product: from Frenemy to Harmony
November 29, 2023
