OmniGraffle 7

OmniGraffle interface displayed on a MacBook Pro showing a multi-level diagram with sidebar outline and inspector panels visible. — OmniGraffle 7 canvas demonstrating complex hierarchical diagram construction with integrated outline navigation and live inspector controls.

Repositioning a Flagship Product Under Financial and Cultural Risk

Context

OmniGraffle was the company’s best-selling application and a primary source of revenue. A major redesign carried meaningful financial risk. If the release underperformed, it would directly impact the company’s stability.

At the same time, the product was showing signs of stagnation. Competing vector and diagramming tools had adopted modern workflows, and users increasingly expected capabilities like artboards. OmniGraffle did not have them. We were losing users to tools that better reflected contemporary professional workflows.

Internally, there was tension. Omni’s culture is deeply engineering-driven, and its products often evolve from the needs of the people building them. Not everyone felt artboards were necessary. Some believed users didn’t need them. Others worried about complexity or disruption to the drawing model.

I believed we were behind market expectations and that the absence of artboards signaled stagnation. I bet significant internal credibility on that position.

Flagship revenue product under structural risk.
Loss of professional users.
Internal resistance to modernization.

The Structural Risk

The risk was not cosmetic. It was strategic.

Without artboards:

We were losing professional users who relied on structured canvases.
We were behind industry standards across vector tools.
The product risked becoming irrelevant in modern workflows.

Artboards were not just a feature request. They were a signal. They communicated whether OmniGraffle was evolving with the market or retreating into legacy behavior.

Getting this wrong meant more than shipping an unpopular feature. It meant risking revenue decline in the company’s most important product.

Product Tension

The CEO supported modernization but encouraged open internal debate. Engineering concerns were valid. The drawing model was complex, and adding artboards required significant backend architectural work.

There were also design tensions. Some advocated for introducing patterns that differed from how Omni’s other apps worked. I pushed back on that. Consistency across the product suite mattered. Introducing divergence for the sake of novelty would increase friction and hurt adoption.

This required repeated arguments, evidence from research, and continued pressure to align around market reality rather than internal preference.

Research and Validation

We conducted:

Pre-development interviews with experienced users
Usability testing on OmniGraffle 6
Analysis of workflow inefficiencies
Evaluation of feature requests and competitive parity

Findings showed:

50% of interviewed users cited the absence of artboards as a serious limitation.
60% requested improvements to Bezier editing.
70% emphasized workflow speed as a priority.
Task success rates revealed friction in common workflows.
New users struggled significantly with onboarding.

The need for structural modernization was clear.

The Architectural Decision

Implementing artboards required changes to the drawing model that many believed would be too disruptive. I worked closely with engineering to explore what was feasible inside the constraints of macOS and existing architecture.

OmniGraffle workspace showing a production workflow diagram split between development and production phases, with color-coded process steps. — Large-scale process mapping in OmniGraffle, illustrating support for detailed, multi-phase workflows across structured development and production timelines.

The implementation ultimately pushed the backend toward more modern frameworks. What began as resistance became an opportunity to evolve the technical foundation in a way that benefited the product long term.

Diagram explaining how an artboard layer in OmniGraffle contains masks and controls the movement of layers above it, while layers below remain unaffected. — Conceptual model illustrating how artboards function as structural containers—isolating and controlling grouped layers without impacting the broader canvas hierarchy.

Artboards improved:

Canvas organization
Asset export workflows
Multi-layout project management
Professional design parity

Structural backend modernization.
Architectural investment tied to market repositioning.

Onboarding as Financial Stabilization

The redesign introduced substantial change, which always carries risk.

We revamped onboarding to:

Clarify new workflows in plain language
Introduce artboards clearly
Reduce first-session confusion
Support new user adoption

OmniGraffle 7 welcome screen featuring links to What’s New, Manual, Slack Channel, Forums, and Support resources. — Onboarding experience for OmniGraffle 7, designed to orient users quickly and connect them to documentation, community, and support resources.

Onboarding reduced friction at the moment of change and softened the financial risk associated with a major structural update.

Results

Following the release:

Download-to-trial conversion increased by 23% on the App Store.
Website conversion increased by 16%.
Sales increased by 33% compared to the same release window of the prior version.
OmniGraffle 7 remained a top-10 grossing app for seven weeks.
Workflow efficiency improved by 12% in usability testing.

23% conversion lift.
33% revenue growth in release window.
Top-10 grossing app for seven weeks.

More importantly, the release repositioned the product in the market. It demonstrated that OmniGraffle was willing to evolve alongside professional expectations rather than protect legacy design decisions.

Reflection

Products cannot be built solely to serve the preferences of the people inside the company. Market expectations matter, especially when revenue depends on them.

Architectural hesitation often masks strategic risk. Sometimes the harder technical path is the safer business path.

Modernization is not about chasing trends. It is about recognizing when a product is falling behind structural expectations and being willing to bet credibility on correcting that course.

In this case, that bet paid off.