12–18 minutes
When Did Marketing Stop Asking Why Blog Header

When Did Marketing Stop Asking Why?

Build better decision-making

There is a moment I see happen in almost every team, and once you notice it, you can not unsee it.

It tends to happen when performance dips, even slightly. Someone opens a dashboard, sees a few numbers in red with downward arrows, and decides on a direction within minutes. They make that decision before there is clarity on why the company is experiencing the dip in performance.

The marketing team heads toward “experimenting,” although the “experiment” has specific performance expectations. The usual changes happen first: The creative needs to change. The budget needs to increase. Maybe another channel needs testing. Or follow what the competitor just did. 

On the surface, it looks like a strong, data-driven response.

But if you pause and ask one simple question, the whole thing starts to fall apart.

Why is this happening?

Teams rarely answer that question. In many cases, they don’t even ask it.

It is not because the team lacks capability, but because the process they are working within does not require it. No one is asking them why. Instead, they are looking at the red numbers and encouraging change, fast change at that. 

When I started in the industry almost 20 years ago, we discussed the importance of undertaking the why in great detail. If I could not communicate that to the leadership team, I would start over. At the time, it was frustrating, but looking back on it today, I am very thankful because I had to build a case, understand context from many perspectives and connect the dots with only a few tools to help me. Today, we have built a marketing environment where tools do more of the heavy lifting, and as a result, people do less of the thinking.

Do not get me wrong, I love the tools too. In this blog article, I am going to share some practical advice on how to flex and develop your critical thinking muscles. It is not a given or something that exists on every team. 

When did marketing become tool-first?

Marketing did not start this way. It used to begin with a level of curiosity that shaped everything else.

Curiosity was always a discussion when hiring someone new. Now, people focus heavily on the tools others use, the apps on their phones, and how they stay ahead of technology. I am not sure whether curiosity has the same requirement it once did.

Teams would spend time understanding who they were trying to influence, what that audience actually cared about, and what decision they were trying to shift. Teams collected qualitative and quantitative data and analyzed it to inform their predictions. 

Only after that would channels, tactics, and execution come into the conversation.

Today, teams often reverse that sequence.

A team selects a platform because it is trending or because it integrates easily with their stack. They plan campaigns around what a tool can do, not what the customer needs. Platform recommendations begin shaping direction before anyone clearly defines the problem.

It sounds efficient, and in many ways it is. But it quietly changes how your team thinks. 

When you start with a tool, you limit the range of questions you ask. Teams start framing the problem based on what the tool can solve, rather than what actually needs solving.

Over time, this creates a pattern in which execution becomes very strong and very fast, while direction becomes increasingly weak.

A familiar scenario you may relate to

One B2B team I worked with had invested heavily in marketing automation and performance tracking tools. Their dashboards were detailed, updated in real time, and widely shared across the organization.

Every month, the team would review performance metrics and make adjustments.

One quarter, they noticed a consistent drop in conversion rates on a key landing page. The immediate response was to test new headlines, adjust the layout, and increase traffic to compensate.

Several weeks passed, along with thousands of dollars, and nothing meaningfully improved.

When the team brought me in to help them move from reactive to proactive decision-making, the issue became clear very quickly.

The problem was not the page.

The traffic driving to it had changed. A new campaign was attracting a broader, less qualified audience, which meant the landing page was now trying to convert people who were earlier in their decision process. There was no interest in the page’s traffic, and even less understanding of what the solution offered or whether it addressed a problem someone had.

The tools had surfaced the symptom, but they had not helped the team understand the cause of the problem. 

To get here, we had to step back, question assumptions, debate openly and connect information across multiple inputs. 

In other words, it required critical thinking. The team hired me to guide and facilitate this process.

Why more data collection alone will never improve decision-making

There is an assumption that more data naturally leads to better decisions. In practice, it often leads to faster decisions.

And faster decisions are not always better ones.

It is also common for teams to misunderstand the difference between data collection, data analysis, and insight development. The majority of teams focus and invest in data collection very consistently. I cannot say the same for data analysis and insight development.

Many teams are now operating in environments where data is constant. Metrics update in real time. Systems trigger alerts automatically. Reports are generated with little effort or context added to the dashboard.

The pressure to respond is real, and the fight for time is even worse. Many might say that the team does not have the luxury of thinking at that level and must rely on tools.

That creates a pattern in which teams move from observation to action, spending very little time on interpretation. They train and reward new team members to do the same, deprioritize the development of critical-thinking skills, and, eventually, the work (the results) suffers. 

Over time, teams may mistake this for constant optimization and experimentation.

You start to notice a gap in how teams interpret and use information in decision-making, and in the quality of questions they ask around the boardroom table.

The gap tools will struggle to fill 

Tools are incredibly effective at execution. Very impressive stuff is happening! I do not think anyone would argue with that. They can optimize performance, automate processes, and scale activity in ways that were not possible even a few years ago. They can create new content, code websites and even speak on your behalf. My kids are constantly pointing out to me what videos are “pure AI”. 

What these tools cannot do is define the problem. They cannot understand the full context, why you made previous decisions, or even your goals unless you share them.

They cannot challenge whether the audience is correct, whether the positioning is relevant, or whether the objective itself needs to change. That context only surfaces when you actively ask for it. Even then, the debate remains lightweight compared to a room of C-suite executives.

They also cannot connect fragmented signals into a clear, meaningful narrative without human interpretation. They are connecting dots only with the information they have access to.

There is a growing reliance on tools to guide decisions, combined with a decreasing emphasis on developing the thinking required to interpret what those tools are showing.

This shows up most noticeably among marketers, who often receive extensive training on platforms and systems but far less on how to question, analyze, and connect information.

That gap is not a reflection of ability. It reflects how teams are structured and how work gets done. The goal is to use the tools and apply critical thinking at every step. 

Critical thinking is built and needs practice

One of the more persistent misconceptions in marketing is that critical thinking is something people either naturally have or do not. It is assumed to be on a team, so you do not need to worry about it. 

In reality, it develops through practice, structure, and reinforcement over time. You need to flex this muscle regularly. Once you recognize that, you will be surprised how good your questioning becomes.

If a team consistently rewards speed, output, and execution, those skills will strengthen. If there is little space to question assumptions or explore alternative explanations, those behaviours will weaken.

Without intentional effort, critical thinking does not disappear, but it does become underused.

And when that happens, marketing starts to look very busy without becoming more effective.

Everyone on the team is very “busy,” and few of the team members can explain why or how the work connects to a greater goal. 

That is when you have to pull the car over, folks! 

How to build critical thinking into your team

Developing critical thinking is not about adding more theory or slowing everything down. It is about introducing simple structures that change how decisions are made.

Start with the problem… every single time

Before discussing any campaign or tactic, the team should be able to clearly articulates the problem they need to solve.

Teams often rush or skip this step, especially under tight timelines or performance pressure. It’s easy to assume they understand the problem because they can see the metric.

It rarely is.

Never assume you already know what the problem is. When you create space to define the problem properly, you will often uncover perspectives the team would have otherwise missed. Someone on your team may connect dots you had not considered or challenge an assumption that has quietly been driving decisions.

For example, instead of saying “we need to improve conversion rates,” a stronger starting point would be:

“We believe prospects are not seeing enough value at the evaluation stage, which is preventing them from moving forward. What else could it be?”

That shift moves the conversation from reacting to a number to exploring a problem.

To help your team build this habit, anchor the discussion with a few simple but powerful questions:

  • What are we actually trying to solve for here?
  • What behaviour are we trying to change?
  • Where in the customer journey is this breaking down?
  • What do we believe is causing this issue?
  • What evidence do we have to support that belief?
  • What assumptions are we making without realizing it?
  • What else could be contributing to this that we have not considered yet?

These questions are not meant to unnecessarily slow teams down. They are meant to make sure you are solving the right problem before you move into execution.

Focus on interpretation first

You often need speed, but you should not rush or skip interpretation.

When reviewing data, build in a step where the team explores multiple explanations before deciding on a course of action. One explanation is insufficient curiosity about the problem. 

In practice, this can be as simple as asking each team member to propose a different hypothesis based on the same data set.

This helps shift the conversation from “what should we do” to “what might be happening with our customer base.” This will lead to stronger decisions.

Redefine what an insight means

Many teams label observations as insights, and that is where a lot of thinking stops too early.

A metric changes. A pattern appears. A report highlights something worth noting. Teams present something as an “insight” and move straight to action.

An observation on its own does not tell you anything new. It simply describes what is happening.

An insight goes further. It explains something. It connects what you are seeing to why it is happening and, more importantly, what that means for the decision you need to make.

For example, saying “conversion rates dropped by 20% last month” is useful but not an insight. It is a starting point.

An insight would explore what changed. Has the audience shifted? Does the messaging no longer align with where the customer is in their journey? Did something external influence intent?

The difference is subtle: One reports. The other interprets.

A simple way to test whether something is truly an insight is to ask a few questions:

  • Does this explain why something is happening, or just what is happening?
  • Does it connect multiple signals or just repeat a single metric?
  • Does it lead to a clear decision or simply suggest that something needs to be done?

If the answer is unclear, it is likely still an observation.

If you want a more structured way to build this capability, I recently shared a step-by-step approach to developing insights within your team, which walks through how to move from raw data to meaningful direction.

Create structured moments for challenge

Critical thinking improves when it is expected from everyone involved. 

In many teams, challenging ideas are seen as something that happens only when there is time or when someone feels confident enough to speak up. As a result, most work moves forward without proper testing.

That is not because the work is weak. It is because the environment does not consistently make space for better thinking to surface and sharpen through healthy debate. 

If you want stronger decisions, you have to build in moments where questioning is part of the process and part of how your team contributes daily.

This does not need to be a formal review or a long meeting. In fact, the lighter it is, the more likely it is to occur naturally and consistently. 

It can be as simple as pausing before execution and asking the team to challenge the direction.

To guide these discussions, you can anchor them with a few key questions:

  • Are we confident this is the right audience, or is this who we can most easily reach?
  • Does this message reflect what the customer actually cares about, or what we want to say?
  • Why is this the right channel for this problem? What assumptions are we making about it?
  • What would someone outside this team question about this approach?
  • If this does not work, what is the most likely reason why?

These moments do not need to derail progress. They simply create a pause long enough for better thinking to catch up with execution.

You know this is happening when someone says, “I am not 100% behind the direction we are headed and here is why.”

This is where stronger ideas are built before your budget is spent. 

Coach the thinking behind decisions

Feedback in marketing is often centred on what was produced.

Was the campaign strong? Did the messaging land? Did the creative perform?

That feedback is important, but it only develops execution. It does not strengthen decision-making before execution.

If you want to build critical thinking across your team, the focus needs to shift from the output to the reasoning behind it. 

Without understanding the thinking, you can not reinforce what should be repeated or challenge what should change.

When reviewing work, create space to explore how the conclusion was reached.

Instead of jumping straight to whether something works, ask:

  • Why did you choose this direction over others?
  • What alternatives did you consider, and why were they ruled out?
  • What evidence supports this approach?
  • What assumptions are you making here?
  • What would change your mind about this direction?

These questions are about making thinking visible.

When teams get used to articulating their reasoning, their confidence grows. Their decisions become more intentional. And over time, they rely less on defaulting to what has worked before or what the tool suggests.

Investing time here is an advantage 

At this point, most teams have access to similar tools, similar data, and similar capabilities.

In many ways, the tech stack has become table stakes.

Having the right platforms in place is no longer a differentiator. It is the baseline requirement to compete.

Which means the advantage has shifted.

It is no longer about who has the most tools, or even the most advanced ones. It is about who knows how to use them with intention.

The teams that consistently perform well are the ones that take the time to understand before they act, question before they optimize, and connect information rather than reacting to it.

You can see this clearly when two teams use the same platform and get very different results. One follows recommendations, adjusts settings, and keeps things moving. The other steps back, challenges what they are seeing, and uses the tool to support a clearly defined strategy.

Tools will continue to get better. They will become faster, more automated, and more intelligent.

That does not remove the need for critical thinking. It increases it.

Building critical thinking within a marketing team does not happen by chance. It requires structure, consistency, and the right environment for better thinking to take shape.

How We Can Help

At Marketing Mile, we work with teams to shift from tool-driven execution to customer-driven strategy. That includes helping define the right problems, strengthening how data is interpreted, and building the habits that lead to better decisions over time.

In many cases, we do not just guide this process. We build and operate the marketing function on behalf of our clients and embed these ways of thinking directly into how work gets done day to day. 

If your team is busy but not progressing as expected, or if decisions are being made quickly without sufficient clarity, it may not be a tool issue. It is often a thinking gap.

If that sounds familiar, let’s talk.

Discover more from Marketing Mile

Subscribe now to keep reading and get access to the full archive.

Continue reading