Case studies
What the problem was, what I did, and what changed, with numbers wherever there are numbers.
Problems reported in chat were getting lost, and sorting each one meant reading 50-message threads. I built an agent that turns every report into a tracked ticket, routes it to the right owner and keeps the person who raised it updated. The team runs it without me.
Two high-risk programmes run as one: moving customers group by group while switching off the old app. I set the rules for who moved when, and ran two testing approaches side by side to bring the timeline forward by weeks.
Weeks of empty results turned out to be two bugs hiding each other. After the fix, the same job finished in two minutes and produced a real, sourced business proposal, with 340 automated tests guarding it.
Career paths, hiring, standards and a leadership layer underneath me, so the function grew without depending on one person. QA went from being seen as a blocker to being trusted in the room where decisions get made.
Under pressure to ship new login security before the busiest period of the year, I ran an evidence-based readiness check. It found real regressions that could have locked customers out, and the release was paused with interim protections in place.
I brought in a new monitoring tool, used it to find exactly where logins were failing, then led the fix across design, engineering and QA. The improvement showed up in the numbers straight after release.
Free, research-backed printable journals, with a journal builder and guides to each technique, built on Next.js. Case study to follow.
Designed and built from the brand up: Next.js, hand-written motion, and tested for accessibility and speed before launch. Case study to follow.
Contact
Thirty minutes to talk through what you’re trying to fix. If I’m not the right fit, I’ll say so, and point you to someone who is.