Operations rarely fail from lack of effort. They fail from accumulated process.
I start by examining how the work actually runs today — before anyone specifies what to build. Most of what slows a business down turns out to be process, not software.
The situation
Most companies are working harder than they need to.
Disconnected systems, manual workarounds, and processes that grew by accident create inefficiencies that slow operations, raise costs, cap growth, and wear down teams and customers alike.
Most organizations know something is off. Fewer are certain where to start, or what better would even look like.
So the work doesn't begin with tools. It begins with how your business actually operates — then simplifies the workflows, aligns systems to support them, and leaves behind something your team can run without me.
Selected work
Consumer lending · regulated financial servicesAbandoned credit applications, recovered in minutes.
Applicants were dropping out partway through the credit application, and the business wanted them back.
The existing application flow end to end, including how operations staff were currently recovering abandoned applications by hand.
Recovery was entirely manual and therefore slow, inconsistent, and capped by staff capacity. The constraint was the process, not the software.
A secure re-engagement path returning applicants directly to where they left off — plus the architectural foundation for modernizing the wider application experience.
Sr. Product Owner, contract · 2025–2026
A maintenance system built entirely from tools they already owned.
How camp maintenance issues — leaking faucets, damaged drywall, everything else — were actually being reported, prioritized, and closed out.
They didn't need a facilities platform. They needed visibility. Every capability required already existed inside the Google tools they were paying for.
Client engagement · no new licence cost
A winery that search engines could not find.
Why an established, operating business was effectively invisible to anyone searching for it online or navigating to it.
Nothing was broken and nothing needed building. The business had simply never been registered with the services that feed search results and mapping.
Client engagement · advisory
A three-in-one platform, proven on our own organization first.
How a small organization actually takes a booking end to end — from a visitor landing on the site through to money in the bank.
The friction wasn't in any one tool. It was in the seams between website, calendar, and payment processor — and in how long it took a non-technical owner to get all three working at all.
SpacelyBooking — built by Decision Craft Solutions
An organization stood up from nothing, in working order.
How registration, intake, and payment would need to work in practice — before selecting a single tool to run them.
Defining the intake flow first meant the payment and scheduling configuration followed the process, rather than the organization reshaping itself around whatever platform it happened to buy.
Co-founder, own venture · 2025–2026
Four applications became one, and onboarding dropped to days.
How new client cases actually got configured, across four flagship applications spanning three divisions.
Most 'customization' wasn't development work at all — it was configuration being routed through the development queue by habit.
Product Delivery Manager · 2022–2023
Ten thousand people moved platforms without stopping work.
How teams across the organization actually used the legacy system — agile and non-agile alike — before any migration plan was set.
Adoption, not data transfer, was the real risk. Working patterns varied enough that a uniform cutover would have stalled delivery.
Product Manager, contract · 2023–2024
One assessment platform serving three states at once.
Each state's testing workflow separately, rather than assuming a shared set of requirements across all three.
A large common core existed underneath genuinely state-specific differences — so standardization and flexibility weren't actually in conflict.
Technical Product Owner, contract · 2024
Engagements
Six ways in, sized to the problem.
Ordered by how much change they require. Most engagements start at the top, and the assessment decides how far down you actually need to go — not every problem needs something built.
Process & Systems Assessment
For when you know something isn't working but aren't certain where to begin. A structured read on where the inefficiencies live and what to address first — including the honest answer if the fix is smaller than you expected.
- Review of how work actually flows today
- Evaluation of the systems already in use
- Bottlenecks, redundancies, and risks identified
- A prioritized roadmap you can act on
Reorganize What You Already Have
Often the tools are fine and the arrangement isn't. Reordering steps, fixing handoffs, and cutting work that no longer earns its place — no new software, no migration, no licence fees.
- Streamlining workflows across teams
- Eliminating redundant and duplicated steps
- Repairing handoffs and communication gaps
- Getting more from tools you already pay for
Automate the Repetitive Work
Where a process is sound but someone is doing it by hand every week. AI and automation applied to the specific steps that warrant it, rather than adopted wholesale because it's expected.
- Identifying which manual work is worth automating
- Applying AI and automation tooling where it fits
- Keeping a person in the loop where judgement matters
- Measuring what the automation actually saved
Integrate & Align Systems
When the individual tools work but don't talk to each other, and staff become the integration layer. Making your systems serve the process rather than dictate it.
- Evaluating current tools and platforms
- Identifying gaps and overlaps in functionality
- Defining how systems connect and share data
- Recommending right-fit solutions, including ones I have no stake in
Build What Doesn't Exist
When the capability genuinely isn't available off the shelf. Custom applications built directly, or a development team led through delivery — whichever fits your budget and timeline.
- Custom application design and delivery
- Leading an existing or contracted development team
- Requirements, architecture, and delivery oversight
- SpacelyBooking, our own platform, was built this way
Implementation & Enablement
Whichever route you take, the work only counts once it sticks. Getting the change delivered, adopted, and owned by your team rather than dependent on outside support.
- Translating business needs into requirements
- Guiding technical teams through delivery
- Training on new processes and systems
- Supporting long-term adoption
Method
The review comes before the build. Always.
Plenty of projects begin with a solution already chosen and requirements gathered to justify it. This one begins a step earlier — with whether the process needs the solution at all.
Understand
Observe the current process end to end — how work actually flows, not how the org chart says it does.
Diagnose
Separate the real constraint from the assumed one, before any solution is on the table.
Redesign
Define clearer processes, then align the systems that support them.
Transfer
Leave the team able to keep improving without ongoing outside help.
Next step
Let's find the opportunity worth acting on.
A conversation about what's working, what isn't, and where there's room to improve. If it isn't a fit, I'll tell you that directly.
Schedule a discovery call