The Co-Design Readiness Gap Is a Leadership Problem, Not a Capacity One

David's analysis in Co-Design Is Right, But Organizations Need a Path to Get There does something genuinely useful: it refuses to let the perfect be the enemy of the good, and it takes seriously the institutional friction that practitioners face when trying to move from principle to practice. The structural barriers he names — compliance frameworks that emphasize coverage over community input, procurement systems that favor speed over participation, staff capacity stretched thin — are real.

But the implicit framing deserves a challenge. When organizations describe their inability to implement co-design as a capacity problem, they're usually describing a symptom. The underlying condition is a leadership and governance structure that hasn't made strategic alignment between community voice and organizational decision-making a genuine priority. That's a different diagnosis, and it points toward different solutions.

What "Capacity Constraints" Usually Mean in Practice

The capacity argument goes like this: co-design takes time, requires community trust-building, demands iterative processes, and most language access teams are already stretched meeting baseline Title VI compliance obligations (opens in new window). All of that is true. But capacity is also a function of what leadership chooses to resource.

Consider how organizations approach other compliance-adjacent priorities. When the Department of Justice updates its web accessibility guidance (opens in new window) or when Section 508 requirements tighten, agencies find ways to redirect staff time, contract differently, and restructure workflows. The capacity materializes because leadership signals that it must. Language access co-design rarely receives that same signal — not because the resources don't exist, but because the strategic case hasn't been made compellingly enough to the people who control those resources.

This is where the CORS framework's emphasis on strategic alignment becomes clarifying rather than abstract. The question isn't whether a given organization has enough FTEs to run community co-design sessions. It's whether co-design is positioned as a strategic input into program effectiveness or as an optional enhancement layered on top of a compliance-driven baseline. Those are structurally different organizational postures, and they produce structurally different resource decisions.

Governance Architecture Matters More Than Staffing

Research on participatory design in public services consistently shows that the programs with the most durable community co-design infrastructure aren't necessarily the ones with the largest teams. They're the ones where community input has a defined pathway into decision-making. According to the National Academies of Sciences, Engineering, and Medicine's work on community engagement (opens in new window), the distinguishing factor in sustained participatory programs is governance architecture — specifically, whether community representatives have formal roles in review and approval processes, not just consultation.

This distinction between consultation and co-governance is where David's framework, as explored in his analysis, could go further. Consultation — asking communities what they think after program parameters are set — is operationally easier and politically safer. Co-governance — giving communities meaningful authority over program design — requires leadership to cede some control, and that's where most organizations actually stall. The barrier isn't a project management problem. It's a power-sharing problem.

The Substance Abuse and Mental Health Services Administration's community engagement framework (opens in new window) makes this distinction explicit: organizations that treat community engagement as a communication function rather than a governance function consistently produce programs that communities don't trust and don't use. Language access is no different.

Strategic Alignment as the Entry Point

What does a leadership-centered approach to this problem actually look like in practice? The Pacific ADA Center (opens in new window) and similar regional technical assistance providers have documented a pattern in organizations that successfully scale community co-design: the shift happens when senior leadership connects co-design outcomes to metrics they're already accountable for — utilization rates, program effectiveness data, complaint and grievance patterns, audit findings.

This is a strategic alignment argument, not a values argument. You can believe deeply in community voice and still fail to institutionalize co-design if you can't connect it to the performance frameworks your organization actually uses to make resource decisions. Conversely, organizations that have made that connection — that can show leadership how co-design reduces rework costs, decreases complaints, and improves program uptake among LEP populations — tend to find that capacity concerns become more tractable.

The lep.gov guidance on meaningful access (opens in new window) provides the compliance floor. But compliance floors don't drive organizational change at the pace or depth that genuine language access equity requires. What drives change is when program leaders can walk into budget conversations with data showing that community co-design is a cost-effective quality intervention — one that produces programs communities actually use — not an additional burden.

This is the kind of strategic reframing that our analytical approach at this publication emphasizes: moving from compliance-as-ceiling to community voice as an operational input with measurable program effects.

The Risk of Accepting the Capacity Frame

There's a real cost to accepting the capacity framing uncritically. When organizations internalize the idea that co-design is something they'll do once they have more resources, they create a permanent deferral mechanism. Resources for discretionary enhancements rarely materialize on their own — they're competed for, and the programs that compete successfully are the ones with clear strategic rationales.

The WCAG development process itself (opens in new window) offers an instructive parallel. The iterative, multi-stakeholder process that produced WCAG wasn't cheap or fast. It was sustained because the organizations involved made a strategic decision that inclusive standard-setting produced better standards — and they built governance structures to support that decision over years. Language access programs that want to move toward genuine co-design need a similar long-horizon strategic commitment, not a capacity plan.

Building on this framework for navigating institutional barriers, the more generative question for practitioners is concrete: what would it take for your organization's leadership to treat community co-design as a strategic input rather than a compliance enhancement? That means identifying which performance metrics your leadership already tracks, mapping where co-design outcomes intersect with those metrics, and building the governance architecture — formal community roles in review and approval, not just comment periods — that makes sustained participation possible. Answering that question honestly, and then working backward from it, is where the real implementation work begins.