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, under-skilled staffing lead to fractured teams and project failure in enterprise contexts.
-
•
Designing the team member experience is as important as designing for users to create effective collaboration.
-
•
Sharing project folklore and a common understanding of history and decisions helps align new team members quickly.
-
•
Clear, honest, and simple job titles that reflect actual work promote team cohesion and prevent mistrust.
-
•
Temporary team assignments benefit from longer terms (6-12 months) rather than brief 3-month bursts to foster productivity.
-
•
Deliberate onboarding reading lists and one-on-one walkthroughs significantly improve context absorption for new team members.
-
•
Creating a shared sense of purpose and collective goals aligns individual effort and reduces siloed, consultant-like behavior.
-
•
A simple, plain-language team code of conduct focusing on behaviors like honesty, collaboration, and accountability can build positive culture.
-
•
Remote work can be supported effectively through frequent office hours, 'unstuck meetings,' and collaborating rituals that sustain connection.
-
•
Onboarding timelines vary; for complex environments a month-long onboarding with gradual integration is necessary for lasting impact.
Notable Quotes
"We cannot fail was the mantra, yet there was no serious onboarding for team members."
"New hires acted more like faceless individual contributors than a real team."
"Project folklore is made up of the stories we tell ourselves about the work we're doing."
"We herded all of our unicorns and named them appropriately with simple meaningful titles."
"Although you can't force culture, you can design for it."
"Speak plainly. Speak simply and plainly and say what you mean to say."
"Collaborate daily; more than one brain is always better for problem solving."
"Research over opinions; decisions should be driven by data and evidence, not hunches."
"It's hard for students who come in — their job isn't just to close tickets, it's to learn and move work forward."
"The pandemic pushed us to host office hours three times a day so people could drop by and connect."
Or choose a question:
More Videos
"Scale isn’t just about quantity, it’s about the quality and impact you have on the outcomes of the organization."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"You can mine metadata from your platform to spot emerging patterns and commoditize new components."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Cisgender binary options in onboarding flows exclude non-binary and gender-expansive identities."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"Appealing to stakeholders’ best interests helps build trust and rapport."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"We mitigated data privacy risks by subscribing to the corporate plan for ChatGPT, which offers enhanced security."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Empowering maker culture invites everyone to be part of a collective endeavor far beyond any individual."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Consistency over business unit efficiency was a design principle to ensure unified interface and language."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"TripAdvisor is really nine major business units each thinking like sub companies instead of one end-to-end user experience."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Most of us in design are very process-oriented, but traditional devops tools are task and issue-centric, making collaboration hard."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022