Skip to main content
Meytal Dahan
Back to insights

Designing a MarTech System for an Enterprise Organization: Aligning Marketing, Sales, and IT

Project managers leading the design of a MarTech system inside a large organization know the challenge isn't technical — it's stakeholders. The marketing team wants creative flexibility, the sales team wants tight integration with the CRM, and the IT team demands compliance with security and privacy standards. Each of them brings different, and sometimes conflicting, requirements. In the MarTech system project, the working methodology was built on "Aligned Personas" — precisely mapping what each group needs and finding the points where those needs overlap. Instead of designing a system that tries to be everything to everyone, we built three main Workflows — one for marketers, one for analysts, and one for managers — each with its own unique emphasis, but all running on the same technical infrastructure. We also created a structured communication process that lets each group receive the updates relevant to them without flooding everyone else. The marketing team got demonstrations of their Workflow, the IT team got API documentation, and management got business demos showing the expected ROI. For project managers working on MarTech, AdTech, or any multi-user system within an organization, the insight is this: don't force a single uniform system on every group. Design distinct Workflows that serve each persona, but on a shared technical infrastructure. That's the difference between a system everyone adopts and a system no one uses.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Marketing & Campaign Analytics
Product ManagersUser Research

Researching the Marketer, Not Just the Metric

In analytics products, users don't want data. They want to know if it's working and what to do next. Every time I run discovery for a marketing dashboard, the same thing surfaces: people get raw numbers before meaning, so they burn energy interpreting instead of acting. That single insight reframes the roadmap, from "more charts" to "faster decisions." Research isn't a quote deck. It's the thing that tells your PM what NOT to build.

Read
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
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.