Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
Why do some project teams work well, while others just can’t seem to get it together? Why do some teams have a strong sense of culture while others feel like a group of strangers working on the same task? When a team comes together, whether it’s for a short-term project or ongoing long-term operations, a culture emerges: you can see it in how the team works toward common goals and how they interact with one another. Although you can’t force team culture, you can design for it. Through an enterprise project case study, we look at onboarding techniques and methods that can be used to deliberately build strong team cultures.
Key Insights
-
•
Poor onboarding and revolving temporary staff can cause high-profile projects to fragment and stall.
-
•
Designing the team member experience is as critical as designing user experience for project success.
-
•
Hiring for 'fit' should focus on skills and ability to ramp up quickly rather than cultural similarity.
-
•
Creating a newbie reading list with project history and business context helps new team members onboard faster and with clarity.
-
•
Telling project folklore orally and in one-on-ones solidifies shared understanding and avoids misinformation.
-
•
Clear, honest job titles discouraging heroism foster a collaborative, team-first mindset.
-
•
A simple, plain-language team code of conduct focusing on respectful, honest communication encourages productive behaviors.
-
•
Collaboration rituals like daily standups and co-working sessions sustain culture even in fully remote teams.
-
•
Allowing sufficient onboarding time (e.g., ~1 month) before expecting productivity improves integration and retention.
-
•
Even small teams can design their own culture and onboarding processes tailored to their context to offset larger organizational dysfunction.
Notable Quotes
"A conference is just a polished snapshot of a conversation that's really going on all year."
"The people working on difficult projects acted more like faceless individual contributors than a real team."
"There wasn't much attention paid to onboarding team members—not the clients or users, but the actual team."
"The project was staffed through a revolving door of panic hires who were expected to run from day one."
"Our team was the only thing you could describe as an actual team—because we deliberately built onboarding and culture."
"We herded all of our unicorns and named them appropriately with clear, meaningful titles."
"Although you can't force culture, you can design for it."
"Hiring for fit is dangerous if you don't do it carefully, so we looked at fit for purpose—skills and ramp-up ability."
"Speak plainly and simply. Say what you mean to say."
"We do a lot of unstuck meetings—where anyone stuck can bring the problem and get brain help without judgment."
Or choose a question:
More Videos
"Some product managers just skipped getting customers involved in the development process at all."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Think about who decides what, when, where, by which criteria and how these decisions connect—this helps influence decision making."
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"If you never want to fully embed yourself in engineering, that’s fine too — you don’t have to show anyone the code you generate."
John DonmoyerShipping your code generation experiments to production
June 11, 2025
"I’ve sat on both sides of the table. I’ve sometimes help both jobs at once which I don’t recommend."
Christian CrumlishIntroduction by our Conference Chair
December 6, 2022
"Our folks are not looking for information about what are wireframes. They want information specific to your organization."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"The future is now, it’s just not evenly distributed."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"What are the small steps teams can take to sustain their energy and well-being over time?"
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
"Designers often resist processes meant to streamline their work because it feels restrictive."
Kristin Skinner Kamdyn Moore8 Types of Measures in Design Operations
April 16, 2020
"Design ops is a flexible and adaptable practice, meaning our goals and outcomes are usually more fluid than stable."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
Latest Books All books
Dig deeper with the Rosenbot
What does it mean for design ops to shift from managing existing processes to architecting infrastructure and cultural change at scale?
What responsibilities should design ops take on regarding frameworks like onboarding and career growth templates?
How does categorizing risk improve prompt design and evaluation in AI products?