— Reflection
What this taught me about leading a multi-surface data product.
The hardest design problem was the seams, not the surfaces.
Each of the five Atlas surfaces was a meaningful product on its own. But the value the operator actually felt was in the seams: the moment a Pinpoint topic appeared inside an Insights paragraph, or a segment built in Explorer pre-filtered Pinpoint, or a peer benchmark surfaced exactly where a number was being read. The work that mattered most rarely showed up in a single screen.
A data product earns its keep by answering the operator's job, not the analyst's curiosity.
The temptation in enterprise analytics is to ship more dimensions, more filters, more configurability. Atlas went the other direction: each surface was sized to a specific question an operator already had on Monday morning. The value of constraint was that operators trusted the answers they got, because the answers were calibrated to their actual decisions.
The right unit of design leadership is the operator's day, not the feature.
Across five surfaces and several years of build, the question I kept returning to was the same: what does a brand-marketing director actually do on a Monday morning? Designing against that question pulled the team out of feature-by-feature thinking and into a workflow we could measure end to end.