11 minutes
Published is not the same as usable Six things the division publishes, the one job each of them has, and why plain language, accessibility and cultural responsiveness have to be design decisions rather than a final check.
What you’ll be able to do Design a public-facing web page, letter, notice, form, presentation or training so that plain language, accessibility and cultural responsiveness are decided while it is being built, not checked after it is finished. Compare the responses to this question and explain your choice: Where should the work start? Document a next step for Published is not the same as usable: Take the next public-facing thing you are asked to help with and write its one job in a sentence before you write anything else. If nobody can agree on that sentence, that disagreement is the first finding. What the division publishes, and what each piece is for A division administers programs. Most Minnesotans never meet a program. They meet a web page they found through a search, a letter that arrived in the mail, a form with a deadline on it, a slide at a public meeting, or a training someone told them to take. Those things are not a description of the work. For the person reading them, they are the work.
That is why the design of a public-facing resource carries as much weight as the policy behind it. A correct policy announced in a notice nobody can act on produces the same result as no announcement: people miss a deadline, call a line already at capacity, or decide the whole thing is not for them. And the parts that stop people are rarely the sentences. They are the reading path, the format, the channel, the timing and the assumed knowledge, all of which are settled before anyone writes a word.
Three qualities have to be built in at the same time. Plain language means a reader can understand it on the first read. Accessibility means the resource works with the ways people actually read: screen readers, magnification, a keyboard, captions, print, and a mind that is tired at four in the afternoon. Cultural responsiveness means it makes sense to someone who does not already know how DHS works. Handled one after another at the end, each one undoes part of the last — the plain rewrite breaks the heading structure, the accessibility repair puts the jargon back, the translation preserves a gap nobody saw. Handled together at the start, they are one piece of design work.
Six public-facing products, and the job each one has Web content Letters Notices Forms Presentations Training
A page is met in the middle, not at the top. Most people arrive from a search or a forwarded link, land halfway down, and read two lines before deciding whether they are in the right place. Its job is to let someone confirm they are in the right place and reach the next step. Design for that: a first line saying what this is and who it is for, real headings a reader can skim and a screen reader can jump between, link text that names its destination, and the action near the top rather than after the background.
A letter arrives without context, often to someone who did not expect it, sometimes months after the conversation it refers to. Its job is to tell one person what has happened, what it means for them, and what they need to do next. Design for that: the decision and the action in the first paragraph, the reason after it, dates written out in full, one named way to ask a question, and nothing essential buried in a paragraph so long the reader gives up before reaching it.
A notice carries an obligation and usually a deadline. Some notices have required wording that is not yours to change. Its job is to make sure a person knows something is required of them and by when. Design for that: separate the required text from the part you control, put a plain summary of what to do above the required text rather than below it, make the date unmissable, and check how long the notice actually takes to arrive before setting the window.
A form is where a resource stops being reading and starts being work. Its job is to collect exactly what is needed to make a decision, and nothing else. Design for that: ask only what will be used, say why anything sensitive is needed, use plain labels rather than program vocabulary, let a person save and return, and make sure every question can be answered by someone who does not have the document you assumed they have.
A slide deck at a public meeting does two jobs at once: it supports a live explanation and it survives afterwards as a handout. Design for both: real text rather than pictures of text, a size people can read from the back, enough contrast for a bright room, every point also carried in the spoken words for anyone who cannot see the screen, captions for anything recorded, and a version sent out in advance for people who need to read ahead or pass it to an interpreter.
Training published for people outside the division is a communication with a longer running time. Its job is to leave someone able to do something differently. Design for that: more than one way in, no timed interactions, captions and transcripts, nothing that depends on color or motion alone to carry meaning, plain vocabulary with program terms defined at first use, and examples that reflect the range of communities in Minnesota rather than one default household.
Decide the structure before the sentences What you can change You control the order of the work: what the resource is for, who it reaches, what it must carry, then the reading path and format, and only then the wording.
What to watch for Do not accept “make it plain language” as the whole task when the structure, channel and deadline are the parts stopping people. Accepting the narrow version of a request is how a resource gets edited three times and still does not work.
Your next step On the next request, ask two questions before you start: what should a person be able to do after this, and which parts are still open to change?
Five questions that decide whether a resource works What should a person be able to do?
One sentence, in plain words. If the team cannot agree on it, that disagreement is the first finding, not a delay.
Where will they meet it?
A search result, a forwarded link, a mailbox, a lobby, a meeting room, a phone. The place decides the format and how much context the opening has to carry.
What do they have to already know?
Every program term, acronym and process step the resource assumes. Each one is a place where a reader can be shut out while the sentence itself reads perfectly well.
How much time does it assume?
Time to receive it, read it, ask someone, gather a document, arrange an interpreter and respond. Count backwards from the deadline and see whether the window is real.
How will you know it worked?
Not by how it reads to you. By watching a few people who actually use it attempt the task it exists for.
Private reflection, kept by you and not collected anywhere: think of something you helped publish. How might your role, your familiarity with the program, or the vocabulary you use every day have shaped what you assumed a reader would already understand?
Carry this forward Every public-facing resource has one job: something a person should be able to do after meeting it. If nobody can write that sentence, more editing will not rescue it.
Plain language, accessibility and cultural responsiveness are the same design work seen from three sides. Done in sequence at the end, each one undoes part of the last.
The parts that stop people most often are structural — the reading path, the format, the channel and the deadline — and they are settled long before anyone writes a sentence.
Publishing is a claim that the resource works. A usability review is the only way to find out whether the claim is true.
A scenario about one change carried by three connected resources, flashcards on the five questions that decide whether a resource works, and a knowledge check on where a remaining problem belongs.
Take the next public-facing thing you are asked to help with and write its one job in a sentence before you write anything else. If nobody can agree on that sentence, that disagreement is the first finding.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Course overview Next lesson Carry this into practice For most Minnesotans, this division is a web page, a letter, a form or a slide at a public meeting. Four lessons on designing those well, ending with a usability review you run on one real resource.
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.
