I help product teams make complexity navigable.
I partner with product teams to build the operational infrastructure that helps them plan, ship, and scale without the process getting in the way of the work.
I take on a small number of engagements with teams that have reached the point where figuring it out as they go has quietly stopped working.
When to bring me in
Most teams don't have a "product operations problem." They have a planning cadence nobody trusts, ownership that blurs at the edges, and a shipping process that works until it doesn't. You might recognize a few of these:
Planning happens, but no one can say with confidence what is actually shipping this quarter.
Work stalls in the gaps between Product, Design, and Engineering, and nobody quite owns the handoff.
You have grown fast, and the process that carried you to here will not carry you to the next stage.
Knowledge lives in people's heads and Slack threads, so onboarding is slow and every answer is a scavenger hunt.
You need real operational infrastructure but are not ready to hire a full-time ops leader to build it.
Leadership wants visibility into delivery health, and right now the answer is a manually updated spreadsheet.
What changes when the operations work
Good operational infrastructure is quiet. Once it is in place, the friction you stopped noticing simply goes away, and the team gets to spend its energy on the product instead of the process. This is the work I build toward.
Predictable delivery
Everyone can say what is shipping this quarter and trust that it will, because the plan and the execution are finally connected.
Clear ownership
Work stops falling into the gaps between teams, because every handoff has a name attached to it.
Shared visibility
Leadership can see delivery health at any time, without anyone assembling it by hand the night before.
Ways to work together
There are three ways to work with me, sized to where your team is. Most teams start with a diagnostic and grow from there.
Operations Diagnostic
I take a focused read on how your team actually plans and ships, and I show you the highest-leverage places to fix it.
This works best for teams that feel the friction but cannot yet name where it comes from.
- Interviews across Product, Design, and Engineering
- A findings report covering what is working, what is breaking, and why
- A prioritized roadmap you can act on with or without me
System Build
I design and stand up the operational system you are missing, built for how your team actually works rather than lifted from a framework.
This is for teams that know what is broken and want it built and adopted, not just diagnosed.
- An SDLC with phase gates and clear ownership
- A quarterly planning and commitment cadence
- A knowledge hub or delivery-health dashboard
Fractional Product Ops
I provide part-time operational leadership, giving your team the senior ops experience it needs before it is ready for a full-time hire.
This suits teams that need steady operational leadership a few hours a week, on retainer.
- A recurring cadence of ops leadership
- Systems maintained and matured over time
- A partner for planning, escalations, and scaling
How I work
How I work matters as much as what I build, because a system only creates value if the team actually adopts it. These are the principles I bring to every engagement:
I build for your team, not from a template.
I design operations around how your people actually work, because a framework lifted from another company rarely survives contact with yours.
I solve for adoption, not just process.
A system only works if people use it, so I design the behavior layer as carefully as the structure and keep removing friction until the right thing to do is also the easy thing.
I build things that outlast me.
You keep the documentation and the ability to run everything without me, because infrastructure that depends on one person is just a slower way to break.
I see systems the way a designer sees an interface.
A decade in UX taught me to notice where people get lost and where the mental model breaks, and I bring that same eye to how teams plan and ship.
How it works
There is no lengthy sales cycle, and we find out quickly whether I am the right fit for what you need.
Intro call
We spend a free half hour on what is going on and whether I can help.
Scoped proposal
I send a clear plan covering what I will do, what you will get, the timeline, and a fixed price.
The work
I build alongside your team rather than in a vacuum, so what I make actually gets used.
Handoff that sticks
You keep the system, the documentation, and the ability to run it without me.
Let's talk about what your team needs.
Tell me where things are getting stuck. If I am the right person to help, we will figure out the smallest useful first step together.
Start a conversation