Standard work is one of the first things a Lean leader teaches every other department: document the current best way to do a task, train to it, and only change it deliberately when you've found something better. Ask most CI teams whether their own template library follows that rule, and you'll get a long pause.

It's a common pattern. Someone in Manufacturing builds an A3 template. Six months later someone in Quality wants something similar, but instead of using the existing one, they build their own version with slightly different fields, because they didn't know the first one existed, or didn't like a field name, or just didn't want to ask. A year in, you've got four templates that all do roughly the same job with no consistency between them. That's template sprawl, and it's waste in exactly the sense Lean means it: duplicated effort, inconsistent data, and no way to compare results across teams because nobody's filling out the same fields.

Treat your template library like a value stream

The fix is the same one you'd recommend to any team with an undocumented process: build a small, standard library and govern it.

That doesn't mean one template for everything. It means a deliberate set, Just Do It, A3, DMAIC, whatever combination matches your organization's actual improvement methods, with a clear owner for each. When someone wants a new template, the question isn't "can I build one," it's "does an existing one already cover this, and if not, who approves a new addition to the standard set." That single gate is usually enough to stop sprawl before it starts.

Embed the coaching, don't just document it

Standard work isn't just about consistency, it's about capturing the current best way of thinking through a problem so it doesn't live only in one person's head. KaiNexus lets you build that directly into a template using ghost text and tooltips, field by field.

This is a bigger lever than it sounds like. Instead of a blank field labeled "Problem Description," you can label it "Define the Gap" and add a tooltip that walks a first-time user through what that actually means, the same coaching a mentor would give them in person. That turns the template itself into a teaching tool, which matters a lot for organizations with high turnover on the front line or teams that are new to structured problem-solving. You're not relying on everyone remembering a training session from eight months ago.

Standardize the strategy layer too

The same governance question applies above the template level: how your Boards nest, and how Projects and Improvements roll up into your strategic goals. If every location builds its own Board hierarchy from scratch, you lose the ability to compare across the organization, which defeats a big part of why you deployed Hoshin Kanri in the first place. Full detail on structuring Projects, Improvements, Attributes, and Boards consistently for strategy deployment is in How to configure KaiNexus for Hoshin Kanri.

The audit question

If you're not sure where you stand, ask this: could a new employee or a new CI leader look at your template library today and tell which templates are the current standard versus which ones are case specific or custom built for a different location? If the answer is no, you don't have standard work, you have a pile of templates that happen to be digital.

Next up: Flow, and the four places work actually gets stuck inside KaiNexus.