Organizing complexity. How LinkedPhone turned one of its most powerful features from an intimidating configuration tool into a system small businesses could actually understand.
Act 01Context
For some businesses, Auto Attendant was the reason they chose LinkedPhone in the first place.
It let a small business behave like a much larger organization. Calls could be routed. Messages could be played. Voicemails could be collected. Teams could receive calls based on conditions. Customers could be guided toward the right destination.
In theory, it was one of the most powerful capabilities in the product. In reality, most customers barely scratched the surface.
The feature was valuable.
The feature was sticky.
The feature was powerful.
But it was also intimidating.
And that contradiction became the beginning of the redesign.
Chapter theme
The challenge was never building a powerful routing system. It was helping people feel confident enough to use it.
"We thought users needed more configuration. What they actually needed was more confidence."
Executive Summary
Challenge
Auto Attendant was one of LinkedPhone's strongest differentiators, yet only a small share of customers ever explored its full capability. Most stopped at basic setup. Advanced configuration went unused.
Breakthrough
We first approached it as a configuration challenge. Eventually we understood it was a confidence challenge. The answer wasn't exposing more power. It was revealing complexity gradually.
Outcome
A single modular architecture where basic and advanced setups became the same system. Users could start simple and scale their configuration as their needs, and their confidence, grew.
Transformation at a glance
Where We Were
Before the redesign, Auto Attendant already existed. Customers used it. Some had specifically purchased LinkedPhone because of it. It was one of the product's strongest differentiators.
However, adoption patterns revealed something interesting. Only a relatively small percentage of users created anything beyond basic routing. Most configurations stayed extremely simple. Many businesses never explored the more advanced possibilities available to them.
The feature suffered from an unusual problem.
It wasn't failing.
But it wasn't reaching its potential either.
Three versions existed at once
The live product, before
Every decision point highlighted, every friction point called out, every confusing interaction marked.
The three states of Auto Attendant, side by side. The challenge wasn't simply improving UI. It was understanding why people stopped.
Act 02Problem
The Problem
On one hand, business owners wanted flexibility.
On the other, business owners wanted simplicity.
Most solutions on the market solved one side. Very few solved both. Enterprise tools generally looked like node builders, flow editors, complex diagrams, technical workflows: large canvases with many states, many decisions, many possibilities.
While powerful, these solutions assumed users already understood how call-routing systems worked. Most LinkedPhone customers didn't. They weren't trying to design call systems. They were trying to answer customers.
Existing setup, annotated
Every decision point highlighted, every friction point called out, every confusing interaction marked.
Customer impact
Users became overwhelmed. Most configurations never progressed beyond basic setup. Advanced functionality stayed hidden behind complexity.
Business impact
One of LinkedPhone's strongest differentiators was underutilized. Customers received only a fraction of the value available to them.
Internal impact
Future feature expansion would only get harder if the underlying architecture stayed difficult to understand.
Investigation
The first instinct was to look at the market. Competitors primarily used node builders, flow editors, workflow diagrams, visual routing systems. At first glance these seemed promising: they represented logic visually, exposed relationships, provided flexibility.
So we explored them. Multiple concepts were built around node-based systems, flow builders, branching architectures, visual routing maps.
Initially they looked impressive.
During design reviews they felt powerful.
During testing they started breaking.
As users interacted with them, a pattern emerged. People spent more time understanding the interface than configuring their business. The software was teaching itself, not helping users achieve outcomes. That observation became critical.
Research question
What if users shouldn't need to understand routing systems at all?
Investigation wall
Competitors, mental models, user observations, node-builder explorations, testing notes.
Insights
Notes, sorted into four themes
Every quote and observation clustered until the same four patterns kept surfacing.
Insight 01
Users wanted outcomes, not systems.
Insight 02
Users rarely start advanced.
Insight 03
Confidence drives exploration.
Insight 04
Power isn't the enemy. Exposure is.
Act 03 · Turning Point
We thought users needed more configuration.
They needed more confidence.
This became the turning point. The goal shifted: from building a more powerful interface to helping people progressively understand complexity. Everything changed after this realization.
Exploration Lab
Every direction taught us something, including the ones that failed. Especially the ones that failed. Each was scored against the same two questions: was it simple, and was it still powerful?
Direction A
Direction B
Direction C · The winner
The percentages above are illustrative evaluation scores from the exploration process, not measured data.
Evolution tree
Breakthrough
Instead of building separate systems for basic and advanced setup, we merged both into a single architecture. Users would only ever see what they needed right now. Complexity stayed available, but hidden until necessary.
The interface started behaving like Lego blocks. Simple blocks. Composable blocks. Expandable blocks. Reusable blocks. Users could build complexity without ever feeling overwhelmed.
One architecture, four depths
The same building blocks, revealed one layer at a time. Depth is a choice the user makes, never a wall they hit.
Composable, not configured
Small blocks that snap together instead of one dense settings panel.
Complexity didn't disappear. It just stopped arriving all at once.
Act 04System
System Architecture
The final architecture revolved around a single, legible grammar.
Basic users
One trigger, one action.
Nothing else on screen. It just works.
Advanced users
Multiple conditions, multiple actions, nested logic.
The same grammar, more deeply composed.
The point
Same system. Different depth.
No one is ever moved to a "pro mode." They grow inside the one they already know.
Design principles
01
Reveal complexity gradually
02
Maintain confidence at every step
03
Keep outcomes visible
04
Encourage exploration, preserve power
Design System Impact
Auto Attendant reinforced a whole family of design-system patterns, and became one of the strongest stress tests of the emerging system.
Every pattern Auto Attendant produced, and how they connect back to the product. Six patterns, one product, one shared grammar.
List structures
Pattern
Progressive disclosure
Pattern
Cards
Component
Accordion behaviors
Interaction
Contextual actions
Pattern
State management
System
Product Showcase
Each screen exists to answer three questions: what problem it solves, why it exists, and how it works. The reasoning matters more than the aesthetics.
The routing overview
A calm home for every rule a business has built, legible at a glance regardless of how deep it goes.
Problem. Users lost track of what their system actually did. Why. Orientation has to come before configuration. How. One scannable list, depth on demand.
Basic setup flow
One trigger, one action, and a business that's answering calls in under a minute.
Problem. First-run intimidation stopped adoption. Why. Early success is what unlocks everything after it. How. The simplest possible expression of the shared grammar.
Advanced configuration
The same interface, deeper. Conditions and branches appear as the user reaches for them, never before.
Problem. Power users previously needed a different tool. Why. Growth should never mean starting over. How. Progressive disclosure inside the same object.
Every other state, at a glance
Add a block
Composable expansion.
Fallbacks & errors
What happens when no rule matches.
Interaction & Motion
Auto Attendant leaned heavily on interaction design. The motion wasn't decoration. It was how the system explained itself.
Accordion expansion
Reveal in place
Context preservation
Never lose your place
Progressive disclosure
Depth on demand
Hierarchy transitions
Level in / out
Expandable logic
Branch as needed
State feedback
Always legible
Accordion motion study
When a section opens, the surrounding context stays visible and stable. Confidence, encoded in motion.
Act 05Impact
Validation
Testing happened continuously: internal reviews, user testing, founder feedback, customer feedback, even friend testing. Patterns consistently pointed the same way.
Simple first.
Advanced later.
Directional results shown; specific figures live in the private appendix.
Ripple Effects
The concept of progressive disclosure escaped Auto Attendant and reshaped how LinkedPhone thought about complexity itself.
Auto Attendant to Design System to Information Architecture to Desktop to Unified Work Model to Lisa. Most importantly, it changed how the company thought about powerful software.
Archive
Available, but never required. Everything that produced the thinking above.
Original deck
Embed
Exploration boards
Figma
Research notes
Doc
Testing outputs
Video
Competitor analysis
Board
Flow maps
Diagram
Lessons
Lesson 01
Complexity isn't the enemy.
Hidden complexity isn't the solution either. The real challenge is revealing complexity at the right moment.
Lesson 02
People don't learn systems. They learn confidence.
Master the emotion and the mechanics follow.
Lesson 03
The most powerful feature isn't the most valuable.
The most understandable feature is.
Lesson 04
Progressive disclosure scales better than simplification.
You don't have to remove power to remove fear.
Legacy
The project fundamentally changed how we approached complexity across LinkedPhone. The lessons learned here later reappeared in Desktop, the Work Model, 10DLC, Website, and Lisa.
The feature itself became more usable. But the larger impact was changing how the entire organization thought about powerful software.
Closing
Power is easy. Clarity is hard. The goal was never to make Auto Attendant more capable. It was to make capability feel approachable.