Back
Sections
Sections
UX/Product Design Case Study

One listening platform, two ways of reading the web

A research product with two separate analysis tracks: Topic, to understand everything said about a subject, and Brand, to measure a brand on its own and against competitors.

Role
Senior Product Designer
Team
Product Owner and engineering team
Product
B2B social listening and brand intelligence SaaS
Platform
Desktop web
Tools
Figma (design, prototyping), FigJam

Challenge

One product had to answer two different questions: what's being said about a topic, and how a brand performs against competitors.

What I did

Competitive research, IA, flows, UI, prototypes and the component libraries for both tracks, against a requirements document written by the product owner and engineers.

Signature decision

Drill-downs that don't cover the page: every widget has an expanded and a collapsed variant, so the page makes room for the panel. See it

Where it stands

Design stage. It hasn't been built or tested, so there are no results yet. Assumptions and estimates are tagged where they appear.

UX/Product Design Case Study

One listening platform, two ways of reading the web

A research product with two separate analysis tracks: Topic, to understand everything said about a subject, and Brand, to measure a brand on its own and against competitors.

Role
Senior Product Designer
Team
Product Owner and engineering team
Product
B2B social listening and brand intelligence SaaS
Platform
Desktop web
Tools
Figma (design, prototyping), FigJam

Challenge

One product had to answer two different questions: what's being said about a topic, and how a brand performs against competitors.

What I did

Competitive research, IA, flows, UI, prototypes and the component libraries for both tracks, against a requirements document written by the product owner and engineers.

Signature decision

Drill-downs that don't cover the page: every widget has an expanded and a collapsed variant, so the page makes room for the panel. See it

Where it stands

Design stage. It hasn't been built or tested, so there are no results yet. Assumptions and estimates are tagged where they appear.

▶Product walkthrough

The whole product, in about three minutes

Seven short chapters with on-screen guidance: Topic setup and insights, the signature drill-down, AI, dashboards, the Brand track and the shared workspace. Built from 31 designed screens and 11 overlays.

Walkthrough built from the Figma design screens with sample data, following the prototype’s transitions: drawers slide in from the right, dropdowns open at their trigger, and drill-down and AI panels open beside the page. Captions explain each step. No sound.
02Project overview

Two questions that needed two different products

Signal Intelligence is part of the Research Intelligence Suite. It collects public mentions from social, news, blogs, forums and more. Topic and Brand studies use the same sources with a different mindset: Topic is exploratory and neutral; Brand is evaluative and comparative.

Track 1 · Topic

Analyse a subject

"What is being said about this topic, and why?"

Used for
Mentions, trends, spikes, sentiment and emotion, themes, influencers and search interest around a topic, keyword set or event
Setup
5 steps: Study Basics · Topic Setup · Sources · Filters · Preview
Analysis
Overview · Media Coverage Trend · Topic Associations · Conversation · Influencer and Author Impact · Search Trends, plus Forecasting (scope open)
Compares
Current vs previous period, and topic vs topic
Track 2 · Brand

Evaluate a brand

"How is my brand performing, and how do we compare?"

Used for
Brand health, reputation and crisis risk, media and campaigns, content, channels and customer care, alone or against competitors
Setup
6 steps: adds Output Type, brand details and Competitors (up to 5)
Analysis
8 modules, from Brand Health to Digital Care
Compares
Self-Brand, Competitor-Only or Self + Competitor

What I owned

Everything on the design side, for both tracks, as the only designer.

Competitive researchInformation architectureUser flowsUI designPrototypesComponent librariesRequirements reconciliation

Who I worked with

A product owner and the engineering team, who wrote the functional requirements document. I designed against it and reconciled the designs with it line by line (section 15).

2analysis tracks on one shared workspace
15analysis areas: 7 Topic sections and 8 Brand modules
~1,650requirements in the FRD, by my count, reconciled with the designs
456component sets and 5,880 variants I built for the library
02The problem

Answering "what's being said, where, and why" takes a patchwork of tools

Research, brand and PR teams stitch together social listening, news monitoring and spreadsheets. The requirements name five consequences:

  • Slow insight cyclesAnalysts spend their time stitching sources together instead of finding signals.
  • Shallow competitor contextComparing a brand with its peers across channels and time is manual.
  • Limited actionabilitySpikes and emerging themes are spotted late; the next step is unclear.
  • Inconsistent reportingStakeholders want reliable dashboards and summaries; output is ad hoc.
  • Governance gapsPlans, quotas and source entitlements are hard to manage in one place.

Inside the tools themselves, there's a smaller problem that analysts hit many times a day: opening a widget's detail covers the rest of the page.

Design question

How might one product explore topics and judge brands, and let an analyst dig into any number without losing sight of the others?

03Signature solution

Drill-downs that don't cover the page

I designed every widget in two variants, Expanded and Collapsed. Opening a drill-down reshapes the page instead of covering it.

The problem

In the listening tools I benchmarked, including Sprinklr, clicking a widget opens a side overlay over the page. It covers everything on the right side of the screen, so moving to another widget means closing the panel, finding the widget and opening it again.

What I did

The clicked widget stays expanded as the active one. Every other widget switches to its collapsed variant: a thumbnail of its type (line graph, pie chart, bar chart, table, post or blog). The page makes room for the panel, and closing it expands everything back.

Options I weighed

Overlay drawer Common pattern

The drill-down V2.0 used, and the one most tools use. The detail gets plenty of room, but it covers half the page.

Inline expansion Explored

The card grows in place across the grid. It keeps context above it, but pushes the widgets below down the page and limits the detail to the card's space.

Split screen, expanded and collapsed Chosen

The panel gets its own space; the page keeps every widget in place, in a compact form that's one click away.

Before and after

The "Before" panel is a reconstruction of the common pattern, built from my own screens.

See it in motion

    Animated recreation of the interaction in the design file, simplified to its layout and sample data.

    The design

    1234
    • 1
      Active widget stays in its expanded view, highlighted.
    • 2
      Collapsed thumbnails keep each widget's place, title and type. Its values return when the panel closes.
    • 3
      Drill-down panel with breadcrumb, date range, and current vs previous period.
    • 4
      Drag handle to resize the page and the panel.
    L0Widget→L1Breakdown→L2Cluster→L3Post, blog, news or author

    Trade-offs. Collapsed widgets show their type, not their values, so side-by-side number comparison still happens in the panel or on a dashboard. And every widget type needs two designed variants, a cost paid once per type (line, pie, bar, table, post, blog) and shared by both tracks.

    An estimate of the time saved Estimate

    Using the Keystroke-Level Model, moving from one widget's drill-down to another's takes six operators with the overlay (decide, point and click to close; find, point and click the next widget) and three with my design.

    Overlay5.3 s
    Expanded and collapsed2.65 s

    Card, Moran and Newell operator times (M = 1.35 s, P = 1.1 s, click = 0.2 s). Loading and scrolling aren't included. This is an estimate to check in the comparison test, not a measured result.

    05Research

    Where established tools leave their users stuck

    I compared four tools across 15 capability areas and mapped 18 pain points on the project's FigJam board, then checked them against the requirements. This was desk research; interviews come first in the validation plan.

    Competitor snapshot

    Sprinklr

    Core
    All-in-one CX, publishing and care
    Built for
    Enterprises, CX teams
    Strength
    Breadth, governance, automation
    Weakness
    Overbuilt for analytics-only users, slow to set up

    Brandwatch

    Core
    Enterprise consumer intelligence
    Built for
    CMOs, analysts, CPG
    Strength
    NLP, personas, deep dashboards
    Weakness
    Steep learning curve, slow for quick analysis

    Meltwater

    Core
    PR, media, social and sales
    Built for
    PR and comms teams
    Strength
    News wires, journalist data
    Weakness
    Dated interface, cost

    Brand24

    Core
    Affordable real-time listening
    Built for
    SMBs, startups
    Strength
    Price, speed, simple UX
    Weakness
    Shallow insights, no prediction

    As recorded during my research. These products change often, so details may have moved on since.

    Pain points an interface can answer

    Pain pointMeltwaterBrand24BrandwatchSprinklrDesign response
    Complex onboarding, steep learning curveGuided setup, three query levels, live preview Designed
    Volume shown without the reasonSpike Analysis and card-level AI Summary Designed
    Shallow influencer analyticsInfluencer and Author Impact section Designed
    Weak sentiment layeringSentiment and emotion by source, region and time Designed
    No demographic and affinity viewAudience profession and interest cards Partly designed
    No trend forecastingForecasting tab designed; its place in scope is open Open
    The pain point applies to that toolDoesn't apply

    "Designed like a research tool, not a publishing tool with add-ons."

    The positioning I took from it: faster to set up than the enterprise suites, deeper than the budget tools. Publishing, scheduling, reply inboxes and ticketing stay out.

    05Users and journey

    Four roles, and the analyst's path through the product Assumed

    The roles come from the audience list and segment-fit ratings on the board. They haven't been validated with interviews yet.

    Research & insights analyst

    Primary. Goes deep: explores a subject, finds patterns and causes, collects evidence.

    TopicBrand
    Job to be done"Tell me what people are saying about X, what changed, and why."

    Brand & marketing manager

    Primary for Brand. Tracks brand health, campaigns and channels against competitors.

    Brand
    Job to be done"Show me how my brand is doing against competitors, and where to act."

    PR & comms lead

    Secondary: the board rates the fit as partial. Watches coverage and needs early warning of spikes.

    BrandSecondary
    Job to be done"Warn me before a spike becomes a crisis."

    Executive / CMO

    Reads dashboards and AI overviews, rarely drills down. Shallow, frequent visits.

    DashboardsAI Overview
    Job to be done"What's happening, and what should we do?"

    Open question. The board rates customer experience teams a poor fit, yet the requirements include a Digital Care module. I'd settle which it is with the PM before designing that module.

    The analyst's journey, from a new study to an explained spike

    Stage 1Set up
    Doing
    Defines keywords, sources and filters
    Thinking
    "Will my query catch the right conversation?"
    Pain today
    Boolean syntax, long onboarding
    Design response
    Three query levels and a live preview
    Stage 2Read the overview
    Doing
    Scans KPIs, the trend and sentiment
    Thinking
    "What's the headline?"
    Pain today
    Cluttered, all-in-one interfaces
    Design response
    One question per section, one card anatomy
    Stage 3Spot a change
    Doing
    Notices a spike or a shift in sentiment
    Thinking
    "Is this real, and why now?"
    Pain today
    Volume without the reason
    Design response
    Spike marker opens Spike Analysis
    Stage 4Investigate
    Doing
    Opens a widget's detail, then the next
    Thinking
    "How does this relate to the other numbers?"
    Pain today
    The overlay covers the other widgets
    Design response
    Expanded and collapsed widgets
    Stage 5Explain and share
    Doing
    Collects evidence, adds cards to a dashboard
    Thinking
    "Can I trust this enough to share it?"
    Pain today
    AI answers not tied to the data
    Design response
    Card-scoped AI Summary, Add to dashboard
    06Goals and scope

    What the design had to achieve, and what's in or out

    Four goals from the requirements, each with the measure I'd track. Targets get set after the first usability baseline.

    Guided, unified setup

    Topic and Brand studies set up with the same pattern.

    • Measure: time to the first launched study, and studies launched without later query edits

    Evidence behind every number

    Sections that each answer one question, down to the individual post.

    • Measure: time to find the posts behind a number

    Explainable changes

    Spikes explained where they appear, with AI at page and card level.

    • Measure: share of spikes explained without leaving the page

    Dashboards that just work

    A default dashboard on first run, built from cards users already know.

    • Measure: dashboards revisited each week per user

    Scope

    Designed

    • Topic setup 5 steps
    • Topic Insights sections 6 + Forecasting
    • Drill-down, expanded and collapsed Shared
    • AI Overview, AI Summary, Spike Analysis Shared
    • Dashboards and Manage Widgets Shared
    • Configure: sources, filters, dashboards Shared
    • Brand Health and Campaign Benchmark Brand

    Specified, still to design

    • Brand setup screens Brand
    • Media & Advertisement, Channel Optimization, Digital Care Brand
    • Loading and error states Shared
    • AI confidence states Shared
    • Alert builder Shared
    • Add Competitor flow Brand

    Out of scope (non-goals)

    • Publishing and scheduling
    • Reply inbox and community management
    • CRM, ticketing and SLAs
    • Paid media buying
    • Long-range forecasting
    07IA and user flows

    Two branches from one "Create new study"

    Both tracks share Setup, Insights, Dashboard and Configure. What's inside Insights makes them different products.

    User flows

    Topic branches on query mode; Brand branches on output type. Paid sources never stop setup: they join as "Pending purchase". Both flows end in the same drill-down loop.

    08Hi-fi · Track 1

    Analysing everything around a topic

    From defining the topic to explaining a spike in its conversation.

    Study Basics→Topic Setup→Sources→Filters→Preview→Insights

    Topic track screens

    Study Basics: the result is visible while it's built

    A progress rail keeps the whole setup in view, and a live preview on the right fills in with every choice.

    Topic Setup: the same query at three levels of difficulty

    Boolean syntax is where non-specialists drop off, so nobody has to start with the hardest option.

    BasicInclude and exclude keywords and hashtags as chips.
    AdvancedA Boolean query field with an operator reference.
    AI Query Generator"Describe what you want to track", then review and insert the query.

    Sources and Filters

    Sources are grouped by what the plan includes; a paid source joins as "Pending purchase" instead of stopping setup. Filters narrow by region and language.

    Preview: a review, not a surprise

    Configuration, AI-suggested terms, cost and a launch-readiness checklist on one screen.

    Trade-off. Five steps is slower for an expert with a query ready. Advanced mode lets them paste it in one go; for everyone else, the preview catches mistakes before any data is collected.

    Insights: each section answers one question

    Instead of one long report, the analysis is split into the questions an analyst asks about a topic.

    1Overview · the headline2Media Coverage Trend · what publishers say3Topic Associations · brands and themes that come up4Conversation · what people feel5Influencer and Author Impact · who drives it6Search Trends · what people search+Forecasting · scope open

    The cards that explain the conversation

    Themes show what it's about, news clusters group coverage into stories, and top posts bring the loudest voices forward.

    09Hi-fi · Track 2

    Evaluating a brand, alone and against competitors

    The same sources, read from the brand owner's side: health, reputation, media, campaigns, content, channels and care.

    Study Basics→Brand Setup→Sources→Competitors→Filters→Preview

    Brand track screens

    Setup starts with one question: whose performance are we measuring? Specified, screens in progress

    The same wizard pattern as Topic, plus only the decisions a brand study needs. The setup model is settled; its screens are still being designed.

    Step 1Study BasicsName, description, cover
    Step 2 · newBrand SetupOutput Type · brand details · keywords
    Step 3SourcesAs in Topic
    Step 4 · newCompetitorsUp to 5 · Direct or Indirect
    Step 5FiltersSkippable
    Step 6PreviewIncludes competitors

    Output Type, chosen first

    Self-Brand analyses the user's own brand, optionally with competitors. Competitor skips the self-brand details and analyses only competitors. Asking first means the rest of setup shows only the fields that matter.

    A query built from the brand

    Alongside Basic and Advanced, the AI generator gets a "Create Brand Query" path: enter the brand and its products or services, and the query is drafted from them.

    Comparison is a mode of the whole study, not a separate tool

    Each card declares which data it shows, and the mode decides what appears.

    Self-Brand[S]

    Your brand's KPIs first, with competitor data as a secondary comparison.

    Competitor-Only[C]

    Only competitors, compared with each other. Self-only metrics are hidden.

    Self + Competitor[S+C]

    Both side by side from the start, with a toggle between views.

    Trade-off. Tagging every Brand card as [S], [C] or [S+C] adds work to each one. In return, no card ever shows a comparison that doesn't make sense for the chosen mode.

    Eight modules, from overall health to customer care

    Each module answers one family of questions about the brand.

    01Brand Health

    Awareness, engagement, perception, reputation and loyalty in one score

    02Media & Advertisement

    Coverage volume and quality, share of voice

    03Campaign Benchmark

    Reach, engagement and resonance against competitors

    04Content Intelligence

    Themes, tone, formats, virality and timing

    05Influencer & Author

    Advocates, detractors and high-impact creators

    06Channel Optimization

    Presence and efficiency per platform

    07Digital Care

    Care volume, response and contact drivers

    08Search Trends

    Search interest in the brand and its categories

    Brand Health: one score, then the reasons behind it

    A composite score across five pillars, benchmarked against the competitor average and best in class, then each pillar broken down.

    Inside the pillars. Sentiment Split S+C; Breakdown by Insight Category S; negative coverage by region S.

    The other modules reuse the same cards

    Different questions, the same card anatomy and the same expanded and collapsed variants as the Topic track.

    Where it stands. Brand Health and Campaign Benchmark are designed in depth, Content Intelligence in part, and Influencer & Author reuses the Topic design. Media & Advertisement, Channel Optimization and Digital Care are specified and mostly still to be designed.

    10Hi-fi · Shared workspace

    Curated Insights to explore, personal Dashboards to keep

    Whether a study is Topic or Brand, the header, dashboards, search and Configure work the same way. The Brands selector appears only in Brand studies.

    Header and toolbar

    Insights and Dashboard tabs, AI Overview, then Search, Duration, Filter and Configure.

    Dashboards: choose and order, don't configure

    A dashboard is a list of cards the user already knows.

    Duration

    Every KPI compares the chosen period with the previous period of the same length.

    Configure: everything that shapes a study, in one place

    Sources, Saved Filters, Alerts, Dashboards and, for Brand studies, Competitors. Source connections are account-wide: one login serves every study.

    Saved Filters and Dashboards. Reusable filter sets for repeat analysis, and templates alongside the user's own dashboards.
    11AI across the journey

    AI answers the question where it comes up

    AI isn't a separate assistant. It's attached to the three moments an analyst asks something, in both tracks.

    "Why did this spike happen?"

    From the marker on a trend line: time, volume, change against average, and the clusters behind it.

    "What does this card mean?"

    AI Summary, scoped to the card it was opened from, so every statement can be checked.

    "What does this page say?"

    AI Overview from the header: highlights, each linked to its card, and which cards moved most.

    Spike Analysis and the page AI Overview.
    AI Summary for one card, with regenerate, copy and export.

    Trade-off. Three entry points mean three scopes to keep consistent. The requirements also ask for confidence scores and a low-confidence state on every AI output; that's the next thing to design.

    12Design system and principles

    One system under both tracks

    I built the libraries every card comes from, whether it sits in a Topic section, a Brand module or a dashboard.

    456component sets, 5,880 variants (V2.0 library)
    245component sets, 2,151 variants (revamp library)
    274variables in 18 collections
    1,033icons in the final icon set

    Colour

    Purple 500#6346E5
    Purple 700#3013B2
    Purple 800#170099
    Chart line#876DFF
    Grey 900#101828
    Grey 600#475467
    Grey 200#E4E7EC
    Page#F2F4F7
    Success#00880D
    Error#F04438
    Warning#F79009
    Coral#FF0EAB

    Typography

    Fira Sans is the system font (Regular, Medium, SemiBold); the revamp introduced Inter.

    Page title24 · SemiBold
    Card title18 · SemiBold
    Body and table text14 · Regular
    Axis labels, captions12 · Regular

    Next system work

    Some screens still mix the two typefaces, and the tokens need a semantic layer (text-primary, surface, border). Consolidating both comes before build.

    Card ShadowInput Field ShadowButton ShadowSpacing 4–256Radius 4–24

    Screen anatomy

    Card anatomy, in both tracks

    Once a user has learned one card, they know them all. Each widget type also has a collapsed variant: line graph, pie chart, bar chart, table, post and blog.

    1234567
    • 1
      Title names what the card answers.
    • 2
      Chart switcher: a default view and alternatives.
    • 3
      AI Summary, scoped to this card.
    • 4
      Menu: add to dashboard, set an alert.
    • 5
      Locked dimension with a sortable metric.
    • 6
      Insight marker on values worth a look.
    • 7
      See All: the way into the drill-down.

    UX laws and principles behind the screens

    13Design process

    Four generations of the design

    The drill-down is the clearest thread through them: from a drawer over the page to a split screen that keeps the page visible. Along the way I also explored inline expansion.

    01Rough work

    First analysis pages

    1280 px frames that mapped the first sections, such as Brand Associations.

    02V2.0

    Full product at 1920 px

    A two-column widget grid, with the drill-down in a drawer over the page.

    Where the overlay problem showed up
    03Revamp

    New shell and wizard

    A left Insights menu, Manage Widgets, the vertical setup wizard and alert templates.

    04Latest

    Split-screen drill-down

    Full-width cards, expanded and collapsed widgets, a resizable panel and native post cards.

    The signature solution
    14Requirements, states and accessibility

    Designing while the requirements were still moving

    The PM and engineers wrote the requirements while I designed. When I reconciled them line by line, a few assumptions changed. Two are already fixed in the screens shown here; the rest are next.

    AreaThe design assumedThe requirements settled onUI change
    Data freshnessLive monitoring, syncing every 5 minutesManual refresh, at least 24 hours apartTo do "Last updated", a Refresh control and the next refresh time
    CompetitorsA Brands selector on Topic screensCompetitors belong to the Brand track only, at most fiveDone Brands selector removed from Topic screens; Brand keeps it
    Comparison period"Current / Past Session" tabsThe previous period of the same lengthDone Renamed to Current period and Previous period
    Paid sourcesPayment inside the setup wizardSources join as "Pending purchase", paid for laterTo do Remove payment from Preview; setup never stops for it
    Topic sections7 tabs, including Forecasting6 sections, with no separate Forecasting sectionOpen Whether Forecasting stays a tab
    Brand modules7 modules8, adding Search Trends and renaming twoTo do Align module names on screen; design Search Trends

    States

    Designed

    • Search before typing: quick access and recent searches
    • Empty Data Sources step: "Add Sources"
    • Empty Add Competitors step
    • Drill-down empty state, the layout the page returns to
    • A source that needs re-authorising

    Still to design

    • Loading skeletons for widgets, drawers and AI
    • Errors: sync failure, API limit, AI generation failure
    • No data for a filter or period; no search results
    • Confirmations: delete, reset, unsaved changes
    Search before typing, one of the designed empty states.

    A study's lifecycle, in both tracks

    DraftSetup not finished Pending activationWaiting on a login or first collection ActiveCollecting PausedBy the user or the system DeletedRestorable

    The lifecycle is specified; its screens are part of the next round.

    Accessibility and screen sizes To specify before handoff

    Not colour alone

    Sentiment and competitor charts always carry a label and a percentage next to the colour, as in the sentiment card.

    Keyboard drill-down

    Opening a drill-down moves focus into the panel, Esc closes it and returns focus to the widget, and each collapsed thumbnail is a button named after its widget.

    Dense data on laptops

    The drag handle and widget resizing are designed. Layouts at 1280 and 1440 px still need specifying.

    15Validation plan

    How I'd test it before build Planned

    Ordered by risk: the decisions that would be most expensive to get wrong go first. Pass marks are my proposal, to agree with the PM.

    Drill-down comparison test

    First

    Both patterns as prototypes, in counterbalanced order. Task: move between three widgets' details and explain a change.

    With
    6 research analysts
    Measure
    Time on task, errors, Single Ease Question (1–7)
    Pass
    Faster median time and an average ease score of 5.5 or more

    Topic setup usability test

    Second

    Create a study from a written brief, starting in Basic mode.

    With
    6 analysts: 3 new to listening tools, 3 experienced
    Measure
    Completion, time to launch, query errors caught at Preview
    Pass
    At least 5 of 6 launch without help

    Brand comparison modes

    Third

    First-click and comprehension tasks on the three modes, plus short interviews to validate the roles.

    With
    5 brand and marketing managers
    Measure
    Correct mode chosen for a given question
    Pass
    Correct first click in at least 4 of 5 tasks

    After launch

    Ongoing

    Product analytics tied to the four goals.

    Track
    Time to first launched study; spikes explained in-page; time to evidence; weekly dashboard revisits; mode chosen by Brand users
    16Learnings

    What this project taught me

    Being the only designer on a product this size meant every structural decision was mine to make, and to defend.

    Separate the questions before designing the screens

    Treating Topic and Brand as one study type with options would have mixed exploratory and evaluative analysis in every card.

    Question the pattern everyone accepts

    Big tools accept that a drill-down covers the page. Two variants per widget removed that trade-off instead of living with it.

    Put AI where the question is

    Tying each answer to a card or a spike makes it checkable, which matters more than making it clever.

    What I'd do differently

    Reconcile with the requirements earlier and more often, so screens never drift from them; and settle the Brand setup and comparison modes before designing the Brand modules, since every module card depends on them.

    A topic is explored. A brand is judged. The product had to know the difference.

    Sole product designer, working with a product manager and engineers.

    Signal Intelligence · UX/Product Design Case Study · Research Intelligence Suite
    MORE WORK

    Continue exploring complex systems.

    Two more case studies across complex products and enterprise design.

    View all work
    Prism

    Prism Design System

    Design systemComponent library
    View case study
    Contact

    If the work resonates, let’s talk.

    Open to Lead Product Designer and UX leadership conversations around 0→1 products, AI-enabled SaaS and complex multi-persona systems.