Workshop Guide
Team Organization Workshop Guide
Turn a group of people into stable, cross-functional teams that can deliver without waiting on each other.
01 / Summary
What Is Team Organization?
Team Organization is the structured practice of deciding how a group of people forms into teams: who belongs on each team, what work each team owns, and what skills each team needs to deliver that work without waiting on someone else. The goal is small, stable, cross-functional teams aligned to a flow of work, rather than groups that mirror the org chart.
Run this workshop when an ART, program, or department needs to stand up new teams or rework teams that are struggling. It sits between ART-level design and team chartering: it takes a defined scope of work and a list of people, and it produces a draft team design, a skills coverage view, a dependency map, and a set of open decisions that leadership can review.
02 / Application
When to Use Team Organization
Team Organization is most useful at the moment teams are being formed or reformed, before people have settled into new working patterns. Use this workshop when the current team structure is the reason work stalls, or when a new scope of work needs teams that do not exist yet.
Standing Up New Teams
When a new ART, program, or product area is launching, run this workshop to turn the people assigned to it into teams with a clear mission, the right skills mix, and a defined team type.
Work Stalls Between Teams
When most work items wait on another team for testing, data, design, or deployment, the team boundaries are likely in the wrong place. This workshop redraws them around the flow of work.
Teams That Are Too Big or Too Small
When a team has grown past the point where everyone can stay aligned, or a team is too thin to finish anything alone, this workshop rebalances membership across teams.
Specialists Spread Too Thin
When the same few people are split across many teams and become the bottleneck for all of them, this workshop makes the allocation visible and decides where those skills should live.
Prerequisites
A Defined Scope of Work
The group needs an agreed boundary: the value stream, ART, product, or set of work streams these teams will own. Without it, the session turns into a debate about scope instead of team design.
A Current People and Skills Inventory
Bring a list of every person in scope with their role, primary and secondary skills, location, and current allocation. The People and Skills tab of the template is built for this.
Roles and Responsibilities
Include the people affected by the design, not just their managers. Teams designed without input from the people on them tend to look balanced on paper and miss the real skills and constraints in practice.
Scheduling and Timing
- Run after ART or program boundaries are agreed and before PI Planning or the first sprint, so new teams can start working together on a clean cadence.
- Plan for about three hours for two to four teams; block a full day, or split across two sessions, when organizing five or more teams.
- Schedule a 30-minute pre-session checkpoint with managers one week before to confirm the people and skills inventory is complete.
- Follow with a Team Charter session for each new team, and review the design after one Planning Interval or quarter to catch size, skills, or load problems early.
03 / Preparation
Preparing for the Workshop
Team design conversations get personal quickly. Preparation keeps them grounded: when the scope of work, the people inventory, and the design criteria are agreed before the session, the group spends its time designing teams instead of debating facts. The checklist below covers what to have ready.
- Confirm the scope of work these teams will own: the value stream, ART, product, or work streams, written down and agreed by leadership.
- Gather a people and skills inventory for everyone in scope: role, primary and secondary skills, location or time zone, reporting line, and current allocation.
- List the handoffs and dependencies that slow work down today, with one or two recent examples of work that stalled between teams.
- Agree on the design criteria in advance with the sponsor: maximum and minimum team size, dedicated membership, and the team types the group may use.
- Prepare the Team Organization Excel Template with the People and Skills tab filled in and the required skills entered on the Skills Coverage tab.
- Confirm the Miro board is set up with a column per proposed team, cards for each person, and a parking lot for open decisions.
- Download and prepare the Facilitator Presentation.
- Track every workshop activity, from preparation through follow-up, using the Team Organization Workshop Checklist. Teams using Jira can import the Team Organization Jira Accelerator.
-
Send scheduling communication with agenda and pre-read materials
Email Template
Subject: [Program/ART Name] – Team Organization Workshop – [Date]Hi team,
We are holding a Team Organization Workshop on [Date] from [Start Time] to [End Time] [Time Zone] via [Platform/Location]. In this session we will design the teams that will deliver [Scope of Work], so each team has a clear mission, the skills it needs, and as few handoffs as possible.
To make the most of our time together, please come prepared with the following:
- Confirmation that your row in the People and Skills sheet is accurate, including secondary skills
- One or two recent examples of work that stalled waiting on another team
- Any constraints that affect where you or your team members can work, such as time zones or planned leave
Today’s session produces a draft design for leadership review, not final assignments. We will talk with everyone affected before any change is announced.
Please reach out with any questions before the session.
Thank you,
[Your Name]
[Title] | Stephens Insight GroupCalendar Invite Copy
Subject: [Program/ART Name] – Team Organization Workshop – [Date]Purpose: Design stable, cross-functional teams for [Scope of Work] and agree on next steps for leadership review.
Please bring: A confirmed People and Skills row, examples of work that stalled between teams, and any known constraints.
Agenda:
– Set the Stage (15 min)
– Confirm Scope and Flow of Work (20 min)
– Inventory People and Skills (30 min)
– Draft Team Options (45 min)
– Test Against Design Criteria (30 min)
– Map Remaining Dependencies (20 min)
– Confirm Teams and Next Steps (20 min)Location/Link: [Meeting Link or Room]
Room and Technology Setup
Seating
Arrange the room so everyone can see the wall or shared screen where proposed teams take shape. Leave space for people to stand and move cards between team columns.
Visual Aids
Post the design criteria and the four team types where everyone can see them. Display the Team Design and Skills Coverage tabs so size and gap checks are visible as the design changes.
Technology
Ensure reliable internet access for all participants. Open the Team Organization Excel template before the session begins, and have your HR or resourcing data on hand to confirm allocations as needed. Test screen sharing ahead of time.
Virtual Setup
Use a platform like Microsoft Teams, Zoom, Google Meet, or Webex with screen sharing enabled. Share the Miro board and the Excel template in real time and confirm all participants have access before the session. Test audio, video, and file access at least 15 minutes before the start.
04 / Facilitation
Running the Workshop
Run this as a working session, not a presentation. Every step moves the group from a list of people toward a team design they can defend, and the worksheet does the checking so the conversation stays on the work rather than on individuals.
Purpose
Design teams around the flow of work so each team can deliver value with as few handoffs and dependencies as possible.
Style
Collaborative and transparent. Make every assumption visible, test options against agreed criteria, and give the people affected a real voice in the design.
Outcome
A draft team design with clear missions, balanced skills, explicit dependencies, and a short list of decisions for leadership.
Duration: Most Team Organization workshops run about three hours for two to four teams. Larger scopes may need a second session for drafting and testing options. Build in buffer for discussion, because that is where the group surfaces the skills and constraints that never show up on an org chart.
Presenting the Team Organization Process
-
Set the Stage: 15 minutes
- Open with the purpose: design teams around the flow of work so they can deliver without constant handoffs.
- Agree on the working norm: the group designs around skills and work, not around individual preferences or titles.
- Confirm that reporting-line, hiring, and funding decisions are out of scope for the room and will be captured for leadership.
-
Confirm Scope and Flow of Work: 20 minutes
- Review the value streams, products, or backlog areas in scope for this group.
- List the distinct flows of work that a single team could own end to end.
- Note any specialist areas, such as complex components or shared platforms, that may need a different team type.
-
Inventory People and Skills: 30 minutes
- Walk the People and Skills tab together: role, primary and secondary skills, location, and current allocation.
- Flag anyone split across more than one team today, and any skill that only one person holds.
- Capture constraints such as time zones, contract end dates, and planned leave in the notes column.
-
Draft Team Options: 45 minutes
- Start with stream-aligned teams that own a flow of work end to end, then add platform, enabling, or complicated subsystem teams only where they are needed.
- Assign each person a Proposed Team in the worksheet, aiming for dedicated membership on one team.
- If the group is split, sketch two options side by side rather than forcing a single answer too early.
-
Test Against Design Criteria: 30 minutes
- Size: confirm each team is within the agreed range, typically ten or fewer people.
- Skills: review the Skills Coverage tab for gaps and single points of failure, and rebalance where needed.
- Load: rate each team’s cognitive load from 1 to 5 and adjust the scope of any team rated 4 or 5.
-
Map Remaining Dependencies: 20 minutes
- List each dependency between proposed teams that the design could not remove.
- Assign an interaction mode to each one: Collaboration, X-as-a-Service, or Facilitation.
- Mark which dependencies can still be designed away and capture the action needed.
-
Confirm Teams and Next Steps: 20 minutes
- Read back each proposed team: name, team type, mission, and members.
- Log every open decision that needs leadership authority with an owner and a due date.
- Agree on who will talk with affected people, when the design will be reviewed, and when each new team will run its Team Charter session.
Common Anti-Patterns to Avoid
-
Copying the org chartGrouping people by function or reporting line recreates the handoffs the workshop is meant to remove. Start from the flow of work and assign skills to it.
-
Splitting people across many teamsFractional allocations look efficient on paper but turn shared specialists into bottlenecks. Aim for dedicated membership and treat every split allocation as a decision to justify.
-
Designing around individuals instead of skillsBuilding teams around who gets along, or who a manager wants to keep, produces teams that cannot deliver alone. Test every option against the Skills Coverage tab.
-
Announcing teams before talking to peopleA design shared before affected people hear it directly erodes trust in the whole change. Treat the session output as a draft and communicate person by person first.
05 / Follow-Up
After the Workshop
A team design only creates value once people are working in it. The follow-up turns the session’s draft into decisions: it records what the group proposed, routes open questions to the leaders who can answer them, and sets the communication and transition steps that move people into their new teams.
Expected Outputs
Skills Coverage Matrix
Team Dependency Map
Open Decisions Log
Transition Plan
Share the completed workbook and draft design with participants and the sponsoring leaders within 24 hours of the session. Mark it clearly as a draft, and hold wider distribution until open decisions are resolved and every affected person has heard about their placement directly.
Follow-Up Communication Template
Hi team,
Thank you for your participation in today’s Team Organization Workshop. Below is a summary of the draft team design and the next steps before anything changes.
Proposed Teams:
[List each team with team type, mission, and members]
Skills Gaps and Single Points of Failure:
[List gaps from the Skills Coverage tab and the proposed response]
Remaining Dependencies:
[List dependencies with their interaction mode and owner]
Decisions Needed from Leadership:
[List open decisions with owner and due date]
The full workbook is available at [Link to Shared Document or Miro Board]. This is a draft for review. No team changes will be announced until we have spoken with everyone affected.
Our next touchpoint is the design review on [Date]. Please share questions or concerns with [Facilitator Name] before then.
Thank you,
[Your Name]
[Title] | Stephens Insight Group
Ongoing Next Steps
- Share the workbook and draft design with participants and sponsoring leaders within 24 hours of the session.
- Resolve open decisions on reporting lines, hiring, and funding before announcing any team changes.
- Talk with each affected person about their placement before the design is shared more widely.
- Update team structures in Jira or your tracking tool, and move backlog items to the teams that now own them.
- Run a Team Charter session with each new team before its first sprint together.
- Review the design after one Planning Interval or quarter, checking team size, skills coverage, cognitive load, and dependencies against the original criteria.
06 / References
References and Resources
- Scaled Agile Framework (SAFe): Agile Teams
- Scaled Agile Framework (SAFe): Organizing Agile Teams and ARTs, Team Topologies at Scale
- Team Topologies: Key Concepts
- The Scrum Guide (2020): The Scrum Team
Complimentary Workshops
Team Charter Workshop
Get a new or reset team explicit about purpose, roles, and working norms before the first sprint.
Story Pointing Workshop
Give the team a shared, repeatable way to size backlog items before they commit to a sprint.
Ready to facilitate?
Download templates and tools to run your own Team Organization session.