executive support for founders and CEOs
An executive operating system for a growing business
Connect priorities, decisions, meetings and accountability without importing heavy corporate machinery.
Create one executive agenda
Translate strategy and immediate pressure into a small set of outcomes, decisions and risks requiring leadership attention. This matters because executive operating system decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Items enter the agenda because they require executive work, not because a function wants visibility. Record the choice, the evidence still required and the person who will return with it. Keep the mechanism proportionate: the purpose is better judgement and follow-through, not additional ceremony.
Give every forum a job
Define the decisions, inputs, participants, frequency and expected outputs for leadership, performance and delivery meetings. This matters because executive operating system decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Remove or redesign meetings that mainly repeat information available elsewhere. Record the choice, the evidence still required and the person who will return with it. Bring specialist judgement into the decision where required while retaining business ownership of the outcome.
Clarify decision rights
State who recommends, decides, contributes, executes and must be informed for recurring and consequential choices. This matters because executive operating system decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Escalation should resolve genuine uncertainty rather than compensate for unclear authority. Record the choice, the evidence still required and the person who will return with it. Keep the mechanism proportionate: the purpose is better judgement and follow-through, not additional ceremony.
Connect measures to action
Use a limited set of outcome and leading measures with thresholds that trigger discussion, intervention or learning. This matters because executive operating system decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. A dashboard earns its place when it changes a decision or behaviour. Record the choice, the evidence still required and the person who will return with it. Bring specialist judgement into the decision where required while retaining business ownership of the outcome.
Hold critical initiatives together
Maintain a joined view of outcomes, owners, dependencies, decisions, evidence and risks across the few projects that matter most. This matters because executive operating system decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Executive grip should focus on removing constraints, not recreating project management at board level. Record the choice, the evidence still required and the person who will return with it. Keep the mechanism proportionate: the purpose is better judgement and follow-through, not additional ceremony.
Close the loop visibly
Record decisions, actions, owners and review dates in a system the team returns to without reconstruction. This matters because executive operating system decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Follow-through is a leadership mechanism, not an administrative afterthought. Record the choice, the evidence still required and the person who will return with it. Bring specialist judgement into the decision where required while retaining business ownership of the outcome.
What to carry into the work
- Items enter the agenda because they require executive work, not because a function wants visibility.
- Remove or redesign meetings that mainly repeat information available elsewhere.
- Escalation should resolve genuine uncertainty rather than compensate for unclear authority.
- A dashboard earns its place when it changes a decision or behaviour.