Marketing has never had more data about its own performance. Every email tracked. Every click counted. Every form submission logged. Every lead scored, staged, routed, and attributed. The reporting infrastructure is enormous. The dashboards are detailed. The team can tell you exactly how many people opened the email, clicked the link, visited the page, downloaded the asset, and entered the pipeline. What nobody can tell you is whether any of those people actually enjoyed the experience. Not whether they converted. Whether they liked it. Whether the email was worth reading. Whether the content taught them something they didn't know. Whether the interaction made them think more highly of the company or less. Whether the experience of being marketed to by your brand felt respectful, useful, and human - or whether it felt like being processed through a machine that doesn't care about them as long as they click the button. That question doesn't appear on any dashboard. It's not a metric anyone tracks. And it might be the most important thing marketing isn't measuring. You optimized for outcomes and forgot about experience The data-driven marketing revolution taught teams to measure everything that can be measured and optimize for the metrics that connect to revenue. That's not wrong - it's necessary. Marketing should be accountable for results. Pipeline contribution matters. Revenue attribution matters. Cost per acquisition matters. But somewhere along the way, the obsession with measurable outcomes created a blind spot for the unmeasurable thing that makes those outcomes possible: how the buyer feels about the experience. A buyer who opens an email, clicks through, and downloads a whitepaper registers as a conversion. The dashboard counts it. The scoring model rewards it. The team celebrates it. But what the dashboard can't tell you is whether that buyer downloaded the whitepaper because it genuinely addressed something they care about - or because the subject line created enough curiosity to get a click, the landing page made it easy to submit, and the content was adequate enough to not feel like a complete waste of time. Both scenarios produce the same metric. One creates a buyer who trusts you more. The other creates a buyer who got what they needed and formed no opinion about you at all - or worse, felt slightly manipulated by the process. The metric says success. The experience says nothing. And since we only measure the metric, we assume the experience was fine. The experience IS the brand In B2B, the buyer's experience of being marketed to is one of the most frequent and formative interactions they have with your brand. More frequent than talking to sales. More formative than visiting your website. The emails they receive, the content they consume, the forms they fill out, the nurtures they're enrolled in - that's their relationship with your company for weeks or months before a human conversation ever happens. If those interactions feel generic, impersonal, and transactional, the buyer forms an impression of a company that's generic, impersonal, and transactional. If those interactions feel thoughtful, relevant, and respectful of their time, the buyer forms a different impression entirely. This impression doesn't show up in a dashboard. But it shows up in every conversation that follows. The buyer who had a positive marketing experience arrives at the first sales call warmer, more trusting, and more willing to engage openly. The buyer who felt processed arrives guarded, sceptical, and already comparing you to the competitor whose marketing felt more human. Sales teams notice this difference even if they can't name it. Some leads arrive "warm" and some arrive "cold" - and the temperature has nothing to do with the scoring model. It has everything to do with how the buyer felt about every interaction that preceded the call. What "liked it" actually means in B2B This isn't about making marketing fun or entertaining. B2B buyers aren't looking for delight. They're looking for respect - respect for their time, their intelligence, and their situation. A buyer likes your marketing when the email they received was worth the 30 seconds it took to read it. When the content delivered on the promise the subject line made. When the form didn't ask for information you should already have. When the nurture adapted to their behavior instead of sending the same sequence regardless of what they did. When the follow-up after a webinar referenced what was discussed instead of pushing a generic demo request. A buyer dislikes your marketing when the email wasted their time with something irrelevant. When the gated asset turned out to be a thinly disguised sales pitch. When the "personalized" message was clearly sent to 10,000 other people. When the nurture kept sending emails about a problem they'd already solved. When every interaction felt like it was designed to extract a conversion rather than provide value. None of this is measured. All of it determines whether the buyer trusts you by the time they reach sales. The metrics we don't have but should Measuring whether someone "liked" a marketing interaction sounds subjective. It is - partially. But there are proxies that most teams never look at. Unsolicited replies. When someone replies to a marketing email - not clicking a CTA, actually replying - that's a signal the content sparked something. Most marketing teams don't track reply rates because marketing emails aren't designed for replies. They're designed for clicks. But a reply is a higher-quality engagement signal than a click will ever be. Content completion. Not just "downloaded" - did they actually read it? Time on page for blog posts and articles gives you a rough measure. For gated content, it's harder, but tracking whether someone who downloaded a guide went on to engage with related content tells you whether the asset delivered value or just collected a form submission. Return visits without a prompt. A buyer who comes back to your website without being emailed, retargeted, or reminded is a buyer who found value the first time. Organic return visits - stripped of campaign-driven traffic - are one of the strongest signals that your marketing is creating a positive experience. Most teams don't segment this because it requires filtering out every campaign touchpoint. Negative signals treated as feedback. Unsubscribes, spam complaints, and declining engagement aren't just metrics to minimize. They're feedback about the experience. A spike in unsubscribes after a specific campaign isn't a deliverability problem - it's the audience telling you that campaign wasn't worth receiving. Most teams treat these signals as problems to solve rather than information to learn from. Start asking The simplest version of this doesn't require any new tools or metrics. It requires asking. After a deal closes, ask the buyer: what was your experience of our marketing before we spoke? What was useful? What wasn't? Was there a moment where something we sent made you more interested - or less? After a deal is lost, ask the same questions. The answers from lost deals are more valuable than the answers from won ones, because they reveal what your marketing did that pushed someone away rather than pulled them in. Build these questions into your post-deal process. Not as a survey - as a conversation. The qualitative feedback you get from ten honest buyer conversations will tell you more about the effectiveness of your marketing experience than a year of dashboard data. The metrics tell you what happened. The buyer tells you how it felt. Both matter. Right now, most marketing teams only have the first one. The teams that add the second will build marketing that doesn't just convert - it earns the kind of trust that makes conversion the natural next step, not a metric to be extracted.

Try this exercise. Pull someone on your marketing team aside - not the person who built the system, someone else - and ask them to explain how a lead moves through your marketing automation environment from first touch to sales handoff. No platform open. No notes. Just a verbal walkthrough. What you'll hear will tell you more about the health of your marketing operations than any dashboard. If they can walk through it clearly - how leads enter, how they get scored, what triggers a lifecycle change, what nurtures they're enrolled in, how they get routed to sales, and what happens after - your system is understood. It can be governed, improved, and trusted. If they hesitate, start sentences with "I think," contradict themselves, or say "you'd have to ask a person who built it" - your system has outgrown your team's understanding. And a system nobody can explain is a system nobody can control. Complexity creeps in without anyone noticing No marketing automation environment starts complicated. Day one is clean. A few campaigns, a simple scoring model, a straightforward lifecycle, clear routing rules. Everyone on the team understands how it works because there isn't much to understand yet. Then the requests start. A new nurture for this segment. A scoring adjustment for that product line. A routing exception for the new territory. A workflow to handle leads from the event that doesn't fit the standard lifecycle. A campaign with conditional logic that branches based on three different field values. An integration with a new tool that writes data back into the MAP. Each addition makes sense on its own. Each one adds a small amount of complexity. Over months and years, the cumulative effect transforms a system that anyone could explain into one that maybe two people fully understand - and one of those people is probably the person who built most of it. The complexity didn't arrive through a single decision. It accumulated through hundreds of small, reasonable decisions made under time pressure, without anyone stepping back to ask whether the whole still makes sense. The "ask Sarah" problem Every marketing operations team has a version of this. A question comes up about why a workflow behaves a certain way, or how a scoring rule was configured, or what happens when a lead meets two conflicting criteria simultaneously. The answer is always the same: ask the person who built it. That person becomes the single point of interpretation for the entire system. Not because they're hoarding knowledge - because the system is too complex for anyone else to hold in their head, and there's no documentation that bridges the gap. This creates three problems that compound over time. The first is fragility. If that person is unavailable - on leave, sick, or simply in a meeting when something breaks - the team is stuck. They can see what the system is doing but they can't explain why it's doing it, which means they can't tell whether the behavior is correct or broken. The second is governance failure. You can't govern what you can't describe. If the team can't explain the scoring logic, they can't evaluate whether it's still appropriate. If they can't walk through the lifecycle, they can't identify where leads are getting stuck. If they can't describe the suppression rules, they can't verify whether contacts are being excluded for valid reasons. Governance requires understanding. Complexity kills understanding. The third is decision-making paralysis. When nobody's confident they understand the full picture, nobody wants to change anything. The automation that might be wrong stays running because the risk of breaking something by fixing it feels higher than the risk of leaving it alone. The system calcifies - not because it's perfect, but because it's too opaque to touch safely. Complexity isn't sophistication There's a widespread assumption in marketing operations that a complex system is a sophisticated one. More workflows means more capability. More scoring rules means more precision. More conditional logic means more intelligence. That's wrong. Sophistication is achieving the right outcome with the minimum necessary complexity. A scoring model with 15 rules that correctly identifies buying intent is more sophisticated than one with 150 rules where nobody can explain why the thresholds are set where they are. A lifecycle with five well-defined stages is more sophisticated than one with twelve stages that the team can't distinguish between without opening the platform. The most effective marketing automation environments aren't the most complex ones. They're the ones where every workflow has a clear purpose, every rule has a documented reason, and anyone on the team can explain the system end to end without needing a diagram or a login. That's not simplicity for its own sake. It's operational maturity - the ability to run a capable system that the team understands well enough to maintain, improve, and trust. The explainability test There's a practical version of this that any team can run. It takes 30 minutes and produces immediately actionable results. Pick three people on the team who work with the platform regularly but didn't build most of the current configuration. Ask each of them separately to explain, without opening the platform, how the following work: the lead scoring model, the lifecycle stages and what triggers transitions between them, and the lead routing logic. Compare their answers. Where they agree, the system is understood. Where they disagree or can't answer, the system has outgrown the team's comprehension. Every point of disagreement or uncertainty is a governance gap - a place where the system is making decisions the team can't verify. The results usually reveal that the team understands the recent additions (the workflows they built themselves) and struggles with the legacy layer (the workflows someone else built months or years ago). That legacy layer is where the highest-risk automations live - the ones that have been running longest, touching the most data, making the most decisions, with the least oversight. The simplification mandate When the explainability test reveals gaps, the instinct is to document what exists. Documentation helps - but it treats the symptom. The cause is that the system grew more complex than it needed to be, and adding documentation on top of unnecessary complexity just makes the complexity official. The harder, more valuable exercise is simplification. Review every active workflow, scoring rule, and lifecycle transition. For each one, ask: does this still serve a current business need? Can someone on the team explain what it does and why? If the answer to either question is no, the workflow is a candidate for retirement. Most teams that run this exercise discover that a meaningful percentage of their active automations are either redundant, outdated, or duplicating logic that exists elsewhere in the system. Removing them doesn't reduce capability - it increases clarity. The system does the same work with fewer moving parts, and the team can explain what remains. The goal isn't a simple system. The goal is a system that's as complex as it needs to be and no more - one where every piece of complexity exists because someone chose it deliberately, documented it clearly, and can justify it today. At Sojourn Solutions, platform audits and simplification are core to how we work with clients. We help teams cut through accumulated complexity, retire what's no longer needed, document what remains, and rebuild the team's understanding of their own environment. If your system has reached the point where nobody can fully explain it, that's the starting point for the conversation - not a problem to work around.

There's a moment that happens about 18 months after a marketing automation platform goes live. Someone in leadership pulls up the original business case, looks at what the platform was supposed to deliver, and compares it to what's actually happening. The numbers don't match. Not dramatically - the platform hasn't failed. But the transformative results that justified the investment haven't materialized either. The team is using the platform every day and getting a fraction of what it's capable of. Most leadership teams blame the platform when this happens. The platform isn't the problem. The platform is a capability, not a result This is the distinction most leadership teams miss. A marketing automation platform is a set of capabilities - things it can do. Scoring, nurturing, segmenting, orchestrating, reporting, integrating, automating. Those capabilities are real. They exist inside the platform the moment it's implemented. But capabilities don't produce results. Operations produce results. The scoring model produces results when it's calibrated against real conversion data and recalibrated quarterly. The nurture produces results when it's built around genuine buyer needs and adapted based on engagement. The reporting produces results when the data feeding it is clean and the attribution model reflects the actual buyer journey. The gap between capability and result is filled by three things: people who understand the platform deeply enough to configure it properly, processes that ensure the configuration stays current as the business changes, and ongoing investment in the operational layer that most organizations treat as an afterthought once the implementation is "done." When leadership evaluates the ROI of the platform, they're usually looking at the license cost against the marketing results. If the results are underwhelming, the conclusion is often that the platform isn't delivering. The platform is delivering exactly what it's been configured to deliver - which, in most organizations, is a fraction of what it's capable of. The implementation isn't the finish line Most platform investments follow the same arc. The implementation is treated as the project. It gets budgeted, staffed, managed, and delivered. The platform goes live. The project closes. The team that implemented it moves on or disbands. And from that point forward, the platform is expected to operate on its own with whatever the internal team can manage. The problem is that implementation is the beginning, not the end. A platform that's well-implemented on day one will start degrading on day two - because the business changes. Products evolve. Audiences shift. The sales team restructures. New campaigns require new workflows. Data accumulates and ages. Integrations drift. AI features ship with platform updates that nobody reviews. Without ongoing operational investment - someone actively maintaining the configuration, optimising the campaigns, recalibrating the models, cleaning the data, documenting the workflows, and governing the AI features - the platform slowly reverts to a basic email sending tool. Not because it can't do more, but because nobody's keeping it tuned to do more. The organizations that get strong ROI from their MAP aren't the ones that spent the most on implementation. They're the ones that invested in operations after implementation - either with a well-resourced internal MOPs team or with an external partner that provides ongoing managed services. The utilization gap Ask your marketing ops team to list every platform capability they actively use. Then compare that list against what the platform actually offers. The gap is almost always wider than leadership expects. The scoring engine exists but the model is basic and hasn't been reviewed. The dynamic content functionality exists but every email uses the same static template. The A/B testing capability exists but nobody runs tests because there's no time. The advanced segmentation exists but the team creates the same three segments for every campaign. The API exists but integrations are minimal. The AI features exist but nobody knows which ones are active or what they do. Each unused capability represents value the organization paid for and isn't capturing. The license fee covers the full platform. The ROI comes from the portion the team actually uses. If the team uses 15%, the ROI is calculated on 15% of the capability - regardless of what was demonstrated in the sales demo. The fix isn't to use everything - not every capability is relevant to every business. The fix is to close the gap between what the organization needs from the platform and what it's currently configured to deliver. That gap analysis is the single most valuable exercise a marketing operations team - internal or external - can perform. People are the missing investment The uncomfortable truth in most marketing automation budget conversations is that the organization spent six or seven figures on the platform and a fraction of that on the people to run it. A sophisticated marketing automation platform requires dedicated operational expertise. Not a marketing generalist who also manages the platform. Not a campaign manager who configures workflows between other tasks. A person - or a team - whose primary job is to understand the platform deeply, configure it properly, maintain it actively, and evolve it as the business changes. Most mid-market organizations don't have this person. Most enterprise organizations have one person doing the work of three. The platform was sized for the ambition. The team was sized for the budget. And the gap between the two is where the ROI leaks. This is where external partners earn their value. A consultancy that provides ongoing managed services for marketing automation doesn't just execute campaigns - it maintains the operational health of the platform, identifies underused capabilities, recalibrates models, governs AI features, and ensures the platform keeps delivering value long after the implementation project closed. The ROI of the platform isn't in the license fee. It's in the operational investment that turns capabilities into results. The organizations that understand this - that budget for operations with the same seriousness they budget for the platform - are the ones getting their money's worth. The question leadership should be asking The next time the marketing automation platform comes up in a budget review, the question shouldn't be "is this platform delivering ROI?" The question should be "are we investing enough in the operations that determine whether it can?" If the answer is a well-resourced MOPs team with time to optimize, govern, and evolve the platform - the ROI will follow. If the answer is a stretched team running on the same configuration that was delivered during implementation two years ago - the ROI won't improve regardless of which platform you're running. The platform doesn't determine the return. How it's run does. And most organizations are underinvesting in exactly the part that makes the difference. At Sojourn Solutions, managed services and ongoing platform optimization are at the core of what we do. We work with organizations to close the gap between what the platform can do and what it's actually delivering - through operational support, model calibration, governance, and the continuous improvement that most internal teams don't have capacity for. If your platform is underperforming relative to what you invested, that's a conversation worth having.

Best practices are supposed to be the shortcut. The proven playbook. The thing that works. Someone figured it out, documented it, and now everyone can skip the hard thinking and go straight to execution. The problem is that everyone did exactly that. And now every B2B company is running the same plays, using the same frameworks, following the same advice - and wondering why nothing stands out. The gated ebook followed by a five-email nurture. The LinkedIn thought leadership carousel with the contrarian hook. The webinar with the panel and the Q&A. The ABM programme targeting the same accounts with the same intent data from the same providers. The lead scoring model weighted the same way it was weighted in every blog post that explained how to set up lead scoring. None of this is wrong. All of it is average. Because when everyone follows the same playbook, the playbook produces the mean, not the edge. Best practices are a floor, not a ceiling. They tell you the minimum viable approach. They don't tell you what's going to make anyone care. How best practices become background noise A best practice starts as an insight. Someone tries something, it works, they share it. Others adopt it because it worked for the first person. Consultancies package it. Vendors build it into their platforms. Conference speakers present it as essential. Within a few years, it's the default - not because it's still the most effective approach, but because it's the safest. This is the lifecycle of every marketing tactic that gets labelled "best practice." It was innovative when one company did it. It was effective when ten companies did it. It became invisible when a thousand companies did it. The buyer who received one gated ebook in 2016 paid attention. The buyer who receives fifteen a month in 2026 doesn't register any of them. The tactic didn't stop working because it's bad. It stopped working because it's ubiquitous. The buyer can't distinguish between your nurture sequence and your competitor's because they're structurally identical - same cadence, same content types, same CTA progression. Best practices made them that way. The safety trap The real appeal of best practices isn't effectiveness - it's safety. Following the established playbook means never having to justify a risky decision. Nobody gets questioned for running a standard nurture. Nobody gets challenged for building a lead scoring model that matches the industry template. Nobody gets fired for doing what everyone else does. Trying something different means taking a risk. What if it doesn't work? What if the numbers dip? What if leadership asks why you didn't follow the proven approach? The incentive structure in most marketing organizations actively punishes experimentation and rewards conformity. Do what works. Don't break things. Hit the numbers. So the team follows the playbook, hits mediocre numbers consistently, and presents them as evidence that the approach is working. The approach is working - in the sense that it produces predictable, average results. It's not working in the sense that it differentiates the company, captures attention, or gives the buyer any reason to choose you over the fifteen other companies doing the exact same thing. Safe marketing is invisible marketing. And invisible marketing is expensive - because you're paying the full cost of production for a fraction of the impact. What happens when someone breaks the playbook Every standout marketing moment in B2B comes from someone doing something the playbook didn't recommend. The company that ungated all its content when everyone else was gating - and saw organic traffic double because AI and search engines could finally find their best work. The team that killed their nurture sequence and replaced it with a single, honest email from a real person - and saw reply rates triple. The brand that published a brutally honest comparison of their product against their top competitor - including where the competitor wins - and became the most trusted source in their category. None of these were best practices when they happened. Some of them have since become best practices - which means they'll stop working soon too, as everyone copies the approach and it becomes the new default. The pattern is consistent: the companies that break through are the ones willing to do something the rest of the industry considers risky, unproven, or counterintuitive. Not reckless - thoughtful experimentation that starts from understanding the buyer rather than following the template. Best practices as a starting point, not a destination The answer isn't to ignore best practices entirely. They exist for a reason - they represent accumulated knowledge about what generally works. A team that knows nothing about lead scoring is better off starting with the standard model than inventing one from scratch. But the team that's still running the standard model two years later without questioning it, adapting it, or testing alternatives isn't being disciplined. They're being lazy. Best practices should be the foundation you build on, not the ceiling you operate under. The questions worth asking about any best practice: does this still work in our specific context, for our specific buyer, in the current market? Is everyone else doing this - and if so, what would be different enough to stand out? What would we try if we weren't afraid of deviating from the norm? Most teams never ask those questions because the playbook provides a comfortable answer. The comfortable answer is also the average answer. And the average answer, in a market where every competitor is following the same playbook, is the invisible answer. The companies that win aren't following the playbook They're writing their own. Not from arrogance - from understanding. They know their buyer well enough to know where the standard approach falls flat. They've tested enough to know which best practices actually work in their context and which ones are just inherited assumptions. They have leadership that tolerates short-term uncertainty in exchange for long-term differentiation. The playbook will always be there for the teams that want safety. It'll produce the same results it always produces - consistent, predictable, and indistinguishable from everyone else. The teams that want something better will have to put the playbook down and start thinking for themselves. That's uncomfortable. It's also the only path to marketing that anyone actually notices.

Journey orchestration is the phrase on every platform vendor's roadmap. The pitch goes like this: instead of running disconnected campaigns across email, ads, web, and events, you orchestrate a seamless, multi-channel experience that adapts in real-time to the buyer's behavior and guides them through a personalized path from awareness to purchase. It sounds transformative. And in the rare cases where the foundation is solid, it genuinely can be. But in most B2B organizations, journey orchestration is being implemented on top of a journey that nobody has actually mapped - and the result is an automated version of a process the team can't describe. You can't orchestrate what you don't understand. And most teams don't understand their buyer's journey nearly as well as they think they do. The internal process isn't the buyer's journey This is where most journey mapping goes wrong. The team sits in a room, draws a funnel on a whiteboard, and maps out stages: awareness, consideration, decision. Each stage gets content types, channels, and touchpoints assigned to it. The result looks logical, sequential, and clean. It's also completely fictional - because it describes the company's internal process, not the buyer's actual experience. The buyer doesn't move through stages in a straight line. They don't start with awareness, progress neatly to consideration, and arrive at decision in the order your whiteboard suggests. They bounce around. They research intensely for a week and then go dark for a month. They revisit content they read three weeks ago because a new stakeholder asked a question. They compare you to a competitor they discovered after your "consideration" stage content was supposed to have locked them in. The journey the team mapped is the journey the team wants the buyer to take. The journey the buyer actually takes is messier, longer, less linear, and driven by internal dynamics the team has no visibility into - budget cycles, competing priorities, organizational politics, and stakeholders who enter the process halfway through. When journey orchestration automates the idealized version of the journey, it creates an experience that feels robotic to the buyer. They get an email about "next steps" when they're still figuring out the problem. They receive bottom-of-funnel content because they visited a pricing page once out of curiosity, not intent. The orchestration moves them forward on the company's timeline, not their own. The data gap underneath the orchestration Even if the journey map were accurate, most organizations don't have the data infrastructure to support genuine orchestration. Journey orchestration requires knowing what the buyer is doing across every channel - email engagement, web behavior, ad interactions, event attendance, sales conversations - and stitching all of that into a coherent picture that updates in real-time. That requires clean, unified data flowing between systems without gaps or delays. Most B2B marketing teams don't have that. The MAP tracks email and form activity. The CRM tracks sales interactions. The ad platform tracks impressions and clicks. The website analytics tracks page visits. The event platform tracks registrations. Each system sees a fragment of the buyer's behavior. None of them see the whole picture. Stitching these fragments together requires identity resolution (matching anonymous web visitors to known contacts), cross-platform data integration (making sure the MAP, CRM, and advertising platforms share the same data in real-time), and a data model that's designed for journey-level analysis rather than campaign-level reporting. Most teams implementing journey orchestration haven't solved any of these problems. They've bought a tool that promises orchestration and plugged it into the same fragmented, partially integrated data ecosystem they've always had. The orchestration runs - but it runs on an incomplete picture of the buyer, making decisions based on the channels it can see and ignoring the ones it can't. Content is the bottleneck nobody plans for Even with a perfect journey map and perfect data, journey orchestration requires something most marketing teams massively underestimate: content. Real orchestration means delivering the right content to the right person at the right time based on their behavior, their role, their stage, and their specific interests. That doesn't mean one ebook per stage. It means multiple content pieces for multiple personas at multiple stages, each relevant enough to justify the interruption. A journey that covers three personas across five stages with two content options per stage-persona combination requires 30 pieces of content — and that's a minimal framework. Add channels (email, ads, web personalization) and the number multiplies. Most teams don't have this content. They have a handful of ebooks, a library of blog posts, and a few case studies. When the orchestration engine reaches for "mid-stage content for the IT buyer persona," there's nothing there - so it serves the generic version, which defeats the purpose of orchestrating in the first place. The team ends up running a "personalized journey" where every persona receives roughly the same content in roughly the same order, with the only variation being the timing. That's not orchestration. That's a nurture sequence with extra infrastructure. Start with understanding, not automation The fix isn't to abandon journey orchestration as a concept. It's to do the foundational work before attempting the automation. Talk to your buyers. Not through surveys - through actual conversations. Interview recent customers and ask how they found you, what they researched, who else they considered, what content was useful, and what made them decide. Interview lost deals and ask the same questions. The patterns in those conversations will tell you more about the actual journey than any whiteboard session. Map what you can observe. Use the data you have - website analytics, email engagement, content consumption, sales conversation notes - to identify the paths buyers actually take, not the paths you want them to take. Where do they enter? What do they engage with first? Where do they drop off? Where do they come back? The observed journey is always different from the assumed journey. Identify the moments that matter. Not every stage needs orchestration. Find the three or four moments in the journey where the buyer's behavior changes - the moment they shift from browsing to researching, from researching to evaluating, from evaluating to deciding. Design your orchestration around those moments rather than trying to automate the entire journey end to end. Audit your content against the journey. Map your existing content to the journey stages and personas. Where are the gaps? Where do you have six assets for one stage and none for another? Fill the gaps before activating the orchestration - otherwise you're automating a content-starved experience that'll disappoint the buyer and waste the investment. Fix the data first. If your systems aren't integrated, your identity resolution is incomplete, or your cross-channel data is fragmented, the orchestration will make decisions on partial information. Every integration gap is a blind spot the orchestration engine can't compensate for. Orchestrate what you understand. Understand before you automate. Journey orchestration is powerful when it's built on a genuine understanding of the buyer, supported by clean data, and fueled by content that's relevant at every stage. Those conditions are rare - not because they're impossible, but because most teams skip the understanding phase and go straight to the automation phase. At Sojourn Solutions, we help organizations build the operational foundation for journey orchestration - from buyer journey mapping and data infrastructure assessment through to campaign architecture and content strategy. The orchestration platform is the last step, not the first. If you're considering journey orchestration or struggling to get value from one you've already implemented, we'd welcome the conversation.

There's a pattern in how marketing teams get evaluated, promoted, and celebrated. Build a complex, multi-channel campaign with sophisticated segmentation, dynamic personalization, and AI-powered optimization across six touchpoints - and the team gets praised for the ambition and the sophistication. Build a simple email from a real person's name with a clear message and a single CTA - the one that actually outperforms the complex version - and nobody's impressed. It doesn't look like enough effort. It doesn't fill a case study. It doesn't win an award. It's just a good email. The industry has built an incentive structure that rewards the appearance of sophistication and punishes the efficiency of simplicity. The result is marketing operations that are more complex than they need to be, producing results that are harder to measure, harder to maintain, and no better than a simpler approach would have delivered. Complexity gets rewarded because it looks like work In most organizations, the value of a project is judged partly by its visible effort. A campaign that took six weeks to build, involved three teams, required a custom integration, and produced a 47-slide post-mortem feels important. A campaign that took an afternoon, used an existing template, and delivered the same result feels trivial. The outcome is the same. The perception isn't. And perception drives careers. This means the incentive for the marketer isn't to find the simplest path to the result. It's to build something that looks proportionate to the expectation. If leadership expects a sophisticated, multi-touch campaign, delivering a single email that works better would feel like underdelivering - even if the numbers prove otherwise. So the team builds the complex version. Not because it's more effective, but because simplicity feels like it needs to be defended while complexity defends itself. Nobody questions a six-week project. Everybody questions why something only took a day. The martech stack is built on this incentive The same dynamic plays out in technology decisions. A lean stack - an MAP, a CRM, and a good process - can execute virtually everything a B2B marketing team needs. But nobody gets budget approval for "we're going to use what we have more effectively." They get budget approval for "we're going to implement a new AI-powered intent data platform that integrates with our existing stack to enable predictive account-level engagement scoring." The second option sounds transformative. The first sounds like maintenance. One gets funded. The other doesn't. Over time, this produces stacks of 15 or 20 tools where five would do the job. Each tool was justified individually. Each tool added a layer of complexity. The stack as a whole became harder to operate, harder to maintain, and harder to extract value from - but it looks impressive on the martech map, and it filled a lot of budget slides with forward-looking investment narratives. The teams running lean stacks with deep expertise and strong processes don't get featured in case studies. The teams running bloated stacks with surface-level usage across everything get invited to speak at conferences about their "marketing transformation journey." The incentives are backwards. Complexity hides accountability There's a quieter reason complexity persists: it's harder to hold accountable. A simple campaign either works or it doesn't. A single email to a defined segment produces a clear result. If it fails, the failure is obvious and traceable - the message didn't resonate, the audience wasn't right, the timing was off. There's nowhere to hide. A complex, multi-channel campaign with eight touchpoints and three audience segments and dynamic content and AI-optimised send times? When that underperforms, the post-mortem has infinite variables. Was it the messaging? The segmentation? The channel mix? The AI? The send time? The landing page? Each variable absorbs a share of the blame and nobody is accountable for the whole. Complexity creates ambiguity. Ambiguity prevents accountability. And in organizations where accountability is uncomfortable, complexity becomes a defence mechanism - not a strategy. The team that runs simple campaigns and measures them honestly will learn faster than the team that runs complex campaigns and analyses them endlessly. Learning requires clear signals. Complexity drowns signals in noise. Simplicity requires more skill, not less This is the part the industry gets backwards. Building something complex is easy - you just keep adding. Another channel, another touchpoint, another integration, another layer. Each addition feels like progress. Building something simple requires restraint. It requires knowing what to leave out. It requires understanding the buyer well enough to know that one clear message will land harder than five layered ones. It requires confidence that a single-channel campaign with the right audience and the right content will outperform a multi-channel campaign with diluted focus. Simplicity means making decisions. Complexity means deferring them. When you build a simple campaign, you've committed to a specific audience, a specific message, and a specific outcome. When you build a complex one, you're hedging - covering multiple audiences, multiple messages, multiple channels, hoping that something will work without having to decide what that something is. The best marketers are the ones who can look at a complex brief and say "we don't need most of this. Here's the one thing that will actually work." That takes more skill than building the complex version. It just looks like less effort - which, in an industry that rewards visible effort, is its own punishment. What would marketing look like if simplicity was rewarded? Fewer campaigns, executed better. Smaller stacks, configured deeper. Shorter content, written with more precision. Clearer messaging, tested honestly. Less time in post-mortems debating which of twelve variables caused the underperformance. More time understanding the buyer well enough to get it right the first time. The team would spend less time building and more time thinking. Less time configuring platforms and more time talking to customers. Less time producing content for the calendar and more time producing content for the buyer. Results would be easier to measure because there would be fewer variables. Accountability would be clearer because there would be fewer places to hide. The work would move faster because there would be less of it to move. And the marketing would be better - because better marketing isn't more marketing. It's the right marketing, aimed at the right person, saying the right thing. The industry won't reward this. Conference stages won't feature the team that sent one brilliant email instead of building a twelve-week campaign. Award submissions won't celebrate the marketer who killed seven tools from the stack and improved results. But the results will speak for themselves. And in the end, that's the only thing that actually matters - even if nobody puts it on a slide.

Here's a question that should be easy to answer: how ready is your marketing operations team for AI? Not "are you using AI" - most teams are, whether they realize it or not. The platform features, the scoring enhancements, the content tools, the send-time optimizers. AI is already inside the stack. That's not the question. The question is whether you know what AI is doing in your environment, whether your data is in a state to support it, whether your team has the skills to manage it, whether there's any governance around it, and whether anyone can confidently say your organization is ready for what comes next - not just the AI you've adopted, but the AI your platform is about to ship, the AI your competitors are deploying, and the AI that regulators are about to start asking questions about. Most teams can't answer that. Not because they're behind - because nobody's asked. Nobody's assessed. Nobody's measured. There's no baseline. And without a baseline, every AI decision is a guess. The confidence gap There's a particular kind of confidence that's common in B2B marketing teams right now. The team is using AI tools. Campaigns are running. Content is being produced faster. The platform's AI features are active. Leadership has been briefed. Everything feels like progress. But underneath that confidence, there are questions nobody's sat down to answer. How mature is your data - not in theory, but right now? When was the last time someone checked whether the fields feeding your AI-powered scoring model are still accurate? Is your consent data current enough to withstand regulatory scrutiny? Are the AI features in your platform configured deliberately, or did they get activated during an upgrade and nobody reviewed them? Does your team know how to evaluate AI outputs, or are they trusting whatever the platform produces? Is there a process for detecting when AI-driven decisions start drifting? Is anyone monitoring whether the AI is actually improving results, or has "we have AI" become the result in itself? The gap between feeling ready and being ready is where the risk lives. And most organizations can't measure that gap because they've never tried. Why self-assessment matters now Three things are converging that make self-assessment urgent rather than optional. Regulatory pressure is arriving. The EU AI Act's main provisions take effect in August 2026. Transparency and documentation requirements apply broadly - not just to high-risk AI systems. Any organization whose automated systems affect EU residents needs to be able to explain what those systems do, what data they use, and how decisions are made. That explanation requires knowing what's running in your environment - which requires an assessment. AI adoption is accelerating without governance keeping pace. Every platform is shipping new AI capabilities every quarter. Teams are activating features faster than they're governing them. The gap between what AI is doing inside the platform and what anyone can explain about it grows with every upgrade cycle. An assessment catches that gap before it becomes a liability. The competitive landscape is splitting. The organizations that understand their AI maturity - where they're strong, where the gaps are, and what to prioritize - are making better decisions about what to adopt, what to defer, and where to invest. The ones operating on assumption are adopting everything, governing nothing, and hoping the results justify the spend. The split between these two groups is getting wider. What an honest assessment reveals Most teams that go through a structured AI readiness assessment are surprised by what they find. Not because the findings are catastrophic - because the picture is uneven in ways they didn't expect. Data readiness is almost always lower than assumed. The team thinks the data is clean because the dashboards look fine. The assessment reveals consent records that haven't been reconciled in two years, scoring models calibrated to a buyer profile that's shifted, and enrichment sources nobody's reviewed since the contract was signed. AI is making decisions on all of it. Governance is almost always more fragmented than it appears. There's a policy somewhere. But the assessment reveals that nobody can produce a complete list of active AI features, nobody owns the AI layer as a distinct operational responsibility, and there's no process for detecting when AI-driven decisions drift. The governance exists in principle but not in practice. Team capability varies dramatically. Some team members are confident and skilled with AI tools. Others are activating features they don't fully understand because nobody provided training. The assessment reveals whether the team's AI capability is broad enough to support the AI footprint they're operating - or whether a few individuals are carrying the entire AI competency while the rest of the team works around it. Alignment across functions is weaker than expected. Marketing, sales, IT, legal, and compliance each have a partial view of AI in the organization. The assessment reveals whether those views are consistent - and they almost never are. Marketing thinks governance is handled. Legal thinks marketing is handling it. IT thinks the platform vendor is handling it. Nobody is handling it. Knowing where you stand changes the conversation The value of an assessment isn't the score. It's what the score makes possible. A team that knows its data readiness is strong but its governance is weak can prioritize governance without questioning its data investment. A team that knows its AI adoption is ahead of its team's capability can invest in training before the gap creates problems. A team that knows it's ahead of its industry peers can move faster with confidence. A team that knows it's behind can make a case for investment with evidence instead of anxiety. Without the assessment, every conversation about AI readiness is based on feeling - and feelings are unreliable. "I think we're in good shape" isn't a strategy. "We assessed at 7/10 on adoption, 4/10 on governance, and 5/10 on data readiness — here's where we need to invest" is a strategy. The baseline turns vague concern into specific action. That's what most teams are missing. Take the assessment Sojourn Solutions is building an industry benchmark report on AI adoption, governance, and operational readiness within marketing operations in 2026. As part of it, we've built an assessment that gives you a clear snapshot of where your organization currently stands. It takes around 7 minutes. You get your results immediately. And your data contributes to an industry-wide picture of where MOPs teams actually are with AI - not where vendors say they should be. Take the AI Benchmark Assessment → The teams that know where they stand will make better decisions than the ones that don't. The assessment is the starting point.

Ask a marketer from 15 years ago what they spent most of their time on and they'd say something like: understanding the customer. Researching what they need. Figuring out how to reach them. Writing something that would make them pay attention. The work was about people - understanding their motivations, their hesitations, their decision-making process. Ask a marketer today what they spend most of their time on and you'll get a very different answer. Configuring the MAP. Setting up workflows. Troubleshooting the CRM integration. Building segments based on field values. Checking why the sync broke. Learning the new feature the platform shipped last week. Figuring out why the report shows different numbers depending on which dashboard you pull it from. The work shifted. Somewhere along the way, marketing became less about understanding the buyer and more about operating the machinery that's supposed to reach them. The platforms won. The people got lost. The platform ate the profession This didn't happen overnight. It happened gradually, one tool at a time. First the email platform arrived, and marketers learned to think in terms of open rates and click rates instead of whether the message actually resonated. Then the marketing automation platform arrived, and marketers learned to think in terms of workflows, triggers, and scoring models instead of whether the buyer's journey made sense. Then the CRM integration arrived, and marketers learned to think in terms of field mappings, sync errors, and lifecycle stages instead of whether sales and marketing were actually aligned on what a good customer looks like. Each tool solved a real problem. Each tool also created a new layer of operational complexity that required someone to manage it. And the person managing it was usually a marketer - someone who was hired to understand customers and gradually became an administrator of systems. The job title says marketing. The job description says platform management. The gap between the two gets wider every year. The skills that get hired for have changed Look at a marketing job posting from 2010 and you'd see requirements like: strong writing skills, understanding of customer psychology, experience with brand positioning, ability to develop messaging that resonates with target audiences. Look at a marketing job posting today and you'll see: experience with Marketo/HubSpot/Eloqua, proficiency in Salesforce, knowledge of HTML/CSS for email templates, experience with marketing attribution tools, familiarity with data management and segmentation. The hiring criteria shifted from understanding people to operating technology. The marketers getting hired today are selected for their ability to work inside platforms, not for their ability to understand the humans those platforms are supposed to reach. This isn't wrong, exactly. The platforms are complex and someone needs to run them. But the imbalance is real. Most marketing teams are over-indexed on people who can operate the machinery and under-indexed on people who can tell you whether the machinery is pointed at the right audience with the right message. The campaign gets built. The buyer gets forgotten. Watch how a campaign gets created in most B2B marketing teams. Someone decides a campaign is needed. A brief gets written - usually focused on the asset (the ebook, the webinar, the email) and the mechanics (the segment, the workflow, the follow-up sequence). The team builds it inside the platform, tests it, and sends it. At no point in that process does someone typically stop and ask: why would the buyer care about this? Not "does this hit our MQL target." Not "does this align with our content calendar." Why would a real person, sitting at their desk, dealing with their actual problems, stop what they're doing to engage with this? That question used to be the starting point. Now it's an afterthought - if it's thought about at all. The process is optimized for building and sending, not for relevance. The team measures whether the campaign went out, not whether it mattered to anyone who received it. The result is a steady stream of technically competent, operationally sound campaigns that nobody particularly wants to receive. The emails are well-formatted. The workflows fire correctly. The segments are clean. And the human on the other end deletes it in two seconds because nothing about it spoke to their actual situation. Data replaced intuition. That's not entirely a good thing. The data-driven marketing movement was supposed to make marketing more effective by grounding decisions in evidence instead of gut feel. And in many ways it has. We know more about buyer behavior than at any point in history. We can track every click, every page visit, every email open, every form submission. But somewhere along the way, the data became a substitute for understanding rather than a tool for deepening it. Teams started making decisions based on what the data said without asking what the data meant. Open rates went up - but did the message actually resonate, or did the subject line just trigger curiosity? Click rates improved - but did the content deliver value, or did the CTA create false urgency? MQLs hit target - but were those leads genuinely interested, or did the scoring model reward activity without distinguishing intent? Data tells you what happened. It doesn't tell you why. And understanding why - why the buyer engaged, why they hesitated, why they chose someone else - requires the kind of empathy, curiosity, and human understanding that no dashboard provides. The best marketers use data to validate and refine their understanding of the buyer. The worst marketers use data to replace that understanding entirely. The difference shows up in the work - one produces campaigns that feel like they were written for a real person, the other produces campaigns that feel like they were assembled by an algorithm. The pendulum needs to swing back This isn't an argument against marketing technology. The platforms are necessary. The data is valuable. The operational infrastructure that makes modern marketing possible at scale is a genuine achievement. But the balance is off. Too many marketing teams have become platform operators who occasionally think about the buyer, when they should be buyer experts who happen to operate platforms. The order matters - because the platform doesn't know who the buyer is. It processes data about them. Understanding them is a human job that no tool, no workflow, and no AI feature will ever fully replace. The teams that still start with the buyer - who is this person, what do they need, what are they worried about, what would actually help them - produce work that feels different. The emails get read. The content gets shared. The campaigns generate conversations, not just clicks. Not because the platform is better, but because someone took the time to understand the person before building the machine. Marketing technology made it possible to reach millions of people with precision and speed. It didn't make it easier to understand any one of them. That's still the hard part. And the teams that remember it's the hard part are the ones producing work that actually matters.

Something has shifted in B2B buying behavior and most marketing teams haven't caught up. The buyer who shows up on your website today is not the same buyer who showed up three years ago. Three years ago, they arrived early in their research process - looking for information, comparing options, trying to understand the category. They needed educating. They needed nurturing. They needed the whitepaper, the webinar, the email sequence that walked them through the problem and the solution. Today's buyer arrives pre-informed. They've already read about your category. They've already compared your product to the alternatives. They've asked an AI assistant to summarize the differences. They've read reviews on G2. They've asked their network on LinkedIn. By the time they land on your website or fill out a form, they're not at the beginning of their research. They're near the end. They don't need educating. They need confirming. And most B2B marketing strategies are still built for the buyer who needed educating. The information gap closed. Marketing didn't notice. B2B marketing strategy has been built for decades on one fundamental assumption: the buyer knows less than the seller. The seller has the expertise, the data, the insights. The buyer needs to be led through a journey - awareness, consideration, decision - with content mapped to each stage. That assumption held when information was scarce. When the only way to learn about a product category was to attend a conference, read a trade publication, or talk to a sales rep. When the vendor controlled the narrative because the vendor controlled the information. That world is gone. Information is abundant, accessible, and increasingly synthesized by AI tools that give the buyer a coherent answer in 30 seconds. The buyer no longer depends on the vendor for information. They depend on the vendor for validation - proof that what they've already learned is accurate, and evidence that this specific vendor can deliver. The marketing strategies that worked in the information-scarce world - gated ebooks that introduce basic concepts, nurture sequences that educate over weeks, webinars that explain the problem before presenting the solution - feel increasingly irrelevant to a buyer who figured all of that out before they engaged with you. What the pre-informed buyer actually wants The pre-informed buyer has specific needs that most B2B marketing isn't serving. They want proof, not education. They already understand the problem and the solution category. What they need is evidence that your company can deliver - case studies with specific results, customer references, implementation timelines, integration details. The content that matters isn't "what is marketing automation?" It's "how did a company like ours implement this and what happened?" They want specifics, not overviews. They've already read the overview. They asked AI for it this morning. What they can't get from AI is the specific detail about your product - how it handles their particular use case, what the implementation actually involves, what the limitations are. Honest, detailed, specific content is what separates your marketing from the AI-generated summary they've already read. They want speed, not sequences. A buyer who's near the end of their evaluation doesn't want to be enrolled in a six-email nurture sequence that starts with "the evolving landscape of..." They want to talk to someone, see the product, and get answers to their specific questions. The time between first engagement and sales conversation should be hours, not weeks. They want honesty, not positioning. Pre-informed buyers have already seen your competitors' messaging. They know what everyone claims. What cuts through is honesty - what your product does well, what it doesn't do, who it's built for, and who should probably look elsewhere. That kind of transparency is rare in B2B, which is exactly why it stands out. The nurture problem Most B2B nurture programmes were designed for a buyer who doesn't exist in the same numbers anymore. The traditional nurture assumes the buyer needs time and education. It sends content at intervals - a blog post this week, a case study next week, an ebook the week after - gradually building awareness and interest until the buyer is "ready" for a sales conversation. For a buyer who arrived pre-informed and ready to evaluate, this nurture isn't nurturing. It's delaying. Every email in the sequence that teaches them something they already know is an email that wastes their time and signals that your company doesn't understand where they are in their process. The nurture programme that works for today's buyer looks different. It's shorter. It focuses on proof and specifics rather than education. It adapts based on what the buyer has already done - if they've visited the pricing page and read a case study, they don't need an introductory email. They need a direct line to sales. The teams that still run education-heavy nurtures on every lead regardless of behavior are training their best prospects to be patient while their competitors are training theirs to be fast. The sales handoff is where most teams lose the pre-informed buyer Even when marketing adapts to the pre-informed buyer, the sales handoff often undoes the work. The buyer arrives having done extensive research. They fill out a form expecting a conversation with someone who understands their situation. Instead, they get a discovery call where the sales rep asks them to explain their business, their challenges, and their requirements from scratch - all information the buyer assumed the company already knew based on their engagement history. This is the moment the pre-informed buyer mentally downgrades the vendor. They did their homework. The vendor didn't. The sales rep is asking questions the marketing data should have already answered - what pages the buyer visited, what content they downloaded, what their company does, how big they are. The fix is operational: make sure the handoff includes context. When a lead is passed to sales, it should come with a complete engagement history, the account's firmographic data, and any intelligence about where they are in their evaluation. The sales rep should know more about the buyer than the buyer expects - not less. Adapt or get filtered out The pre-informed buyer isn't a trend that's going to reverse. AI tools are getting better at synthesizing information. Review platforms are getting more comprehensive. Peer networks are more connected. The amount of research a buyer can do before engaging with any vendor is only going to increase. Marketing teams that adapt will shift their content strategy from education to evidence. They'll shorten their nurtures. They'll speed up their handoffs. They'll invest in the kind of specific, honest, proof-heavy content that a pre-informed buyer actually needs - and they'll stop producing the introductory content that AI can generate better and faster than any marketing team. Marketing teams that don't adapt will keep building awareness campaigns for buyers who are already aware, nurture sequences for buyers who don't need nurturing, and educational content for buyers who already graduated. They'll wonder why engagement is declining, why form fills are dropping, and why the buyers who do engage seem impatient and unimpressed. The buyer got smarter. The question is whether your marketing catches up - or keeps talking to the buyer who used to exist.

There's a specific kind of marketing team that's always busy. Always launching something. Always behind on something else. The roadmap has 30 initiatives, 15 are in progress, 8 are overdue, and someone just added 3 more because the CEO saw something a competitor did. The team is exhausted. The work is spread across too many things to do any of them well. Campaigns launch half-finished because there wasn't time to QA properly. Content goes out without being reviewed because the next piece is already due. Reports get skipped because nobody has time to analyze what happened - they're too busy setting up what happens next. This team says yes to everything. And that's exactly why they're underperforming. Yes is the default. That's the problem. In most marketing organizations, saying yes is the path of least resistance. A request comes in from sales - "can we do a campaign for this segment?" Yes. The CEO wants a presence at a new event - yes. Product marketing needs email support for a launch - yes. A partner wants co-branded content - yes. Someone read an article about a new channel and wants to test it - yes. Each individual yes is reasonable. The campaign makes sense. The event could be valuable. The launch needs support. The partner relationship matters. Saying no to any one of them feels like obstruction - like the marketing team is being difficult instead of being helpful. But the aggregate of every yes is a team doing 20 things at 50% instead of 10 things at 100%. Resources get spread thinner with every commitment. Quality drops because there's not enough time to do the work properly. Impact drops because nothing gets the attention it needs to actually perform. The team isn't underperforming because it lacks talent or tools. It's underperforming because it never said no - and the workload grew until the quality of everything suffered equally. The cost of every yes is invisible When you say yes to a new initiative, the cost isn't just the time it takes to execute. It's the time it takes away from everything else. Every campaign that gets added to the roadmap pushes other campaigns back. Every ad hoc request that gets accepted delays the planned work. Every "quick project" that leadership drops in consumes the buffer that was supposed to protect the team's ability to do their core work well. These costs are invisible because they don't appear on a balance sheet. Nobody tracks the campaign that went out without proper QA because the team was building something else. Nobody measures the optimization that didn't happen because there was no time for analysis. Nobody counts the strategic work that got postponed indefinitely because the team was too busy executing requests. But the impact shows up. It shows up in campaigns that underperform because they were rushed. In content that doesn't convert because it was produced to hit a deadline, not to serve the buyer. In a team that's burning out because the workload never stops growing and nobody is authorized to push back. What saying no actually looks like Saying no doesn't mean being unhelpful. It means being honest about capacity and ruthless about prioritization. When a request comes in, the response isn't "no, we can't do that." It's "we can do that, but here's what it displaces." Making the trade-off visible is the most important thing a marketing leader can do - because most of the people making requests have no idea what the team is already working on. The CEO who asks for a presence at an event doesn't know the team is in the middle of a platform migration. The sales leader who wants a campaign for a new segment doesn't know the team is behind on three existing campaigns. The product manager who needs launch support doesn't know the team just lost a person and hasn't backfilled the role. When the trade-off is visible - "we can do the event, but we'll need to push the nurture redesign to next quarter" - the requestor can make an informed decision. Sometimes the event is more important. Sometimes it's not. But the decision is made with full information instead of blind optimism about the team's capacity. This requires marketing leadership to protect the team's bandwidth the same way engineering leadership protects sprint capacity. Nobody walks up to an engineering team and says "add this feature by Friday" without understanding the sprint. Marketing deserves the same discipline. Prioritization is the highest-value skill in marketing The teams that outperform aren't the ones doing the most. They're the ones doing the right things - and only the right things. That means having a clear framework for what gets done and what doesn't. Not a vague sense of priorities - an explicit, documented list that the team and its stakeholders agree on. These are the three things we're focused on this quarter. These are the requests we'll accept. These are the ones we'll defer. Here's why. When everything is a priority, nothing is. That's not a motivational poster line - it's the operating reality of most marketing teams. The quarterly plan has 15 "priorities" which means it has zero, because the team will spend the quarter reacting to whatever is loudest rather than executing against what matters most. The teams that say no have shorter priority lists. They commit to fewer things and execute them properly. Their campaigns are better because they had time to plan, build, test, and optimize. Their content is stronger because someone actually reviewed it. Their reporting is meaningful because someone had time to analyze it. The output looks like less. The impact is more. That trade-off is hard to sell internally - especially in organizations that measure marketing by volume of activity. But the teams that make the shift consistently outperform the ones that stay on the hamster wheel. How to build the muscle Saying no is a skill most marketing teams haven't practiced. It feels uncomfortable, especially in cultures where being busy is equated with being valuable. Building the muscle takes deliberate effort. Start with the intake process. Every request should go through a single channel - not direct messages, not hallway conversations, not emails to individual team members. A single intake point makes the total volume visible, which is the first step toward managing it. Evaluate every request against the quarterly priorities. If it aligns, it goes on the roadmap. If it doesn't, it gets logged for future consideration - but it doesn't get worked on now. The log is important because it shows the team isn't dismissing requests. It's sequencing them. Make capacity visible. Whether it's a kanban board, a sprint plan, or a simple shared document - the team's current workload should be visible to anyone who wants to add to it. When a stakeholder can see that the team is at capacity, the conversation shifts from "why won't you do this?" to "what should we deprioritize to make room?" Review quarterly. At the end of each quarter, look at what got done, what got deferred, and what the impact was. Over time, this builds evidence that focused execution outperforms scattered activity - and that evidence makes it easier to say no next quarter. The courage to be focused The marketing team that says yes to everything will always look busy. Dashboards will show activity. Content will ship. Campaigns will launch. The team will be exhausted and the results will be average across the board. The marketing team that says no will look less busy. Fewer things will ship. Some stakeholders will be frustrated that their request got deferred. But the things that do ship will be better - better planned, better executed, better measured, and more likely to produce the results that actually matter. The difference isn't talent. It's discipline. And the hardest part of that discipline is the first time someone says "can you do this?" and the answer is "not right now - here's why." That conversation is uncomfortable. It's also the beginning of a marketing team that actually delivers instead of one that just stays busy.

There's a test you can run to see how your organization thinks about marketing ops. Look at where the team sits in the org chart. Look at who they report to. Look at what they get asked to do on a daily basis. Then look at what gets said about them in leadership meetings. If the answers are "buried under demand gen," "a marketing manager who doesn't understand the platform," "build this email, fix this list, pull this report," and "nothing - they don't come up" - then your organization treats marketing ops as a support function. A service desk. The team that makes things go when someone else decides what should go. That's how most organizations treat MOPs. And it's costing them far more than they realize. The service desk trap When marketing ops is treated as a support function, the work becomes reactive. The team doesn't plan. They respond. Campaign requests arrive and get built. Data issues get flagged and get fixed. Reports get requested and get pulled. The team is permanently in execution mode, processing a queue of requests from other teams who decide what gets done and when. This feels productive. The team is busy. The queue is always full. Campaigns go out. Reports get delivered. From the outside, marketing ops looks like it's working. From the inside, the team is drowning. There's no time to audit the platform. No time to optimize scoring models. No time to document workflows. No time to evaluate whether the campaigns being requested are the right campaigns, or whether the data underneath them is reliable, or whether the reporting structure actually measures what matters. The team knows the platform better than anyone in the organization. They see every campaign, every data flow, every automation, every integration. They know where the problems are. They know what's broken, what's inefficient, and what's creating risk. But nobody asks them, because their role is defined as "build what we tell you to build," not "tell us what we should build." The cost of excluding MOPs from strategy When marketing ops is excluded from strategic decisions, those decisions get made without the one team that understands the operational reality. The CMO decides to launch an ABM programme. Nobody asks MOPs whether the data architecture supports account-level targeting. It doesn't. The team spends three months building workarounds. Leadership decides to migrate platforms. Nobody asks MOPs about the complexity of the current automation environment. The migration timeline is set at three months. It takes nine. The extra six months weren't caused by the new platform being difficult - they were caused by the old platform being far more complex than anyone outside MOPs understood. Someone in the leadership team approves a new tool. Nobody asks MOPs whether it integrates with the existing stack. It doesn't — not cleanly. The team spends weeks building a custom integration that a five-minute conversation would have flagged before the purchase. These aren't hypothetical scenarios. They're patterns that repeat in every organization that treats MOPs as execution rather than strategy. The decisions get made upstairs, the consequences get absorbed downstairs, and the team that could have prevented the problem wasn't in the room when the decision was made. What MOPs actually knows Marketing ops sits at the intersection of marketing strategy, data, technology, and revenue operations. No other function in the organization has that cross-functional visibility. MOPs knows which campaigns are actually driving pipeline - not what the dashboard says, but what the data actually shows when you dig past the vanity metrics. They know which segments are engaged and which are exhausted. They know which parts of the lead lifecycle are working and which are leaking. They know where the data is clean and where it's not. They know which integrations are stable and which are held together with workarounds. They know which automations are running as intended and which have drifted. They know where the compliance risks sit - which consent records are current, which suppression rules make sense, and which AI features are running without anyone monitoring them. This knowledge isn't just operational - it's strategic. A CMO who understands the state of their marketing infrastructure, data quality, and automation environment makes better decisions than one who doesn't. And the only team that can provide that understanding is MOPs. But when MOPs is buried in the org chart as a service desk, that knowledge never reaches the people making decisions. It stays trapped in the team that has it, used only to react to problems instead of prevent them. The org chart problem Where MOPs sits in the organization determines what it's allowed to do. And in most companies, MOPs sits too low. When MOPs reports to a demand gen manager, the team's priorities get set by campaign timelines and lead targets. There's no mandate to audit, optimize, or advise - just to build and send. The work is defined by the queue, and the queue is defined by someone whose job is to generate leads, not to build operational infrastructure. When MOPs reports to a VP or director of marketing operations - or better, to the CMO directly - the team's mandate expands. They can prioritize platform health alongside campaign execution. They can flag data quality issues before they become pipeline problems. They can advise on technology decisions before the purchase, not after. They can build the governance, documentation, and process infrastructure that every organization needs and nobody wants to fund. The reporting line doesn't just affect the team's authority. It affects what the organization sees as MOPs' purpose. If MOPs reports to a campaign manager, MOPs is a campaign support team. If MOPs reports to the CMO, MOPs is an operational function with strategic input. The team's capabilities don't change. The organization's willingness to use them does. What changes when MOPs gets a strategic seat The shift isn't dramatic. It doesn't require a reorganisation or a new title. It requires including MOPs in the conversations where decisions get made - and then actually listening to what they say. Before a platform purchase, MOPs evaluates the integration requirements and flags complications the vendor won't mention. Before a migration, MOPs maps the current automation environment so the timeline reflects reality. Before an ABM launch, MOPs assesses whether the data supports account-level targeting. Before an AI feature gets activated, MOPs checks what data it consumes and whether that data is reliable. These are five-minute conversations that save months of rework. But they only happen when MOPs is in the room - and when the organization recognizes that the team building the campaigns also understands the infrastructure those campaigns depend on. The best marketing operations teams aren't the ones that build the fastest. They're the ones that get asked "should we do this?" before they get told "build this." That question is the difference between a support function and a strategic one. The team you're underusing is the one that knows the most Every organization that's invested in a marketing automation platform, a CRM integration, a data infrastructure, and a campaign operation has already invested in marketing ops - whether they think of it that way or not. The team exists. The knowledge exists. The cross-functional visibility exists. The question is whether the organization uses that investment fully or wastes it by limiting MOPs to building emails and pulling reports. One path produces a marketing operation that's reliable, scalable, and strategically informed. The other produces a service desk that's permanently overwhelmed and permanently undervalued. The platform doesn't care who decides the strategy. But the strategy works better when the people who understand the platform are involved in making it. That's not a radical idea. It's just one that most organizations haven't acted on yet.

The EU AI Act becomes broadly applicable on 2 August 2026. For some organisations, that date will represent the final stage of a carefully managed programme involving legal, security, IT, data and every business team using AI. For others, it will mark the beginning of a frantic search for a spreadsheet somebody vaguely remembers creating last year. Your Marketing Operations should probably start checking which camp it is in. Because while the conversation about AI compliance has largely been happening in boardrooms, legal teams and technology departments, much of the actual use is happening inside marketing. It is embedded in platforms. Added to campaign processes. Connected to customer data. Used to create content, prioritise accounts, recommend actions, personalise experiences and communicate directly with prospects. In some cases, it is doing all of that without anybody having formally decided that it should. That is the uncomfortable part. The biggest immediate challenge for Marketing Operations may not be understanding every article of the EU AI Act. It may be working out what the organisation is already using, what those systems are doing and who is responsible for them. Marketing did not wait for the governance meeting AI did not enter most marketing organisations through a carefully controlled transformation programme. It arrived through product updates. A copywriting feature appeared inside a campaign platform. A meeting tool started producing summaries. A media platform introduced automated creative. A salesperson connected a browser extension to the CRM. Somebody uploaded a customer list into a tool to “see what it could do.” Then came the pilots, custom assistants, automated workflows and agents. Each individual decision may have seemed small. Together, they have created a network of systems using company information, customer data and business rules in ways that are not always visible from the centre. The problem is not necessarily that all of this activity is reckless. Some of it may be entirely sensible and low risk. The problem is that many organisations cannot describe it accurately. Ask which AI systems marketing uses and you may receive a list of officially purchased tools. That is not the same thing. The real list also includes AI features inside existing platforms, free tools used by individuals, systems trialled by agencies, functions switched on by vendors, integrations created by employees and automations nobody has looked at since the person who built them left. If your inventory only includes products with “AI” in the contract title, it is probably already wrong. Buying the platform does not settle ownership One of the easiest mistakes is assuming the technology team owns anything involving AI. It may own the contract. It may manage access. It may review the security. None of that means it understands how marketing is using the system. Legal may interpret the regulation, but legal does not build campaign workflows. IT may approve the platform, but IT does not decide which customer data should be used for personalisation. Procurement may negotiate the agreement, but procurement does not know whether an automated recommendation is being treated as an interesting suggestion or as an instruction that nobody questions. The team using the system owns part of the responsibility because it owns the business context. In Marketing Operations, that context matters. A tool generating rough ideas for internal campaign planning is not doing the same job as a system deciding which people receive an offer. A feature correcting grammar is not the same as a chatbot communicating directly with customers. A model suggesting possible target accounts is not the same as a process automatically excluding people from an opportunity. The technology may look similar on a systems diagram. The consequences are not. That means Marketing Operations cannot simply hand the entire subject to legal and wait for a policy document. It needs to explain what the systems actually do. You cannot govern an invisible stack The first practical job is not writing a 70-page AI policy. It is finding the technology. Marketing Operations needs an inventory that reflects reality rather than the approved software catalogue. For each system, the organisation needs to know what it does, which team uses it, what information it can access, what it produces and whether its output affects customers, employees or business decisions. It also needs a named owner. “Marketing” is not an owner. “The automation team” is not much better. Ownership needs to reach an identifiable person who understands the use case and can answer questions about it. That does not mean this person carries every legal obligation alone. It means somebody is responsible for making sure the system does not disappear into the organisational wallpaper. The inventory should also cover features inside platforms the organisation already owns. This is where things get messy. Software providers are racing to add AI functions to almost everything, often enabled through ordinary product releases. A platform that was reviewed two years ago may now behave quite differently. The contract may not have changed. The risk may have. Marketing Operations should therefore be asking vendors direct questions. Which features use AI? What data do they access? Is customer information used to improve external models? Can the feature be disabled? Are actions logged? Can a human review the output? What happens when the system gets something wrong? A shiny product page containing the words “responsible” and “enterprise-grade” is not an adequate answer. The deadline is not the starting gun There is also a dangerous assumption that organisations have until August to begin thinking about this. They do not. Some requirements are already applicable, including the obligation for organisations providing or using AI systems to ensure that relevant staff have a sufficient level of AI literacy. That does not mean every marketer needs to become a machine-learning engineer. It means people should understand enough about the systems they use to recognise their limitations, apply appropriate judgement and avoid creating obvious harm. A generic one-hour training course followed by a multiple-choice quiz may produce a completion certificate. It does not necessarily produce competent use. The training should reflect the job. A content writer needs to understand accuracy, attribution, confidentiality and the risks of publishing generated material without proper review. A campaign manager needs to understand what can happen when a system creates segments, selects audiences or changes workflows. A Marketing Operations leader needs to understand permissions, data access, monitoring, approval processes and accountability. The person connecting a tool to the CRM needs considerably more than a reminder not to paste passwords into a chat window. Training should match what people are actually allowed to do, otherwise, the organisation has technically educated everybody while practically preparing nobody. Transparency is about more than adding a disclaimer From 2 August 2026, transparency obligations under the EU AI Act will apply to certain systems and content. For marketing teams, this is likely to bring particular attention to customer-facing chatbots, synthetic images, video or audio, deepfake-style material and some AI-generated text relating to matters of public interest. This does not mean every AI-assisted email subject line needs a warning label large enough to frighten the recipient. It does mean organisations need to understand where disclosure is required and ensure the process exists to make it happen. That process cannot rely entirely on the person publishing the content remembering to tick a box. Marketing Operations should help build disclosure and review requirements into workflows. Where content must be identified, the system should support it. Where a customer is interacting with a machine, that should not be hidden behind deliberately vague language and a stock photograph of someone wearing a headset. Transparency is not just a legal inconvenience. It is part of preserving trust. Most customers will accept that organisations use automation. What they will not appreciate is feeling tricked. The hidden issue is decision-making Content generation receives most of the attention because it is visible. The harder questions sit underneath it. What is the organisation allowing AI to decide? Marketing systems increasingly recommend audiences, prioritise accounts, predict behaviour, adapt journeys, score leads and select the next action. Again, not every automated marketing decision falls into the most heavily regulated category. Claims that every lead score is suddenly a major EU AI Act emergency are not particularly helpful. But the absence of a dramatic legal classification does not make a process sensible. Marketing Operations should still understand which decisions are automated, which are influenced by automated recommendations and where human judgement remains. It should be possible to explain why a person entered a particular journey, received a specific message or was excluded from an opportunity. It should also be possible to challenge the system. If the team treats every recommendation as correct because it arrived inside a polished dashboard, there is no meaningful oversight. There is just a human clicking “approve” to make the workflow look respectable. Governance should improve the work This is the point where many organisations make governance unnecessarily painful. They create committees, forms, approval stages and policy documents without fixing the way work happens. Employees then find unofficial routes around the process because the official one takes six weeks and requires a meeting with fourteen people. Good governance should make acceptable uses easier and questionable uses harder. People should know which tools are approved, what they can use them for and when additional review is required. There should be a straightforward route for proposing a new use case. Higher-risk activity should receive closer scrutiny. Routine, low-impact activity should not require an emergency summit. Marketing Operations is well placed to help design this because it already understands workflows, permissions, quality assurance and operational controls. Or at least it should. If the team can build a 47-step nurture programme with six branches and three regional exceptions, it can probably design a sensible approval process for an AI-enabled campaign. What Marketing Operations needs to do now The immediate priority is visibility. Find the systems. Document the use cases. Identify the data involved. Assign owners. Review access. Check vendor terms. Understand which outputs reach customers and which decisions are being influenced. Then look at the controls. Can people review outputs before they are used? Are important actions logged? Is there a clear escalation route? Can the organisation stop the system quickly? Does somebody periodically check whether it is still doing what it was intended to do? Finally, look at the people. Do they understand the tools they use? Do they know what information they can enter? Do they know when human review is mandatory? Would they recognise a poor or inappropriate output, or are they trusting the system because it sounds confident? None of this requires Marketing Operations to become the legal department. It requires the team to behave like the operational owner of marketing technology. Which, inconveniently, is exactly what the name suggests. August will expose the gaps, not create them The EU AI Act is not suddenly going to make poorly controlled technology risky on 2 August. That risk already exists. The deadline simply makes it harder for organisations to continue pretending that nobody owns it. Marketing Operations has an opportunity here. It can wait for legal to send around a policy and then attempt to bolt it onto a marketing stack that nobody has fully mapped. Or it can take the lead in understanding how AI is actually being used, where it touches customers and data, and what practical controls need to exist. That is not bureaucratic housekeeping. It is the difference between using AI as part of a functioning operation and scattering it across the business until something embarrassing forces everyone to pay attention. The deadline is approaching... The first question is not whether your organisation is compliant. It is whether Marketing Operations even knows what it owns. Discover our AI Services