Technology
Your technology should make the business work better.
Existing systems may be capable of more. The issue could be configuration, disconnected data, a process mismatch or adoption rather than missing software.
Does this feel familiar?
Systems everywhere. Still working in spreadsheets?
- Reports disagree
- Manual bridges between systems
- Software features remain unused
Recognition is the beginning
Follow the work
Build the connection from business need to value. A system is one part of that chain.
An illustrative starting point for investigation; the actual flow depends on your business.
- 01
Business need
Name the business outcome the capability must improve.
What might slow this down?
A tool is selected before the problem is understood.
Assess the impact using actual cases and evidence.
- 02
Process
Define how work should flow and who owns it.
What might slow this down?
The system repeats an inefficient or unclear process.
Assess the impact using actual cases and evidence.
- 03
Information
Identify the information people need to act.
What might slow this down?
Incomplete or conflicting data undermines decisions.
Assess the impact using actual cases and evidence.
- 04
System
Assess what existing systems can already support.
What might slow this down?
Configuration and integration gaps are mistaken for missing software.
Assess the impact using actual cases and evidence.
- 05
Adoption
Make the capability usable in everyday work.
What might slow this down?
People lack clear roles, confidence or a reason to use it.
Assess the impact using actual cases and evidence.
- 06
Value
Check whether the business outcome actually improved.
What might slow this down?
Features are delivered, but business benefit is not measured.
Assess the impact using actual cases and evidence.
What could be happening?
A different cause needs a different solution.
These are possible drivers to investigate, not a diagnosis of your business.
The visible symptom
Systems everywhere. Still working in spreadsheets?
Potential drivers to investigate
Process fit
Does the system fit how the work should flow?
Data quality
Can people trust the information they use?
Integration gaps
Where is information re-entered or reconciled?
User adoption
What stops useful capabilities being used?
How I may help
Fix the cause.
Improve the outcome.
Start with the work that should improve. Use existing capability wherever it can do the job.
The response may involve process, ownership, controls, existing systems, integration, automation, AI or new technology where justified.
Or don’t invest.
Explore how I helpExperience that puts technology in perspective
Two decades around technology taught me something surprisingly useful: don’t start with technology.
I’ve led substantial change across applications, infrastructure, cloud, integration and automation, including programmes involving 50+ applications and thousands of technology assets.
Selected experience from my career, before this independent practice.
I’ve seen the value technology can create — and what happens when a poor process is automated, ownership remains unclear or people do not adopt the capability they already have.
Knowing technology also means knowing when not to use it.
Start with the business need
- Fix process or ownership first
- Use existing capability better
- Integrate information
- Automate useful work
- Introduce a justified capability
Weigh benefit, effort, risk and adoption.
And sometimes:don’t invest.
Evidence before investment
Observe. Connect. Prove.
Quantify. Decide.
Follow actual work, test likely causes and assess the business impact before committing to a change.
- 01
Observe
Follow actual work.
- 02
Connect
Link symptoms to possible causes.
- 03
Prove
Test the explanation against evidence.
- 04
Quantify
Assess the business impact.
- 05
Decide
Choose what is worth changing.
What could improve?
Potential improvements depend on the diagnosis and your starting point.
- Better visibility
- Less manual effort
- Technology tied to business value
Connected outcomes
One change can reach further.
- Efficiency
Connected information can remove repeated manual effort.
- People
Clear roles and training help technology become useful.
- Customer Experience
Reliable information supports consistent customer updates.
Let’s start a conversation
Before the next technology investment, let’s establish what actually needs changing.
A number that concerns you. A frustrating process. Something that should work better. You don’t need the root cause, a solution or a formal project brief.
In 30 minutes, we can explore what’s happening, what may be driving it and what deserves closer attention. A starting point, not a complete diagnosis or a commitment to a larger engagement.