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.
Related articles

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.