Team Self-Selection Workshop

---

Origins

Team self-selection as a deliberate workshop format was developed and popularized by Sandy Mamoli and David Mole at Trade Me in New Zealand and documented in their book Creating Great Teams: How Self-Selection Lets People Excel¹. The approach grew out of frustration with traditional team formation — weeks of leadership-led reorganization meetings, top-down team assignments, and the predictable cycle of teams forming, complaining, and reforming.

The premise is straightforward but uncomfortable for many organizations: people generally know better than their managers which team they would do best work on. If you give them the constraints (size, skill mix, business goals) and let them organize themselves within those constraints, the result is usually faster, more committed, and produces healthier teams than any top-down assignment would. The discomfort comes from giving up control over an outcome leaders are accustomed to owning.

What the Workshop Does

A self-selection workshop is a structured event in which a group of people forms multiple teams by their own choice, within constraints set by leadership. It typically happens at:

• Initial team formation: a new product area is being staffed, or a department is structuring itself into teams for the first time.
• Reorganization: an existing organization is reshaping its teams around new product strategy or business priorities.
• Periodic refresh: some organizations rerun self-selection at scheduled intervals (annually, when major strategy shifts, after a fiscal year) to allow people to move to teams where they want to be.

The output is a set of teams that participants chose to be on. The participation in the choice produces commitment that no assignment can replicate.

The Constraints

The constraints leadership sets are the foundation of the workshop. They define what an acceptable outcome looks like without dictating who ends up where.

• Number of teams: determined by leadership in advance based on the work to be done.
• Team size targets: each team has a target headcount and an acceptable range (e.g., "5–8 people").
• Required skill mix per team: each team must have a minimum set of capabilities (e.g., "at least one experienced backend engineer," "at least one designer," "at least one tester").
• Mission per team: each team has a clearly described purpose — what product, what customer, what goal.
• Business-critical roles: occasionally individuals are pre-assigned to specific teams (e.g., the tech lead for a critical legacy system stays where they are). This should be the exception, not the rule.

The art of the constraints is keeping them firm enough to ensure viable teams but loose enough that participants have real choice. Over-constrained workshops are theater; under-constrained ones produce unbalanced teams.

The Workshop Format

A typical self-selection workshop runs for 2–4 hours. Larger groups or more complex constraints may need longer.

1. Pre-work (weeks before)

Leadership defines and announces the new team structure: how many teams, what each team's mission is, what skill mix each requires. The full set of teams is published well in advance so participants can think about their preferences.

2. Set the scene (15 min)

On the workshop day, walk through the format, the constraints, and the success criteria. Make explicit: the goal is for every team to be filled with the right skill mix; everyone gets a team they chose.

3. Round 1: Initial selection (15–30 min)

Each participant stands by the team they want to be on (physically, on a board, or in a digital tool). The visual shows where the natural energy is and where the team-fit problems are.

4. Round 2: Negotiation (30–60 min)

Where teams are over- or under-filled, or where required skills are missing, the group negotiates. The facilitator highlights the constraints that aren't yet met: "Team Beta needs a senior engineer; Team Gamma has three." Participants discuss who might move, what trade-offs each move involves, what reservations need to be aired.

5. Subsequent rounds as needed (30–60 min)

Continue rounds until all teams are within constraint. Typical workshops resolve in 2–4 rounds. The facilitator's job is to surface the structural problems and let the group solve them, not to make assignments.

6. Confirm and commit (15 min)

Once teams meet constraints, each person publicly confirms the team they are on. Each team has a short conversation about how they'll start working together.

What Makes It Work

• Genuine choice: participants must believe their preferences will be honored. The first time a workshop is overridden by leadership after the fact, future workshops become theater.
• Real constraints: vague constraints produce ad hoc decisions. Specific constraints give the group something to optimize against together.
• Public process: the rounds happen in the open. Quiet side-deals and pre-arranged outcomes destroy the trust the format depends on.
• Leadership presence without intervention: leaders are in the room to clarify constraints and answer questions, not to overrule the group.
• Trust the process: workshops feel chaotic in round 1 and resolve by round 3 or 4. Cutting the process short to "just assign people" defeats the purpose.

Common Pitfalls

• Stars cluster: high-status individuals or popular teams attract too many participants. The negotiation rounds exist to address this; if they're cut short, the imbalance persists.
• Some teams sit empty: a team with an unpopular mission may be everyone's last choice. Either the mission needs reframing, or leadership has set up a workshop where someone is being assigned by default. Be honest about which.
• Last-pick anxiety: people who don't get their first choice can feel pressured or unwelcomed. The facilitator must hold space for those moments and help the group resolve them with dignity.
• Social pressure overrides judgement: people pick teams because their friends did, not because the work suits them. Pre-work should emphasize that the team's mission matters more than its membership.
• Leadership reneges: the workshop happens, the assignments are made, and then leadership adjusts them privately afterward. The format dies the moment this happens, and trust takes years to rebuild.
• Mandatory all-at-once: forcing the entire organization through the process simultaneously can overwhelm. Some teams resist participating, which undermines the result for those that do.

Coaching Tips

Set Specific Constraints

"Have the right mix" is too vague. "Each team needs at least one senior backend engineer and at least one designer" is workable. Specificity is what makes the workshop converge.

Announce the Missions Early

People need time to think before the workshop. Publishing team missions days or weeks in advance is worth far more than a 30-minute briefing on the day.

Hold the Line on Honor

Negotiate with leadership before the workshop: the result will be respected. If leaders aren't ready to commit to that, run a different format.

Make Trade-offs Visible

When a team is over-full, name the trade-off explicitly: "to make this team work, two of you would need to move to another team that needs your skill." Don't just point at the imbalance.

Protect Last-Pick Dignity

People who don't get their first choice are vulnerable in the moment. Coach the group to be welcoming — "we need you, here's why" — not grudgingly accepting.

Run It Again Within a Year

People's interests and team contexts change. An organization that runs self-selection once and never again is treating it as an event; the practice works when it becomes a rhythm.

Summary

Team self-selection is a deliberately uncomfortable practice for leaders accustomed to building teams themselves. The discomfort is the price of getting the result the format produces: teams whose members chose to be there, who feel ownership of the mission, and who start with the kind of commitment that top-down assignment can never deliver. The format succeeds when leadership trusts the constraints to do their work and trusts the group to optimize within them.

The mechanics are not the hard part. The hard part is giving up the prerogative to assign people, and resisting the temptation to "fix" the outcome afterward. Once an organization runs a workshop and respects its result, future workshops become routine. The first one is the one that establishes whether the practice will work.

Back to Discovery Workshops