Conceptual illustration of an open notebook, plant, and wooden steps for advisory work
From the problem to a practical test · Conceptual illustration
  1. Understand where the work waits
  2. Find a change worth testing
  3. Test and learn together
Discuss an operating challenge

I help mission-driven teams understand where work stalls and what can be simplified.

This may be useful if decisions keep circling back, handoffs slow down delivery, or new AI tools add review work instead of removing it.

My experience includes turning around inherited operational platforms at TikTok, leading reliability and latency work at PayPal, and enabling DevOps adoption within SP Group’s audit and security constraints. In the platform work, changing user flows and connecting alarm response to service ownership made existing tools more useful to engineering teams. The work involved both technical changes and how teams adopted them.

That experience is relevant when a tool exists but teams struggle to use it, responsibility is hard to locate, or delivery has to improve without bypassing necessary controls.

I start with one problem. We trace where the work waits, who has to decide, and what people keep checking by hand. Then we work out which change is worth testing. Sometimes that means a better tool. Sometimes it means fewer approvals or clearer ownership. Depending on what we find, the useful output might be a diagnosis of the bottleneck, a map of decisions and owners, AI use-case triage, or a small test of a changed workflow.

This approach may be useful for nonprofit boards, social-impact organizations, and technical or leadership teams facing these problems. I am less useful for a standalone software build or a generic AI demo.

If that sounds familiar, get in touch on LinkedIn and tell me what is happening.

Let’s connect

Have an operating problem to talk through?

Get in touch on LinkedIn ↗