Technology programmes often fail because they underestimate the importance of participation.
A solution may be technically capable and strategically well intentioned but still struggle to gain acceptance if it does not reflect how people actually work.
Staff may see it as an additional administrative requirement, a mechanism for monitoring performance or a threat to professional roles.
These concerns cannot be resolved through training alone. They need to be considered during the design of the solution.
Co-design brings staff into the process from the beginning.
Teams help define the problem, map the current workflow, identify risks and establish what a useful outcome should look like.
This creates a more accurate understanding of the operational context.
It can reveal important exceptions, dependencies and informal practices that may not appear in official process documentation.
A six-step co-design framework
- 01
Discovery
Speak with staff across relevant roles to understand the current process and its difficulties.
- 02
Workflow mapping
Document how information, tasks and decisions currently move through the organisation.
- 03
Opportunity definition
Identify where AI, automation or process redesign could create value without removing necessary professional judgement.
- 04
Prototype development
Build a limited version of the proposed workflow using representative information.
- 05
User testing
Allow staff to test the prototype through realistic scenarios and provide structured feedback.
- 06
Refinement and implementation
Improve the solution, establish governance and introduce it through a controlled rollout.
This process also supports organisational learning.
Staff develop a clearer understanding of what AI can and cannot do, while leadership gains evidence about where further investment may be justified.
Co-design should not be confused with designing by committee.
The process still requires clear decision-making, technical expertise and strategic direction.
Participation provides the operational evidence required to make those decisions well.
The result is not simply greater staff acceptance. It is a better solution.
When AI is designed with staff, implementation becomes part of a wider improvement process rather than the introduction of an unfamiliar technology.
Teams can see the relationship between the original problem, their contribution and the resulting change.
That connection is essential if AI is to become a trusted part of professional practice.