I help mission-driven and high-complexity teams find the real constraint, reduce the load around it, and rebuild a simpler operating model.
This is useful when a team is doing a lot and still not getting the result it needs. The issue is often not effort. The blocker may be workflow, incentives, trust, coordination, decision rights, or speed.
What this can produce
- a bottleneck or constraint diagnosis
- a decision map
- a simpler operating rhythm
- AI use-case triage
- handoff and ownership cleanup
- clearer board or leadership alignment
- a 30-day test plan
What usually goes wrong
- The team is busy, but the work does not compound.
- AI adds tools, demos, or process, but not less manual review.
- Complexity makes it hard to see what matters, who decides, and where handoffs stall.
- Growth adds coordination overhead faster than the operating model can absorb it.
How I approach it
- Get clear on the real constraint.
- Separate the work that moves it from the work around the work.
- Strip away tools, rituals, or approval paths that add load without improving judgment.
- Rebuild cadence, roles, and tools around a simpler operating model.
Best fit
I am most useful when the work sits between people, tools, process, and judgment:
- Nonprofit boards steering mission, risk, and operating tradeoffs
- Education or social-impact teams growing faster than their operating model
- Technical teams using AI but not yet reducing manual load
- Social service organizations carrying operational drag across handoffs and partners
- Leadership teams stuck in recurring decisions without clearer movement
Not the right fit
I am less useful if the problem is only a software build, a generic AI demo, or a strategy document that does not need operating change.
Common situations
Busy, but not moving Symptom: plenty of activity, little improvement. What usually helps: define the constraint and stop feeding the work around it.
Too many decisions, too little clarity Symptom: recurring debates, low confidence, slow follow-through. What usually helps: narrow the variables and be explicit about what matters most.
AI that adds noise instead of relief Symptom: more tools and experiments, but not less operational load. What usually helps: start from the work that should disappear, the signal that should improve, or the decision that should get faster.
Growth that makes the system shakier Symptom: each step up in scale adds fragility. What usually helps: simplify the operating model before adding more layers.
What a conversation can look like
A useful advisory conversation usually starts with diagnosis, not a framework.
We would look at where the system is dragging, what decisions keep recurring, what work is not compounding, and whether AI or tooling is actually reducing load. From there, the output may be a sharper problem statement, a simpler operating rhythm, a decision map, or a short set of changes the team can test.
If the challenge is hidden complexity, uneven execution, or a system that has become harder to steer than it should be, I can usually help.
If your team is carrying too much activity and not enough clarity, send me the operating knot you are trying to untangle.