Organisations are often reasonably good at deciding what should happen. They are less consistently good at creating the conditions that allow it to happen.
A policy may state that repairs should be performed to an approved standard, distributors should maintain certain capabilities, customers should receive consistent service, or management should receive particular information. None of those statements, however, creates the capability required to deliver the intended result.
Between policy and execution sits an operating system.
That system has to answer practical questions. Who is responsible? What level of competence is required? What tools, parts and technical information are needed? Which decisions can be made locally, and what needs escalation? How is performance measured, and what happens when the standard cannot be met?
These questions are less visible than the policy itself, but they determine whether it has any operational meaning.
The gap becomes particularly apparent in regional or international organisations. A headquarters standard may be entirely reasonable while the capability required to implement it differs significantly by market. One country may have an established technical network, another may depend on a distributor, while a third may require a regional specialist centre.
Consistency therefore does not necessarily mean that every market should operate identically. The more useful objective is to establish consistent outcomes through operating arrangements appropriate to local conditions.
That requires breaking the policy into the capabilities necessary to deliver it.
For example, a requirement for an approved repair process may imply defined repair categories, trained technicians, approved materials, suitable machinery, access to technical documentation, traceability, quality checks, escalation rules, parts availability and record keeping.
Only when those elements are in place does the original policy become executable.
This principle applies well beyond after-sales. A new sales process is not implemented simply because a presentation has been distributed. CRM discipline is not established because fields have been added to a system. A quality standard is not operational merely because a document has been approved, and a strategy is not implemented simply because management has communicated it.
The practical discipline is to take each important policy statement and ask: What must be true operationally for this to work?
That question normally exposes dependencies that the original policy does not show. Some involve people and competence; others concern information, systems, equipment, organisational responsibilities or decision rights. There may also be commercial constraints, particularly where implementation depends on independent distributors, suppliers or service partners.
Once these dependencies are visible, implementation becomes a management problem that can be planned, resourced, measured and progressively improved, rather than an expectation that has merely been communicated.
The distinction matters because organisations frequently mistake formal agreement for operational readiness. A policy can be approved, responsibilities assigned and deadlines established while the underlying capability remains incomplete.
Effective implementation therefore requires more than compliance with the written instruction. It requires evidence that the intended process can actually operate, that exceptions can be managed and that performance can be sustained.
Policy defines intent. Execution requires the organisation, resources and processes capable of delivering it.