If you lead continuous improvement, you spend your days coaching other teams through Lean thinking. Standardize the process. Make the work visible. Find the bottleneck. Respect people's time. Ask most CI leaders when they last pointed that same discipline at their own CI program, whatever it happens to run on, and you'll get a long pause.
We ran a series on exactly that question, written with KaiNexus customers in mind. None of it requires KaiNexus. Six of the ideas apply just as well to a whiteboard in a hallway, a shared Excel workbook, or a laminated form on a wall, and every one of them is something you can check this week on whatever you're running on.
Here's the short version of each, with a question to actually go ask.
1. Configuration is a process, not a setup task
Every required field, every approval step, every form and board you create is a process decision, the same kind you'd scrutinize in someone else's workflow. Most of them get made once, under conditions that no longer exist, and never get revisited.
Ask this week: pick the newest required field or approval step in your process and find out what problem it was added to solve. If nobody remembers, that's your answer.
Why Your CI Platform Should Practice What It Preaches
2. Make it visible, not just available
A board someone glances at during a huddle should answer one question in three seconds: what needs attention right now. That's as true taped to a wall as it is on a screen. A Kanban board covered edge to edge in sticky notes stops working as a status display the same way a spreadsheet with forty columns does. Both need a squint and a few seconds of hunting before anyone can tell what's on fire. Software just makes it easier to cram in more than a whiteboard ever could.
Ask this week: hand your primary board to someone who's never seen it and time how long it takes them to tell you what needs attention. If the fix feels like adding a legend, the real fix is subtraction.
Visual Management: Make the Work Visible, Not Just Available
3. Six versions of the same A3, half of them outdated
Template sprawl happens the way any other waste does. Someone builds a new form instead of reusing what exists, because they didn't know it existed or wanted it a little different. On a shared drive that's six versions. On paper it's the laminated template one team has that nobody else in the building knows about.
Ask this week: could a new hire look at your forms and tell which one is the current standard? Ask one.
Standard Work for Configuration
4. Find out where the pipeline is actually stuck
Work stalls in four predictable places: ideas that sit unassigned, work that goes overdue and stays that way, progress that goes quiet without closing out, and results waiting on an approval nobody's chasing. Each erodes trust a little differently. On a huddle board, it's a card that hasn't moved in three weeks and nobody's asked why. In a spreadsheet, it's a status column where half the rows have said "In Progress" since Q1. The tool doesn't create the bottleneck. It decides whether anyone notices before it becomes normal.
Ask this week: find your oldest open item and figure out which of those four things happened to it. Then find out whether anyone had noticed.
Flow: What's Actually Stalling Your Improvement Pipeline
5. The no-delete rule
Deleting an idea that didn't pan out feels like tidying up. It erases the one piece of evidence that someone engaged with a real problem, and it tells them their input wasn't worth a response. A cleared spreadsheet row and a tossed index card send the same message.
Ask this week: how many ideas from the last quarter got closed with an actual explanation the submitter could read?
Respect for People: The No-Delete Rule and the Notification You Didn't Need
6. Audit your own system the way you audit theirs
Participation data is a diagnostic, not a scoreboard. Low engagement from one team isn't automatically a people problem. It might mean their workflow is heavier than everyone else's, or their form asks for more than they realistically have on hand when they're filling it out. Same goes for the form nobody's revised since 2019 and the workbook with twelve tabs where three get opened.
Ask this week: pull the team with the lowest participation and ask them what's in their way before you coach anybody on engagement.
If any of the above made you wince a little, that's not a criticism. It's the exact blind spot Lean leaders are trained to spot in everyone except themselves.
Already a KaiNexus customer? There's a seventh post in this series on what happens when some of this triage and first-pass coaching gets built into the platform itself: What Happens When the Coaching Habit Becomes Part of the Tool.
.svg)
Add a Comment