Product, systems & webMelodyArc

One product language across complex operations and the story around them

Leading end-to-end design for MelodyArc’s support-operations platform, with 250+ shipped screens, a shared design-system contribution, and three generations of the company’s marketing experience.

Role: UX Design Lead
Duration: July 2023–present
Team: Product & engineering
Scope: Platform, system, motion & web

MelodyArc support-operations workspace showing agents, ticket queue, conversation, and customer context — A unified MelodyArc workspace that keeps queue context, conversation, and customer information in view.

Challenge

MelodyArc brings together people, rules, data, and AI for complex support operations. The design challenge spans more than individual screens: agents need dense context without losing the current task, product teams need reusable patterns as the platform grows, and the marketing experience needs to explain an evolving category clearly.

My role covers that connected surface area—from core product workflows and system patterns to motion and the Framer-built company site.

Evidence

This overview focuses on shipped scope rather than confidential customer or business metrics. The clearest public evidence is the breadth of production work and the evolution of the product story.

250+

product screens shipped

marketing iterations designed and built

shared product language across workflows

What scale made visible

At 250+ screens, small inconsistencies multiply quickly. Reusable states, hierarchy, component behavior, and motion guidance became product infrastructure—not polish added after a flow was complete.

Model the work

Map operational roles, queue states, decision points, and the context each task requires.

Systemize patterns

Turn repeated interaction and visual decisions into shared components and guidance.

Ship & evolve

Partner through implementation, then adapt both product and marketing as the platform changes.

Decisions

Keep task and context together. The core workspace holds the queue, conversation, and customer information within one operational frame.
Treat the design system as delivery infrastructure. Shared components, states, spacing, and motion behavior reduce drift as new workflows are added.
Use motion to explain state and sequence. Product motion supports orientation and feedback; marketing motion helps make orchestration concepts tangible.
Let the marketing site evolve with positioning. Three distinct iterations moved from support-operations framing, through AI-operator language, to the current enterprise orchestration story.

First MelodyArc marketing site with support-operations positioning and an AI workflow diagram — **Iteration one:** support operations on one AI-powered platform.

Second MelodyArc marketing site introducing AI operators with a light indigo visual system — **Iteration two:** AI operators and an expanded product narrative.

Current MelodyArc marketing site explaining orchestration, execution, and record product layers — **Current site:** enterprise orchestration expressed as a clear three-layer system. Visit melodyarc.com

Outcome

The work has produced more than 250 shipped product screens, contributed a reusable design-system foundation, established product-motion patterns, and delivered three marketing iterations. Together, those outputs give the platform and its public story a more coherent language as both continue to evolve.

This overview reports shipped design scope. Confidential customer and business metrics are intentionally not inferred or published.

Reflection

Designing across product and marketing creates a useful feedback loop: product work keeps the story honest, while explaining the product exposes where the experience or vocabulary is still unclear. The ongoing challenge is to preserve that coherence as the platform adds more roles, decisions, and automation.