Back to Work 0→1 Product · Mobile · Brand

Wing Tel Alpha

Building product systems before I had the vocabulary for it. Founding designer for a telecom startup — mobile app, web dashboard, component library, and brand, all from scratch. Scaled to 5,500 users.

Role Founding Designer (Solo)
Timeline 2016 – 2017
Platform Mobile (iOS) · Web
Tools Sketch · Illustrator · Photoshop · Invision

Building Product Systems Before I Had the Vocabulary

Wing Tel was an MVNO — a Mobile Virtual Network Operator offering transparent mobile plans. As the sole designer, I built every layer of the product from scratch: brand, app, web dashboard, and a component library. The thinking I developed here — reusable components, state systems, information hierarchy — is the same thinking I now apply at enterprise scale.

5,500
Active Users Scaled To
During my time as founding designer
Product covered full account management: plan selection, usage tracking, billing, topping up, and customer support.
0→1
Full product built from scratch
No existing design system, brand, or patterns
iOS + Web
Platforms designed
Mobile app + web account dashboard
7
Core deliverables
App · Dashboard · Brand · DS · Marketing · Ads · User flows
2016
Component system built
Before "design systems" was common language

Mobile App, Brand System & Design Thinking

Wing Tel typography system and iOS app mockups
Typography system — Fira Sans and Avenir
App prototype screens — usage dashboard and billing
App information architecture and flow diagram
App prototype — payment and empty states
Wing Tel color system
Wing Tel web — plan selection page
Wing Tel marketing website homepage

How I Actually Built It

Mobile-First Telecom UX

Telecom Has Unique Complexity

Users primarily manage accounts on mobile. That meant every interaction had to be instantly scannable:

  • Usage at a glance: data/minutes/texts on home screen
  • Quick actions: top-up and plan changes in 2 taps
  • Transparent billing: clear breakdown of charges, no hidden fees
  • Self-service: reduce support calls through intuitive design
Early Design System Thinking

Component Architecture From Day One

Even without the formal language of design systems, I built with reuse in mind:

  • Buttons: 3 types, 4 states each
  • Form inputs: text, dropdown, radio, checkbox
  • Cards: usage cards, plan cards, billing cards
  • Navigation: tab bar, header nav
  • Status indicators: badges, progress bars, alerts

Engineers could reuse components across features without custom design work — accelerating development and maintaining consistency as the product grew.

Account Management Patterns

Complex Data, Simple Interface

Telecom account management is inherently complex: usage over time, multiple lines, billing history, security. I designed patterns that handled this:

  • Card-based layouts for scannable information
  • Progress bars for usage visualization
  • Color-coded status: green = safe, yellow = warning, red = limit
  • Clear CTAs for the most common actions
What 0→1 teaches you

When there's nothing to inherit, every decision is yours. You learn to establish design direction without a brand, build systems from first principles, make confident calls with incomplete information, and communicate rationale to engineers and founders who need to trust your judgment. It's the hardest and most formative design experience I've had.

What This Work Taught Me

01

Starting from zero teaches you things working on mature products doesn't

There's no existing system to inherit, no design lead to check with, no brand guidelines to reference. Every decision is yours — which is uncomfortable until it isn't. Wing Tel is where I learned to make confident design calls with incomplete information, because waiting for certainty wasn't an option on a 4-person team with 3 months of runway.

02

Domain Knowledge Matters

Telecom UX has unique constraints: regulatory requirements around terms and privacy, technical complexity around network status and data throttling, customer expectations around reliability and billing clarity. Learning a domain deeply — not just its UI patterns but its actual business logic — makes you a better product designer in any domain.

03

Founding Team Dynamics

As a founding designer, you're not just executing — you're influencing product strategy. Communicating design rationale, prioritizing features with limited resources, knowing when to push back and when to ship fast: these are strategic skills that sit alongside craft. Wing Tel is where I first learned how to work at the intersection of design and product decision-making.

See where this led

Workhuman Careers Refresh

Product design — rebuilding a funnel that was losing 97% of candidates

View Case Study All Work