The problems we're built for.
Digital Change Partners is a new practice. Case studies will be published here as engagements complete and clients agree to share them.
Until then, here are the kinds of problems we work on, and how engagements are typically shaped.
Problems we're built for
Typical problems, plainly stated.
Businesses
Growth has outpaced our systems. What worked at 20 people is breaking at 80.
Systems, Automation & EfficiencyLeadership wants an AI position before the next board meeting.
AI & Emerging Technology
Professional services
Our people spend too much of their time on work nobody can bill for.
Systems, Automation & EfficiencyWe need clear rules on AI before a client asks us how we use it.
AI & Emerging Technology
Not-for-profits
Every funder wants a different report, and we build each one by hand.
Systems, Automation & EfficiencyWe invested in a new system and the team still works around it.
Capability, Change & Implementation
Local government
Our digital strategy is approved. Delivery is where it gets stuck.
Capability, Change & Implementation
Membership organisations
Our member data is spread across systems that don't agree with each other.
Strategy & Transformation
Engagement shapes
Illustrative
How engagements are typically shaped
Each example below is illustrative: how an engagement is typically shaped, not a client story. No organisation is named or implied.
01Illustrative
Turning fragmented reporting into live organisational intelligence
Systems, Automation & Efficiency · Strategy & Transformation
- The problem
- Leaders make decisions from reports assembled by hand from several systems. Each takes days, arrives late and is argued over.
- The approach
- Map where each number comes from and who relies on it. Agree a single source for the measures that matter. Automate the data flow and build a small set of dashboards with the people who use them.
- What changes
- Reporting becomes current rather than retrospective, and time spent assembling it goes back into interpreting it.
02Illustrative
Moving from informal AI use to confident, governed practice
AI & Emerging Technology · Capability, Change & Implementation
- The problem
- Staff are using AI tools with no shared rules. Leadership is uneasy but doesn't want to ban something useful.
- The approach
- Find out how AI is actually being used. Assess risk and readiness. Co-design a governance framework and policy, identify two or three use cases worth doing and build capability to use them well.
- What changes
- AI use becomes visible and guided, and the organisation can explain its position to its board, staff and stakeholders.
03Illustrative
Finding the duplicated work before automating anything
Systems, Automation & Efficiency
- The problem
- A team feels overloaded, and the instinct is to buy another tool.
- The approach
- Trace a small number of core processes end to end. Identify double handling, waiting and workarounds. Redesign the process first, then automate only the steps that remain.
- What changes
- Fewer steps, fewer handoffs and a clear case for any technology that is still needed.
04Illustrative
Turning an approved strategy into a working roadmap
Strategy & Transformation · Capability, Change & Implementation
- The problem
- A digital strategy has been endorsed, but it describes intentions rather than actions, and nobody is sure what happens first.
- The approach
- Translate the strategy into prioritised initiatives with owners, sequence and decision points. Set up a light governance rhythm and support the first initiatives through delivery.
- What changes
- The strategy becomes a plan people can act on, with visible progress and a clear basis for saying no.
05Illustrative
Rescuing a system rollout that didn't land
Capability, Change & Implementation · Systems, Automation & Efficiency
- The problem
- A new platform went live, but usage is low and old workarounds are creeping back.
- The approach
- Talk to users to find out why. Fix the process and configuration issues that make the new way harder than the old one. Rebuild training around real tasks and support teams through a second rollout.
- What changes
- The system becomes the normal way of working, and the investment starts to pay back.
Have a problem like these?
Tell us what you're trying to change. A few sentences is enough to start.