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
"If you value innovation and design, then you're investing in creativity."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"I never want to walk into a review with my stakeholders at the SVP level and see something for the first time."
Amy MarquezINVEST: Discussion
June 15, 2018
"When you look at data without training, confirmation bias makes you just find what you already believe."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"How do you organize a design team to work within a changing environment without freaking everybody out."
Alicia MootyDesign Staffing Models
September 30, 2021
"Research in science fiction helps make research real and creative all the time."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"You can’t really advocate for UX or move an organization forward without interacting with your team and business colleagues."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"It’s very difficult to align researcher goals with business growth, but that’s exactly what we try to do."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Large companies demand certainty, but certainty is the opposite of innovation."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Typically, data analytics teams are big and well-funded, while UX research teams are smaller and struggle for resources."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
