The foundation. Before LinkedPhone could redesign its product, it had to redesign how the company understood itself.
Act 01Context
Over three years, LinkedPhone evolved from a simple business phone system into a growing platform: communication tools, customer workflows, automation, AI, compliance infrastructure, a website, onboarding, eventually an AI receptionist.
The product was growing. The company was growing. The complexity was growing.
But something else was happening underneath. Everyone was slowly developing a different definition of what LinkedPhone actually was.
Most case studies begin with a product. This one begins with a company.
Chapter theme
The challenge was never scaling features. It was scaling understanding.
A wall of a hundred sticky notes, a dozen contradictions, slowly collapsing into one sentence: "LinkedPhone helps small businesses never miss an opportunity."
Executive Summary
Challenge
LinkedPhone had evolved rapidly across products, teams and segments. Different teams were solving different problems, and had quietly started describing the company differently too.
Breakthrough
The problem wasn't design consistency, product architecture, or branding. It was language. Before redesigning the product, the company needed to redesign how it understood itself.
Outcome
A shared language emerged: a common philosophy, vocabulary and definition of value. Every major initiative that followed, Inbox, Auto Attendant, the Website, Lisa, inherited something from it.
Transformation at a glance
Where We Were
When I joined LinkedPhone, the company already had a successful, straightforward product: business phone numbers, call routing, basic customer communication, simple team collaboration.
But growth introduces complexity. Every successful feature creates new responsibilities. Every new customer segment introduces new needs. Every solution creates new systems.
Over time the product expanded into messaging, a shared inbox, contact management, team collaboration, auto attendants, routing logic, compliance, a website ecosystem, AI capabilities, customer workflows. Each addition solved a real problem.
But collectively, they created a different one.
The company understood each individual feature. Fewer people understood the entire system.
Phone system to platform
Messaging, Inbox, teams, routing, compliance, automation, AI: every stage that was added, and how fast it arrived.
Act 02Problem
The Problem
One of the most surprising discoveries: nobody was wrong. But nobody was fully aligned either. Ask five teams "what is LinkedPhone?" and you'd get five true, incomplete answers.
"A modern business communications platform."
Marketing
"A tool for helping customers manage conversations."
Support
"A telephony infrastructure platform."
Engineering
"A business phone solution."
Sales
Every answer contained truth. No answer contained the whole truth.
Fragmentation was invisible.
Nobody woke up and said "we are fragmented," because fragmentation rarely feels like fragmentation. It feels like longer debates, slower decisions, confusing priorities, inconsistent messaging, design disagreements, product ambiguity. The symptoms appeared everywhere. The cause stayed hidden.
Investigation
Instead of jumping into solutions, the team started asking questions: cross-functional workshops, whiteboarding sessions, strategy reviews, product mapping, brand exercises, customer journey mapping, feature audits.
Not searching for features. Searching for meaning.
Questions asked
What business are we actually in?
What value do customers buy?
What makes us different?
What should never change, and what can?
Every team's answer, on the wall
Clusters forming around recurring themes, connections drawn, gaps highlighted.
Insights
Insight 01
The fragmentation was conceptual.
Insight 02
Features were leading the story.
Insight 03
Everyone had a different mental model.
Insight 04
Consistency starts before design.
Act 03 · Turning Point
We thought we were redesigning a product.
We were redefining a company.
The goal stopped being alignment on decisions, and became alignment on meaning. Not agreement, understanding. Everything since traces back to this shift.
Exploration Lab
Many directions were explored. Most failed quickly, for reasons worth keeping on record.
Phone Company
Rejected · too limiting
Communication Platform
Rejected · too generic
Software Suite
Rejected · too broad
Business Operating Layer
Interesting, too abstract
Direction D
Direction E · The winner
The percentages above are illustrative evaluation scores from the exploration process, not measured data.
Breakthrough
Not branding. Not marketing. Not design. Several themes kept resurfacing across every workshop until they became undeniable, and became the company itself.
The shared language framework
Design systems don't create consistency. Shared language does.
Act 04System
System Architecture
A shared language only matters if it changes what gets built. It needed to run all the way down to individual product decisions.
One word, traced all the way down to a shipped decision. This is the chain every later chapter runs through.
Design System Impact
Visual design
Cleaner interfaces
Content design
Consistent terminology
Interaction design
Confidence-driven onboarding
Information architecture
Clearer navigation
Component systems
Shared patterns
Shared expectations
Across every team
Product Showcase
Rather than show a single screen, the evidence is everything that came after: each later chapter is what happens when a company finally agrees on what it's building.
Interaction & Motion
Simple onboarding. Guided creation. Progressive disclosure. Contextual help. Every interaction pattern that followed was built to reduce intimidation and raise confidence, the same two words from the framework above.
Act 05Impact
Validation
For the first time, different teams could explain LinkedPhone in remarkably similar ways.
Ripple Effects
This is one of the most important diagrams in the entire portfolio, because almost nothing after this chapter happened independently of it.
Shared Language to Design System, Auto Attendant, Beyond Scaling, the Work Model and the Website, to 10DLC and Call Intelligence, to the future AI platform. Every arrow on this page starts at this chapter.
Archive
Workshop decks
Embed
Whiteboards
Miro
Product maps
Doc
Voting sessions
Board
Brand explorations
Board
Architecture reviews
Doc
Lessons
Lesson 01
Features scale. Meaning fragments.
Growth multiplies capability faster than it multiplies shared understanding.
Lesson 02
Alignment is not agreement.
Alignment is shared understanding. You can disagree on tactics and still be aligned on meaning.
Lesson 03
Products become coherent when companies do.
Not before.
Lesson 04
The hardest design problem wasn't the interface.
It was the vocabulary underneath it.
Legacy
Every major initiative that followed inherited something from this work. Not a screen. Not a component. Not a workflow.
A way of thinking. And that became one of the highest-leverage design contributions of the entire transformation.
Closing
Most portfolios start at the screen. This one starts at the belief system. Every chapter after this one is what happens once a company finally agrees on what it's building.