What I do
Three areas of work. All connected by the same goal: making your organisation work better than it does today.
Process improvement
Most organisations do not have bad people. They have processes that were never designed, they accumulated. A workaround became a step. A manual check became a job. A spreadsheet became the system of record.
I map what is actually happening today, identify where time and effort are being lost, and redesign the process so that it is simpler, faster, and possible to follow consistently.
What this involves
- Current state process mapping, how things actually work today
- Identifying waste, duplication, and unnecessary complexity
- Redesigning processes that are simpler and more consistent
- Documentation that people can actually follow
- KPI frameworks so you can measure improvement over time
Good fit for: Organisations that are scaling and finding their early-stage processes are no longer working. Companies preparing for a system implementation where clean processes are essential.
Technology implementation
Choosing and implementing the right tool is harder than it looks. The vendor demo is always impressive. The reality after go-live is often different. I help organisations get from a good idea to a working system, one that fits how the business actually operates.
I work across the full implementation lifecycle: requirements, selection, design, delivery, and the critical stabilisation period after go-live. I specialise in the gap between IT and operations, the place where most implementations run into trouble.
What this involves
- Requirements definition in business language, not technical jargon
- Tool selection and vendor evaluation
- Implementation planning and delivery oversight
- Integration with existing systems and workflows
- Post go-live stabilisation and hypercare
- Automation of repetitive manual steps
Good fit for: Businesses implementing their first serious operational platform. Organisations that have implemented a system and are not getting the value they expected.
Change & adoption
The most common reason technology implementations fail is not the technology. It is the people. Not because they are difficult, because change is uncomfortable, and nobody has taken the time to explain why this change is worth their discomfort.
I work directly with the people who resist change. I listen to their concerns, I address them honestly, and I design adoption processes that make the transition feel like a step forward rather than a disruption. I have particular experience with teams that are older, less comfortable with technology, or working in regulated environments where change carries compliance risk.
What this involves
- Stakeholder mapping and change impact assessment
- Training design that matches how people actually learn
- Super user and champion networks
- Communication that explains why, not just what
- Adoption tracking and follow-through
- Working directly with resistant individuals and teams
Good fit for: Any organisation going through a significant operational change. Particularly relevant where there are older team members, high-compliance environments, or previous change efforts that did not land.
I bridge the gap between IT and the business
Technical teams speak in systems, APIs, and data models. Business teams speak in outcomes, timelines, and operational impact. I translate between them, ensuring both sides understand each other and both sides are working toward the same result.
This is where most implementations get stuck. It is also where I spend most of my time.
IT says
"The API integration is ready. We need business sign-off on the data mapping."
The business hears
"Are you saying the system is ready? Can we go live now?"
Not sure which of these fits your situation?
Most engagements involve elements of all three. Let's start with a conversation and figure out together what would help most.