The hard part is knowing what not to fix

Before I design anything, I want to see how the work actually happens: who gets stuck, where the time goes, which step everyone quietly dreads. Then I find the one change worth making and prove it with a small live pilot before it scales, so the fix is earned rather than assumed. Only then do I design the interface that carries it. I start in the service, not the screen.

Lately that has meant a retail quoting tool, a repair shop's CRM, a national broadcaster's community platform. Different worlds, same job: take a messy, real operation and turn it into something simpler to use and measurably better.

It traces back to five years in architecture. Designing a building taught me to think in systems before surfaces: how people move through a space, where they pause, how it makes them feel. I bring the same lens to products, and service design and systems thinking are that instinct, reinterpreted.

Dayal Sebastian

Experience

Education & Fellowships

Capabilities

Design & Product

  • End-to-end Product Design
  • UX / UI Design
  • Prototyping & MVPs
  • Service & Workflow Design
  • Design Systems
  • AI-assisted Prototyping
  • Stakeholder Management

Research & Methods

  • User Research & Testing
  • Jobs to Be Done (JTBD)
  • Problem Framing
  • User Journey Mapping
  • Service Blueprinting
  • Ethnographic Research
  • Agile / SAFe Delivery

Tools

  • Figma
  • Framer
  • Adobe Creative Suite
  • Web / CMS Platforms
  • Claude Code

Interested in working together? I'd love to hear from you.

dayalsebastian@outlook.com

Also on LinkedIn.