THE DCA APPROACH
Define. Communicate. Assure.
A practical management philosophy for connecting what an organisation intends to achieve with what actually happens.
Developed by David Bowman, the DCA approach helps leaders establish achievable requirements, make responsibilities understood and use evidence to assess delivery.
FROM MANAGEMENT INTENT TO EVERYDAY WORK
Where does the connection break?
A management team agrees a direction. Procedures are written, responsibilities are allocated and people get on with their work. Over time, different interpretations, competing priorities and practical constraints can pull delivery away from the original intention.
The organisation may still have extensive documentation and regular reporting. What becomes uncertain is whether its requirements are workable, whether people understand them and whether the available evidence confirms the intended result.
DCA provides a structure for investigating that uncertainty and deciding what needs to change.
THREE CONNECTED PRINCIPLES
Clear enough to act on. Practical enough to deliver.
01
Define
What must be achieved, and is it achievable?
Establish the intended outcome, relevant requirements, ownership and the conditions for success. Consider the people, time, competence, information and equipment needed to deliver.
A requirement that exceeds available resources needs a management decision. The organisation must address the constraint, adjust the approach or reconsider the commitment.
Define what evidence would demonstrate success and how exceptions should be handled before work begins.
02
Communicate
Do the people involved understand what to do?
Give people the current information, context and instruction relevant to their responsibilities. Make ownership, handovers, decision authority and escalation routes clear.
Check understanding through discussion, demonstration or appropriate assessment. A distributed document or recorded acknowledgement alone gives limited insight into practical understanding.
Keep communication active when requirements change, and give people a way to raise ambiguity, conflicts or practical difficulties.
03
Assure
What evidence supports confidence in the result?
Review evidence against the intended outcome. Use appropriate checks, observations, records and performance information to establish whether the work meets its requirements.
Investigate gaps and recurring exceptions. Establish whether the cause sits in the requirement, resources, communication, execution or the way performance is assessed.
Assign the response and verify its effectiveness. Feed what is learned back into the requirements and the way people work.
AN ILLUSTRATIVE EXAMPLE
A customer complaint keeps coming back.
The complaint is logged, someone responds and the action is marked complete. A month later, the same issue returns. DCA helps management examine the whole process.
Define the complete outcome
Specify the required response, investigation, authority and timescale. Establish what must be resolved before closure and who will check whether the action was effective.
Check that the responsible people have the time, information and authority to carry out the investigation.
Communicate the responsibilities
Make the handover between customer service, operations and management explicit. Explain who investigates, who approves changes and who communicates with the customer.
Ensure everyone understands what completion means and when an unresolved issue must be escalated.
Assure the improvement
Examine the investigation and the evidence of change. Check subsequent work and complaint patterns to assess whether the cause has been addressed.
Use the findings to improve the process, its resources or its instructions where necessary.
APPLYING DCA IN YOUR ORGANISATION
Start with one process that matters.
Choose a process with a recognisable problem: recurring complaints, slow approvals, unreliable handovers, overdue actions or uncertainty over competence.
Follow a real example from the original requirement through to its outcome. Speak to the people involved, examine the available evidence and identify where assumptions replace clear decisions.
Agree practical changes, assign ownership and establish how their effect will be reviewed. Extend the approach when the revised process demonstrates that it works.
Questions for your next management meeting
Can we explain the intended outcome clearly?
Have we provided the resources needed to achieve it?
Do the people involved understand their responsibilities?
What evidence would show us that the process is failing?
Who acts on that evidence, and how do we check the response?
DCA AND ZEBSOFT
Give the approach a practical operating structure.
DCA can be applied using your existing management arrangements. Where the organisation needs a connected platform, Zebsoft supports the relationship between requirements, responsibilities, work and evidence.
Documents, tasks, training records, audits and corrective actions can be managed within a shared structure. Management still determines what is required, provides resources and judges whether the evidence supports the intended outcome.
As the developer of DCA and co-founder of Zebsoft, I connect the management philosophy with its practical application.
