About

The person behind the work.

Experience
14+ yearsUX Research & Innovation · Mastercard Digital Labs
Education
MBA & BA PsychologyWashington University · University of Missouri
Engagements
$6M+ delivered (in 18 months)Government · banking · payments · health
Based
San Francisco, CAAvailable for select engagements
The short version

I'm Matt Barham, founder of Onyx Studios — a UX researcher and innovation strategist. Most of my career was built inside Mastercard Digital Labs, a team chartered to bring structured innovation to enterprise clients: federal government, global card issuers, regional banks, prepaid providers, healthcare startups, and more — an innovation lab consistently recognized among the world's best.

What I actually do is de-risk — ultra-deep planning and cheap pressure-testing of the assumptions a strategy rests on, before they turn into expensive mistakes. It comes in two doors: founders pre-launch, making sure they build the right thing; and product teams post-launch, finding what's quietly broken and costing them. A second of friction, a wrong assumption, a feature nobody needs — multiplied at scale, those are the most expensive kind of small.

I learned this in payments, where getting it wrong is measured in billions of transactions and regulatory consequences. Fintech was the crucible, not the cage — the discipline travels to any domain where the cost of being wrong is high. Onyx Studios is that work in its most useful form: faster, more direct, without the organizational overhead that delays the insight that matters.

How I work

A long list doesn't make me a jack-of-all-trades — it makes me a master of translation.

Across disciplines, I connect dots others miss and make things make sense. The right methods get pulled for the problem in the room — not the other way around. Here's the working toolkit.

70+named research, product, and facilitation methods I work in fluently
175+structured activities in the working library they draw from

UX Research — Qualitative

15
Usability testing (mod & unmod)Contextual inquiry & field studiesJourney & experience mappingJobs-to-be-done interviewsFocus groups & interviewsPersona developmentInformation architectureCard sort & tree testingDiary studiesParticipatory design workshopsExploratory concept testingHeuristic evaluationAccessibility (WCAG / ADA)Research frameworks & playbooksSupport documentation

UX Research — Quantitative

9
A/B testingMultivariate testingStatistical & data analysisRegression analysisBehavioral analyticsCompetitive benchmarkingLarge-scale surveysKPI capture & analysisProduct & market performance metrics

Product & Innovation

24
Design-thinking facilitationProduct vision & strategyRoadmappingMVP scopingService designBusiness case developmentMarket research & opportunity sizingCompetitive analysisBacklog prioritizationRequirement definitionUser stories & acceptance criteriaSprint planningDesign experimentsRisk assessment (viability/feasibility/desirability)Innovation portfolio managementCustomer segmentation & ecosystem mappingGo-to-market planningChange management & adoptionKPI definition & trackingUsage & engagement analyticsWireframing & low-fi prototypingExecutive communication & storytellingProject management leadershipAgile / PM tooling

Relationships & Sales

23
Workshop & multi-party facilitationWorkshop-to-implementation transitionStakeholder consensus buildingRelationship mapping & alignmentExecutive stakeholder advisoryExecutive sponsor narrativesStrategic account planningValue proposition designROI & value-realization analysisBusiness case developmentNegotiation & renewal managementCross-sell / upsell strategyCustomer success & onboarding strategyCustomer health analysisOutcome-driven roadmapsPartner ecosystem developmentCross-functional collaborationConflict resolutionMentorship & team leadershipPresentation creation & deliveryTechnical solution demonstrationsRisk managementSalesforce / CRM management
Building the function, not just the deliverable

Fixing the handoff so research arrived in time to matter

  • Good research is useless if it lands after the decisions are made.
  • At Mastercard I built the operating model for the User Experience Group — how research, design, and development hand off — because the failure was never bad work; it was work that showed up too late to change anything.
  • It worked, so I recreated the model for the entire Employee Experience department — research stopped being the thing teams involve last.
  • The deliverable is rarely the point. It's the system that gets the right thinking into the room at the right time.
Reading the signal early

The expensive problem, spotted while it was still cheap

  • An all-employee survey was being read mostly for its headline scores — so I asked instead for the raw employee-experience verbatims.
  • In them: a newly acquired company running national-scale payment rails heading for a breakdown — people on two separate laptops to do one job, two companies' worth of help desks, no clean way to ship to production.
  • Senior leadership was convinced everything was fine — the people meant to be watching had stopped looking at the bigger picture.
  • I flagged it roughly six months before it boiled over to the acquired company's CEO — exactly the breakdown the verbatims had predicted.
  • Find the expensive problem while it's still cheap to fix.
Let's talk

You don't need it figured out before you reach out.

The best engagements I've had started with someone saying "something's missing and I can't quite name it."

That's enough. Let's start there.