• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we have the pleasure of sitting down with Henk-jan ter Brugge, Head of global digital programs and Martech at Philips.

Summary: Henk-jan works like a pirate inside the navy, exposing inefficiency with data, redesigning roles around real capabilities, and breaking AI promises into measurable wins backed by clean data and clear standards. He treats composability as an operating model with budgets tied to usage, gives local teams autonomy within guardrails, and measures martech by how it serves people and drives revenue. Ops leaders earn influence by pulling in allies and securing executive sponsorship, while reporting debates matter less than accountability and outcomes. Real innovation comes from embracing the long tail of smaller tools, working with vendors who integrate into the ecosystem, building adoption models with champions, and protecting energy through ruthless prioritization.

In this Episode…

• Embracing the Digital Pirate Mindset in Martech
• Why Composable Martech Stacks Work in High Seas Regulated Enterprises
• Rethinking Martech as People Tech
• Elevating Martech Teams Beyond Button Pushing
• Where Martech Should Report in the Organization
• Unlocking Innovation Through the Long Tail of Martech
• Philips Digital Marketing & e-Commerce Stack

About Henk-jan

Henk-jan ter Brugge is Head of Digital Programs and Martech at Philips, where he leads the global digital marketing and ecommerce technology team. With over a decade at Philips, he has driven transformation across CRM, ecommerce, sales enablement, web experience, ad tech, analytics, and AI innovation. 

Henk-jan is a lean and agile certified leader who believes technology is an enabler, but it’s people who create the real impact. His career spans international experience in Seoul, Paris, and Shanghai, and he is a frequent keynote speaker on martech, salestech, and digital transformation. Passionate about improving health and wellbeing through meaningful innovation, he connects strategy, technology, and change management to deliver customer value at scale.

Disclaimer: The views and opinions expressed by Henk-jan in this episode are his own and do not necessarily reflect the official position of Philips.

Embracing the Digital Pirate Mindset in Martech

Pirates were early system hackers. They rewrote rules on their ships, experimented with shared decision-making, and introduced ideas like equal pay centuries before they reached land. That spirit of rewriting norms has carried into Henk-jan’s work in martech. He frames the pirate as someone inside the navy, pushing the big ship to move differently, rather than a rogue causing chaos on the outside.

Corporate inertia creates its own myths. Vendor onboarding still takes 12 to 18 months in some organizations. Translation cycles hold content hostage for weeks. Colleagues accept these delays as culture, with a shrug and a “that’s just how we do things.” Henk-jan refuses to let tradition dictate output. He arms himself with data and turns it into proof. If a team claims a translation cycle takes three months, he presents the real number: 10, 15, maybe 20 days.

“Everything we say can be data driven. If someone tells me translation takes three months, I can show with data that it takes 10, 15, maybe 20 days. The data talks there.”

The pirate mindset works only when it builds coalitions. Lone rebels fade out in corporate structures. Movements form when people across teams share the same impatience for inefficiency and the same hunger for progress. That is why Henk-jan focuses on allies who welcome change. With them, he introduces controlled experiments that rewire expectations step by step until the new way becomes the default.

One of his boldest moves came in team design. He rebranded product owners as platform managers. They stopped acting like ticket clerks and became capability builders, consultants, and business partners. They handled strategy, education, and enablement, while still owning the backlog. A time study revealed that 70 percent of team energy had been going into internal operations. After the shift, 60 percent went directly into business-facing work. The lesson was clear: titles shape behavior, and behavior shapes impact.

Key takeaway: The digital pirate mindset thrives when you expose inefficiency with data, recruit allies who share your appetite for change, and redesign roles so teams build capabilities instead of servicing tickets. Work inside the system, use transparency to gain trust, and experiment in controlled steps. That way you can redirect energy from internal bureaucracy toward direct customer value, creating momentum that compounds over time.

Back to the top ⬆️

Why Clean Data Is the Real Treasure Map for AI in Marketing Ops

Speaking of chasing treasures… AI has forced leadership teams to finally pay attention to the quality of their data. Henk-jan described it with a simple observation: “Everybody in the company becomes a technologist in a way, even the CEO.” Executives want automation, optimization, and sharper analytics, but none of those things matter without reliable data flowing through the system.

Requests for a CDP illustrate the problem. Leaders hear the acronym and assume it represents an instant fix. Henk-jan has seen this cycle many times and insists the smarter move is to break the vision into small, practical wins. CEOs need short stories they can tell at the end of a quarter, stories that show how clean data lifted conversion or reduced wasted spend. Large programs gain momentum when they stack up these smaller wins rather than selling one massive transformation.

“The only way to do that well is to slice it up, basically to show some promising use cases. Talking CEO, they need some impactful stories they need to have at the end of the quarter to show what we have delivered.”

Clean data depends on discipline across the organization. Henk-jan stressed the need for rules: standards for how data is collected, shared definitions across content systems, and taxonomies that keep categories consistent. Integrations and lifecycle management depend on that structure. Without it, AI experiments turn into siloed pilots that never scale.

AI becomes useful only when the groundwork is finished. Leaders may chase demos that look impressive, but real value comes from standards, integration discipline, and lifecycle maturity. These foundations create systems that grow stronger over time rather than projects that fizzle out after launch.

Key takeaway: Clean data gives AI something to stand on. Break big promises into small, measurable wins that executives can celebrate at the end of a quarter. Pair those wins with clear rules on data standards, integration discipline, and taxonomy. That way you can build credibility quickly, prove value, and create a foundation where AI programs expand instead of stall.

Back to the top ⬆️

Why Composable Martech Stacks Work in High Seas Regulated Enterprises

Composable stacks sound exciting in theory, but at enterprise scale the question is always about execution. Henk-jan calls it the “cradle to grave” lifecycle of martech, and he is not exaggerating. Every new tool at Philips runs through a process: onboarding, building and deploying, adopting, improving, and eventually decommissioning. Each step matters because every skipped detail becomes someone’s day-to-day problem.

He warns against the common trap of treating tools like silver bullets. Buying a platform for insights or personalization only matters if there are people inside the business who can operate it. Henk-jan has seen too many organizations forget that. At Philips, every business unit funds what it uses, whether that is ecommerce, CRM, or analytics. Sixteen business units means sixteen different realities, so budgets are tied to adoption rather than inflated global mandates. That way unused tools do not drain resources.

When asked about enabling agility without blowing up governance, Henk-jan is blunt. At global scale you have three paths: accept the global setup, challenge it, or build it yourself. Local teams that choose to run their own system, like HubSpot or Eloqua, must also commit the staff and budget to keep it alive. He keeps one CMS instance to avoid chaos, but local markets decide how to run it. Transparency is the lever here. He gives teams “the keys to the castle” so they can dig into data models and test ideas, provided they do not break the ecosystem.

“We buy tech for use cases, but someone in the organization still needs to do the work with that tool,” Henk-jan explains.

He also makes a point that industry veterans often whisper about but rarely say directly: the value happens locally. Global teams can set guardrails, but it is the regions and markets that shape customer experience. That is why he often describes himself less as a martech leader and more as a people technology leader. His team works across marketing, sales, product, IT, supply chain, and procurement. The work is not about stacking tools, it is about orchestrating the entire revenue cycle so it runs as one system.

Key takeaway: Treat composability as an operating model, not a buzzword. Break every platform into a clear lifecycle with ownership at each stage. Tie budgets to usage so unused tools do not linger. Give local teams autonomy within guardrails, and let them learn by working with the data directly. The stack will only be as agile as the people who run it, so train them, fund them, and hold them accountable for adoption. That way composability delivers flexibility without collapsing governance.

Back to the top ⬆️

Rethinking Martech as People Tech

Martech has become a catchall term that creates more confusion than clarity. Each department brings its own definition. For some, it means CRM and campaign tools. For others, it points to analytics, CDPs, or content systems. Henk-jan compares this ambiguity to a poor user interface. When teams believe they are aligned but each imagines a different meaning, they waste energy arguing about scope instead of producing impact.

“If I got a dollar for every time we thought we were aligned with stakeholders, I’d be rich,” Henk-jan said.

The conversation shifts when you frame technology as people tech. Customers interact with systems every time they visit a website or app. Employees interact with systems when they grind through decks in PowerPoint, which Henk-jan jokes is still the most common enterprise martech tool. Technology becomes less about the label and more about how it serves the humans who use it, whether they are outside customers or inside employees.

At Philips, that framing carries revenue responsibility. Henk-jan’s team manages ecommerce technology and shares ownership of the P&L. When analytics reveal that shoppers abandon carts, his group delivers the insight back to managers who adjust strategies. Sales rise because the technology function feeds live customer behavior back into the business. Martech in this context is not campaign ownership. It is architecture for customer experience with direct accountability for commercial results.

The slowest teams fail here. Six to twelve months spent onboarding software is a red flag. Buying tools based on vendor demos that overpromise creates setbacks. Companies that cannot identify which features generate revenue carry technical debt that directly harms marketing. The teams that win move fast, measure rigorously, and prioritize the few features that actually shift business outcomes. Henk-jan believes that this ability to manage martech as a business discipline creates long-term advantage.

Key takeaway: Treat martech as people tech. Align definitions so teams speak the same language, involve technology leaders in revenue accountability, and shorten delivery cycles. Measure tools by how well they serve people and how quickly they contribute to growth. That way you can turn your stack from a liability into a competitive edge.

Back to the top ⬆️

Elevating Martech Teams Beyond Button Pushing

Marketing ops teams manage the hidden machinery that keeps customer interactions consistent, timely, and scalable. Their work spans systems, workflows, and logic that connect dozens of tools. The problem is that this work often goes unnoticed. Henk-jan argues that the best way to change this perception is to invite people outside the core tech group into the process. Product owners, data analysts, and frontline marketers can bring fresh thinking that strengthens outcomes when they are given context and a chance to collaborate.

“Go to those people that are not in your tech team,” Henk-jan said. “They will be so happy to think along with you in how to make the experience better.”

The impact multiplies when teams share knowledge. Marketers gain technical fluency and make better decisions about tools and campaigns. Product owners learn how customer value drives business priorities. Ops leaders gain allies across departments who advocate for investments without needing a long explanation. This is how teams evolve from ticket takers into partners shaping strategy.

Self-service tools have accelerated this trend. A landing page that once required months of waiting can now be built in hours. AI is pushing this even further, enabling people with little technical background to complete tasks that previously demanded specialized teams. That freedom creates opportunity, but it also raises the stakes for ops leaders. Their job now includes maintaining the system while knowing when to step in, when to decline requests, and when to let colleagues experiment on their own.

The invisible nature of ops work creates tension. Henk-jan admits he has considered pulling the plug on a core system for twenty minutes to show how quickly the phones would light up. He never followed through, but the thought reflects a frustration many leaders feel. Their work is only recognized during a crisis, even though it sustains the business every day. In reality, the discipline that prevents chaos is the same discipline that enables innovation.

Internal structure determines whether this influence translates into authority. Control of the tech budget, reporting lines, and executive sponsorship all shape how much weight ops leaders carry. Without strong allies at the top, even the smartest roadmap can stall. Ops leaders who build coalitions and secure sponsorship extend their influence beyond execution. They gain the ability to shape priorities for the entire organization.

Key takeaway: Ops leaders can elevate their role by involving colleagues from outside the tech team, sharing context that builds mutual understanding, and guiding business partners as they take on more technical tasks. Self-service tools and AI expand what non-technical people can achieve, but they also increase the importance of ops in protecting system stability. Building influence depends on securing executive sponsorship and creating a network of allies. That way you can transform marketing ops from a hidden support function into a visible driver of customer and business value.

Back to the top ⬆️

Where Martech Should Report in the Organization

Every leadership team debates where martech belongs. Marketing wants to keep it close, RevOps argues for control, IT fights for ownership, and finance sometimes tries to pull it under their wing. Each option comes with trade-offs, but Henk-jan is blunt: reporting lines matter less than leaders assume. The real question is whether the business side commits to owning outcomes while IT protects the technical backbone.

Martech needs to be divided into categories. Lightweight tools like SEO plug-ins can sit inside marketing without drama. Enterprise platforms like CRM, ecommerce, or content management systems require more discipline. These contracts run for years, touch dozens of processes, and face strict compliance rules. IT has the expertise to keep platforms stable, secure, and integrated into broader architecture. Business teams must take accountability for why these systems exist, what outcomes they deliver, and how value is measured.

“A missed opportunity doesn’t show up on your balance sheet,” Henk-jan says, quoting Rory Sutherland.

That quote exposes the blind spot when CFOs claim ownership. Finance tracks expenses but rarely sees the ripple effects of cost-driven decisions. Dropping a tool might look efficient in a spreadsheet. In practice, companies hire more staff, burn time retraining, and lose customer experience advantages that never hit the ledger. Numbers alone miss the hidden costs of slower execution and lost growth.

The smarter path is treating martech like a living investment. ROI models cannot die the day procurement signs the contract. They need ongoing care. A $500 plugin, a $5,000 workflow tool, and a $100,000 enterprise suite deserve different levels of KPI tracking. Henk-jan argues that business leaders must revisit those KPIs continuously. Without that, stacks grow bloated, platforms lose purpose, and budgets get wasted on tools that no longer match the strategy.

Key takeaway: Stop obsessing over the reporting line debate and focus on accountability. IT should handle platform stability and compliance. Business leaders must define outcomes, track KPIs, and revisit business cases regularly. Finance can support, but cost alone cannot dictate martech decisions. That way you can keep your stack efficient, purposeful, and directly tied to growth.

Back to the top ⬆️

Unlocking Innovation Through the Long Tail of Martech

Enterprises have spent years cutting tools, chasing savings that looked impressive in reports but delivered little real benefit. Henk-jan explains that he once believed removing smaller applications was the smart play. Later experience showed him that trimming long-tail tools rarely drives meaningful outcomes. The bigger opportunity lies in focusing attention on the tools that create measurable impact, whether they cost millions or almost nothing.

The long tail of martech, often called the hyper tail, is where much of the industry’s experimentation thrives. These niche tools are not systems of record that take years to implement and consume huge budgets. They are lightweight applications that deliver targeted value when paired with teams who know their customers best. Henk-jan argues that organizations should pay more attention to these edge solutions, since they can spark creativity, speed, and differentiation that larger platforms struggle to provide.

At Philips, he has seen both paths play out. When the company evaluated account-based marketing tools, the decision came down to going with a major vendor or piecing together smaller apps. His team eventually chose the larger vendor because they were also buying expertise, reference customers, and additional support. That decision highlights an important nuance. The long tail is not a rejection of enterprise platforms. It is recognition that agility often lives in smaller, specialized tools that can be adopted quickly and adapted locally.

The uncomfortable truth is that many companies continue to pour millions into implementing basic systems such as CDPs, CRMs, and CMS platforms, while ignoring the speed and customer proximity that smaller tools provide. Global leaders like Henk-jan believe the future lies in enabling local teams to select and build the micro tools that meet their unique needs. Headquarters can set the direction, but impact comes from teams who experiment directly with customers and adapt faster than procurement cycles allow.

Key takeaway: Enterprises should focus their energy on securing core systems while actively embracing the long tail of martech. Smaller, specialized tools create speed, enable local differentiation, and deliver innovation that large vendors cannot provide at the same pace.

Back to the top ⬆️

The Limits of Vendor Isolation in Martech

An email from an account manager quitting over the frustration of logging in and out of more than fifteen different tools captured the cost of poor vendor collaboration. That single message carried more weight than any quarterly report, because it showed the human toll of disconnected stacks. When vendors fail to integrate, the burden shifts onto employees, and the daily grind becomes unbearable.

Strong vendor relationships begin with context. Philips openly publishes its martech stack, which means every vendor can see how the stack has evolved and what systems are already in place. The vendors who stand out are the ones who study that information and arrive ready to talk about where their solution fits. Instead of repeating tired sales scripts, they focus on concrete opportunities that make sense inside the existing ecosystem.

Pricing transparency changes the dynamic as well. Procurement teams focus on cost reduction, while business teams push for speed and innovation. Vendors who create standardized contracts across clients remove this tension entirely. Henk-jan values those relationships because they allow him to share openly, run workshops, and plan strategy without worrying about how every detail might affect renewal negotiations.

“When I know I’m paying the same as my peers, I can share anything. I can have any discussion, any workshop, any reference session at any time,” Henk-jan explained.

The weakest vendor relationships come from companies that only focus inward. Quarterly reviews often circle around feature requests and usage metrics, but they rarely bring ecosystem partners into the discussion. This siloed thinking prevents bigger conversations about cross-tool collaboration and shared capabilities. Henk-jan prefers vendors who think beyond their own product and invite others to the table. That level of cooperation reduces noise and creates solutions tied to actual business outcomes.

Key takeaway: Vendors win long-term relationships when they integrate into the client’s ecosystem, maintain contract transparency, and bring partners into the conversation. That way you can remove friction, build trust, and focus directly on solving real business problems instead of adding to the chaos.

Back to the top ⬆️

Philips Digital Marketing & e-Commerce Stack

Henk-jan was asked to name a few underrated tools in his stack. He dismissed the idea of giving quick vendor shoutouts because they would only reflect recency bias. What mattered to him was not the tool itself but the messy process of figuring out how it landed inside a complex organization.

One content platform forced his team into that reality. The vendor measured customer NPS, and the score was ugly: minus ten. That number stung, yet it exposed what was happening on the ground. The tool was complicated, the average marketer dreaded using it, and adoption would continue to stall without a different structure.

“We measure platform happiness every month, but some tools will never be loved. They are too complex. The answer is to set up champions who really know it and sit close to the business.”

His team responded by building a new adoption model. They placed a platform manager directly inside the business. They trained champions who could speak both the technical language of the platform and the practical needs of marketers. They gave ownership to specialists rather than pushing every market to figure it out on their own. That way teams had trusted translators who removed frustration and created wins faster.

The shift worked. The platform that once generated annoyance became usable. Markets stopped fighting with it and started benefiting from it. The lesson was clear: technology alone never drives adoption. The operating model, the champions, and the human scaffolding around the platform decide whether a tool adds value or collects dust.

Key takeaway: Adoption models create impact, not vendor logos. Measure platform sentiment honestly, confront the ugly data, and invest in champions who can absorb complexity for the wider team. That way you can turn even the most hated tools into quiet drivers of business value.

Back to the top ⬆️

How to Use Weekly Prioritization to Protect Energy

Henk-jan builds balance around simple rules that anyone can test. He treats authenticity as fuel. Pretending to be someone else drains energy, while showing up as yourself gives stamina for the long haul. He sees optimism as another non-negotiable. Choosing it takes courage, but it makes leadership lighter and creates room to make harder calls without losing momentum.

“Stay true to yourself, being yourself, staying authentic, because otherwise it costs you a lot of energy, especially in the age of AI.”

He keeps his optimism grounded with routines that force clarity. Every Friday he reviews the upcoming week as if he were leaving for holiday midweek. If he had only three working days, what would matter most? That small mental exercise forces trade-offs. It shrinks the noise and puts attention on the work that actually moves the needle. Combined with saying no more often than yes, it saves his team from drowning in meetings that only look important on paper.

He points out that leaders love to talk about self-reflection, yet treat it as optional. A one-hour block for personal growth is usually the first to get deleted when the week gets busy. Protecting that time is harder than scheduling it, but the payoff is long-term energy. Henk-jan also leans on community instead of isolation. Sharing bad days with colleagues, recharging with family, and keeping sports in his weekly rhythm are as central to his performance as hitting KPIs.

Identity plays a big role in how he views leadership. You are more than your role, and forgetting that leads to burnout. He gets energy from connecting with peers at conferences, not by buying into the polished perfection of vendor pitches but by hearing the human stories underneath. That way he can see that everyone is struggling in some form, which makes the work feel lighter.

Key takeaway: Protecting energy means treating authenticity as fuel, choosing optimism deliberately, and forcing clarity with weekly prioritization exercises. Guard your self-reflection time like any other meeting, lean on your community when the weight feels heavy, and remind yourself that your identity is bigger than your job title. That way you can sustain energy, make sharper decisions, and lead without burning out.

Back to the top ⬆️

Episode Recap

Henk-jan thinks like a pirate inside the navy. He pushes change from within by exposing inefficiency with data and building coalitions that turn experiments into new norms. When he rebranded product owners as platform managers, ticket clerks became capability builders, and team energy shifted toward business impact almost overnight.

AI has forced leaders to care about data, but clean inputs and consistent rules matter more than flashy demos. Henk-jan breaks big visions into quarterly wins that executives can retell as stories. Composable stacks follow the same logic. Every tool has a lifecycle, budgets stay tied to usage, and local teams earn freedom only if they commit to running their systems.

Martech as a term isn’t dead but… for him, martech works best as people tech. Customers feel it in abandoned carts, employees feel it in clunky systems, and his team feels it in shared revenue targets. Ops teams carry that weight quietly, but their discipline sustains both stability and innovation. Influence grows when they open the work to colleagues and build allies across the business.

The same principle guides his view of vendors and adoption. Strong vendors walk in with context and contract transparency. Weak ones stay stuck in silos. Even hated platforms can be turned around when champions absorb the complexity and sit close to the business.

Through it all, Henk-jan protects his energy. He treats authenticity as fuel, optimism as a choice, and weekly prioritization as a ritual that keeps the noise in check. He knows identity is bigger than a job title, and that reminder keeps him steady while steering the big ship forward.

Listen to the full episode ⬇️ or Back to the top ⬆️

Follow Henk👇

• LinkedIn

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed