Marketing technology, product development, and UX usually run as three parallel organizations with three roadmaps. This framework treats them as one operating model — shared cadence, shared artifacts, shared decision gates — and documents it as a set of interactive references teams can actually use.
Marketing operates in campaign cycles measured against pipeline. Product operates in sprints measured against velocity. UX operates in research cycles measured against usability outcomes. Each has legitimate methods — and each optimizes locally while the customer experiences all three as a single product.
The symptoms are familiar: martech stacks selected without product input, features shipped without messaging, research findings that never reach campaign strategy, and handoffs where accountability quietly evaporates.
The approach here is structural rather than exhortative. Instead of asking teams to "collaborate more," it defines explicit roles, shared artifacts, and sprint gates where the three disciplines are required to converge — so integration is a property of the process, not of individual goodwill.
Each is a standalone interactive reference — open it, explore it, hand it to a team. Start with the integration overview if you want the whole system on one screen.
The full operating model on one screen — how marketing, product development, and UX interlock as a single system.
Who does what in an agile UX practice, and the artifacts each role owns — from research plans to design systems.
Open framework →The end-to-end process flow from discovery through delivery, with the gates where disciplines converge and sign off.
Open framework →The martech landscape mapped as an ecosystem, showing where UX responsibility sits inside campaign, analytics, and CX tooling.
Open framework →The two disciplines combined into one guide — shared cadence, shared metrics, and the touchpoints where they exchange work.
Open framework →This framework reflects how I approach every engagement: make the operating model explicit, define the gates where disciplines must converge, and document it in a form teams can use without me in the room. The same method scales from a martech stack to a 1000-application enterprise portfolio.