8 minutes
Noticing who a process was built for The core drill. A portal, a meeting, a hire — name the default person.
What you’ll be able to do Identify the practical implication of “Noticing who a process was built for” and apply it to one live DHS decision connected to Acceptance in DHS Work. Compare the responses to this question and explain your choice: How should the team use the concept? Document a next step for Noticing who a process was built for: Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed. The pattern sentence Complete it without a villain:
This process was built for someone who can ________. It is harder for someone who ________.
If you cannot fill the blanks, you are still in Minimization — not because you are a bad person, because the who is still invisible to you.
Three desks Front desk / portal Meeting Hire
Built for: daytime, English, a printer, a stable login. Harder for: language access, shift work, no broadband, a screen reader.
Built for: people who hear in the room, read the night-before deck, speak over each other. Harder for: captions, processing time, remote greater Minnesota.
Built for: people who already know the acronyms, can write a 48-hour sample unpaid, can wait for a delayed posting. Harder for: everyone else. Name the skill. “Fit” is not a who.
If the default person is “anyone,” you have not noticed yet. Anyone is Minimization’s favorite client.
Apply this — write the pattern sentence One process.
Built for someone who can ____.
Harder for someone who ____.
Save it for From noticing to shifting.
Put this lesson to work What you can change You control whether noticing who a process was built for changes a live DHS process connected to Acceptance in DHS Work or remains information on a page.
What to watch for The team completes the learning, keeps the same default, assigns no owner, and never checks who carries the burden.
Your next step Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed.
Carry this forward The core drill. A portal, a meeting, a hire — name the default person.
You control whether noticing who a process was built for changes a live DHS process connected to Acceptance in DHS Work or remains information on a page.
Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed.
Completion is shown by a scenario decision, a knowledge-check response and a saved one-minute commitment.
Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Carry this into practice Notice difference without ranking it — and without pretending everyone is the same.
Return to the experience: What did you notice or try, whose perspective informed it, and what would you keep or adjust?
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.
