I am forming a team for my improvement project. How many people do I need? Should they be from the same department, or should I involve cross-functional members? I want to make sure I have enough help without making the team too large to manage. Any advice on team composition?
Effective Green Belt project teams consist of four to seven cross-functional members selected based on subject matter expertise, process influence, and the ability to contribute directly to the DMAIC project phases.
4 answers
A large team is simply a lack of project definition. Keep it lean, ideally four to six contributors. If you are struggling to manage the team, your scope is likely too broad, or you have filled the room with people whose only job is to nod. Efficiency is the goal; bureaucracy is the enemy.
You need a cross-functional mix. If your improvement project only involves your own department, you are likely looking at a micro-task, not a Green Belt-level improvement. A true improvement requires breaking down silos. If you do not have someone from an external department providing a different perspective on your process, you are prone to confirmation bias. Use the SIPOC model to identify your suppliers and customers; pull your core team from those identified areas.
If someone cannot explain their process contribution in ten seconds, they do not belong in the room. Efficiency matters more than committee participation.
Optimal team size for a Green Belt project is typically five to seven members. Anything beyond this creates communication overhead that dilutes focus. Regarding composition, cross-functional representation is not just a preference; it is a requirement for process integrity. If your project impacts the upstream or downstream flow, you must have representation from those departments to avoid localized optimizations that negatively impact the broader system.
Focus on selecting members based on these three criteria:
- Subject Matter Expertise: Individuals who execute the process daily.
- Analytical Capability: Team members capable of interpreting basic data sets.
- Influence: Someone with the authority to implement changes within their respective silo.
Avoid the trap of gathering stakeholders just to be inclusive. Inclusions must be driven by data requirements, not politics. If someone does not contribute directly to the DMAIC phases, they are a distraction, not a team member.
Thank you for this advice, Supriya. I often worry about whether my team size is appropriate, and these criteria regarding analytical capability and influence are certainly helpful to keep in mind.
Supriya, your focus on data requirements over politics is a relief. I have seen too many projects lose momentum because of unnecessary stakeholders, so this direct approach makes a lot of sense.
Stop looking for friends; look for people who know where the bodies are buried in your process. A team of more than six people is a meeting, not a project group. If you have ten people, you are wasting the company's time.
Cross-functional is non-negotiable. If your process touches inventory and engineering, you need representatives from both. Without them, you will develop a solution that works on paper but fails the moment it hits the real world. I have seen too many Green Belts ignore the guys on the floor and then wonder why their solution was rejected in the pilot phase. Get the people who actually touch the parts, not the supervisors who just talk about them.
Prioritize members who actually understand the current state. If they cannot explain the current process failures with data, do not waste a seat on them. Keep the team small, keep them accountable, and cut anyone who just shows up to collect hours.
Chad, I completely agree that involving the people who actually touch the parts is essential. I need to make sure I am prioritizing those boots-on-the-ground insights to avoid those common pilot phase failures.
To ensure success, apply the RACI framework during the selection process. A team size of five to seven remains the industry standard for agile improvement projects. Exceeding eight members significantly increases entropy, leading to decision paralysis. Use the following structure to build your team:
- The Process Owner: Maintains accountability for the long-term sustainment.
- The Subject Matter Expert: Provides the granular technical data required for root cause analysis.
- The Data Analyst: Ensures statistical validity of the findings.
- The Cross-Functional Stakeholder: Represents the downstream impact, ensuring the solution does not create a bottleneck elsewhere.
Adopt a systems-oriented approach. Your team should represent the entire value stream, not just the segment currently undergoing modification. By integrating cross-functional members early, you leverage the diverse perspectives necessary to identify non-value-added activities that might be invisible to those within a single department. Maintain a Kanban board to track their tasks; if a member cannot be assigned a clear, deliverable-based card, they are not adding value to the project lifecycle.
Supriya, I appreciate the emphasis on including members who actually execute the process daily. Ensuring that subject matter experts are at the center of the DMAIC phases seems like a vital strategy.