Field Notes_002 _Priority setting at CEO level: the Monday-morning framework

Field Notes — A permanent reference for the CEO who has read every priority framework and still finds the team working on too many things

There are at least a dozen well-known priority frameworks in circulation. Eisenhower's matrix. OKRs. RICE. OGSM. Hoshin Kanri. The 4DX disciplines of execution. ICE scoring. MoSCoW. Each gets adopted by an ambitious management team. Each gets quietly discarded eighteen months later. And the company's underlying prioritization problem - the team is working on too many things and none of them feel decisive - remains exactly where it was.

The reason these frameworks fail is not that any of them is wrong. They are all useful, applied seriously, at the right altitude. They fail because they assume something that the people leading the company have not yet done.

This is the second entry in the Field Notesseries. The first looked at why mid-market companies stall structurally between €5M and €20M. This one goes one layer up the stack: why the people running the company struggle to get the team aligned on what to actually do this week - and what the operational answer looks like. The piece is written for the audience that lives with the consequences - founders, owner-managers, CEOs, division heads, executive teams - anyone whose week is judged on what the company moved, not on what they personally did.

Why the frameworks fail

The frameworks are not the source of focus. They are the expression of it.

Every priority methodology, stripped of its branding, presupposes that someone in the leadership - typically a founder, owner-manager, or CEO - has already done the harder, lonelier work upstream. Defining what the company is trying to win. In which markets. On what terms. At the explicit cost of what else.

When the leadership has done that work, almost any framework will perform reasonably well. When the leadership has not done that work, no framework will compensate. The team will dutifully fill in the OKR template and end up with twelve "objectives," because twelve is what the unprioritised company actually contains. The Eisenhower matrix will get four quadrants of urgent-and-important, because no one at the top has decided which fires belong to whom.

A leadership team that has not done the upstream work cannot be saved by a framework downstream. The framework is the operational scaffolding for a decision that has already been made elsewhere.

The one concept underneath

Strip away the apparatus, and every priority framework reduces to a single operational principle: focus is a function of conviction in the growth vectors and discipline in saying no to everything else.

Conviction is built by doing the analysis once, properly. Honest segmentation of the market. A real reading of where the company has structural advantage and where it does not. Margin profiles that survive a downturn. Customer types that fund the next stage rather than fund the current quarter. The realistic shape of the next eighteen months - not the optimistic shape, the realistic one. From that analysis falls a small set of growth vectors - usually three to five - that the company will commit to.

Discipline is the ongoing work of declining adjacent opportunities that look individually rational but together dilute the structure. A new geography that a customer is asking for. A new product line that an employee is excited about. A new channel that a competitor has just announced. Each one looks reasonable in isolation. Each one, if accepted, taxes the structure faster than the structure can adapt.

Iteration is not the enemy of focus. The vectors get refined as evidence accumulates. The growth vectors are not the destination; they are the tracks. But the tracks change rarely - quarterly at the strategic level, annually at the structural level - not weekly because a customer asked for something off-vector. A growth vector that is rewritten every month is not a vector. It is a wish list.

The signal-to-noise problem

The defining condition of running a modern company is not strategic uncertainty. It is informational saturation.

Every operator runs in a VUCA environment - volatile, uncertain, complex, ambiguous. New customer demands, new technology cycles, new geopolitical events, new competitor moves, new internal data dashboards, new internal frustrations, new external opportunities. The volume of signal-shaped noise is permanently higher than any leadership team's attention budget. There is no future state in which there will be less of it.

The skill the modern leader most needs is not strategy generation. It is signal extraction.

What separates the visionaries that get cited in business books - Steve Jobs, Elon Musk, in an earlier generation Andy Grove - is not their idea-generation rate. Looked at honestly, their hit rate on individual ideas is similar to that of competitors. What is different is their editing discipline. The willingness to look at twelve possible directions and say: this one. Not the other eleven. Not even the second-best one. This one.

Steve Jobs put it in the simplest available form: focus is about saying no. The hardest no is not no to a bad idea. The hardest no is no to a good idea that does not fit the vector.

That editing discipline is what most owner-managers and founder-CEOs underdevelop. They are good at seeing opportunities - that is often how they got to mid-market scale in the first place. They are weaker at refusing them, because refusing was never the muscle that built the early-stage business.

The dual lens — the bridge and the engine room

One of my mentors put it in a single line that I have not been able to improve on: you have to run the company from the bridge and from the engine room at the same time.

The bridge sets the heading. The engine room makes the ship move. Either one without the other is half a vessel.

The leader who only stands on the bridge - vision, strategy, narrative - drifts from execution. The team executes things that are not aligned with the heading because the heading is not specific enough to translate into next week's calendar. The vision sounds inspiring at the all-hands and produces nothing observable on Wednesday afternoon.

The leader who only stays in the engine room - operational fires, customer escalations, supplier issues - loses altitude. The company optimises locally, the most senior person in the building becomes the most senior firefighter in the building, and the company stops moving in any defined direction. Each fire gets put out. The fires multiply faster than they get extinguished.

Drucker's formulation captures the failure mode exactly: there is nothing so useless as doing efficiently that which should not be done at all. Operational excellence on the wrong work is not a smaller version of the right work. It is a category-different mistake - wasted execution capacity that the company will not get back.

The bridge and the engine room is the forcing function. The leader has to demand of themselves, every week, two things at once: look at every operational decision through the lens of where it takes the company at altitude - and look at every strategic statement through the lens of what specifically changes Monday morning. One without the other is half a job. Most leaders are stronger at one of the two and unconsciously avoid the other. The work is to deliberately strengthen the weaker side.

The Monday-morning framework

What follows is not a fifth-or-sixth priority framework competing with the ones above. It is the operational expression of the dual lens, refined over eighteen months in the operator chair.

Three priorities for the week. Each Monday, the management team aligns on three priorities for the next five working days. Not ten. Three. They are stated as outcomes, not as activities. "Sign the new distribution contract with ...." is a priority. "Work on the contract" is not. A priority that cannot be named in a single sentence has not been thought through yet.

Three initiatives for the quarter. Each quarter-start, the management team commits to three initiatives that move the growth vectors. Not twelve. Three. Anything not aligned to a growth vector is either dropped explicitly or moved to a parking lot with a date attached. The parking lot is real - items can come back when their conditions are met -but it is not a hiding place for ideas the team is reluctant to kill.

The no-list, named. The single most important output of the Monday session is not what gets prioritised. It is what gets deprioritised - visibly, on the record, with the team's understanding. Items go on the no-list with a one-line reason. If the CEO does not own the no-list, every team member ends up working on a different version of yes, and the company gets dilution disguised as alignment.

Review against the agreed list, not against new arrivals. Drift is the enemy. Mid-week additions to the priority list are signals that the upstream work was incomplete or that the environment has changed materially. Both are worth paying attention to - but the default response to a mid-week addition is parked, reviewed Monday, not escalated, replaces a priority.

Outcomes are reviewed; activities are not. The CEO does not pre-approve activity. The CEO reviews whether the named outcomes were achieved by the named owner. A missed outcome opens a structural conversation: was the goal mis-set, was the owner under-resourced, or was the focus wrong? An achieved outcome closes the loop and frees the slot for the next priority.

This framework does not invent anything. It enforces, week after week, what the famous frameworks all assume.

The Sunday-afternoon habit

The framework lives or dies on a single habit upstream of it.

My week does not start on Monday morning. It starts on Sunday afternoon.

Two hours, roughly. A notebook. One strong coffee. The work has three parts.

The first is review. What did I actually do this week? Which growth vectors did the activity align to? Which ones moved as a result? Which ones did I tell myself I was working on, but the calendar shows I in fact ignored? The honest answer is almost always more uncomfortable than the optimistic answer. The reason this exercise works is that, by Sunday, the calendar is settled - there is no negotiation left, only data.

The second is scanning for what I am overlooking. The signal-to-noise problem is not solved by working faster through the inputs. It is solved by deliberately scanning for signals that did not arrive in the inbox. The risk that has not yet become a fire. The opportunity that has not yet become a request. The team conversation that needs to happen before someone resigns. The customer relationship that has been quiet for too long. This scan is the most important thirty minutes of my week. The work is mostly

The third is naming three priorities for the week to come. Three. They go in writing, in the same place every week, and they map either to the company's growth vectors or to the no-list. If a candidate priority does not pass that test, it does not survive Sunday afternoon - and therefore does not get to consume Monday morning.

There is a structural reason this work happens on Sunday and not on Monday. By Monday morning, the inbox already wins. Reactive mode starts the moment the laptop opens. The Sunday version of me has the altitude to set priorities that the Monday version of me will protect. Without the Sunday session, the Monday version is alone with the operational gravity, and the operational gravity is undefeated against the unprepared CEO.

This is sometimes called Sunday blues. Most CEOs experience the slow descent into Monday as a mood problem. I have come to think of it as a structural problem with a structural solution. The two hours upstream of Monday are the cheapest, highest-leverage two hours in the operator's week. I do not skip them.

The harder discipline

Priority setting at CEO level is not a tooling problem. It is a discipline problem dressed up as a tooling problem. The frameworks all work, in the sense that any of them, applied seriously, would do most of what the team needs.

What none of the frameworks can do - and what the framework above does not pretend to do either - is the upstream work. Define the growth vectors. Refuse the adjacent opportunities. Hold the dual lens. Protect the Sunday session against the inbox.

That work is unaccompanied. It is not delegable. It is also the work that compounds - the only work, week over week, that actually moves the ceiling.

Ruben Claessens is CEO of an industrial group in Belgium and founder of LIDI Partners BV. Field Notes is the public archive of his work on operatorship, governance, and Belgian mid-market reality.

— Brussels, May 2026