Between team leaders and the front office. Make or break every shift.
The group leader is the lean role that lives or dies on whether a coach can coach. The job is not to run a team. The job is to develop the people who run teams, run the cross-team huddle that catches problems falling between teams, and own a chunk of the value stream big enough to see patterns the team leaders cannot. Get this layer right and lean takes root. Get it wrong and the shop reverts to firefighting within a quarter.
"The team leader makes the shift. The group leader makes the team leader."
A group leader's day is built on a defined rhythm anchored by leader standard work. The standard work is not optional; it is what separates the role from a generic supervisor's role.
The day starts with the tier-two huddle, usually 15 to 20 minutes. Each team leader brings the two or three issues from yesterday's tier-one huddle that crossed team boundaries or could not be solved at the team level. The group leader's job is to triage: which issues stay with the team leader to keep working, which need cross-team coordination, and which need to escalate to the plant manager. This is part of the broader system of tiered meetings that connects the floor to the front office.
The mid-day work is gemba presence. The group leader walks each team for a defined window every day, usually 20 minutes per team. The walk is not an inspection. It is a coaching opportunity for the team leader: what is in your way, what is your team trying to fix, what do you need from me. This is where most of the group leader's value gets created.
The afternoon work is coaching cycles. The group leader picks one team leader and one problem and runs a coaching kata cycle: what is the target condition, what is the actual condition, what is in the way, what is the next experiment. This is the slow, deliberate work that develops the team leaders over months. Skip it and the team leaders never grow past where they started.
Across all three, the group leader owns the value stream's daily metrics, the recurring problems, and the development of two to five team leaders.
Imagine a 50-person contract assembly shop with three cells: kit prep, sub-assembly, and final test. Each cell has a team leader. Above them, the shop owner has historically run the whole floor herself. As the shop grew past 40 people, the owner could not coach all three team leaders, run the huddles, and still do strategy and customer work.
The shop creates a group leader position. The first hire is one of the senior team leaders, promoted with explicit training in coaching kata and tier-meeting facilitation. His leader standard work: 7:30 tier-two huddle, 8:00 to 8:20 walk kit prep with the team leader, 8:20 to 8:40 walk sub-assembly, 8:40 to 9:00 walk final test, 2:00 coaching cycle with one team leader, 4:00 close-out and prep for tomorrow's huddle.
Within three months the owner has bandwidth back for strategy. The team leaders have grown noticeably because someone is coaching them every day. The cross-cell issues that used to fester for a week now surface in the tier-two huddle the morning after they appear. That is what the group-leader layer is for.
The group leader sits above the lean team leader and inside the broader category of front-line leadership. The role's daily rhythm is held together by leader standard work, and its primary forum is the tier-two layer of the tiered meetings cascade. Together these four define the layered leadership system that keeps lean working in shops too large for one person to run alone.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.
.svg)
.svg)
%201.svg){kind=logo}
.png)
.svg)
.svg)
