A dated design review. This examines the transition guidance published for November 2–9, 2026. It is not current claim advice. Check the official Unemployment Insurance Agency page for current information.
Michigan’s Unemployment Insurance Agency (UIA) homepage announces a transition to MiUI, a replacement unemployment system. In the supplied desktop screenshot, a large agency banner and introduction precede a notice explaining the launch and shutdown dates.
The notice contains important information. But the most consequential instruction for someone receiving benefits is in another resource: the agency’s October 30 transition checklist.
The evidence changes the priority.
The official checklist tells claimants to finish tasks in the old system before 4:30 p.m. on November 2. It makes an exception to normal certification scheduling for that day, warns of possible payment delays if certification is not completed before the cutoff, and says past weeks can be certified when the replacement system opens, scheduled for 8 a.m. on November 9.
The homepage’s transition notice gives the old system’s closing time but does not include that assigned-day exception or the possible payment consequence. The checklist is available farther down the homepage under Latest News. The question is whether the person most affected should have to find it to discover the urgent instruction.
Our assessment
The page gives general agency orientation more visual priority than a consequential, time-sensitive task. That is the main failure by our standards. A visitor should not need to work out the importance of an instruction by comparing a homepage, an announcement and a checklist.
This is our evaluation of the design. It does not establish that any individual missed certification, lost benefits or suffered a payment delay because of the page.
1. Put the action beside the deadline.
Our standard: begin with the visitor’s journey.
The notice emphasizes a November 9 rollout. For a claimant arriving before the November 2 cutoff, the immediate question is what needs doing before access ends. Put that action, its deadline, the scheduling exception and the possible consequence together, with a direct route to the official checklist.
2. Make a limited screen earn its space.
Our standard: give each element a job.
The screenshot shows a large photographic banner, agency title, breadcrumb and introductory paragraph before the notice. Agency identification matters. On a transition day, it should leave room for the instruction that affects the visitor’s next move. A concise, prominent transition message could coexist with the broader agency homepage.
3. Separate different people’s tasks.
Our standard: explain the choice and next action.
Claimants and employers have different transition responsibilities. Label those paths in ordinary language. A person receiving benefits should not have to infer which general “user” instructions apply to them.
4. Explain access changes from the affected person’s perspective.
Our standard: make availability understandable.
The notice says phone claim filing and the old phone certification service will end. It describes the new system as faster on digital devices. The launch overview provides further help options. The first explanation should also guide someone who lacks a usable device, internet access or confidence with the new process. Expected improvements should not substitute for that route.
Phone certification, filing a claim by phone and speaking to customer service are distinct activities. The checklist says customer-service phone support resumes after launch; that does not mean phone certification or phone claim filing returns.
5. Change the guidance when the situation changes.
Our standard: make the promised action match its real state.
Before the cutoff, foreground the preparation task. During the outage, distinguish unavailable claim actions from information resources that remain accessible, and show the scheduled reopening time. After launch is confirmed, show the working entry route and recovery guidance. A dated notice needs an owner and an update condition.
My independent opinion
People visiting an unemployment service may be trying to protect their income while navigating an unfamiliar process. I would judge this page first by whether it helps that person preserve their options. Visual polish and a modernization announcement are secondary to that responsibility.
The failure here is avoidable work imposed on the visitor at the point where the service already requires them to adapt. Clearer information cannot remove the outage, but it can reduce the work of discovering what the outage means. That is a meaningful part of access.
This evidence supports a strong criticism of the information hierarchy. It does not show deliberate obstruction, establish unlawful conduct or tell us the agency’s motives.
What the rest of the page gets right
The full homepage includes a claimant roadmap, login and certification links, appointment information, language assistance, training resources and the transition checklist. It would be inaccurate to say help or action routes are absent from the whole site.
The strongest argument for the existing layout is that an agency homepage serves multiple audiences and links to more detailed guidance. A notice cannot contain every detail. We still think the action and payment-timing consequence deserve immediate prominence because the agency itself identifies their importance.
What a better journey would demonstrate
- Before a deadline, a claimant can identify the required action, cutoff, relevant exception and consequence from the first screen.
- During an outage, a visitor can tell which tasks are unavailable, what help remains and when the next update is expected.
- After a confirmed launch, the actual entry and recovery routes work, and phone support is clearly distinguished from phone filing and certification.
- The same understanding survives a narrow screen, keyboard use, larger text and assistive technology.
These are acceptance questions for a future review. This case does not claim that those usability or accessibility tests have been performed.
Sources and scope
- Michigan UIA homepage · Public page reviewed November 2, 2026.
- UIA transition downtime checklist · Agency publication dated October 30, 2026.
- Overview of MiUI’s launch · Official detail about the transition and access changes.
- DRKNYT methods and design principles · Our evaluation framework; it is not a legal standard imposed on Michigan.
Evidence includes one supplied desktop screenshot and the official public pages. Its exact capture time is unknown. We did not inspect anyone’s claim, submit a form, test the chatbot, measure accessibility conformance or study actual payment outcomes. We preserve the distinction between a visible design problem, a plausible burden and measured harm.