Skip to main content
Meytal Dahan
Back to insights

Researching the Marketer, Not Just the Metric

When I research for analytics products, the trap is assuming the user wants data. They don't. Marketers and campaign managers want to know whether the campaign is working and what to do next. That distinction shapes everything I learn in discovery. For PMs, this is where research earns its keep, because it reframes the roadmap away from "more charts" toward "faster decisions." In my interviews I watch how people actually open a dashboard on a Monday morning, what question is in their head, and how many tabs they have to cross-reference before they trust a number. The pattern I keep finding is that raw figures arrive before meaning, so people spend their energy interpreting instead of acting. That insight is what justifies an Insights-Before-Numbers structure, where the analyzed takeaway leads and the supporting figures sit underneath. Research also surfaces how different roles diverge on shared data: an analyst validating, a manager deciding, which protects the PM from building one bloated view for everyone. I deliver findings as decisions the team can prioritize, not a slide of quotes. Good research narrows scope; it tells you what not to build.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Marketing & Campaign Analytics
Engineering Leaders

Data Visualization in MarTech: How Do You Design Charts That Don't Collapse Under Massive Data?

Engineering leaders on MarTech systems: dashboards with real-time visualizations are a performance nightmare. In our campaign management system project we built "Skeleton Loading" — every chart loads separately, a fast experience even under load. Every visualization passed through a "Performance Impact" filter. Design + performance = a system that works in production.

Read
Marketing & Campaign Analytics
Project ManagersDelivery & Handoff to Development

A Handoff the Team Can Actually Build From

A handoff isn't the moment you share a file. It's a quality gate. If I only hand over the happy path, the team builds the happy path, and every loading, empty, and error state becomes a clarification ticket mid-sprint. So I spec the states, the interactions, the shared-vs-specific components, all on existing Design System tokens. A good handoff makes delivery assembly, not archaeology.

Read
Marketing & Campaign Analytics
Engineering LeadersDesign Systems

Why a Design System Is Shared Infrastructure for MarTech

A design system for an analytics product isn't a style guide — it's shared infrastructure. Marketers, analysts, and campaign managers all sit on the same data layer. If you hand-build each role's screens, you maintain three front-ends that drift apart every release. Encode the rules once — insight cards, metric tiles, loading skeletons — and let engineering compose workflows from stable primitives. A fix ships everywhere at once. The real payoff isn't the launch sprint. It's the maintenance years.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.