Understand the Human · Website & Content
The basic truth
Most websites are organized the way the company is organized.
Navigation named after divisions. Products grouped by the line they’re manufactured in. A resources section that mirrors which department produced each file. It all makes complete sense from the inside, because from the inside it is the structure — it’s how the meetings are run and how the budget is split.
The visitor doesn’t have your org chart. They arrived with a question, and the question doesn’t respect your departments. “Can this cut the material I actually use?” touches three product lines, two support articles and a spec sheet nobody has updated. So they hunt, and hunting is expensive attention that was supposed to go toward deciding you were competent.
If your site structure is legible to your employees and confusing to your buyers, it’s serving the wrong people.
What to do
Organize around the job, not the catalogue. Industrial buyers think in applications: the material, the thickness, the tolerance, the volume, the thing they’re trying to produce. They do not think in product families — those are your categories, invented for your convenience.
You don’t have to throw out the product structure. You have to add the door people actually walk through, and the application view is usually it.
Write for the seat, not the average. There is no average visitor — the average of an engineer and a CFO is a person who doesn’t exist, and designing for them produces a site that fits nobody. The same purchase gets researched from several seats, and each needs something different to be able to say yes:
| Who’s reading | What they need to find | What convinces them |
|---|---|---|
| The engineer | Specs, tolerances, materials, real comparisons | Detail that survives scrutiny |
| The operator | Setup, training, maintenance, support | That it won’t become their problem |
| The owner / CFO | Cost of ownership, lead time, downtime risk | That this is a defensible decision |
| Purchasing | Terms, availability, alternatives, references | That they can justify it upward |
Assume they’re scanning, not reading. People take the first acceptable answer, not the best one — they satisfice. That’s not laziness, it’s how anyone gets through a workday. So the useful question isn’t “is the answer on the site?” It’s “is the answer findable by someone who is skimming, mildly annoyed, and about to try a competitor instead?”
Lead with the consequence, not the property. A homepage can proudly explain the tensile strength of a new alloy without ever mentioning what that does for the person reading — that it means fewer stoppages, or a part that stops failing in the field. The specification is true and it belongs on the site. It just isn’t the reason anyone cares.
The common trap
Building the site you would want if you already knew everything you know.
This is the honest version of the trap, and it’s why it’s so hard to see. Nobody sets out to write an inward-facing website. It happens because the people building it are experts, and experts genuinely cannot remember not knowing. Your acronyms feel like plain English. The distinction between two of your product lines feels obvious. The order of the navigation feels natural because it matches the order in your head.
Every one of those is a small tax on a stranger, and they compound.
The related failure is designing for the average, which feels rigorous and is actually a way of avoiding the harder question of who specifically. Averages smooth away exactly the differences that determine whether a page works — and a page written for everyone is usually a page that persuades no one, because it never gets specific enough to be useful to anybody in particular.
The tell: you have to explain your own website to people. If your sales team routinely says “it’s under Resources, then Technical, then scroll down” — that’s not a training issue. That’s the site telling you it was built from the inside.
The deeper judgment
Understanding your buyer is not a phase you complete before the build. It’s visible in the structure afterward, and it’s visible to strangers within seconds.
Anyone can tell the difference between a site organized by people who talk to customers and one organized by people who talk to each other. They can’t always articulate it — they just experience one as “this company gets it” and the other as vague unease, and then they leave. They punish the confusion silently. You never get the complaint; you get the absence.
Which is the uncomfortable part: your site is also where you find out whether you understood. The behavior is the answer — what people look for, where they stall, what they never find. That makes this cell inseparable from Improve With Wisdom × Website & Content: diagnose before you redesign, because a redesign that skips the diagnosis just rebuilds the same misunderstanding in a newer typeface.
And underneath: do not remove expertise from the moments where trust is being formed. A website is where most B2B trust now forms, long before anyone calls. The structure of the thing is an expertise decision, not a design decision — and it’s usually made by whoever is least likely to have talked to a customer that week.
Where this thread goes
Structure gets them to the right page. What’s on it decides whether they believe you.
- Show the expertise, the proof, and the people — Earn Trust · Website & Content
- Diagnose behavior before you redesign — Improve With Wisdom, Not Hype · Website & Content
- Same buyer, one moment earlier — before they ever reached the site — Understand the Human · Search & Advertising