Redesigning a high-risk enterprise IVR builder for safety and scale

// SCENE 01

Context & business goal

Ipscape's IVR management system ('Vault') let operations teams create and maintain voice workflows for high-volume contact centers. Over time it had become too complex to safely use, inflexible, and highly dependent on engineering for changes.

// SCENE 02

The challenge

• ▸No way to visualize complete workflows — only partial, local views.
• ▸Editing was 'dangerous' — removing an object could silently break the flow.
• ▸Impossible to add objects mid-flow safely. No warnings, validation, or safeguards.
• ▸No visibility into dependencies between workflows.
• ▸Missing essential objects: voicemail, capture/record, callback logic.

// SCENE 03

Discovery

• ▸Mapped the existing system, objects, and editing failure modes.
• ▸Benchmarked Typeform, Salesforce, and Zendesk for canvas-based editing, drag-and-drop composition, multi-select, history/undo, preview & validation.
• ▸Interviewed admins, ops, and engineers — surfacing 'dangerous' editing, no audit history, no full-path preview, fragile dependencies.

// SCENE 04

Experience principles for IVR 2.0

• ▸Safety by default — warnings, validation, safe edit modes, undo/history.
• ▸Full visibility — always show complete IVR architecture.
• ▸Flexible editing — add, remove, move objects anywhere without breaking the flow.
• ▸Scalable logic composition — drag-and-drop, templates, reusable patterns.
• ▸Cross-workflow awareness — visualize links and dependencies.
• ▸Low cognitive load — clear naming and grouping aligned to how ops teams think.

// SCENE 05

Reflection

A systems-thinking, risk-aware redesign of a high-stakes internal tool where architecture — not UI polish — was the real challenge.