Understanding Team Inceptions: A Guide to Building Stronger Teams

What is a Team Inception?

A team inception is a bundle of activities designed to mark the beginning of a new phase for a team.  It aims to align the team members on how they want to collaborate, clarify their scope and objectives,  plan projects and tasks effectively and foster a sense of motivation and belonging.

When Should You Consider Running an Inception?

Team inception is particularly valuable during moments of change when alignment among project or team members is essential. Here are some scenarios where an inception might be beneficial:

• Changes in Existing Teams
  • new Tech Lead or Engineering Manager
  • new Product Manager or Product Owner
  • Arrival or departure of team members
• New Projects or Team Initiatives
• Changes in Existing Projects
  • Shifts in direction, goals, or team composition

Promised Outcomes of a Team Inception

The ultimate aim of a team inception is to cultivate an agile, high-performing team, as highlighted by Lyssa Adkins.• For more insights, check out our LinkedIn post.• Learn more about high performing teams from Lyssa Adkins on her blog

Additionally, the process seeks to transform any emerging dysfunctions into healthy team behaviors. Understanding the Five Dysfunctions of a Team (by Patrick Lencioni) can guide this transformation:

1. Absence of trust
2. Fear of conflict
3. Lack of commitment
4. Avoidance of accountability
5. Inattention to resultsFor further reading on this topic, visit The Table Group or check out Lencioni’s book on Amazon.

Who Can Initiate an Inception Process?

Anyone who senses misalignment or dysfunction within the team can call for an inception. Look out for “red flag” behaviors such as:• Frequent absences from work• Avoidance of interactions with other team members• Counterproductive or toxic communication• Lack of clear priorities• Disengaged team members.

Call to action:

If you’re a team member, approach your lead, agile coach, or HR business partners to express your need for an inception. If you’re a Project Manager (PM), Engineering Manager (EM), or Agile Coach, bring this idea to your team or counterparts.Always involve the entire team in discussions about the need for an inception. Transparency fosters trust and sets a positive tone for the process.

Your Investment and Commitment to This Process

Engaging in a Team Inception requires:

• Patience
• Adherence
• Decisiveness and flexibility
• Empathy, vulnerability and approachability

Remember, your emotional investment is just as crucial as the hours spent working.

Addressing time Concerns: “But we have to WORK, we have no time for this!”

The time required for a team inception can vary significantly based on your team’s needs. Generally, expect to invest anywhere from 2 hours to 5 full days. Keep in mind that this process initiates change and development that require ongoing attention; it’s not just a “quick meeting.”

Conversations you don’t have create more friction in the future.

By investing time now, you reduce risks and help your team deliver valuable outcomes for the business.

Who Facilitates and Drives This Process?

While it’s ideal to engage a neutral facilitator if you’re involved in the team’s operations or management, this may not always be possible. Here are some options:

Options for Facilitation

1. Switching Hats: Imagine a scenario in which you are the one facilitating, framing the topic, and instructing the team members on the activity. The team is discussing and you want to contribute but also need to take notes and watch the time. “Let me step out of my facilitator role and put on the hat I am wearing as a team member/ FE designer: my experience/ opinion is…”. And then move back to your facilitator duties. This happens naturally, even if it doesn't necessarily sound like it.
2. Collaborative Facilitation: Team members can alternate facilitation roles while seeking support from an agile coach or scrum master in designing session agendas.

Important Considerations:

• Someone must take charge of the inception project to ensure smooth progress.
• Gaining backing from upper management can create transparency and build long-term trust.

Six Steps to Conducting a Team Inception

1. Share Your Needs: Present the idea of a team inception to your manager and get their approval.
2. Announce to Team Members: Discuss and align on the starting date, review the project plan, gather questions and concerns, and select an “Inception Project Lead” or facilitator.
3. Kick-off Session: Dedicate time to explore:
   • Relationship building and collaboration needs
   • Team vision, roadmap, and backlog
   • Simple working agreements covering communication and collaboration
   • Feedback sharing among team members
4. Assess Team Happiness and Performance:
   • Use tools like the Agile High Performance Tree for concrete behaviors.
   • Reflect on Lencioni’s Five Dysfunctions to identify underlying issues.
5. Celebrate!: Create high-energy moments that foster connection—dance together, record a fun video message for the company, or cook as a team.
6. Schedule Follow-Up: Plan your first retrospective within three weeks post-inception to check in on processes and overall team happiness.

By following these steps, you’ll set your team on a path toward enhanced collaboration and performance!

‍