Selected work
Eight engagements, and what each one actually found.
Client names are withheld unless permission has been given. In two of these, the answer was that nothing needed to be built at all.
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