Confusion is the enemy — even inside your own stack

Nobody would ship a landing page with forty fields above the fold and call it done. You'd know on sight it was broken: too much at once, no clear next action, confusion doing what confusion always does, which is send people away.

Then we open Salesforce and do exactly that to our own team.

The lead layout has two hundred fields. The dashboard has nine charts and no headline. The "new opportunity" flow asks for information the rep couldn't possibly have yet. Somewhere a well-meaning ops person added every field anyone ever requested, and now the people who live in the tool eight hours a day are paying a confusion tax we'd never dream of charging a prospect.

Here's the reframe that changed how I build internal tools: your sales team is a user. Your CS team is a user. The exec skimming a pipeline dashboard on their phone before a board call is a user. They have intent, limited attention, and somewhere better to be — same as any visitor to a landing page. The care you'd bring to a homepage is the care the tool deserves.

What that looks like in practice:

• A record layout shows what the rep needs to act on right now and hides the rest behind a click. Not every field carries equal weight; the layout should say so.
• A dashboard leads with the answer, not the data. "Pipeline is $4.2M, down 9% week over week, driven by two slipped enterprise deals" up top. The charts are the evidence, not the headline.
• A form asks only for what the person can actually provide at that step — nothing that could be derived, defaulted, or filled in later by a job.
• Every tool has one purpose you can state in a sentence. If you can't, that's the bug.

That last one is the whole game. Years ago I wrote about web design and hammered on a single idea: design with purpose, because confusion is your worst enemy. A site that doesn't tell you what to do loses you. An internal tool that doesn't tell your rep what to do loses something more expensive — their belief that the system is worth using. That's the moment they go build a shadow spreadsheet, and your data integrity quietly starts to rot.

An example. I inherited a lead-routing view once that showed every rep every unworked lead in their region, sorted by created date. Technically complete. Functionally useless — nobody could tell which of four hundred rows to touch first, so they touched whatever sat on top, which was the oldest and coldest. We cut it down to one question: who should I call next? One list, scored, ten names, refreshed hourly. Same underlying data. The only change was deciding what the tool was for and deleting everything that didn't serve it.

You can run this test on any internal tool you own. Sit a real user in front of it and watch — don't explain, just watch. Every place they hesitate, squint, or ask "wait, what am I looking at?" is a confusion tax you've been quietly charging your own team. Then do the unglamorous work: cut, reorder, and relabel until the hesitation is gone.

Building internal tools people actually want to use isn't a lower bar than building a good landing page. It's the same bar. The only real difference is that your users can't bounce — they just stop trusting the thing, which is worse.

Your team is a user. Confusion is still the enemy. Build like they could leave.