8 minutes
The along-loop A repeatable method: name, invite, sequence, listen, close, repair.
What you’ll be able to do Identify the practical implication of “The along-loop” 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 The along-loop: Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed. The method fits on one page. If it needs a binder, it will not be used on a busy day. How do you know it is working? Leaders need a loop that survives a busy week. Not a 40-page change-management plan. Six moves: name what is changing and what is ending; invite the people who will live with it while the design can move; sequence who knows before the public; listen to resistance as data; close the loop in writing; repair without making the messenger do your guilt work.
This lesson is the job-aid underneath the job aid — why each step exists, and what “good enough” looks like.
In this lesson Run the along-loop on a change you already own.
Write a know / don’t know / when we’ll know note.
Use questions that invite holes in the plan.
Avoid the usual pitfalls: fake influence, one email, and punishing candor.
The along-loop 1. Name — the work and the ending One page: what will be different on a named date, what stops, who is affected, what is not changing. If you cannot say what ends, people will keep both worlds running.
2. Invite — while it can still move Put the Monday-morning roles in the draft. Say what they can still change. If they can change nothing, do not call it a workshop. Call it a briefing and be decent about it.
3. Sequence — who acts before the public Supervisors, public-facing staff, partners, then notices. Book access: captions, interpreters, plain language, time. A change meeting some people cannot use is a decision to exclude.
4. Listen — resistance as data “What will break if we do this as written?” is a better prompt than “any questions?” Write down what you hear. If you will not change it, say why. Silence after a big news is not a vote of confidence.
5. Close — the loop in writing What we heard. What we changed. What we will not change and why. Who owns questions. When the next update comes, even if the next update is “nothing new.”
6. Repair — without theater You will miss. Name it, restore comparable information the same day, change the checklist, and do not make the person who was left out lead the sharing circle.
Listening is a control, like a date or a budget. If it is not on the plan, it will not happen.
A usable status line You do not need a perfect comms plan to start. You need a door: “Here is what we know, what we don’t, and when we’ll know more. Here is what you can still influence. Here is how to tell us what will break.” Then mean it.
Comparing weak and strong methods Weak Strong Too heavy
A slide deck, a go-live party, a training roster. Questions go to a generic inbox. Leaders learn about holes from the press or from a county board.
One page, named owner, Monday-morning roles in the draft, a sequence that beats the public letter, a written close-the-loop note, a repair within a day of a miss.
A 40-page change-management plan nobody opens. If the method takes longer than the change, it will not be used. Keep it short and mandatory.
Habits that hold under pressure Name a sponsor
Someone with enough authority to change the design or to tell the truth when it cannot change. If “the project” owns it, no one does.
Know / don’t know
Inventing certainty is how you bounce later. A dated “we don’t know yet” is adult. A fake FAQ is not.
Protect the messenger
Thank the person who names a hole in front of other people. If you wince, the next hole arrives as a crisis.
Stop something
New work without stopped work is a staffing decision you did not admit. Name what comes off the plate, even if the answer is overtime you will actually pay.
The hardest part is not the loop. It is delaying a date when the people who must act are not ready. That pause is leadership. Shipping an unusable change on time is not.
Pitfalls and better moves Pitfall: “Any questions?” as the whole engagement Ask “what will break?” and wait. Count to ten. Questions after a power announcement are not a reliable sample.
Pitfall: “We’ll remember next time.” Write the miss into the one-pager. Memory is not a control.
Pitfall: treating access as a later translation If the change notice is unusable, the change did not reach people. Captions, plain language, and interpreters are part of the sequence, not a sequel.
Better: close in the room “Before we lock this — who is not here who will live with it, and what will break?” That sentence changes more behavior than a branded campaign.
Where in the loop? Write what stops on the go-live date.
Choose a category Name / invite Sequence / listen Close / repair Brief public-facing staff before the client letter is mailed.
Choose a category Name / invite Sequence / listen Close / repair Send “what we heard, what we changed, what we won’t.”
Choose a category Name / invite Sequence / listen Close / repair A county partner was left off the draft; you call the same day and add their cut.
Choose a category Name / invite Sequence / listen Close / repair Ask “what will break?” and wait through the silence.
Choose a category Name / invite Sequence / listen Close / repair Check matches Reset Last lesson: practice on a change already on your calendar, and how to repair a miss without making it the messenger’s job.
Put this lesson to work What you can change You control whether the along-loop 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.
Fictional working example
Follow a counter change from draft to repair A fictional team is changing how visitors request a callback. This timeline keeps input connected to a decision and a response.
1
While the draft is open → Explain what would start and stop, then ask staff and affected people what the proposal misses.
Examine this handoff Name what can still change. Inviting input after implementation is a different kind of conversation.
2
Before the public announcement → Prepare the staff who will explain and use the new process.
Examine this handoff Test the actual instructions and fallback. An announcement should not be the first time the counter team encounters the procedure.
3
When a failure is reported → A caller says the new callback window does not work with their shift.
Examine this handoff Treat this as evidence to investigate. Check whether another window or channel can work instead of assuming resistance to change.
4
After the repair Explain what changed, what remains unresolved and how to report another problem.
Examine this handoff Return the answer to the people who contributed. A repair entry without report-back leaves them guessing.
Try it with the work At which point can the reported shift conflict still change the procedure?
Draft a report-back note naming the issue, response, remaining limit and next review.
Carry this forward A repeatable method: name, invite, sequence, listen, close, repair.
You control whether the along-loop 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.
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.
