Density isn't the problem.

The 737 first flew in 1967. The cockpits get updated, but the way pilots read information hasn’t changed much. Dense, unstyled, all the data at once. Pilots are trained to read it and act on it under pressure.

Now they bid for vacation, training, and lines on a company-issued iPad.

The first time I ran research sessions on the Vacation Bidding tool, I expected pilots to push back on density. They didn’t. They asked for more.

Experienced pilots wanted every column. Every filter. Every sort. No limits on the data. Don’t hide it behind a “show details” link. They were already doing the math in their heads. The screen just had to keep up.

Newer pilots wanted something different. Less time in the cockpit, less fluency with raw data, more comfort with iPads. They wanted hand-holding. Saved views, guided flows, weighted sorting where the app does some of the prioritizing for them. They built their bids by leaning on the structure the tool offered.

Both groups want all the data. They want it presented differently.

You can’t strip features to “simplify” because experienced pilots will be frustrated. You can’t lead with raw density because newer pilots will be lost. Every screen has to carry the data and the structure to navigate it, without the structure becoming its own kind of clutter.

We landed on a pattern: every bidding flow has a power-user mode and a guided mode, sharing the same data. Density is available.

Most UX advice tells you to reduce cognitive load. Hide complexity. Use progressive disclosure. For consumer products with general-population users, that advice is right.

For expert users in shifting domains, it’s incomplete.

The job isn’t to simplify. It’s to make density navigable for fluent users and learnable for new ones.