WEEK 36 · GOVERNANCE

Say your entire program out loud, start to finish, and mark every sentence that will not close.

You can read your own program on the page and it holds together fine. Say it out loud and you hear the places where it does not.

Submitted by Neil Watkins · MondayMove

May 15, 2026

It's that time of year when you get to defend your program.

You show how your practitioners improved the fabric of capabilities, and you do it without pointing out the flaws or the weakness you knew it had. We speak in risk reduction. Maturity, not gaps. That's the genre, everybody in the room understands the genre, and there is nothing dishonest about any of it.

The part worth talking about happened before that. I spent all week defending my program in my head, before the questions started.

That week matters more than the meeting does. I can make better questions than anyone else, because I know my program. Give me an hour with it and I will build the question that lands on the thing I already know is soft.

Nobody else can. The questions that come back to you grow out of a framework or last quarter's incident, which is why they keep landing in the places where you already have an answer ready.

Most of us treat preparation as rehearsal, assembling the narrative and running the delivery until it lands clean. Preparation is the hard truth exercise, and it's the only audit your program gets where the auditor already knows where the soft spots are.

The exercise runs in a different language than the meeting does. There you speak risk reduction and maturity. The exercise has to speak gaps, out loud, to yourself, or the meeting turns into the place where you learn about them.

Here are the three I built this week. How strong is your program defined, in writing, to show completeness? Does every part of the fabric have a clearly assigned owner, and are those owners aware of their ownership? Can you describe, in clear methods, the maturity of each part, and when looked at in totality, do those parts complete the fabric needed to address the risks?

Watch where your answers go. If the answer is a product name, you have not answered. A tool sitting in the environment with a default policy and nobody behind it covers exactly nothing, and the coverage map still counts it green anyway, year after year.

The answer that holds names a person, the signal that reaches them, and what they do next. Not by describing the tools, by showing how practitioners operate against risk. That version invites a follow-up question, and a follow-up is the only real evidence you were believed.

One more thing, and it is the part I did not expect. Writing it down gets you partway. Saying it out loud finds the rest, and the distance between those two is much larger than it has any right to be. Your ear notices what your eye forgives.

So, here's the MondayMove

Say your entire program out loud, start to finish, with nobody in the room. Begin at a risk you carry, talk your way through to the practitioner who acts on it, and mark every sentence your voice will not finish.

It will show you the places your program is weak before somebody else finds it for you.

Friday Follow-Up

Where I expect this one to break.

Nobody has run this one and reported back yet, so here is the honest version: the five places I expect it to come apart, called in advance.

Submitted by Neil Watkins · MondayMove

September 4, 2026

MondayMove gives you one concrete action every Monday. FridayFollowUp closes the loop.

Each Friday, a short dispatch on what practitioners actually found when they ran the week's move: where they got stuck, what surprised them, and what to do next. Not sanitized case studies. Field notes. Practitioner to practitioner.

Monday asked you to say your entire program out loud, start to finish, with nobody in the room, and to mark every sentence your voice would not finish.

Nobody has reported back yet. So here is the honest version instead. These are the places I expect this move to break, called in advance, and I would rather be wrong out loud than fill this space with responses that do not exist.

Most people will not actually say it. They will read it in their head, decide that counts, and get the same clean result they have been getting for years. Silent reading is the exact thing this move exists to defeat, and it is what your brain will offer you about thirty seconds after the door closes. If your mouth is not moving, you are not running the exercise.

The first two minutes will feel ridiculous. Talking through your own program to an empty room is not a thing anybody admits to doing, and there is no version of it that looks dignified from the hallway. Do it anyway. The feeling goes the moment the first sentence refuses to end, because at that point you have something.

I expect the maturity part to be where the voice stops. Most programs can produce a score for any capability you point at, and almost none can describe the method that produced the score. A rating nobody can explain out loud is a number somebody assigned in a workshop once, and it has been sitting in the sheet getting older ever since.

At least one sentence will end on a product name where a person belongs. That is the one you will not want to mark, because marking it turns it into a finding with your name on it. Mark it anyway.

One more, and this is the one worth watching. The account gets shorter every time you say it, and that is not always progress. A second pass drops the parts you could not defend rather than repairing them, so the smooth version on Thursday may just be the one with the hard parts sanded off. Keep your first list of marks.

Next week, take the sentence that would not finish and say it out loud to the practitioner who operates that part of the program. Do not send it to them. Say it, and ask them to finish it for you.

Whatever they say next is the thing you were missing.

Keep going. See what a week can do.

No correct answers here. This is practitioner-to-practitioner. The more honest the responses, the more useful this gets for everyone reading on Monday morning.

See you then.

Discussion