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.
Designing the team experience: Building culture through onboarding
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
"Sometimes assumptions break down, like credit cards without expiration dates in India; you have to listen carefully to customers."
Ross SmithBreaking Barriers with Empathy
June 9, 2017
"Designers want more time to prototype and really ensure what ships is successful, but we just don’t have enough people or time."
Kevin M. HoffmanTheme 2: Enterprise Team Journey
June 3, 2019
"Communication matters—sending an email to an executive with spelling mistakes can ruin your respect."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"Testing with real users humanizes the problems and reveals simple fixes like changing one label or color."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
October 2, 2023
"Ops folks are the linchpin connecting leadership and designers, orchestrating all the instruments."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
"Tracking implementation commitments after each design network group keeps momentum and accountability."
Prerna MakanawalaAchieving Balanced Design Consistency
June 9, 2021
"All our components can be data bound so the developer can point to any data source like CMS or JSON to populate UI elements naturally."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"Successful organizations continually test, use larger sample sizes, and measure UX performance to manage what they can’t measure."
Dana Bishop2022: The Year UX Demonstrates its Business Impact
March 11, 2022
"For OKRs to work, incentives have to focus on learning, customer centricity, and evidence-based decision making, not just delivery."
Jeff GothelfWho does what by how much?
November 20, 2025
