Practice

Some Patterns

The same pattern, project after project: ask until the real problem surfaces, pick the right tool, know when I'm in the zone.

Some of My Favorite Questions

"It's six months from now. You are really happy. What has changed?"

"What's actually in your way — the manual task you dread, the approval stuck somewhere, the data you don't have?"

"What does the team already know that leadership needs to hear?"

"What are you reading?"

Two Kinds of Problems.

🩹
Duct Tape
When something doesn't hold together — I build the structure
Siloed teams Inconsistent data Unclear ownership No shared process Missing documentation Scattered reporting

The pieces are real. The seams aren't. Three teams running parallel and not talking, five spreadsheets answering one question five ways. I build the seams: shared definitions, operating rhythm, one map everyone agrees on.

🪣
Drano
When something isn't moving — I clear the path
Stuck workflows Manual bottlenecks Stalled projects Buried insights Waiting on sign-off Technical debt blocking features

The work is real. The team is ready. Something's just stuck — an owner unclear, a queue unprioritized, a decision waiting on someone who doesn't know they're the bottleneck. I find what it is and clear it.

My Professional Sweet Spot

JOB SATISFACTION Hand me the vision, get out of the way. CREATIVE FREEDOM < Less More >
Overspecified, over-constrained.
Process for its own sake.
Peak: trusted with the vision,
given room to lead.
Undefined, unmoored.
Nothing to push against.

What I Bring.

🗂️
Building what doesn't exist yet
Project Management Process Design Agile / Scrum Gap Analysis
🔄
Making complexity legible
Translating Complexity Stakeholder Management Technical Writing Cross-functional Teams Executive Comms
📊
Turning numbers into decisions
Requirements Analysis Working in Code Visualization