Heuristics H10 4 min read ★ Series Finale

Great UX is being there when it's not easy

10 Heuristic 10 Help and Documentation

Even though it's better if the system can be used without documentation, it may be necessary to provide help. It should be easy to search, focused on the user's task, and list concrete steps.

The best products are intuitive. But even the best designs confuse someone at some point. What makes a product truly user-centered isn't the absence of confusion — it's the presence of helpful, human support right when it's needed.

01 — Real-world story

The IKEA manual nobody reads — until they do

Real-world analogy — the flatpack wardrobe

You try without it. Then you reach for it. And it saves you

Most of us have a love-hate relationship with IKEA. You buy a wardrobe, carry it home in a flatpack box, and what do you do first? Try building it without the manual.

Then — 45 minutes and a few misplaced wooden dowels later — you reach for the booklet. And it saves you. Not because you're bad at assembling things. But because the manual was designed well enough to be useful exactly when you needed it.

The best IKEA manuals use clear visuals showing exactly where each part goes, avoid paragraphs of confusing text, highlight warnings with recognisable icons, and offer troubleshooting steps at the end.

Now imagine if IKEA gave you just the parts with no manual at all. That's exactly how a product without good documentation feels.

Same product. Same parts. The manual isn't the product — but its presence or absence defines the entire experience of building it.

02 — The old vs new approach

From "RTFM" to "We've got you."

Old approach

"RTFM — Read the Manual."

Help was the user's problem. Documentation existed in dense manuals, technical wikis, and PDFs nobody read. If you couldn't figure it out, that was on you. The product didn't need to care.

Modern UX standard

"We're here when you need us."

Help is designed as part of the experience. Contextual tooltips, inline examples, onboarding flows, searchable FAQs — designed to meet users at the point of confusion, not after they've already given up.

"The shift isn't just philosophical — it's practical. Help that's hard to find is help that doesn't exist. The best documentation feels like part of the product, not an afterthought bolted on the side."

— The shift in H10

03 — Help patterns in UX

How good products embed help into the experience

There are many ways to provide help — and the best ones don't interrupt the user's task. They sit quietly at the point of confusion, ready when needed, invisible when not.

Inline tooltips

Small contextual hints that appear when a user hovers or focuses on a field. No page navigation needed — help comes to the user.

Searchable FAQs

Help content that users can search by what they're actually trying to do — not by how the product team categorised it. Real questions, real answers.

Contextual hints

Hints that appear based on what the user is doing — not randomly. If a user hesitates on a step, the system surfaces relevant guidance automatically.

Always-visible support

A Help or Support option that's always accessible from the menu — not buried five levels deep. Users shouldn't have to work to find help.

04 — Embedded help

Help as part of the experience, not separate from it

The difference between good and bad help isn't the quality of the content — it's the placement. Help buried in a separate documentation portal is rarely found in the moment of need. Help embedded at the point of confusion is exactly what users need, exactly when they need it.

Same form. Left: the user is confused and help is a scroll away. Right: a question mark icon reveals the format inline — help appears at the exact point of confusion, without leaving the task.

05 — What to design for

Support users with empathy

Make help easy to find — no one should have to dig for it

Help options should be visible and accessible from anywhere in the product. If users have to search for your Help section, it's already too hard to find.

Embed help within the experience

Tooltips, inline hints, onboarding overlays, contextual icons — these meet users at the point of confusion, not after they've already given up.

Use visuals, examples, and simple language

Help content should be as carefully designed as the product itself. Clear screenshots, plain language, concrete examples — not technical jargon and dense paragraphs.

Don't punish users for needing help

Needing help is human. The tone, accessibility, and design of your help system should make users feel supported — not embarrassed for not knowing.

06 — Closing thought

The best products are still there when they're hard

Even the most intuitive designs can confuse someone at some point. That's not a failure of design — it's a reality of designing for millions of different people with different backgrounds, contexts, and expectations.

What makes a product truly user-centered is not the absence of confusion — but the presence of helpful, human support right when it's needed. The IKEA manual nobody reads until they need it — but when they do, it's exactly right. That's the standard.

The closing thought of the series

Great UX is not just about making things easy. It's about being there when they're not.

★ 10-week series — complete

NN heuristics as I see it

Ten weeks. Ten heuristics. Ten real-life stories that connect design principles to the world we actually live in. From dosas to dance classes, from wash basins to WhatsApp — UX really is everywhere.

What's next

This series is complete — but the thinking continues. New articles exploring design communication, designer growth, and empathy in practice are coming. The goal remains the same: helping designers see UX everywhere, not just on screens.