How I Work
Methodology
As an outside observer, I'm able to provide a fresh perspective, identifying any potential blind spots. I use a variety of methods to uncover how work moves across an organization and where any gaps in ownership, process, or expected value might exist.
My job is to close those gaps. I do it by going to the source: Slack threads, Jira tickets, Git commits, meeting transcripts, sales calls, and customer feedback. The signal I'm looking for isn't what teams say they prioritize; it's what the work record shows they do with their time. That gap between stated priority and actual effort is where the most important opportunities tend to live, and it's difficult for organizations to surface it from the inside.
I come in as an outside partner who observes, diagnoses, coaches, and builds. When the engagement ends, the client owns everything: the processes are documented, the frameworks are in place, and the team knows how to run them without me.
Engagement Arc
Operating Diagnostic
Two to three weeks
The engagement begins with the diagnostic. I conduct structured interviews and workshops with the project sponsor, core decision makers, and key team members, and review internal documentation, OKRs, and the places where work actually happens. At the end, I deliver three artifacts: a process alignment map, a decision friction audit, and a prioritized recommendation roadmap. The findings presentation is a working session, not a report handoff.
Build Scoping
One week
If the diagnostic surfaces work worth building, I scope the build directly from the findings, tying every item in the scope to a specific gap identified in the diagnostic. Nothing gets added because it seems useful in the abstract.
Build Engagement
Three to six months
The build is a mix of structured working sessions, async document review, and time spent in meetings observing how teams operate. Deliverables are defined at scoping and do not shift without a documented reason. The engagement closes with a before-and-after operating view, a decision-making framework, and a 30/60/90 day plan with clear milestones and accountable owners.
Knowledge Transfer
Ongoing through engagement close
Every process is documented before the engagement closes, and the goal is a team that can run the system without me in the room.