Standing Tactical Orders

Standing Tactical Orders: Ten Defaults Your Field Team Can Follow When No Leader Is Around

Here’s the deal. Most jobsites run on the memory and mood of whoever happens to be standing there. When that person is good, the day goes well. When that person is in a meeting, at another site, or having a rough week, the crew guesses. Then we call the result a discipline problem.

It is not a discipline problem. It is a missing default. Standing tactical orders are how you fix that, and they are the part of field enablement most programs never write down.

When Nobody Is There to Ask

You know this one. A crew hits a zone that is not ready. The substrate is wrong, or the last trade left equipment in the way, and nobody with authority is nearby. So the crew does what a decade of pressure trained them to do. They work around it, install over it, and keep moving, because stopping feels like the punishable option. Or a foreman spots a problem at seven in the morning and says nothing, because on his last three projects surfacing one got him a lecture about attitude. It travels downstream and shows up in month nine as rework with three trades tangled in it.

None of that is bad character. That is what happens when the standard exists only inside a leader’s head. If the rule is not written, the rule is whoever is loudest.

Where the Idea Comes From

I first learned about standing tactical orders from historical references to General Patton. He is a controversial figure, and I am not asking anybody to admire him. I am pointing at a mechanic. His standing tactical orders were written down, and his units moved faster and operated more effectively than any other American formation of the period. Because they were written, the pattern outlived him and was copied for decades.

Written defaults are why. Not charisma, and not shouting. Written defaults let a unit see as a group, know as a group, and act as a group even when the commander is nowhere in sight. That is what a construction program needs, so we distilled ours down as a group into ten. These are safe to follow anywhere on the project, with or without a leader present.

The ten standing tactical orders:

• We build people before we build things
• We treat everyone like our customer
• Ensure your finished work never becomes a bottleneck for the next trade
• One team, one build
• We do not start until we are ready to finish, with full kit
• Planning and preparation should make installation the easiest thing we do
• If you see, hear, feel, or sense something wrong, stop, call, resolve
• Problems are not a problem, hiding problems is the only problem
• We blame the system, the process, or the behavior, not the people
• Total participation

Ten lines, every one of them decidable by a craft worker standing alone in a zone at six in the morning.

Build People Before You Build Things

Start with the first one, because the other nine depend on it. We build people before we build things, which means enabling four things before boots hit the ground: mindset, systems and processes, culture, and skills.

The mindset piece is a real switch. Classical business management puts profits first, control of people second, and protection of the internal leadership team third. It does not work, it hurts people, and it manufactures waste, and it is still the water our industry swims in. Lean management inverts the order. Our own people first, our clients second, the business third, with the firm condition that we make money, because we focus on people, process, and quality.

The systems and processes then have to enable that mindset, and the culture has to make it normal. Culture means the common beliefs and actions of a social group, so it is not a poster. It is what your crews do at ten in the morning when something goes wrong. The skills piece is the one people misread. You are already an expert at your trade, and nobody needs to fix you. What we owe you is a match: an expert paired with a system, a process, a culture, and an environment worthy of that expertise.

Do Not Be the Bottleneck, and Do Not Start Half Cocked

Orders two and three are about what you hand the next person. Our client is our customer, and so is the project delivery team, the vendors, the neighbors, the end users, and the successor trade. When you finish a zone, hand it off clean, safe, organized, punched out, and ready, with nothing of yours left behind.

If that sounds soft, here is the hard version. We cannot hurt other trades and win ourselves. The pace of another crew is the pace of my crew. Even from a pure bottom dollar view, their success is my success financially, so protecting the next crew is not sentiment. It is arithmetic. In Japan I learned the word for this. Meiwaku carries the idea of not being a burden on others, and you see it in the cities. Everyone stands on one side of the escalator. The streets stay clean even though public trash cans are rare.

There is a related point about real bottlenecks. If your trade genuinely is the constraint, everyone should give you first pick on the forklift, the crane, the hoist, and the flow of information. Not because you are more important, but because your pace is everybody’s pace and we subordinate to the constraint. To find the true constraint, we first have to make sure the bottleneck is never bad behavior.

Orders five and six handle the front end. We do not start until we are ready to finish, with full kit. Think of an IKEA box: clear instructions, nothing missing. Full kit means materials, equipment, tools, information, permissions, layout, safety and quality planning, the space itself, and the training. Nobody should be let into a zone before that is true, not as gatekeeping but as protection. Then the pattern is plan, build, finish.

That is why planning and preparation should make installation the easiest thing we do. If anything is going to be hard, let it be the design, precon, work packaging, prefab, logistics, pull planning, and foreman planning. We discomfort the project delivery team so we can comfort the workers. Not because craft workers need coddling, they are professionals, but because planning is where the money is made. When I was finishing concrete, the harder I visibly struggled, the more people liked me. That is backwards. Inside a worker’s strike zone, the question is whether the work is frictionless, because frictionless means the planners did their job.

Stop, Call, Resolve, and Never Blame the Person

Orders seven through nine change a culture fastest.

If you see, hear, feel, or sense something wrong, pause the work, call the team, and resolve it at the source. Stop, call, resolve. Toyota reportedly stops its line on the order of two thousand times a day. Somebody senses something off, they pull the andon, and the line does not restart until the issue is resolved. On our sites the signal can be a light, a call, or a field app. The mechanism matters less than the rule: we stop and resolve before we proceed, and we never push. Pushing always hurts a project. Then, problems are not a problem. Hiding problems is the only problem. Hidden problems become stops and restarts, rework, delay, and waste. Surfaced problems get solved at the root.

Order nine is where some people trip, so stay with me. We blame the system, the process, or the behavior, and never the person’s true self. A behavior can change, a culture can change, and a system can be rebuilt. Pinning a failure on a person ends the investigation where the learning should have started. Consider Alaska Airlines Flight 261. Investigators looking for who did it found a system: a jackscrew that failed on worn threads, a maintenance interval extended for financial reasons, a regulator that approved it, and mechanics who were not permitted to replace the part. Everybody came to work that day intending to do their best, and 88 people died in the Pacific. Nobody wakes up wanting to do a bad job. So we are hard on the process and easy on our people, and easy does not mean permissive. It means supported.

Total Participation Is the One That Carries the Rest

Order ten is the multiplier. See as a group, know as a group, act as a group.

In Japan a sensei asked me what one hundred minus one is. I said ninety nine. He said no, it is zero. If one person, one crew, or one step is not participating, you do not have a system at all. That is a hard standard, and the right one. Information gets shared, teams stay aligned, and standards get followed together. We do not do this well in the Western world, and we should, because we have outstanding people.

Signs your standing tactical orders are not live yet:

• Crews work around a not ready zone instead of stopping and calling
• Problems surface in schedule meetings weeks after somebody in the field first saw them
• Root cause conversations end with a name instead of a system

Why This Reaches Past the Jobsite

None of this is really about compliance. It is about what a jobsite does to a person over a career. A crew that can stop work without fear goes home with their fingers and their dignity. A foreman who can surface a problem at seven in the morning is not carrying it home at seven at night. A trade partner who gets a clean, kitted, ready zone finishes on Friday and makes his daughter’s game. Written defaults protect schedules and quality, and they protect families, which is the return nobody puts on a dashboard.

That is why these orders and Takt planning belong together. Takt gives you zones on a rhythm, so a clean handoff has a defined moment and a defined standard, and the standing tactical orders tell everyone how to behave inside that rhythm when no leader is watching. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Tools like LeanTakt make the flow visible, and written defaults keep people participating in it.

So here is the challenge for this week. Pick three of the ten, write them on the wall in the trailer, read them aloud in your next huddle, and hold them yourself first when it costs you something.

Taiichi Ohno said it plainly: “Having no problems is the biggest problem of all.” Write the defaults down. Let people use them.

On we go.

FAQ

Are standing tactical orders the same thing as a safety policy or a handbook?

No. A handbook describes procedure and lives in a binder. Standing tactical orders are short defaults a craft worker can act on alone in a zone without permission. They should be few enough to remember, blunt enough to apply under pressure, and consistent enough that following them never gets somebody in trouble.

How do I stop work without getting blamed for the delay?

That is the fear the eighth and ninth orders exist to remove, and leadership removes it by responding well the first several times somebody uses it. Stopping to resolve an issue at the source costs less than pushing through and discovering it later. If your organization punishes a stop, the stop is not the problem.

How does this connect to Takt planning?

Takt gives the project zones on a rhythm, which creates a defined handoff moment and a standard for what a completed zone looks like. The standing tactical orders govern behavior inside that structure. Rhythm without agreed behavior collapses, and good behavior without rhythm has nothing to protect.