Intercultural Practice and Equity · Complex systems

History, Disability and Public Institutions

Four lessons on what public disability systems were first built to do, how ableism and racial inequity worked together inside them, why distrust is an accurate memory rather than a communications problem, and how to read a current initiative through the history it inherits.

40–45 minutes · 4 lessons · Voluntary learning

Start learning

Course outline

What the system was built to do
Public disability systems began as custodial systems. The buildings mostly closed; many of the categories, thresholds and defaults written for them are still in service.
11 minutes
Two histories, one system
Ableism and racial inequity were never separate tracks in public administration. Where they met, the effects compounded, and some of that compounding is visible in current program data.
11 minutes
Trust is a record, not a feeling
When a community approaches a state program slowly, that is usually accurate memory rather than a communications failure. What earned the distrust, and what changes it.
11 minutes
Reading a current initiative through its history
A five-question review you run on something you are working on now, ending in one design change with a name and a date attached.
11 minutes

Share this course

What you’ll be able to do

Explore and practice

Describe how institutionalization, segregation and exclusion by public systems shaped the programs the division administers now, and point to one place in a current process where that history is still visible.
Explain how ableism and racial inequity operated together inside the same public systems, and identify one current practice where both could be producing unequal access.
Explain community distrust of public systems as a reasonable response to a documented record, and name what an institution has to do, rather than say, for that to change.
Distinguish a change that alters a design from one that only explains it or moves the work onto the person affected.
Complete a historical context review for one initiative you are working on now, ending in a single design change with an owner and a review point.

What you can take into your work

Four worked scenarios drawn from rule revision, program evaluation, community engagement and a pre-launch review, each with a recommended response and the reasoning behind it.
A knowledge check in every lesson with feedback that explains the usable answer.
Sorting practice that separates documented history from the patterns it leaves behind and the assumptions worth checking, and that separates real design changes from explanations and from burden shifted onto the person.
A completed historical context review for one current initiative, kept with the project file rather than in a personal folder.

Choose one rule, form, threshold or process you are working on now. Run the five-question historical context review with one long-serving colleague and one paid community advisor, and finish it with a single design change that has a name and a date attached.

Read the introduction

Public disability systems in Minnesota did not begin as service systems. They began as custodial systems, built to hold and separate people, and the shift toward supporting a life in the community came later, under sustained pressure from families, self-advocates, litigation and federal law. This module is about what that origin left behind. It looks at the arrangements we inherited and still administer; at how ableism and racial inequity operated inside the same system rather than on separate tracks; at why some communities approach a state program slowly, and what that tells a public administrator; and it ends with a five-question historical context review you run on something you are working on right now. Nothing here is scored, ranked or collected, and the reflection prompts are yours alone.

History, disability and public institutions

One page for anyone revising a rule, a form, a process, a measure or a plan

The buildings closed. Most of the rules written for them did not.

Keep the inherited arrangements, the compounding of ableism and racial inequity, and the five review questions in view while you revise a long-standing requirement, interpret program data, plan an engagement, or prepare an initiative for launch.

The system began as a custodial system. A service system built on top of one inherits its categories, thresholds and defaults unless somebody removes them deliberately.
“That was a long time ago” is true about events and false about arrangements. Ask what the requirement was written to do, and whether that is still the question.
Ableism and racial inequity ran through the same offices and the same discretion. Look at more than one thing at once or you will report an average that hides the gap.
Present-day disparity does not require present-day intent, and naming it is a design task rather than an accusation.
Distrust is information about the record, not a communications problem. Open with what happened to the last round of input, even when the answer is nothing.
Trust follows verifiable behavior: small promises kept, changes reported back, harm corrected, expertise paid for.
Name what has genuinely improved as carefully as what has not. Accuracy in both directions is what makes the finding credible to colleagues.
Where the work touches Tribal Nations or Native American communities, the Office of Indian Affairs and the DHS offices that handle tribal matters lead; this program defers to them.

Run the historical context review on one initiative you are working on now, and finish it with a single design change that has an owner and a review date.

The historical context review, in short

What does this initiative inherit, and what purpose was that arrangement built to serve?
Who was it built for, and who did it screen out? Be specific about both.
What has genuinely changed since, and what has not?
Who carries the cost of the leftover now, and where does it land hardest?
What is the first design change, who owns it, and when is it reviewed?

When you are revising something long-standing

Write one line beside each requirement saying what decision it informs; a blank line is a candidate for removal.
Check whether the assessment opens by asking what a person cannot do, and whether it needs to.
Look for substitute decision-making treated as the default, and for settings offered because nothing else is available nearby.
Ask a long-serving colleague what the requirement was originally for before you rewrite its wording.
Finish with one change, one owner and one date, at the top of the page.

When you are reading program data

Break the measure out by race, primary language, county and disability type, and by the intersections rather than one at a time.
Where cells are small, combine periods or group geographies instead of dropping the question.
Decide in advance what you will do if a gap appears, so the answer is not improvised under pressure.
Treat an unexplained difference as a question about the design, and ask the people inside it before publishing a conclusion.
Watch for discretion clauses: “as appropriate” and “where feasible” are where variation lives.

When a community is slow to engage

Find out what was asked of them last time and what they were told afterward.
Open with that account, even when it is that nothing came of it, and say plainly that it is late.
Go through organizations people already use, rather than through your own mailing list.
Pay for time and expertise, and arrange the payment route before the first invitation.
Never read low attendance as low need; read it as evidence about the relationship.

Who this helps

Policy and program staff, whose revisions decide which inherited requirement survives another cycle — a useful place to start.
Quality, compliance and performance staff, who see the same findings recur and can ask what design keeps producing them — a useful place to start.
Data, research and evaluation staff, who choose the resolution at which a gap becomes visible or stays hidden — a useful place to start.
Executive and senior leaders, who decide whether a review ends in an acknowledgment or in a change with a name and a date attached — a useful place to start.
Operations, fiscal, contracting, communications and engagement colleagues, who hold the payment routes, the notices and the relationships this work depends on.

Related modules

Tribal sovereignty and state responsibilities
Race, disability, and unequal outcomes
Trauma-responsive public administration
Power, conflict, and repair
Ethical decision-making

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.

Sources and further reading

Minnesota Governor's Council on Developmental Disabilities
Minnesota's council on developmental disabilities, which maintains extensive public material on the state's institutional history, self-advocacy and the move to community services.
Parallels in Time: A History of Developmental Disabilities
The council's public history of developmental disabilities, covering custodial institutions, the eugenics era, exclusion from schooling, and the rights movement that changed them.
Parallels in Time II: 1950 to the Present
The second part of the same history, covering deinstitutionalization, self-advocacy, litigation and the development of home and community-based services.
ADA.gov, Olmstead: Community integration for everyone
U.S. Department of Justice material on Olmstead v. L.C. (1999) and the integration mandate under Title II of the Americans with Disabilities Act.
Minnesota Olmstead Implementation Office
Minnesota's Olmstead Plan work toward integrated, self-determined lives, including the state's commitments, measures and public reporting.
Minnesota Council on Disability
Minnesota's advisory council on disability policy, access and rights, including guidance for state agencies working with disabled Minnesotans.
U.S. Department of Justice, Civil Rights Division
Federal civil rights enforcement, including disability rights, and the historical record of consent decrees and investigations involving public institutions.
Minnesota Framework for Universal Multicultural Instructional Design
The design reference for this curriculum: multiple ways to engage, culturally responsive materials and accessible instruction.

All research and sources across the program

Opening your page…

You can still use the navigation while it loads.

History, Disability and Public Institutions

40–45 minutes · 4 lessons · Voluntary learning

Course outline

What the system was built to do

Public disability systems began as custodial systems. The buildings mostly closed; many of the categories, thresholds and defaults written for them are still in service.

11 minutes

Two histories, one system

Ableism and racial inequity were never separate tracks in public administration. Where they met, the effects compounded, and some of that compounding is visible in current program data.

11 minutes

Trust is a record, not a feeling

When a community approaches a state program slowly, that is usually accurate memory rather than a communications failure. What earned the distrust, and what changes it.

11 minutes

Reading a current initiative through its history

A five-question review you run on something you are working on now, ending in one design change with a name and a date attached.

11 minutes

Sources and further reading

Minnesota Governor's Council on Developmental Disabilities

Minnesota's council on developmental disabilities, which maintains extensive public material on the state's institutional history, self-advocacy and the move to community services.

Parallels in Time: A History of Developmental Disabilities

The council's public history of developmental disabilities, covering custodial institutions, the eugenics era, exclusion from schooling, and the rights movement that changed them.

Parallels in Time II: 1950 to the Present

The second part of the same history, covering deinstitutionalization, self-advocacy, litigation and the development of home and community-based services.

ADA.gov, Olmstead: Community integration for everyone

U.S. Department of Justice material on Olmstead v. L.C. (1999) and the integration mandate under Title II of the Americans with Disabilities Act.

Minnesota Olmstead Implementation Office

Minnesota's Olmstead Plan work toward integrated, self-determined lives, including the state's commitments, measures and public reporting.

Minnesota Council on Disability

Minnesota's advisory council on disability policy, access and rights, including guidance for state agencies working with disabled Minnesotans.

U.S. Department of Justice, Civil Rights Division

Federal civil rights enforcement, including disability rights, and the historical record of consent decrees and investigations involving public institutions.

Minnesota Framework for Universal Multicultural Instructional Design

The design reference for this curriculum: multiple ways to engage, culturally responsive materials and accessible instruction.