Part 9: The Capacity Reckoning: What Transformation Actually Costs

3-5 FTE. $400,000-$800,000 annually. Dedicated data systems. Formal partnership agreements. Monthly coordination meetings with preparation, facilitation, and follow-up.

That's what genuine community quarterback work costs. Not programs. Not services. Just the coordination, accountability, and integration functions that make everything else work together.

Most organizations claiming quarterback identity operate with a fraction of this capacity. They've built impressive physical infrastructure—schools, housing, commercial space. They've recruited quality partners. They've designed elegant theories of change.

And they've staffed the coordination function with half a position and good intentions.

This is the capacity reckoning. The moment when you calculate what transformation actually requires and compare it to what you've actually resourced. For most organizations, the gap is painful. What you do about it determines everything.

You've designed partnership architecture that could produce transformation. Now the uncomfortable question: Do you actually have the capacity to execute it?

The Capabilities You Actually Need

Genuine quarterback work requires specific expertise that many organizations lack. Inventory what your role demands, then assess honestly what you possess versus what you need.

Data analysis and performance monitoring. Someone must collect, clean, analyze, and visualize data on progress toward both finish lines. They must identify patterns, flag concerns, and translate data into actionable insights. This isn't a casual add-on to someone's job. It requires dedicated expertise, time, and tools.

Most organizations assume they'll "track progress" without recognizing that meaningful measurement requires substantial investment. The dashboard that tells you whether transformation is happening doesn't build itself.

Facilitation and conflict navigation. You must facilitate productive cross-partner meetings, navigate disagreements when they arise, and build consensus while maintaining focus on transformation. Poor facilitation wastes partner time and erodes trust. Skilled facilitation creates the collaborative problem-solving that drives improvement.

This is a specialized skill. Not everyone who can run a meeting can facilitate collective action toward difficult goals.

Partnership management. Maintaining authority while building trust requires sophisticated relationship skills. You must have difficult conversations about underperformance. You must negotiate agreements that balance accountability with support. You must manage tensions when organizational interests conflict with collective goals.

If these conversations don't happen—or happen badly—your accountability architecture exists only on paper.

Technical assistance across domains. You must understand education, housing, workforce, and health well enough to provide meaningful support and translate across sectors. Deep expertise in every domain isn't realistic, but working knowledge sufficient to ask good questions and broker solutions is essential.

Partners working in silos don't naturally understand each other's constraints. Someone must bridge those gaps.

Community engagement. You must maintain authentic relationships with your target population, ensure community voice shapes strategy, and organize residents for advocacy when systems change requires it. This demands cultural competency, relational investment, and organizing skills that can't be reduced to a checkbox.

Fundraising. Quarterback functions rarely fit neatly into funder categories. Someone must make the case for coordination, data systems, and accountability infrastructure—functions that funders often don't value as highly as direct services but that are essential for transformation.

For each capability: Must it be in-house or can it be contracted? What mix of generalists and specialists serves your context? What can be built through training versus must be hired? What partnerships could provide access to needed expertise?

The Infrastructure Reality

The accountability architecture you designed in Dimension 4 requires significant infrastructure. Without it, accountability remains rhetorical because no one actually knows whether transformation is happening.

Data systems and measurement infrastructure. What data must you collect to track progress toward both finish lines? How will it be collected, with what frequency, by whom? How will data be shared across partners while protecting privacy? What technology platforms support data integration and visualization? What analytic capacity turns data into insight?

Infrastructure requirements typically include: Systems for tracking target population members longitudinally across services. Data sharing agreements enabling integrated analysis. Dashboards showing collective progress toward both finish lines. Capacity to produce regular reports for partners, funders, and community. Integration with partners' existing systems where possible.

Coordination processes. The system-integrator role requires structured processes that demand substantial staff time.

Map all regular convenings: Quarterly all-partner data review meetings. Monthly one-on-ones with Tier 1 partners. Annual strategic planning retreats. Ad-hoc problem-solving sessions when issues emerge. Each convening requires preparation, facilitation, documentation, and follow-up.

Clarify decision-making protocols: How are decisions made across partners? What requires consensus versus your authority? How are conflicts resolved?

Establish communication infrastructure: How is information shared between meetings? What platforms support ongoing coordination?

Estimate the total time requirements. Identify staff positions responsible by name and percentage of time. Document decision-making authority and escalation paths.

The Bottom Line

Calculate the actual budget and staffing needed to execute what transformation requires.

Budget for quarterback functions: Salaries for coordination staff—partnership managers, data analysts, community organizers. Technology costs for data systems and communication platforms. Convening costs for meeting space, materials, food. Technical assistance budget. Evaluation costs. Communications and reporting.

FTE positions required: A mid-sized quarterback orchestrating 5-7 partners might need: 1.0 FTE partnership/coordination director. 0.5-1.0 FTE data analyst. 0.5 FTE community engagement. Plus executive leadership time. Total: 3-5 FTE dedicated to quarterback functions, not including program staff if you also directly deliver services.

Sustainable funding model: What's the total annual budget for quarterback functions? What funding sources are available? Is the model sustainable for the timeframe transformation requires—15-20 years—or dependent on time-limited grants?

The reality check questions: Are you resourced to do what transformation requires? If not, do you scale back commitment, reduce partner count, or commit to raising substantial additional resources? Is your current funding model sustainable?

The Feedback Loops

When organizations complete this assessment honestly, they typically realize their design exceeds their resources. This produces essential feedback loops back to earlier decisions.

Loop back to role definition. If you've defined yourself as direct service provider plus systems integrator plus capacity builder, but analysis reveals you can only do one of those roles well with available resources, revise. Perhaps you become a pure orchestrator. Perhaps you narrow which functions you fulfill intensively versus lightly.

Loop back to partnership architecture. If your designed accountability requires monthly data reviews with seven partners, individual check-ins with each, quarterly cross-sector meetings, and annual planning retreats—totaling over 150 hours of coordination time annually that no staff person has available—simplify. Reduce partner count to what you can actually coordinate. Or commit to hiring coordination capacity.

Loop back to your theory of change. If your change pathway assumes you can orchestrate eight partners across four sectors with seamless data integration and sophisticated continuous improvement, but you have neither the data systems, coordination capacity, nor funding to make that happen—focus on fewer change levers. Reduce partners to what you can genuinely orchestrate. Or acknowledge that your theory of change rests on capacity you don't possess and cannot quickly build.

Loop back to target population. If the population commitment you made requires capacity you don't possess and cannot quickly build, narrow your target population to match what you can actually resource. Better to achieve genuine transformation for 500 children than to claim commitment to 2,000 children you cannot actually serve toward either finish line.

The Three Choices

This dimension forces a choice between three paths.

Path One: Align design with capacity. Take on only what you can execute well. Build capacity incrementally as resources allow. Resist the temptation to over-promise. Accept that effective quarterback work—even at modest scale—demands more capacity than most organizations possess.

Path Two: Commit to multi-year capacity building. Accept that full implementation requires resources you'll need years to secure. Build a realistic timeline. Operate at reduced scope while capacity develops. Be transparent with partners and community about what you can and cannot yet do.

Path Three: Proceed with fantasy planning. Design impressive systems on paper without infrastructure to implement them. Assume capacity will somehow materialize. Discover, after several years and substantial frustration, that coordination without adequate capacity produces activity without transformation.

The organizations that successfully produce transformation choose Path One or Path Two. They design within constraints. They build capacity intentionally. They acknowledge what effective quarterback work actually costs.

The organizations that fail choose Path Three. They design what looks impressive. They assume lower-capacity versions will work well enough. They discover that the gap between designed systems and actual capacity renders the design irrelevant.

This dimension determines whether everything that preceded it represents serious strategic planning or expensive performance art that cannot possibly produce the transformation communities deserve.

The Honest Assessment

The capacity reckoning is uncomfortable. But it's better to confront it now than to discover it after years of wondering why transformation isn't materializing.

The gap between designed system and actual capacity becomes undeniable. What you do with that gap determines whether your work produces transformation or frustration.

You've now worked through all five dimensions: target population and finish lines, change pathway and assumptions, barriers and leverage, quarterback role, partnership architecture, and capacity requirements. But this isn't the end.

This framework isn't linear. It's iterative. And understanding that iteration is essential to making it work.