Co-Design Stalls in Operations, Not Just in Leadership Suites

Jamie's argument in The Co-Design Readiness Gap Is a Leadership Problem, Not a Capacity One is analytically clean: organizations that claim they lack capacity for co-design are really describing a leadership failure to prioritize it. That reframe is valuable. It cuts through the learned helplessness that lets institutions off the hook for structural choices they've made. But it risks overcorrecting — treating leadership will as both necessary and sufficient, when the operational layer has its own friction that executive commitment alone doesn't dissolve.

This isn't a defense of capacity as an excuse. It's an argument that operational complexity in multilingual accessibility work is substantive enough to warrant its own diagnostic framework, separate from but adjacent to the leadership question.

Where Executive Commitment Meets Operational Reality

Organizations that have genuinely committed leadership on language access — and some do — still routinely struggle to execute co-design at scale. The National Council on Disability's 2023 report on language access (opens in new window) documented that even agencies with formal language access plans and dedicated staff frequently fail to integrate community input into iterative design processes. The gap isn't always a leadership signal problem. Sometimes it's a workflow architecture problem.

Consider what co-design actually requires at the operational level for a mid-sized public agency serving multiple language communities. You need community liaisons who speak the target languages and understand the service domain. You need meeting infrastructure — accessible venues, interpretation, childcare, scheduling that accommodates shift workers. You need document translation workflows that can handle draft materials, not just final publications. You need feedback synthesis processes that can translate qualitative community input into actionable design specifications. And you need all of this to run in parallel with existing service delivery obligations.

The Great Lakes ADA Center's guidance on inclusive planning (opens in new window) consistently emphasizes that community engagement infrastructure takes years to build and requires sustained investment in relationships, not just one-time budget allocations. That's an operational architecture challenge, not a leadership signal one.

Procurement Constraints Are Structural, Not Motivational

Jamie's original analysis references procurement systems that favor speed over participation. That's accurate, but the mechanism matters. Government procurement frameworks — particularly those governed by competitive bidding requirements and fiscal year spending cycles — create genuine constraints that leadership intent doesn't override.

When a language access contract goes out for bid, the Federal Acquisition Regulation (opens in new window) and its state-level equivalents impose timeline and documentation requirements that compress the co-design window regardless of what program leadership wants. Vendors are selected partly on cost efficiency metrics that don't account for community engagement overhead. Contract deliverables are specified before community input has shaped them — which is precisely the inversion that co-design requires.

This isn't a problem that a motivated director solves by sending a signal. It requires procurement reform, which involves legal counsel, contracting officers, budget analysts, and often legislative or regulatory action. The Section 508 compliance ecosystem (opens in new window) has spent decades working through analogous procurement challenges, and the progress has been incremental and contested even where leadership commitment was strong.

Language Community Diversity Adds Operational Complexity

There's a dimension that often gets compressed in co-design discussions: the internal heterogeneity of language communities. Title VI obligations under Department of Justice guidance (opens in new window) apply to meaningful access for limited English proficient individuals, but the communities covered by that obligation are not monolithic.

A Spanish-speaking community in a southwestern city includes recent immigrants, multigenerational residents, urban and rural populations, and individuals with varying literacy levels in both Spanish and English. Co-design that authentically represents that community requires not one engagement process but several, with different facilitation approaches, different trust-building timelines, and different feedback synthesis challenges. Multiply that across the four or five language communities a typical urban agency serves, and the operational complexity compounds quickly.

WCAG 2.2 success criteria (opens in new window) address technical accessibility standards but don't prescribe community engagement methodology — and for good reason. The methodology has to be contextually adapted. That adaptation work is skilled, time-intensive, and not easily systematized. As explored in Jamie's analysis, leadership frameworks matter. But so does the practitioner knowledge required to execute community-specific engagement.

The Workforce Gap Is Real and Measurable

The workforce dimension deserves direct treatment. There is a documented shortage of practitioners who combine language access expertise, accessibility knowledge, and community engagement skills. The Pacific ADA Center's training resources (opens in new window) reflect demand for this skill set that consistently outpaces the supply of trained practitioners.

This shortage wasn't created by leadership failure to prioritize. It's a pipeline problem reflecting decades of underinvestment in accessibility and language access as professional disciplines. Organizations that want to implement co-design often cannot hire or contract for the expertise they need, regardless of budget availability. Leadership can allocate resources; it cannot conjure a workforce that hasn't been developed.

The Northeast ADA Center (opens in new window) has documented similar dynamics in disability services — organizations with genuine commitment to inclusive practices that struggle to find staff with the cross-disciplinary competencies required. The solution is professional development investment over years, not a leadership directive.

Toward a Dual-Track Diagnostic

Building on Jamie's framework, the more useful diagnostic asks two questions simultaneously rather than prioritizing one over the other: Where is leadership failing to make co-design a strategic priority? And where are operational systems creating friction that leadership commitment alone cannot resolve?

The answers point to different interventions. Leadership gaps require governance changes, accountability structures, and strategic realignment. Operational gaps require workflow redesign, procurement reform, workforce development, and often multi-year infrastructure investment. Organizations that address only one dimension will continue to stall on the other.

For practitioners working in this space — program managers, language access coordinators, and accessibility specialists who sit between executive intent and community engagement — the operational analysis isn't an excuse. It's a map. Understanding where the friction lives is the prerequisite to moving through it, whether that means escalating to leadership, redesigning a workflow, or making the case for a longer implementation timeline.

The practical starting point: run the dual-track diagnostic before proposing any intervention. If procurement timelines are compressing your co-design window, that's a contracting problem requiring legal and budget stakeholders — not a memo from the director. If your agency serves five language communities and has one liaison, that's a staffing gap with a multi-year solution horizon. Name the actual constraint, then route it to the right fix.

The co-design readiness gap is real. Its causes are plural. Accurate diagnosis requires holding both dimensions at once.