Start with a picture of the current business
Before setting objectives, gather information about the offer, customers, acquisition, delivery and available resources. Understand what sustains the business and what limits its next step. The diagnosis should distinguish facts, estimates and assumptions, so that the plan does not treat every statement with the same degree of certainty when choices need to be made.
You can organise that picture on one page: what you sell, to whom, how enquiries arrive, how you deliver and who performs the work. Add existing commitments and recurring difficulties. The description should show how the business operates, including work that depends on one person or on information scattered across several places.
When data is missing, identify the decision that the gap prevents you from making. You do not need to measure everything before starting, but you should recognise decisions based on limited observation. Customer conversations, proposal examples and project records may clarify questions that a monthly revenue total leaves unanswered about the way the business works.
Choose an outcome that guides decisions
An objective should describe the change you want in the business and the period over which you will observe it. Connect that change to the identified difficulty and existing resources. The wording should support choices: when two initiatives compete, the team should be able to discuss which contributes more directly to the intended outcome and why.
“Improve the business” gives no operational direction. Reducing project delays, improving the suitability of enquiries or strengthening customer continuity are more specific examples. The actual objective should come from your context and an initial reference point, so that you can later establish whether something changed as a result of the work undertaken.
Avoid combining outcomes that require conflicting decisions without discussing priority. Increasing variety, reducing complexity and accelerating delivery may compete for the same resources. Strategic discussion involves choosing an order and accepting the consequences. A plan becomes clearer when it explains what will take precedence when the team faces that difficult choice in practice.
Set priorities and accept what must wait
Priorities should reflect expected impact, effort, dependencies and execution capacity. Choose a set the team can undertake without ignoring existing commitments. Record what will be postponed and why, because a strategic decision includes protecting attention and resources for the work selected, rather than simply adding more items to an already demanding operational workload.
One initiative may depend on another: launching a new offer might require clarifying delivery or preparing someone to support it. If that dependency is absent from the plan, the team begins tasks that later become blocked. Organising the sequence helps establish what needs to be resolved before the next stage of work can begin.
I value questions that could change a decision before too much effort is invested in execution. An available tool or attractive opportunity does not require opening another workstream. The digital business models guide helps compare alternatives when the choice involves changing how the company creates and delivers value to the people it serves.
Turn the priority into an executable initiative
An initiative needs an owner, an expected outcome and a first step clear enough to begin. Define the information required, people involved and decisions needing approval. This framework makes it possible to follow the work without turning the plan into an extensive list of tasks disconnected from the objective that justified undertaking them.
Instead of writing only “improve sales”, you could organise a review of the journey from enquiry to proposal. The work includes collecting examples, identifying recurring questions and trying a change. This is an illustrative example. Your chosen initiative should address the difficulty revealed by the diagnosis and fit the capacity actually available in the business.
The owner follows progress and signals blockages; that does not mean performing everything alone. Others may provide information, approve changes or carry out tasks. Writing down these relationships prevents dependence on implicit expectations. Clarity about the final decision is particularly important when several functions participate in the same work and need to coordinate their contributions.
Use a simple board to follow the plan
A tracking board should show the connection between the objective, initiative, owner and evidence of progress. Keep only information that helps decisions. Updating it should be simple enough to continue during normal operations, including when delays occur or results differ from the initial expectation and the team needs to discuss what to do next.
Use the structure below as a starting point and adapt its fields to the company. The example organises the conversation without prescribing a tool or meeting frequency. What matters is being able to understand what changed and which decision is needed to continue the work with clarity about responsibilities and the intended outcome.
| Field | What to record |
|---|---|
| Difficulty | Observed situation and available examples |
| Objective | Desired change and initial reference point |
| Initiative | Work chosen to contribute to that change |
| Owner | Person following progress and blockages |
| Evidence | Information used to assess the effect |
| Next decision | Continue, adjust, gather data or stop |
Review the plan without changing everything at each signal
Review should compare what happened with the initial expectation and the conditions of the period. Examine whether enough work was completed, whether the hypothesis made sense and whether new information emerged. Adjusting the plan requires an identifiable reason, avoiding both persistence from habit and abandoning an initiative before understanding what the experience actually showed.
A week with few enquiries may have different causes from a continuing acquisition difficulty. A delay may reflect an unforeseen dependency rather than insufficient effort. Recording context helps separate those situations and choose between correcting execution, changing the initiative or reconsidering the objective itself based on the information now available to the team.
When a decision changes, record the reason and what you learned. That record helps the team understand the change without repeating the entire discussion. AI for business owners can support information organisation, but conclusions need to be checked against the data and the knowledge of people who follow the operation in practice.
Connect planning with how you work
The plan needs to fit the team's actual availability and connect with everyday decisions. Review commitments, capacity and responsibilities before adding initiatives. Strategy becomes useful when it helps accept, decline or sequence work, maintaining a clear relationship between the chosen direction and what is being executed by the people responsible for moving the business forward.
If the founder still approves every detail, implementation may depend more on their diary than on the quality of the plan. The delegation and processes guide explores that organisation. The aim is to give the team context and criteria for action while retaining approval at the points where it is necessary for the business.
To discuss priorities, use the individual mentoring form. Present the current situation, main difficulty and alternatives under consideration. That preparation makes it possible to work on a concrete decision and identify which information or execution is missing before it can become a plan you can follow and use in your business.