Surviving a Marketing Technology Implementation
summary
Maps show ~4,000 martech choices and the concrete lesson is to prioritize people and process over shiny tools: document current workflows, do old-school manual testing to surface gaps, and avoid simply porting old processes into Eloqua or similar systems. Plan longer so you can execute quickly, choose tools that minimize admin, aim for a one-year roadmap with quarterly reviews, and expect 6–12 month rollouts. Sell the project internally by proving the user payoff and winning over the least technical users.
AI-written summary · about
chapters (6)
- 0:00Introduction to tech implementation
- 3:52Common pitfalls in implementations
- 6:22Focus on people and process first
- 9:27User payoff and adoption strategies
- 12:57Keep analysis simple and actionable
- 14:25Understand your buying cycle
related talks
06mIgnite - A DevOps Necessary Evil: Marketing
26mA quick tour of delivery management (and why it matters)
35mPlatform Engineering Is Not About Tech
30mWhy most technology migrations fail (and what we've learned along the way)
20mPlatform Engineering Is Not About Tech
09mInterview with
25mImplementation Case to Optimize IT Investments
29mTales from the Platform Adoption Mines