Kanban for the Crew

Kanban for the Crew: Taking a Proven Office Tool Down to the Zone

Here’s the deal. Most people who have heard of Kanban or Scrum boards think of them as an office tool, something the project manager and project engineer use to track submittals and paperwork. That is true, and it is also only half the story. The same board, the same logic, and the same discipline belongs at the crew level too, inside the actual zone where the work happens.

I want to walk through both halves of this, because understanding how they connect is what makes the whole system genuinely powerful instead of just two separate tools that happen to share a name.

The Office Version, Done Right

In the Takt production system, I recommend running a Kanban or Scrum board with four columns. Backlog, meaning everything that eventually needs to get done. Sprint backlog, meaning the specific slice of that backlog you intend to work on in the current period, usually a week. In progress. And done.

Each item on the board lives on its own sticky, and that sticky carries two important pieces of information. A Fibonacci number representing the level of effort the task actually requires, and a clear description that includes a genuine definition of done. That definition of done matters more than people realize. It removes ambiguity about what the finished product actually looks like, so anyone glancing at that sticky, not just the person who wrote it, understands exactly what is expected before it can move to the done column.

This board belongs somewhere specific, in the trailer, near the project managers and project engineers, where it becomes part of the actual daily rhythm rather than a static display nobody interacts with. It ties directly into the meeting cycle the rest of the project runs on, from team meetings and strategic planning through the trade partner weekly tactical, the afternoon foreman huddle, the morning worker huddle, and crew preparation. The project delivery team itself should be standing up for five to fifteen minutes a day specifically to clear the way, meaning removing whatever is blocking the field from moving forward.

Why the Office Always Aligns to the Field

Here is the principle that keeps this whole system honest. If a project engineer is working on one submittal and the field signals that a different submittal has become more urgent, the order of the stickies changes to match what the field actually needs. The office is not a separate team working on its own priorities. It is the same team, in a different geographic location, supporting the work happening in the zones.

Watch for these signs your office Kanban board has drifted away from this principle:

• Sticky priority order that has not changed in weeks despite the field’s actual needs shifting
• A board that exists but is not connected to the daily huddle and meeting cycle
• Stickies without a genuine definition of done, leaving room for disagreement about whether something is actually finished

That alignment, office serving field rather than field waiting on office, is the whole reason this tool works. A board that does not move when field priorities move is just decoration.

The Idea That Changed How I See Kanban

Here is something that genuinely shifted my thinking recently, and I want to give credit where it belongs. Hal Macomber challenged me to dig deeper into Kanban, and in doing that research, something clicked that I had not fully connected before.

A lot of contractors genuinely want visibility inside the installation work package itself, within a specific zone, within a specific Takt time, down to the detailed steps a crew actually needs to complete, sometimes down to the hour or even the minute. That level of granularity is exactly what a Kanban board can provide, and it does not have to live only at the office level. It can live at the crew level too.

What Crew Level Kanban Actually Looks Like

The format can flex to whatever fits the crew, electronic, physical stickies, a simple written list, or dedicated software. What matters is not the medium. What matters is that the crew has a clear, shared view of what falls into backlog, what is currently in progress, and what is genuinely done, with items moving from left to right as work actually happens.

Add a target time to each item, and the board becomes something more than a to-do list. It becomes a real production tool, giving the crew a shared, visible sense of pace inside their own zone and Takt time, the same way the office board gives project managers a shared, visible sense of pace across the whole project. A crew working from a board like this can see at a glance whether they are ahead, on pace, or falling behind on the specific steps inside their own scope, rather than only finding out at the end of the day whether the zone finished on time.

This is also where the concept genuinely earns its place next to the standing tactical order about stopping, calling, and resolving problems at the source. A crew watching its own board in real time notices a slipping pace long before a superintendent would catch it during a walk through, which means the roadblock behind that slip gets identified and raised while it is still small and cheap to fix.

Why This Matters Beyond Just Visibility

None of this is really about the board itself. It is about giving every level of a project, from the project engineer in the trailer to the crew standing in a zone, the same basic tool for seeing their own work clearly and moving it forward with intention instead of guessing.

A crew with a genuine backlog, in progress, and done structure, with clear definitions of done for each step, does not need to ask a superintendent every hour what comes next. The board already answers that. And a crew that can see its own pace against a target time can raise a problem early, the moment they notice they are falling behind, rather than discovering it only when the whole zone is already late. That is exactly the kind of early visibility that turns a roadblock into a quick fix instead of a schedule crisis.

There is also a real ownership benefit here that is easy to overlook. A crew moving its own stickies from backlog to in progress to done is actively tracking its own performance, rather than waiting to be told how the day went. That shift, from being measured by someone else to measuring your own progress in real time, tends to change how a crew relates to the work itself.

Bringing This Into Your Own Project

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build both levels of this system, the office Kanban board tied into your daily meeting cycle, and a crew level version that gives your zones the same visibility down to the hour or the step. Getting both levels working together, and genuinely aligned so the office always serves the field, is what turns this from a nice idea into a real production tool.

So here is the challenge. If your project already runs an office level Kanban board, ask whether it is genuinely tied into your daily huddle cycle and whether its priority order actually shifts when the field’s needs shift. If it does not have a crew level version yet, pick one zone this week and try it, even with something as simple as three columns and a stack of stickies, and see what changes when the crew can see their own progress clearly.

Jason Schroeder said it plainly: “We always align the office to the field.” Build both boards around that principle, and the whole system stays honest.

On we go.

FAQ

What is the difference between the office level Kanban board and a crew level one?
The office level board typically tracks larger items like submittals, procurement, and coordination tasks managed by project managers and project engineers, usually on a weekly sprint cadence. A crew level board tracks the detailed steps inside a specific installation work package, zone, and Takt time, sometimes down to the hour or the minute. Both use the same backlog, in progress, and done structure, just at different levels of granularity.

Why does the definition of done matter so much on a Kanban sticky?
Because without it, different people can interpret when a task is actually finished differently, which creates disputes and inconsistency about what counts as complete. A clear definition of done removes that ambiguity, so anyone looking at the sticky, not just the person who created it, understands exactly what the finished result needs to look like before it moves to the done column.

How do you decide the right target time for a crew level Kanban item?
Target times should reflect a realistic estimate of how long a specific step actually takes within the crew’s Takt time and the zone’s overall pace, rather than an arbitrary number. Basing it on genuine production data, similar to how zone sizes and cycle times get calculated in a pull plan, keeps the board an honest reflection of pace rather than a source of false pressure.