How I Work
It might start because new leadership wants a strategic plan that actually gets used. It might start because a program is underperforming: an audit finding, a financial problem, a board that's lost confidence in how something's being run. It might start because a board is asking a harder question, is this organization headed for trouble, and weighing whether the answer is new revenue, a new program, or a merger. There's no fixed list of ways in. Whatever brings the conversation, the work that follows runs the same course.
Every engagement starts with a diagnostic, not a proposal. That means time in the building: reviewing the org chart, the funding structure, the compliance history, and the systems staff use every day. It means honest conversations with board members, program staff, and funders about what's working and what isn't. The output isn't a slide deck. It's a clear, specific picture of where the organization stands today, in language that holds up when frontline staff ask the hard questions, not just when it's presented to the board.
That includes testing the presenting problem itself: a program that looks like a quality problem might really be a structural one, reporting lines that don't match how work gets done, leaving staff unsupported and stakeholders in the dark. A merger conversation might really be about a board's unspoken fear of a funding cliff. What the diagnostic finds is what drives what happens next.
Whatever the assessment points toward, the next step turns direction into infrastructure: dashboards, reporting cadences, and decision points that make progress visible month to month, not just at the annual retreat. The specifics change by sector. What DDS wants to see in a corrective action plan, what CMS looks for in a PACE review, and what a board needs to track risk, are different questions with different answers.
Infrastructure is only as good as the people responsible for operating it. This phase is about instilling the culture that organizations run on systems, not on any one person. That starts with coaching teams to notice when day-to-day practice has quietly drifted from the system, and to know whether it's the practice that needs to bend back or the system that needs to catch up.
It also means coaching leaders on the relationship skills that get a regulator or a funder to yes, not making the case myself and leaving. It means sitting in the room while a program director learns to facilitate a hard conversation, not facilitating it for them indefinitely. It means helping a leadership team understand who actually has the authority to say yes to something, and how to build a case that gets them there. The goal is a team that can do all of this without me, not a team that depends on me to keep doing it.
What stays is the habit that the culture builds: running decisions through the systems built to hold them, and catching it when practice and system drift apart.
Coming back a year later isn't the same as starting over. The org chart, the funding structure, the relationships with the board and funders, that's already built, and it means whatever comes next moves faster than it would with someone new.
Sometimes what surfaces is systems drift: a decision made on the floor in the middle of a busy week that never made its way back into the plan, the policy, or the dashboard, so the system quietly stops matching how the work actually happens. Catching that from the inside is hard, the people closest to the work are often the last to see it change. Sometimes it's a new question entirely, a strategic plan due for a hard look, a program considering a change nobody's tested yet, a funder conversation that needs a relationship someone new hasn't built. Either way, it's not something I pitch upfront. It tends to come out of the work itself: an ED or a COO who's seen the value of having that outside eye in the room, and wants it there again when the next thing comes up.
If any of this resonates, a conversation is the right next step.
No pitch deck. No proposal before we've spoken.