Information architecture for how buyers actually think

Look closely at most B2B websites and you can reverse-engineer the company's org chart from the navigation. There is a tab for each team, a page for each internal function, a structure that makes perfect sense to the people who built it and very little to the buyer trying to work out whether the product solves their problem. The site is a map of the company. It should be a map of the decision.

Why do B2B sites mirror the org chart?

This happens for an understandable reason. The site gets built by the people inside the company, and they know it from the inside. They know that the platform team and the services team are different, that this feature belongs to one product line and that one to another. So the navigation quietly reflects those internal boundaries, because to the people making it, those boundaries are obvious and real. To the buyer, they are invisible and irrelevant.

How do buyers move through a site?

Buyers do not arrive thinking in departments. They arrive with a problem and a question. Can this help me do the thing I am trying to do, is it credible, and is it for a company like mine. Good information architecture organises the site around that journey, so that each step answers the question the buyer is actually asking at that moment, in the order they ask it. The structure does the selling, before a word of copy is read.

How do you design information architecture around the buyer?

The way to get there is to stop starting from the sitemap and start from the buyer. What is the first thing they need to understand, what would they need to believe next, and what is the last reassurance they need before they act. Those questions produce an order, and that order is your architecture. It rarely matches the org chart, and it should not. The buyer does not care how you are organised. They care whether you understood them.

How can you test whether the structure works?

There is a useful test for whether the structure is working. Give someone who has never seen the site the question a real buyer has, and watch them try to find the answer. If they hesitate, or backtrack, or end up somewhere that clearly was built for a different reader, the architecture is telling them about you when it should be answering them. Every moment of that friction is a moment where a good prospect decides it is easier to look elsewhere.

Structure is not the glamorous part of a website. It is easy to skip past on the way to the design. But it is the part the buyer feels first and remembers longest, because it is the difference between a site that seems to understand them and one they have to decode. Build it around how they think, not how you are arranged, and everything you put on top of it works harder.