Two hundred dominoes, one Y-shaped target, and repeated timed runs gave a 2017 training group a visible way to test change. In the solo Constructrr episode that followed, Brittanie Campbell-Turner explained what the Improvement Kata exercise taught her about measurement, focus, coaching, and operator input.
The useful lesson was not the domino pattern itself. It was the routine described in the episode: measure the current condition, choose one obstacle, test one change, and learn before moving on.
Improvement starts with what the work is doing now
A simple lesson in the episode was this: if the team cannot describe the current condition, it cannot honestly say whether it improved anything.
That sounds obvious, but it is where many improvement efforts wobble. A group feels friction, jumps to ideas, and starts moving pieces around before it has a baseline. The meeting sounds productive because people are engaged. The work still stays vague because no one can say what the original condition actually was.
In the training exercise described in the episode, the group had a visible target for speed and quality. That made each change easier to judge. The point was not the dominoes. The point was that learning becomes more honest when the team can compare expected and actual results against a known starting point.
One obstacle is enough for one cycle
Another lesson in the episode was focus. The coaching questions narrow attention to the obstacle being addressed now, not every obstacle that might matter eventually.
That matters because improvement work can become a form of drift. The team names several causes and competing fixes, then leaves with no clear test. A narrower cycle gives the team one obstacle and one action to measure, which makes the comparison easier to see.
The method does not deny complexity. It gives the team a defined comparison: one obstacle, one experiment, and one review point.
A coach helps the team think, not just comply
The episode also spent time on the role of the coach. A coach is not there only to hand over the right answer. The better use of the role is to help the learner see what is happening, what is missing, and what should be tested next.
That distinction matters in construction because experienced people are often under pressure to decide quickly. Speed has value. So does building a team that can recognize problems without waiting for a more senior person to rescue the moment.
A question-based coaching rhythm helps with that. What is the target condition? What is happening now? One coaching question asks what obstacle the team is working on next. Another asks when the team will review what happened. Those questions slow the impulse to guess and strengthen the habit of learning from the work itself.
The people doing the work have to shape the answer
The episode also showed that a coach-learner exchange can still miss something important if it never brings in the people doing the work. The learner may summarize the process. The operators still know where interference, confusion, or wasted motion actually shows up.
In that 2017 episode, I described operator feedback as a key training takeaway. I said, “You really do have to ask and collaborate.” The people closest to the work can help identify what is getting in the way and whether the test changed the measured condition.
Start with one recurring task the team wants to improve. Before the next review, write down the current condition in plain language, select one obstacle, and ask the people doing the work what they would measure. Run one small test, record the result, and let that comparison determine the next question.
The next improvement decision should come from what the team observed, not from how energetic the discussion felt.
