Frequently Asked Questions


"How is this different from strategic planning? We just did that."

Strategic planning answers what you want to achieve. I design how you'll achieve it systematically. Your strategic plan identified priorities - I build the operational infrastructure to execute them consistently. Think of strategic planning as the architectural drawing; I build the plumbing and electrical systems that make the building actually work.

Most strategic plans fail not because the vision was wrong, but because there were no systems to translate quarterly goals into weekly actions with clear accountability.

"We're too busy/overwhelmed to take this on right now."

I get it - this is the nonprofit paradox. You need systems most when you're too busy to build them. But here's the thing: continuing without systems only makes you busier. Every week you delay is another week of staff duplicating work, decisions getting bottlenecked, and you personally becoming the solution to every operational challenge.

I design my engagements to work around your existing commitments. The goal is to reduce your workload, not add to it.

“You say you work from first principles? What does that look like?”

Working from first principles means we don't start with solutions, we start by understanding the most fundamental components of a problem. It’s a disciplined approach to building a project from the ground up, based on what is true, not what is assumed.

This is done by following a three-part process:

  • Root Cause Diagnosis: We begin by methodically identifying the symptoms of an issue and asking fundamental questions to uncover the core, underlying problem. We don’t accept the initial diagnosis; we challenge it.

  • Systems Design: We design the foundational systems required for success. This includes defining clear processes, decision-making frameworks (governance), and information flows.

  • Implementation Strategy: We embed these new systems into a project plan, ensuring that all actions and deliverables are directly connected to a stable, reliable operational foundation.

"How do you ensure systems don't kill our culture/mission focus?"

This is the fear that keeps many nonprofit leaders up at night - that becoming "more systematic" means deprioritizing clients. I've worked exclusively in mission-driven organizations for 13 years. I understand that culture and values aren't obstacles to efficiency - they're the foundation good systems are built on.

Good systems actually protect your culture by ensuring mission-critical work doesn't get lost in the day to day. When your team isn't constantly firefighting operational problems, they have more energy for the work that matters most.

"What if our situation is too unique? We're not like other nonprofits."

You're right that your specific context matters enormously. But the operational challenges are remarkably consistent. I don't bring cookie-cutter solutions. I spend significant time understanding your culture, constraints, and existing strengths before designing anything. The systems we build will be uniquely yours, but they'll solve universal problems.

"This sounds expensive. How do we justify spending on 'overhead'?"

Let's reframe this: you're not spending on overhead, you're investing in organizational capacity. Poor systems are incredibly expensive - they just hide their costs in staff burnout, missed opportunities, board frustration, and leadership exhaustion.

Consider the hidden cost of your current situation: How many hours does your team spend each week on work that should be routine? How many decisions get delayed because processes are unclear? How much institutional knowledge walks out the door when people leave?

Most clients see ROI within the first quarter - not just in time savings, but in their team's capacity to take on more strategic work.

"What's the time commitment for our staff?"

Typical weekly commitment:

  • Leadership: 2-3 hours (usually in meetings you're already having)

  • Key staff: 1-2 hours (mostly interviews and feedback sessions)

  • Implementation: Happens gradually, integrated into existing workflows

The goal is that within 2-3 months, everyone is spending less time on operational confusion and more time on mission-critical work.

"How do we know this will actually stick after you leave?"

My approach is designed for sustainability:

  • Documentation: Everything gets written down in formats your team can maintain

  • Training: I teach your team the frameworks, not just the solutions

  • Simple systems: Complex systems break down; elegant systems endure

  • Internal ownership: Your team co-creates the systems, so they understand and believe in them

"What if we're not ready for this level of change?"

Ready looks like: steady revenue, programs that work, staff who care, and leadership that recognizes growth requires more than good intentions. If you're questioning whether your current approach is sustainable, you're probably ready.

We can always adjust scope and timeline based on your capacity. The important thing is starting somewhere.

"Can you work with our existing consultants/vendors?"

Absolutely. I work alongside fundraising consultants, program evaluators, and technology vendors. In fact, I make their work more effective by ensuring you have the operational infrastructure to implement their recommendations.

I'm not competing with specialized expertise - I'm building the foundation that makes specialized expertise actionable.

"How do we get our board on board with this investment?"

I can help you make the case. The board presentation usually focuses on:

  • Risk mitigation: What happens if key people leave and processes aren't documented?

  • Growth readiness: How systems enable you to handle larger grants and expanded programs

  • Fiduciary responsibility: Good systems are part of good governance

  • ROI projections: Time savings, reduced errors, improved donor stewardship

Many board members immediately understand the value once it's framed. Happy to provide templates and talking points.