Fortune 100 Planning Tool

Jacques Ramphal·3 min read

A strategic planning interface for an organization managing data across business units, budgets, and initiatives at scale.

Key Learning

Enterprise tools fail when they try to show everything or summarize everything. The design problem is finding the layer in between.

Overview

The data existed. What the organization didn't have was a way to look across it without collapsing the complexity that makes it useful.

Enterprise planning tools tend toward one of two failure modes: show everything (overwhelming) or summarize everything (useless). The challenge was finding the layer in between: a view that gave decision-makers enough overview to act while preserving the detail that mattered. The users were executives and planners making resource decisions on tight timelines, not analysts who lived in the tool.

The Constraint

The organizational data had multiple layers, multiple owners, multiple formats, and flattening it to make it displayable would have destroyed its value.

Finance owned budget, operations owned initiatives, leadership owned the cross-unit view. None of those pieces had ever lived in the same interface before. Getting them into a single tool required careful decisions about what surfaced by default, what required a tap to reveal, and what could safely live a level down.

Approach

Navigation as the primary problem

The instinct in data-heavy tools is to reach for visualization — better charts, more filters, richer displays. These users were executives and planners making resource decisions on tight timelines, not analysts who lived in the tool. The design problem was navigation: how a user moves from overview to a specific line item and back without losing their place.

The hierarchy went portfolio → business unit → initiative → detail. Each layer had a distinct visual treatment that made it immediately recognizable. Transitions between layers needed to feel continuous rather than disjointed.

Data kept legible

Charts only appeared where a chart communicated something a table couldn't. That constraint requires constant pressure to maintain. There's always a request for a graph, and most of the time a well-structured table serves the actual need better. Keeping visualization conservative preserved the readability the tool's value depended on.

Outcome

The tool launched and became the primary planning interface for the organization, replacing a process that had run across disconnected spreadsheets and email threads.

Strategic planning moved from a fragmented, document-driven process into a shared interface with a common vocabulary. The client came back with iteration requests rather than structural concerns, which for a first version is the outcome you want.

What I Learned

When an interface stops being something people think about and becomes something they just use, the design has done its job. That's a harder standard than visual quality or feature completeness, and it takes longer to know whether you've met it.