8 minutes
Who finds out last Empty chairs are data. Map who lives with the change before you lock it.
What you’ll be able to do Identify the practical implication of “Who finds out last” and apply it to one live DHS decision connected to Change Management: Bringing People Along. Compare the responses to this question and explain your choice: What should happen before the work is locked? Document a next step for Who finds out last: Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed. The empty chairs are the lesson: who is not here while the design is still soft? What the work actually shows Stakeholder maps often list offices, not people who will absorb the hit. “Internal” hides the night shift. “Partners” hides a Tribal Nation with a government-to-government relationship. “Customers” hides a person who needs an interpreter to read the notice. If your map is a logo collage, it will fail at the counter.
This lesson is the evidence of practice — who is usually missing, and how that missing shows up as “resistance” later.
In this lesson Map who lives with the change, not who owns the slide.
Treat Tribal consultation and labor relations as paths, not checkboxes.
See how language and disability access travel with every rollout.
Name the harm of using the public as the staff briefing.
If they are not in the draft, they will be in the incident report.
Who is usually missing The people who meet the public Eligibility workers, contact-center staff, facility staff, investigators, and county colleagues. They know where the form will snag. They are often invited to “review” after lock. That is decoration.
People who cannot use the default channel Staff and members of the public who need captions, plain language, interpreters, or extra time. A rollout webinar without captions is a change meeting some people cannot attend. Access is part of bringing people along.
Tribal Nations Minnesota DHS has a Tribal and Urban Indian Relations function to support ongoing consultation. Tribal Nations are governments. Do not park them in a stakeholder list next to a vendor. If you are unsure whether consultation applies, ask early — not after the date is printed.
The people who will lose unofficial power Every old system had unofficial experts. If you do not invite them, they will keep the old way alive because it is how they still help clients. Bring them in as designers, not as obstacles.
The public is not your quality-assurance team. If they are teaching staff the change, the map failed.
Mechanism: last-in is a method When you brief leadership first, then comms, then supervisors, then staff, then counties, then the public, you are not being careful. You are concentrating information at the top until it is too late to use. Reverse the test: who has to act first on Monday morning? Brief them while the design can still move.
What people actually experience Rumor first
Staff hear it from a Facebook comment or a client. Trust drops before you have said a word. Speed without a named owner still loses to rumor.
English-only notice
Households with limited English proficiency meet the change as a denial or a missed deadline. Outreach then looks like “low engagement.”
County surprise
A statewide date ignores local peak weeks, staffing, or another system outage. Partners spend their credibility calming people you did not warn.
Punished messenger
The person who flags a hole is labeled negative. Next time the room is quiet. You have trained silence.
Reading the same rollout three ways Org-chart map Work map Power map
Administrations, divisions, named directors. Useful for approvals. Blind to the counter, the county, and the night shift.
Who touches the case, the phone, the notice, the building, the data. This is the map that predicts failure.
Who can delay you legally or politically: labor, Tribal governments, federal partners, advocates, the press. Ignoring them is not bravery. It is a later, worse meeting.
From observation to explanation When a rollout “surprises” the front line, do not start with “we have a communications problem.” Start with the chairs. You will often find a closed design, a backwards sequence, and a map of offices instead of work.
How to check your map without a consultant Name five people who will touch it Monday Not five directors. Five actual roles. If you cannot name them, you do not have a rollout plan. You have a hope.
Ask who hears it from the public first That person should have seen the notice, the script, and the exception path before the public did.
Ask who can say this is not ready If the only people who can delay go-live are already committed to the date, the map has no brake.
Limits of this scan A chair test will not replace formal consultation, labor notice, or a civil-rights review. It will stop you from being shocked that the missing people did not cheer.
Who is missing? Night-shift facility staff who will use the new handoff.
Choose a category Front line / public-facing Partner government Access / formal path A Tribal Nation whose members will get the new notice.
Choose a category Front line / public-facing Partner government Access / formal path ASL users who cannot use the uncaptioned launch webinar.
Choose a category Front line / public-facing Partner government Access / formal path County eligibility supervisors in a peak SNAP week.
Choose a category Front line / public-facing Partner government Access / formal path The bargaining path for a change in work hours.
Choose a category Front line / public-facing Partner government Access / formal path Check matches Reset Next: two honest frames — announce-and-hope versus design-with — and when each is actually required.
Put this lesson to work What you can change You control whether who finds out last changes a live DHS process connected to Change Management: Bringing People Along 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 Empty chairs are data. Map who lives with the change before you lock it.
You control whether who finds out last changes a live DHS process connected to Change Management: Bringing People Along 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, a completed sort 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.
Mark this lesson completeReset this lesson
Previous lesson Next lesson Carry this into practice Do not announce a change and call it leadership — bring the people who will live with it along.
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.