8 minutes
How leaders actually work A repeatable method: plan, check, consult, repair.
What you’ll be able to do Identify the practical implication of “How leaders actually work” and apply it to one live DHS decision connected to Accessibility as Leadership Responsibility. Compare the responses to this question and explain your choice: What belongs in your plan before the invitation goes out? Document a next step for How leaders actually work: 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 is visible before anyone sits down.
How do you know it is working? Leaders need a method that survives a busy week. Not a binder. A short loop: plan access with the work, check it in the room, consult specialists when the question is formal or complex, and repair without punishing the person who needed access.
This lesson is the job-aid underneath the job aid — why each step exists, and what “good enough” looks like.
In this lesson Run a before / during / after access loop on real work.
Know when to contact EOAD instead of improvising.
Use questions that invite needs without forcing disclosure.
Avoid the usual pitfalls: delay, oversharing, and “we’ll catch it next time.”
The access loop Before — plan the four doors When you set the date, book communication support. When you build the agenda, send it early in an accessible file. When you choose the room or platform, check the path in. Put one line on the invite: how to request access, and that requests will not be treated as a problem.
During — watch who can take part Use the microphone. Repeat questions. Describe what is on screen. Do not talk over captions. If the hybrid setup fails, pause. A meeting that continues while half the team cannot hear is a decision.
After — notes, formats, and repair Send notes in a real document, not a screenshot. Follow up on any request that was not fully met. If someone was excluded, say so and fix the next instance. Do not ask them to educate the whole team as unpaid labor unless that is a role they want.
Escalate — EOAD, HR, language access Accommodation disputes, complaints, medical documentation questions, and anything that looks like discrimination or retaliation leave the huddle and enter process. Phone: 651-431-3040. ADA: dhs_ada@state.mn.us. Other EOAD: dhs.equalopportunity@state.mn.us. Do not include private details in ordinary email.
After is a leadership moment: who received the same information, in a format they can use.
A usable invitation line You do not need a medical story to plan a meeting. You need a door. Use language like: “Tell us what you need to participate — captions, interpreter, accessible file, extra time, or another format. We will not treat the request as a problem.” Then mean it.
Comparing weak and strong methods Weak Strong Too heavy
Access is mentioned in an annual training. Requests go to a generic inbox that nobody monitors. Leaders learn about barriers from exit interviews. Documents are “final” before they are accessible.
Access is on the project checklist beside budget and comms. One person is named to book interpreters. Templates are accessible. Leaders notice who is silent because they could not use the last file.
A 40-page protocol nobody opens. The method has to fit a Tuesday. If your checklist takes longer than the meeting, it will not be used. Keep it short and mandatory.
Habits that hold under pressure Name a booker
Someone is responsible for interpreters and captions the same way someone is responsible for the room. If “anyone” owns it, no one does.
Accessible means the file
Not the intention. Headings, alt text, contrast, tags. “We could describe it if asked” is not an accessible document.
Confidentiality
Disability details stay with the people who must know. Do not announce someone’s accommodation in a team meeting as a teachable moment.
No retaliation
Watch your own irritation. Extra scrutiny after a request is a pattern investigators know well. Name the work, not the person, when something is hard to schedule.
The hardest part is not the checklist. It is slowing a project when access is not ready. That pause is leadership. Shipping an unusable product on time is not.
Pitfalls and better moves Pitfall: “Tell us your disability.” Ask what someone needs to participate. Documentation, if required, belongs in the proper process — not a staff meeting. Curiosity is not a right.
Pitfall: “We’ll remember next time.” Write the miss in the notes and assign a fix. Memory is not a control. If the same miss happens twice, it is the method.
Pitfall: treating language access as extra printing If the public cannot read the notice, the notice did not go out. Translation and interpreters are part of the communication, not a sequel.
Better: close the loop in the room “Before we decide — can everyone use what is on screen and in the packet?” That one sentence changes behavior more than a poster.
Where in the loop? Book CART when you send the calendar invite.
Choose a category Before During After Escalate Pause because remote staff cannot see the whiteboard.
Choose a category Before During After Escalate Send tagged notes the same day.
Choose a category Before During After Escalate A staff member says they were mocked after requesting an interpreter.
Choose a category Before During After Escalate Put request instructions on the public event page.
Choose a category Before During After Escalate Check matches Reset Last lesson: practice, a seven-day transfer, and how to repair a miss without making it the requester’s job.
Put this lesson to work What you can change You control whether how leaders actually work changes a live DHS process connected to Accessibility as Leadership Responsibility 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 A repeatable method: plan, check, consult, repair.
You control whether how leaders actually work changes a live DHS process connected to Accessibility as Leadership Responsibility 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 Carry this into practice Lead access on purpose — in meetings, hiring, communications, and everyday DHS work.
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.
