WEEK 27 · FORWARD MOVES

Write your next 90-day commitment in one sentence.

The fundamentals didn't change. The blast radius did.

Submitted by Neil Watkins · MondayMove

Every security team is running the same conversation right now. What did we accomplish in the first half, and what gets the focus for Q3. Most of those conversations end with a slide deck and no written commitment. This one ends with a sentence.

The mid-year review is one of the most reliable rituals in security work. Teams pull together metrics, review the roadmap, tally up what shipped and what slipped. It is thorough, sometimes useful, and almost always ends the same way: a room full of people who agree on what matters, followed by a week where everyone goes back to what they were already doing.

The problem is not the review. The problem is what happens at the end of it. A review without a written commitment is just a conversation. Conversations fade. The written sentence does not.

Security programs improve when someone names the one thing, writes it down, and makes it visible to the team. Not a roadmap. Not a prioritized backlog. One sentence. The kind that fits in an email subject line or a Slack message and still means something three weeks later when the next alert queue blows up and everyone forgets what quarter it is.

Six weeks of MondayMove practice gave practitioners six concrete reference points. Six moments where the team touched something real. A privileged group. A detection rule. An AI agent's log schema. A control environment assessed against what was already running. That is enough to look back and ask which of those actually moved the needle.

Most mid-year reflections are backward-looking by design. What did we accomplish? What did we miss? How do we explain the delta to leadership? Those are useful questions, but they answer the wrong one. The question worth asking at the midpoint is a different one. Given what we now know, what is the one thing Q3 needs to get right?

The fundamentals did not change in the first half. The blast radius did. AI expanded the scope of what can go wrong when the basics are missing. An orphaned account, an unlogged agent, a privileged group nobody audited. Each of those was a manageable risk two years ago. Today each one is a wider door. The commitment to Q3 should start from that reality, not from last quarter's metrics.

So, here's the MondayMove

Look back at the past six weeks. Find the one move that changed how your team thinks or surfaced a gap nobody was looking for. Write the next 90-day commitment those six weeks point toward, in one sentence. Send it to your team before noon.

One sentence, sent before lunch. That is how Q3 starts with something to point at.

Friday Follow-Up

The Sentence You Wrote and Didn't Send

Writing it was manageable. Sending it was the move.

Submitted by Neil Watkins · MondayMove

July 3, 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.

This week's move was the simplest one yet and, for a lot of practitioners, the hardest. Write your 90-day security commitment in one sentence and send it to the team before noon.

The constraint turned out to be the whole exercise. Most practitioners who tried this wrote a paragraph first. Cutting it to one sentence required deciding what actually mattered, which is the point, but also the place where most people got stuck. Not because they didn't know their priorities. Because knowing your priorities and choosing between them are two different things.

A few people reported that picking the one move from the past six weeks that mattered most was harder than the writing itself. If you ran all six weeks, choosing one felt like dismissing the others. If you skipped some, honestly naming the one you avoided was more useful than naming one you ran. That honesty gap is worth sitting with. The move you skipped is often the one that tells you something.

The friction with real teeth was the sending. Writing the sentence was manageable. Putting it in the team channel or the Monday morning email made it real in a way that holding it in a draft didn't. Several practitioners wrote the sentence and sat on it. That gap between written and sent is where commitment becomes accountability. If you drafted it and haven't sent it, that is the move. Send it now.

The new arc starts Monday. Before you run next week's move, pull up the sentence you wrote and read it once. Ask whether this Monday's action serves the commitment or competes with it. If the answer is competes, that is useful information about whether the commitment is actually the priority or whether it is already becoming a document.

One sentence, one filter. That is how a 90-day commitment stays load-bearing instead of decorative.

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