Operational Design Is Product Design

When I joined Ignite Reading as the first design hire, there were forty things broken. The product UI needed work. The tutoring experience needed refinement. The reporting dashboard was minimal. Any of these would have made a visible, portfolio-ready first project.

I chose to redesign the school onboarding spreadsheet.

Not because it was glamorous. Because every week the onboarding took to complete was a week 200,000 students did not get tutoring. The spreadsheet was not an operational problem. It was an academic outcome problem measured at a different layer of the company.

The leverage hierarchy

Most design work happens at the interface layer. Users see a screen, interact with it, and something happens. This is important work. It is also, in most mature products, not where the highest leverage lives.

The highest leverage usually lives one or two layers below the interface:

The operational layer — how the product gets deployed, configured, and maintained. If onboarding takes three weeks instead of three days, every feature behind that onboarding wall is three weeks less useful.

The data layer — what the product measures, how it measures it, and what decisions those measurements inform. At Verizon, the team had been measuring conversion at checkout. The actual problem was that customers were arriving at checkout with the wrong expectations because the configurator above it was showing the wrong price. The metric was correct. The diagnosis was wrong.

The organizational layer — how teams are structured, how decisions get made, how information flows. A product designed by a team organized around modules will feel modular. Reorganize around workflows and the product starts to feel integrated, without changing a single component.

Why designers avoid it

Operational design does not screenshot well. You cannot put a spreadsheet-to-platform migration on Dribbble. There is no hero image for "I spent six weeks talking to district administrators about their enrollment workflow."

But this avoidance is exactly why it is high-leverage. The best designers are competing for the visible work. The operational work is sitting there, uncontested, with disproportionate impact waiting to be claimed.

The trait I screen for

If I were hiring my replacement at any role I have held, the trait I would screen hardest for is whether they are willing to design a spreadsheet replacement with the same care they bring to a hero screen.

Most senior designers are not. They want the consumer-facing work. They want the redesign. They want the thing that goes in the portfolio.

The designers who change companies are the ones who look at the operational layer — the onboarding flow, the migration protocol, the career framework, the pricing model — and see it as design work. Because it is. It is just design work that most designers have been trained to look past.