4.1 Team Types and Constraints
Key Takeaways
- The three team types named in the ASQ Body of Knowledge are virtual, cross-functional, and self-directed.
- Cross-functional teams are the default for DMAIC because value streams cross departmental boundaries that no single manager controls.
- Virtual teams need explicit decision rules and asynchronous documentation because informal corridor coordination is unavailable.
- A time-zone spread beyond about six hours removes the shared working window and forces asynchronous working agreements.
- Self-directed teams suit stable, well-understood processes with a mature workforce, not exploratory analytical projects.
Team types named in the Body of Knowledge
| Type | Definition | Best suited to | Principal risk |
|---|---|---|---|
| Cross-functional | Members drawn from multiple functions, each contributing domain expertise, led by a project leader | DMAIC projects spanning a value stream | Competing functional priorities and split loyalty |
| Virtual | Members distributed across sites, countries, or time zones, collaborating primarily through technology | Multi-site processes, scarce specialist expertise | Weak informal communication, slow decisions, low trust |
| Self-directed | Team manages its own work, scheduling, and often quality decisions without a designated supervisor | Stable, well-understood processes; sustaining improvement after handover | Requires mature skills and clear boundaries; poor fit for exploratory work |
A real Six Sigma team is often two of these at once. A defect-reduction project across three plants is cross-functional and virtual, and it inherits the risks of both.
Choosing against constraints
The Body of Knowledge names four constraint classes explicitly. Work through them in order.
Geography
Co-located teams coordinate for free: the corridor conversation, the shared whiteboard, and the walk to the gemba all happen without scheduling. Distribute the team and every one of those becomes a calendar event.
- Single site: co-located cross-functional team; daily 15-minute stand-up at the process.
- Two to three sites, same region: cross-functional core at the lead site, with named site representatives and a monthly in-person working session.
- Global: virtual team with a documented working agreement, a single shared repository, and a rotating meeting time so the same region is not always inconvenienced.
One rule holds regardless: the Measure phase needs someone physically at the process. Data collected by a remote analyst from a system extract, without anyone watching the process run, is the most reliable way to build an accurate model of a process that does not exist.
Technology availability
Team design must match the tools actually available to every member, not the tools available at headquarters. Plant-floor members may have shared kiosks rather than personal computers; contract manufacturers may be outside your network entirely; regulated environments may prohibit external file sharing. If a member cannot reach the shared repository, they are not on the team no matter what the charter says. Check before you design: video conferencing, shared document editing, statistical software licences, access to the MES or ERP data, and permission to move data across borders.
Staff schedules
A three-shift process cannot be represented by a team that meets at 10 a.m. on weekdays. Practical countermeasures:
- Rotate the meeting time across shifts, or hold a short handover briefing at each shift change.
- Recruit a shift representative from every shift rather than only the day shift, because shift-to-shift differences are frequently the dominant source of variation.
- Budget backfill. A team member cannot leave a running line unattended for a two-hour workshop.
Time zones
Overlap window is the binding constraint:
| Spread | Shared working window | Working mode |
|---|---|---|
| 0-3 hours | 5+ hours | Treat as co-located; synchronous meetings work |
| 4-6 hours | 2-3 hours | Reserve the overlap for decisions only; do analysis asynchronously |
| 7+ hours | Effectively none | Fully asynchronous; decisions by documented proposal with a response deadline |
For spreads beyond six hours, adopt a follow-the-sun handover: each region ends its day by posting what changed, what is blocked, and what the next region should decide.
Working agreements for virtual teams
Virtual teams fail on ambiguity, not on distance. A short written working agreement removes most of it:
- Decision rule. Which decisions the team may take alone, which need the sponsor, and what happens if a member does not respond within the deadline.
- Response time expectation. For example, 24 working hours for a posted proposal.
- Single source of truth. One repository for data, charter, and analysis; no decisions in chat.
- Camera and language norms. Non-native speakers need agenda and materials in advance.
- Meeting hygiene. Agenda circulated ahead, pre-work stated, notes and actions posted the same day.
Self-directed teams and the handover
Self-directed teams matter most at the end of a project. A control plan handed to a supervised team that has no authority to adjust the process will be followed until the first conflict with output targets. A self-directed team with defined boundaries -- adjust within these limits, escalate outside them -- sustains the gain because it can act. Self-direction requires three conditions: the members have the technical skill, the boundaries are written down, and the reward system does not punish stopping the line.
Worked example
A packaging defect project spans two plants seven time zones apart, involves quality, maintenance, and a contract label supplier, and runs across three shifts.
The correct structure is a cross-functional virtual team with: a co-located core at the plant carrying the majority of the defects; a named shift representative at each site; the supplier included as a member rather than consulted as a vendor; a two-hour weekly overlap window reserved for decisions; asynchronous data posting between sessions; and an explicit rule that Measure-phase observation happens locally at each site rather than from system extracts alone.
A DMAIC project spans two facilities nine time zones apart. What working mode does that constraint dictate?
Which team type is the default choice for a Six Sigma project whose process runs through purchasing, production, and logistics?
A team studying a three-shift filling line recruits all members from the day shift for scheduling convenience. What is the most likely analytical consequence?