A strategy can sound sensible in a meeting and still be difficult to carry out. The owner may not have approved the required time, the person doing the work may see an unresolved dependency, or two teams may be interpreting the same priority differently. These gaps often become visible only after somebody tries to act.
Brian Tracy’s Business Strategy argues that planning should involve the people who authorise the direction and the people who will implement it. It also emphasises focused discussion and outside perspective. For a small business, the practical task is to organise those contributions so that decisions have authority, delivery constraints are understood and the resulting work has clear ownership. The process below is an adaptation for that setting, with suggested meeting structures and an illustrative example.
Connect participation with the work ahead
Implementation is the work of turning an agreed direction into operating decisions, changed practices and observable results. A plan is easier to assess when the people who understand those steps can examine it before commitments become fixed.
Their contribution extends beyond enthusiasm. Someone who handles customer questions may know which promise causes confusion. Someone who schedules production may know that the proposed launch depends on information that arrives too late. Someone responsible for spending may identify an approval limit that the planning group has overlooked.
Participation also allows people to understand why a choice was made and which alternatives were considered. That understanding helps when they face an unexpected situation later. They can apply the intent of the plan rather than waiting for instructions about every exception.
However, attendance alone does not establish support or feasibility. People need a genuine opportunity to raise concerns, and the decision process must show how those concerns were considered. A meeting that asks for input after the route is already fixed should be described as an implementation briefing rather than an open strategy discussion.
Identify authority before inviting the group
Decision authority is the right to approve a choice and commit the resources needed to carry it out. In a small business this may sit with one owner, several co-owners or different people for different kinds of commitment. Identify the actual arrangement rather than assuming a senior title settles it.
Ask which decisions the session is expected to make. Choosing a trial, changing a customer promise and committing spending may require different approvals. The people attending need to know whether they are making the final decision, recommending an option or developing alternatives for later approval.
Tracy places particular weight on the participation of the person with ultimate responsibility. The useful principle is that the plan should not be developed in isolation from someone who can reject its central commitments. Their understanding of the evidence and trade-offs matters as much as their eventual signature.
Where full attendance is impractical, agree the decision boundaries beforehand and arrange a review before commitments are treated as final. Record what remains conditional. This is a practical accommodation for a small team, and it carries a limitation: an absent decision-maker may still miss context that a written summary cannot fully convey.
Include the people who understand delivery
Implementers are the people whose work must change, or whose contribution is required, for the strategy to succeed. Map them from the proposed activities. A plan involving new product choices may affect design, ordering, production, customer communication and support, even when only two people perform all those functions.
Start with the work sequence and identify where knowledge sits. The most useful participant may be the person who routinely resolves awkward exceptions, rather than the person with the most senior job title. Include the knowledge needed to challenge the plan’s assumptions.
Not everyone needs to attend every discussion. Some people can provide evidence beforehand, join for a relevant decision or review a proposed handover. The key is to ensure that their information reaches the decision while it can still change the outcome.
| Contribution | What it adds to planning | What should be clear |
|---|---|---|
| Resource approval | Authority to commit time and spending | Which decisions can be approved |
| Customer knowledge | Understanding of needs and recurring difficulties | Which observations support the proposal |
| Delivery knowledge | Practical sequence, capacity and exceptions | What must be possible before work starts |
| Coordination | A view across connected activities | Who will resolve conflicting commitments |
| Independent challenge | Questions the group may overlook | How concerns will be recorded and assessed |
For a small business, these are contributions rather than five positions to create. One person may provide several, but the group should still consider whether any important perspective is missing.
Prepare evidence and a decision brief
A decision brief is a short account of the issue, the evidence available, the options to consider and the decision required. Preparing it before the session lets participants spend more time examining choices and less time discovering basic facts.
Keep the brief proportionate. State the customer or business problem, the current position, the proposed objective and the practical constraints. Include what is uncertain and what remains open for discussion. Avoid presenting the preferred option in much greater detail than alternatives unless the evidence genuinely supports that difference.
Ask participants to bring examples from their work. A recent order with missing information, a repeated customer question or an observed production delay can reveal more than a general statement that communication needs improvement. Use examples to investigate the process rather than to assign personal blame.
Share the material early enough for people to read it during their available working time. If preparation is necessary, allow for it in the plan. A request for thoughtful input is less credible when the people providing it have no capacity to prepare.
Design a session around decisions
Tracy recommends several days away from interruptions. That reflects Tracy’s preferred planning format, but the underlying requirement for a small business is adequate attention to the decisions being made. A contained issue may be handled through shorter prepared sessions, while a major change can require more time and investigation.
Choose a format that matches the scope. Separate collecting evidence, evaluating alternatives and authorising commitments when combining them would rush the decision. If information is missing, assign the investigation and reconvene instead of trying to resolve an empirical question through repeated opinion.
A useful sequence is to confirm the problem, examine the baseline, compare routes, test the preferred route against constraints, then agree actions and approvals. Make the intended output of each stage explicit. This helps the group notice when it is polishing an idea before agreeing that it addresses the right problem.
Protect the discussion from routine interruptions while allowing an appropriate way to handle genuinely urgent operating needs. The aim is enough continuity for careful thinking. The venue and meeting length should support that purpose rather than becoming measures of how serious the strategy is.
Make disagreement useful
People may hesitate to challenge an owner or a colleague who has invested substantial effort in an idea. Invite concerns explicitly and ask for the observation or reasoning behind them. The person leading the meeting can help by describing their preferred option as a proposal that needs examination.
Distinguish disagreements about facts, assumptions, preferences and authority. A factual disagreement may need better records. An assumption can be tested. A preference may require a trade-off. A question of authority must be clarified before the group treats its discussion as approval.
Ask what would have to be true for a proposal to work. This gives supporters and critics a shared task. Instead of arguing generally about whether a faster service is sensible, they can examine available capacity, required information and how exceptions would be handled.
Participation does not mean every decision requires unanimity. Once the relevant evidence and objections have been considered, the authorised person can decide and explain why. Record a material unresolved concern together with the condition that would trigger a review. Agreement to proceed can coexist with uncertainty about the outcome.
Decide whether facilitation would help
A facilitator helps a group structure discussion, examine assumptions and reach clear decisions. The role concerns the quality of the process. It is distinct from owning the business decision or being an expert in every operational issue under discussion.
Tracy strongly favours an outside facilitator. For a small business, the relevant question is what difficulty outside help would address. Competing owners, a discussion that repeatedly stalls or a leader who needs to participate fully may make independent facilitation useful. A straightforward, well-prepared decision may be manageable within the team.
If outside help is used, clarify its purpose and boundaries. The facilitator should understand the decision, the participants and the information available. Their role should include surfacing differences and documenting decisions, rather than producing agreement by suppressing difficult questions.
A trusted peer can sometimes provide a useful challenge, but familiarity and neutrality should not be assumed. Consider what information is appropriate to share and whether the person has an interest in a particular outcome. Whatever the arrangement, the business retains responsibility for the final commitments.
Worked example: agreeing a delivery improvement
This is an illustration. A small Australian maker of office accessories wants to shorten the time between receiving a complete order and dispatching it. The owner favours adding a faster dispatch promise to the website. The person assembling orders believes the main difficulty is frequent changes after work has been scheduled.
The owner can approve the offer and allocate time. A part-time coordinator manages order information, while the assembler understands production and packing. The three people prepare a brief using recent order records and agree that the first meeting will decide whether a limited process trial is ready to run.
Each participant spends one hour reviewing the material. A two-hour joint session then uses six person-hours: three people multiplied by two hours. Including the three preparation hours, the initial planning commitment is nine person-hours. Recording this matters because the meeting takes capacity away from other work even when nobody purchases outside assistance.
The discussion reveals that the proposed faster promise depends on knowing when an order is complete and ready for scheduling. At present, the coordinator and assembler use different interpretations. The group decides to test a shared readiness check before considering a broader customer promise.
| Commitment | Person coordinating it | Completion condition |
|---|---|---|
| Define required order information | Coordinator | Requirements checked against recent exceptions |
| Test the readiness check in production | Assembler | Trial orders and exceptions recorded |
| Approve the trial’s capacity | Owner | Time allocated and competing work deferred |
| Review the result | Owner, with both implementers | Evidence considered and next decision recorded |
The owner allows 12 hours for trial work over the following two weeks, separate from the nine planning hours. Four hours go to preparing the check, six to using it and recording exceptions, and two to analysing the records. The allocation totals 12 hours, and the group identifies the promotional work that will be deferred to make room.
Before beginning, they agree what the test can establish. It can show whether the readiness definition is usable and whether changes after scheduling become less frequent under the trial conditions. A small trial will not establish a reliable dispatch promise for every product and order volume.
At the review, the coordinator reports that one product option still produces missing information. The assembler reports that the check works for the other options. Because the unresolved issue is specific, the owner approves a revision and keeps the wider promise pending. The participants can explain both the decision and the evidence still needed.
Turn participation into clear commitments
A decision record captures what was decided, why, who authorised it and what happens next. It can be brief, but it should distinguish an approved commitment from an idea discussed and an issue awaiting evidence.
Assign one coordinating owner to each action. This does not mean that person performs every task. It means they maintain the view of progress, seek help when necessary and bring unresolved dependencies to the appropriate decision-maker.
Give the owner the authority and access required to do that work. Responsibility for improving a process is difficult to exercise if the person cannot consult the people using it or obtain the relevant records. If another approval is necessary, identify who provides it and when.
Define a handover as the point where information or responsibility moves from one person or activity to another. Specify what must be complete at that point. Ready for production, ready for review and ready for release should mean something the receiving person can recognise and check.
This is where the participation principle becomes tangible. The people receiving the work should help define what ready means. Otherwise, one person’s completion can simply become another person’s unresolved problem.
Keep the team involved after the session
Planning participation loses value if the record disappears into a folder and later changes are made without explanation. Share the decisions with affected people, including those who did not attend. Explain the objective, the immediate changes and the limits of what has been approved.
Use a short follow-up rhythm that matches the work. Ask whether commitments are progressing, whether dependencies are available and whether new observations challenge the chosen route. Keep operational updates separate from decisions that require the owner to reconsider resources or direction.
When a commitment slips, identify the reason before assigning more work. The estimate may have been wrong, an approval may be missing or another priority may have displaced it. A visible adjustment to scope or timing is more useful than maintaining a date everyone knows is unrealistic.
Close completed actions with evidence appropriate to their purpose. Finishing a document may be enough for a preparation task; a changed process needs evidence that people can use it. To structure the broader choices behind those commitments, Turning business goals into a workable strategy sets out a planning method from baseline to review.
Adapt the process to a very small team
A solo founder still performs several roles: setting direction, authorising resources and doing the work. Separate those perspectives during planning. First describe the intended outcome, then examine delivery requirements, then decide what can realistically be committed. This can expose conflicts that remain hidden when every thought is treated as a single decision.
Use outside evidence to challenge assumptions even when no formal planning group exists. Customer observations, records of earlier attempts and feedback from an appropriate peer can improve the reasoning. None replaces the founder’s responsibility to assess the information and choose a course of action.
For an Australian business with people working across locations or on different days, participation may require a mix of written input and scheduled discussion. Give everyone the same current brief and make the resulting decisions accessible. Being unavailable at one meeting should not make a person’s practical knowledge invisible.
Respect the limits of each person’s actual role and availability. A contractor, part-time employee or occasional collaborator cannot be treated as an unlimited resource simply because their input is useful. Confirm the work involved and the capacity available before allocating responsibility in the finished plan.
Common mistakes that undermine implementation
One mistake is inviting the final approver only after the group has settled the direction. This can leave important limits undiscovered until late in the process. Involve that person while the central trade-offs are being examined, or make the provisional status explicit.
Another is asking implementers to endorse a plan without allowing them to change it. Their knowledge is most useful before assumptions harden into commitments. If an objection cannot be resolved immediately, document it and decide how it will be investigated.
A third is allowing participation to blur responsibility. Everyone contributed does not establish who can approve a change or who will coordinate the next action. Write those responsibilities down, especially when work crosses several functions.
Finally, avoid treating discussion length as evidence of commitment. A long session can still end without a clear decision, while a short prepared discussion can settle a contained issue. Judge the process by the quality of the evidence, the clarity of the choices and whether the work has the support it requires.
Questions to ask
- Who can authorise the direction and commit the necessary resources?
- Whose practical knowledge could change the proposed plan?
- Which decisions are open, and which constraints are already fixed?
- How will concerns be raised, recorded and resolved?
- Does each commitment have an owner, capacity and a completion condition?
- When will the team review evidence and adjust the plan?
Bringing it together
Involving the right people makes a strategy easier to challenge, authorise and deliver. Decision-makers contribute authority and priorities; implementers contribute knowledge of what the work requires. Both need to understand the evidence and the trade-offs behind the chosen route.
Build the process around clear decisions, then preserve that clarity in everyday work. A useful planning session ends with supported commitments, visible uncertainties and a practical way to review what happens next.
Source: Brian Tracy, Business Strategy. Methods and examples are practical adaptations. Figures in this article are illustrations, not data. This article is general business information.
