Co-Design Is Right, But Organizations Need a Path to Get There

Keisha's argument in Community Voice Is the Missing Infrastructure in Language Access is analytically sound. When LEP communities are excluded from designing the programs built to serve them, the resulting infrastructure tends to fail in predictable ways — wrong terminology, mismatched literacy levels, culturally tone-deaf communication patterns. The evidence from AHRQ's health literacy research (opens in new window) and related fields supports this conclusion.

But there's a gap between diagnosing the problem correctly and prescribing a workable path forward. Co-design is the right destination. The harder question — and the one practitioners actually struggle with — is how organizations navigate the institutional, legal, and capacity constraints that make genuine community co-design difficult to implement at scale. Naming the blind spot is necessary. It isn't sufficient.

Why Structural Barriers to Language Access Co-Design Are Real, Not Excuses

Organizations that fail to incorporate community voice into language access programs are often doing so not because they've made a deliberate choice to exclude communities, but because they're operating inside institutional structures that make co-design genuinely difficult. This distinction matters for anyone trying to change practice rather than just critique it.

Title VI of the Civil Rights Act, enforced through DOJ's language access guidance (opens in new window), establishes compliance obligations but says relatively little about how community input should be gathered or weighted in program design. The DOJ's Language Access Assessment and Planning Tool (opens in new window) provides a framework for self-assessment, but the emphasis is on coverage and capacity — interpreter availability, translated document inventories, staff training — not on participatory design processes. Compliance frameworks, by their nature, create floors, not ceilings. Organizations optimizing for compliance have little structural incentive to go further.

Procurement cycles compound this. Government agencies and large nonprofits typically contract language access services through competitive bidding processes that evaluate vendors on cost, credentialing, and turnaround time. There is rarely a mechanism to evaluate whether a vendor's translation methodology incorporates community feedback loops. The Pacific ADA Center (opens in new window) and other regional technical assistance providers have documented this pattern in their work with state and local government clients — compliance infrastructure gets built around what's measurable, not what's effective.

Co-Design Requires Organizational Readiness That Most Groups Haven't Built

Genuine community co-design — not token consultation, not a focus group after the program is already designed — requires specific organizational capacities that take time and resources to develop. Organizations need trusted relationships with community organizations before they need those relationships for a specific project. They need staff with community engagement skills, not just language skills. They need decision-making processes flexible enough to actually incorporate community feedback rather than document it and move on.

As explored previously in this series, many of the operational failures in language access programs are downstream consequences of design errors. That's accurate. But those design errors often persist because organizations lack the infrastructure to do co-design well, not because they've consciously rejected it. The Great Lakes ADA Center's technical assistance resources (opens in new window) on community engagement consistently identify this gap — organizations want to do better but don't know what better looks like operationally.

This is where the CORS framework becomes useful for practitioners. The community dimension — which Keisha rightly centers — doesn't exist independently of operational, risk, and strategic dimensions. An organization that lacks operational capacity for community engagement will produce performative co-design even when it's trying to do the real thing. The risk dimension matters too: organizations that have been sued or sanctioned for language access failures often become more compliance-focused, not less, which can push them further from genuine community engagement rather than closer to it.

What a Complete Analysis of Language Access Co-Design Requires

The original article's critique is strongest when it identifies the design process problem — organizations building language access infrastructure on assumptions rather than evidence gathered from communities. That framing is more useful than a simple compliance-versus-strategy debate because it locates the failure at the level of methodology, not just resources or intent.

But a complete analysis has to grapple with what organizations need to change their methodology. Section 508 compliance resources (opens in new window) in the federal technology space offer an instructive parallel. Accessibility advocates spent years arguing — correctly — that technical compliance without user testing produced accessible-on-paper, inaccessible-in-practice digital products. The field eventually moved toward incorporating disabled users in testing and design. That shift happened not just because advocates named the problem, but because technical assistance providers developed concrete methodologies, procurement language changed to require user testing, and early adopters demonstrated that the approach was feasible.

Language access needs the same infrastructure of implementation support. The Northeast ADA Center (opens in new window) and other regional centers have begun developing community engagement frameworks specifically for language access contexts, but this work is early-stage and under-resourced relative to the need.

There's also a scale problem that co-design frameworks don't always address directly. A community health center serving a relatively concentrated LEP population in a single language has a realistic path to genuine co-design. A state agency administering benefits programs across dozens of language communities in a geographically dispersed service area faces a fundamentally different challenge. The methodology has to scale, or it will remain a practice limited to well-resourced organizations serving concentrated populations.

The Practical Theory of Change Practitioners Actually Need

Building on this framework for community-centered language access, the field needs more than a diagnosis of what's missing. It needs a practical theory of change: what does the path from current practice to genuine co-design look like for different types of organizations, at different scales, operating under different compliance regimes?

That means developing co-design methodologies that are documented, replicable, and adaptable to different organizational contexts. It means pushing DOJ language access guidance (opens in new window) and LEP.gov resources (opens in new window) to incorporate community engagement standards, not just coverage metrics. It means building the case — with outcome data — that co-design produces better results for the people it's meant to serve, so organizations can justify the investment internally.

Community voice is the missing infrastructure. That's the right diagnosis. The next analytical step is mapping the specific barriers that keep organizations from building it, and developing the tools to remove them. Critique without pathway isn't enough for the practitioners who need to change what happens Monday morning.