11 minutes
Design the default, not the exception Defaults, deadlines, proof, measures and contract terms are where person-centered intentions either survive or quietly become someone else’s problem.
What you’ll be able to do Identify the default in a policy, measure, notice or contract you influence, and describe one change that moves a common need out of the exception process and into the design. Compare the responses to this question and explain your choice: What change matters most before this goes out? Document a next step for Design the default, not the exception: Find one need your process currently handles by exception. Estimate how many people have it, and write what it would take to make it the default. The default is the real policy Most of what a person experiences was decided by a handful of quiet choices: which channel is standard, how long the window is, what proof counts, what the first sentence of the notice says, and who has to ask for anything different. Those choices are the default, and the default is the real policy. Everything else is an exception, available to whoever knows it exists.
That is why exception-based design tends to reverse the intent of the people who wrote it. The flexibility is real, and it reaches the person who has an advocate, a strong command of English, a flexible job and the confidence to press. The person it was designed for, working nights, reading the letter in a second language, already told no once before, never asks.
The same logic runs through data and purchasing. A measure tells a program what to optimize; if the only thing counted is agency activity, no one is accountable for whether the activity worked. A contract decides what gets built and who gets paid to check it. These are not administrative details around the edge of person-centered practice. In statewide work, they are where it lives.
What the question changes in four kinds of work Policy and guidance Data and measures Contracts and purchasing Communication and notices
The draft names what a person must do, by when, in what language, with what proof — and says what happens when they cannot. The exception process stays small because the default already fits the common case.
The measure says something about the person’s experience, not only the agency’s activity: not notices sent but whether people could act on them; not applications received but who is missing and why. Results are looked at separately by language, region, age and disability, because an average hides the people a program is failing.
Accessibility, plain language, translation and paid review by people who use the services sit in the scope, the budget and the scoring, not in the hopes. The evidence each vendor must produce is written down before award.
The first lines say what happened, what the person must do, by when, and what to do if that is not possible — in plain words, in the languages the program serves, with a way to reach a person who can actually help.
Identical is not the same as fair Where identical treatment comes from “One process for everyone” feels like fairness, and in public administration it also protects something real: consistency, predictability and equal application of the law. The trouble starts when sameness of process is treated as proof of sameness of result.
The frame this program uses This program uses the intercultural development continuum — denial, polarization, minimization, acceptance, adaptation and integration — to describe how an organization moves. Minimization is the stage where difference is acknowledged and then treated as unimportant: we serve everyone the same way. Acceptance and adaptation keep the standard and change the design so it actually reaches people whose circumstances differ. These stages describe the work of an organization. They are never a label, a score or a record about any individual person.
What adaptation is not It is not lowering a standard, waiving a legal requirement or treating people as fragile. Accessibility and language access are obligations that come from law and policy, not favors this program invented. Adaptation means the program does what it was created to do for the people it was created for.
Defaults worth checking in anything you own Channel: what happens for somebody with no reliable mail, no printer, no smartphone, or nowhere quiet to take a call.
Timing: whether the window assumes a weekday, a car, a clinic appointment that can be had inside it, and a household with no crisis in progress.
Proof: whether the document required is one the person can actually obtain, and who cannot obtain it.
Language and reading: whether the first sentence tells somebody who does not already know how DHS works what has happened and what to do next.
Who has to ask: whether a common need is met by default, or only for the person who knows the exception exists.
What happens on failure: whether missing a step ends the service, pauses it, or triggers a call from a person.
Make the routine exception the rule What you can change You control whether a known need is designed in or handled case by case.
What to watch for Do not answer a pattern with a workaround. If staff have built the same workaround more than a few times, the design is wrong, not the people using it.
Your next step Name one exception your team grants routinely, and start the work to make it the default before the next review point.
Private reflection, for you alone and never recorded: What might accessibility mean here beyond a legal minimum? Does this process make sense to people who do not already know how DHS works?
Carry this forward The default decides who has to ask. Anything available only by exception is available mostly to people with time, language, confidence and somebody to advocate for them.
Measures teach a system what counts as real. Count notices sent, and the system will send notices. Count whether people could act on them, and the design starts to change.
A contract or grant is a design document. What you require, fund and score becomes what the person receives; what you call preferred gets negotiated away.
Adapting a process to how people actually live is not lowering the standard. The standard is whether the program does what it was created to do, for the people it was created for.
A tabbed comparison of what the question changes in policy, data, purchasing and communication, a procurement scenario, and a knowledge check on exceptions that are granted almost every time.
Find one need your process currently handles by exception. Estimate how many people have it, and write what it would take to make it the default.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
