Dossier 02 // Logic, Made Visible Case study · Design LeadershipStory time · Design Leadership

Designing the future of intelligent workflow automation

Transforming rule creation from a technical bottleneck into an intuitive visual operating system that is built for scale, owned by everyone, and far harder to outgrow.I sprung rule creation out of the code dungeon and turned it into a visual operating system anyone can play with. Built to scale, owned by everyone, and a lot more fun to use.

Role
Primary Design POC
Domain
Enterprise Automation
Scope
Strategy → Systems → Execution
Outcome
70% faster rule creation
01
The problem

Enterprise rule engines are broken by design

The tools that run business-critical automation were quietly failing the people who depend on them most. Logic lived in code, so operations teams couldn't touch it. Dependencies went undocumented, so workflows broke in production for reasons nobody could see. The pain wasn't cosmetic: it was structural, and it was expensive.

83%of ops teams needed an engineer to change even a simple rule
4xslower to get a workflow live vs. modern tooling
60%of failures traced to undocumented rule dependencies
12+stakeholders who couldn't audit logic without a developer

Baseline figures from the project's discovery phase.

02
The vision

An operating system for business decisions

Not a workflow tool. Not another rule engine. The bet was to treat visual logic as a first-class product: readable, scalable, and owned across the organisation instead of locked inside engineering. The market kept offering the same false trade: tools simple enough for business users were too shallow for the enterprise, and tools powerful enough for the enterprise were unusable for the people who actually run operations. This closed that gap.

03
The approach

Making complex logic feel simple

A visual node canvas

Logic flows left to right like thinking does. Drag-and-drop blocks map to real business concepts, and connective lines make every dependency explicit and auditable by anyone.

Progressive disclosure

Beginners land in a guided, templated space. Power features (branching, nested conditions) appear only as a user's actions signal readiness. The interface teaches as it expands.

AI as infrastructure

Embedded reasoning, not a chatbot: it recommends the next node, flags contradictory rules before production, and translates any workflow into plain-English anyone can read.

A system, not screens

Every component was decided at the system level: governed primitives, shared states, tokens. Adding a new surface takes minutes, not weeks, and stays consistent by construction.

The outcome

Design that moved the metrics that matter

70%faster rule creation vs. the legacy engine
45%fewer requests routed through engineering
60%faster onboarding to a first autonomous workflow
3xgrowth in active workflow builders across teams

Workflow error rates dropped measurably once visual validation rails and conflict detection shipped, translating straight into fewer production incidents.

The interface was the intervention: it didn't just build rules faster, it handed business teams ownership of their own logic.

Go deeper

The full interactive deck

The complete walkthrough: the problem landscape, the product vision, and the key design decisions that made complex logic feel simple.

intelligent-workflow-os · case study Open full ↗

Interactive case study

Loads an embedded presentation from gamma.site.

The working prototype

The rule builder: try it yourself

A clickable, interactive prototype of the visual rule engine. Build logic the way the case study describes.

rule-engine · prototype Open full ↗

Interactive prototype

Loads an interactive prototype from figma.site.