Most enterprise project failures are organizational before they are technical. My role is to help leaders to identify orgainizational gaps and understand root causes, and help facilitate the changes needed. My responsibility is to name gaps accurately and without accusation, and design accountability into the engagement.
Organizations reach an inflection point when the way they operate stops being sufficient — a competitor is moving faster, a market is shifting, or a significant change is on the horizon that the current structure isn't built to absorb. The pressure is real. The instinct to act on it quickly is understandable. Many fall into the "quick win" trap, at the expense of scalability and future growth. Organizations that focus first on the "what" and "why" with intention are far more likely to select a "how" pathway that is truly transformative.
This practice helps organizations develop that understanding — and build the operational and governance conditions that make meaningful change executable, not just planned.
I work in both advisory and embedded capacities. Understanding how an organization actually operates — as distinct from how it believes it operates — often requires being in the room: observing, participating, and building the relationships that surface what formal reporting doesn't capture. My background in anthropology wasn't an accident. Participant observation is a real methodology, and it transfers directly to organizational work.
Project management is part of how I work. It is not what differentiates it.
Discovery and due diligence come before any commitment to scope, timeline, or approach. That process is not always comfortable. It surfaces what an organization doesn't yet know about itself, across every level. But it is what makes execution possible. You cannot talk about how until there is a clear understanding of what and why.
My analysis is frank and comprehensive. It looks across the full organizational picture, not just the project plan, and names what it finds. Proper resourcing, clear ownership, and realistic scope are often what a well-run engagement produces. They are not conditions I demand before I start. But getting there requires an honest picture of where you're starting from, and I will give you that picture even when it's inconvenient.
I assess potential engagements as carefully as clients assess me. I've declined work where the organizational conditions weren't there and weren't addressable. That's not a judgment. It's how good work starts.
Organizational Diagnosis
Before work begins and through early engagement, I assess what the organization doesn't know about itself: gaps in documentation, ownership, and decision authority that will materialize as risks if they're not named first. This includes understanding what existing systems, processes, and institutional knowledge actually do, which is often less documented than anyone expects.
Delivery Governance
During active engagement, I manage the conditions that make delivery possible: Is the right work happening in the right sequence? Are decisions being made by the right people, at the right level? Is scope being managed formally, or absorbing informally? Are the obligations that belong to the organization being met, or quietly absorbed by the project team?
Accountability Structure Design
Throughout the engagement, I build the conditions so that accountability is visible without requiring me to personally hold it, and sustainable after I leave. Good decisions are center stage. The frameworks, registers, and governance structures that emerge from an engagement exist to make good decisions possible, visible, and repeatable. Not to fulfill a project management checklist.
Artificial intelligence is generating genuine organizational pressure: to adopt it, differentiate with it, or respond to competitors who claim to be using it. That pressure is real, and in some cases so is the opportunity.
What's also real: organizations that move to AI implementation without a clear picture of their current operations are spending significant money to automate processes they don't fully understand, on foundations they haven't examined. The result is expensive, and the disappointment is predictable.
Core operations, decision ownership, process clarity, documentation of how things actually work: the foundational work is unglamorous. It is also what determines whether AI delivers anything useful. I do that work. It tends to matter most before anyone wants to talk about it.
Every engagement produces documents: governance frameworks, risk logs, decision records, accountability structures. Those matter. But they are not the goal.
The goal is an organization that owns what we built together and can continue improving on it after I leave. I work to put myself out of a job on every engagement. The measure of a successful one isn't that the client needs me to stay. It's that the conditions we created hold without me, and that when a new challenge arrives, they want to bring me back for that.
Honesty. Thoroughness. Analysis that is sourced, rigorous, and delivered without hedging. My absolute best, every time.
This practice is solution-oriented and forward-facing. The point of surfacing what's unclear is not to document problems but to resolve them. I will continuously work to create the conditions where decisions, ownership, and risks are visible and understood. I won't leave things on the table. If something matters to the engagement, it gets named, addressed, and owned.