When designers are required to solve for the hardest case, they tend to end up solving for everyone. This is not an accident or a happy side effect. It is a logic built into the nature of constraint itself, and it has implications that reach well beyond architecture and product design into the way communities, teams, and organisations think and decide.

The curb cut and what followed

Kerb cuts were mandated in the United States for wheelchair users. Within a short time, everyone was using them: people pushing buggies, cyclists, delivery workers, travellers with luggage, elderly pedestrians who had simply found the step difficult. The design made for the person with the greatest constraint turned out to be better design for the street as a whole.

The pattern repeated everywhere it was tried. Captions, developed for deaf and hard-of-hearing viewers, are now used by hundreds of millions of people watching in noisy environments, learning a second language, or simply preferring to read along. Voice control, built for people who could not use a keyboard, is now standard on every device. Packaging designed to be opened by people with limited grip strength becomes easier for everyone who has ever wrestled with a sealed box. Plain language, developed to make legal and medical documents accessible to people with cognitive disabilities, turns out to produce clearer documents for every reader.

The person at the edge of the design requirement was not the special case to be accommodated. They were the signal that the existing design had not been good enough.

Why constraint generates better thinking

When you design only for the typical user, you produce something that works adequately for the average case and fails quietly at the edges. You never find out about the failure because the people experiencing it are not in the room. When you design for the most constrained case first, you are forced to be more honest about what the thing actually needs to do. You cannot rely on workarounds. You cannot assume shared context. You have to solve the problem rather than approximate it.

This is why the presence of disabled people in a design process, when that presence is genuine rather than tokenistic, tends to produce better outcomes for everyone. Not because disability is instructive in some inspirational sense, but because the constraints it surfaces are real constraints that the design was always going to encounter. The person who named them first has done the design team a service it did not know it needed.

The same principle inside organisations and communities

When an organisation has to explain a decision clearly enough for someone who processes information differently, it usually ends up explaining it more clearly to everyone. When a community meeting is designed to work for people who cannot stay for three hours, or who need visual support alongside verbal discussion, or who require time to think before responding rather than an expectation of immediate contribution, it tends to become a better meeting for all participants.

The constraint that drove the redesign improved the experience of the people it was already serving. This is not a reason to be grateful to disabled or neurodivergent members for the service they have inadvertently rendered. It is a reason to stop treating their presence as a complication and start treating it as a design resource that the community or organisation has been wasting.

Questions for reflection

  • What processes or practices in your organisation or community were designed with only the typical participant in mind, and what constraints have been quietly absorbing ever since?
  • Where has solving for a harder case in your experience produced something better for everyone? What did that teach you about the original design?
  • Who in your community or organisation experiences constraints that your current systems do not accommodate well? What would you learn about the system if you started there?
  • What is the difference between accommodating a constraint and letting a constraint improve the design?
  • If you treated the most constrained person in your next gathering as your primary design informant rather than your most challenging participant, what would you do differently?

The curb cut effect was named and documented by Angela Glover Blackwell, whose 2017 essay in the Stanford Social Innovation Review remains the clearest account of how designing for exclusion reveals the limits of design that thought it was already finished.