Situation Analysis: What Most Marketing Teams Skip Before Planning
A situation analysis is a structured assessment of where a business stands before any marketing strategy is written. It maps internal strengths and weaknesses against external market conditions, competitive dynamics, and customer realities, giving planners a factual foundation rather than a set of assumptions dressed up as insight.
Done properly, it stops teams from building campaigns on top of things that are no longer true. Done poorly, it becomes a slide deck ritual that delays the work without improving it.
Key Takeaways
- A situation analysis is only useful if it changes what you decide to do. If your plan looks identical before and after, the analysis was decoration.
- Most teams over-invest in SWOT and under-invest in the customer reality section. That imbalance produces strategies that sound logical but miss the market.
- Internal data is the most underused input. Revenue by segment, churn patterns, and conversion drop-off points tell you more than most external research.
- Competitive analysis inside a situation analysis should focus on positioning gaps, not feature lists. What space is genuinely available is the question worth answering.
- The output of a situation analysis is not a document. It is a set of decisions about where to play and what to prioritise.
In This Article
- What a Situation Analysis Actually Contains
- Why the Internal Audit Is Where Most Teams Lie to Themselves
- How to Approach the Customer Reality Section Without Spending Six Months on Research
- Competitive Analysis Inside a Situation Analysis: What to Actually Look For
- SWOT: Still Useful, Still Misused
- The Market Context Section: What Belongs Here and What Doesn’t
- From Analysis to Strategic Implication: The Step Most Teams Skip
- How Long a Situation Analysis Should Take
- Common Mistakes That Undermine the Whole Process
What a Situation Analysis Actually Contains
The term gets used loosely. Some teams treat it as a SWOT exercise with a few market statistics bolted on. Others produce 40-page documents that nobody reads past slide six. Neither version is particularly useful.
A working situation analysis has five distinct components. Each one feeds the next, and the connections between them are where the real insight lives.
The first component is the internal audit: what the business actually does well, where it underperforms, what resources it has available, and what constraints are real versus assumed. This is harder than it sounds because internal audits tend to attract optimism. People describe the business as they want it to be rather than as it is.
The second is the customer analysis: who is currently buying, why they buy, what they value, and where the friction points are in the purchase process. This is the section most teams shortchange, usually because it requires primary research and primary research takes time. The shortcut is to use internal data instead, which is often better anyway.
The third is the competitive landscape: who else is competing for the same customers, how they are positioned, where they are investing, and what space is genuinely unoccupied. This is not a feature comparison table. It is a positioning map.
The fourth is the market context: macro trends, regulatory conditions, technology shifts, and category dynamics that will affect how the market behaves over the planning period. The BCG fintech analysis is a useful example of how structural market forces can reshape competitive dynamics faster than most planning cycles anticipate.
The fifth is the synthesis: what the analysis means for strategy. Most situation analyses stop before this step, which is the only step that matters.
If you want to go deeper on the research methods that feed each of these components, the Market Research and Competitive Intel hub covers the full toolkit, from customer interviews to competitive monitoring to category analysis.
Why the Internal Audit Is Where Most Teams Lie to Themselves
I have sat in more planning sessions than I can count where the internal audit section of a situation analysis was effectively a list of things the leadership team was proud of. Strengths were described in aspirational terms. Weaknesses were framed as “areas for development.” The result was a strategy built on a flattering self-portrait rather than an accurate one.
The most useful internal audits are built from data rather than opinion. Revenue concentration by customer segment tells you something real about dependency and risk. Conversion rates at each stage of the funnel tell you where the business is leaking. Customer retention rates tell you whether the product is delivering on its promise. These are not comfortable numbers to present, but they are the ones that produce better strategy.
When I was running an agency and we went through a serious growth phase, scaling from around 20 people to over 100, the internal audit was the discipline that kept us honest. We had to be clear about which client relationships were genuinely profitable, which service lines had real margin, and which capabilities we were claiming to have but had not yet built properly. The gap between the pitch deck version of the agency and the operational reality was the thing we had to close before we could grow sustainably.
The same principle applies to any marketing situation analysis. The internal section is not a celebration. It is a diagnosis.
How to Approach the Customer Reality Section Without Spending Six Months on Research
Customer analysis is the section that planning teams consistently underinvest in, and the reasons are usually practical rather than philosophical. Primary research takes time. Qual interviews require someone to run them. Surveys need designing, fielding, and analysing. When a planning deadline is two weeks away, the customer section gets compressed into a few demographic slides and a persona document that nobody believes.
There is a faster route that produces better output. Start with internal data. Look at what your highest-value customers have in common, not just demographically but behaviourally. What did they buy first? How quickly did they return? What channel brought them in? Where did they drop off before converting? This data exists in most CRMs and analytics platforms and it tells you more about customer reality than a survey of 500 people who may or may not represent your actual market.
Supplement that with direct customer feedback. Tools like Hotjar’s real-time feedback can surface friction points and user sentiment without requiring a formal research programme. Combine that with a handful of customer interviews, five to eight is usually enough to identify patterns, and you have a customer section that is grounded in reality rather than assumption.
The question to answer in this section is not “who are our customers.” It is “why do our best customers choose us, and what would make them leave.” Those are the two levers that strategy needs to pull.
Competitive Analysis Inside a Situation Analysis: What to Actually Look For
Competitive analysis inside a situation analysis is not the same as a standalone competitor review. The purpose here is narrower and more specific: you are trying to understand what positioning space is available and where your competitors are vulnerable, not produce an exhaustive profile of every player in the market.
The most common mistake is building a feature comparison matrix. This tells you what competitors offer but not how they are perceived, which is the thing that actually shapes purchase decisions. A competitor who claims to be the premium option is not necessarily perceived as such. A competitor who is investing heavily in a particular channel may be doing so because that channel is working, or because they have run out of ideas everywhere else.
What you want to map is positioning, not product. Where does each competitor sit on the axes that matter to your customers? Price versus quality, specialist versus generalist, established versus challenger. Then look at where the map is crowded and where it is empty. The empty space is not automatically an opportunity, sometimes it is empty because nobody wants to be there, but it is the starting point for a positioning conversation.
I spent a period judging the Effie Awards, which gives you an unusual view of competitive strategy because you see the thinking behind campaigns rather than just the campaigns themselves. The entries that stood out were almost always the ones where the team had identified a genuine gap in how the category was being sold, not just a gap in product features. The situation analysis is where that kind of gap should first appear.
SWOT: Still Useful, Still Misused
SWOT gets a bad reputation because most SWOT analyses are done badly. The strengths section lists things the business is proud of rather than things it does better than competitors. The weaknesses section is sanitised. The opportunities section is a wishlist. The threats section is a collection of things nobody knows how to address.
Used properly, a SWOT is a synthesis tool, not a brainstorm. It should be populated after the internal audit, customer analysis, competitive review, and market context sections are complete, not before. The strengths and weaknesses should be relative, meaning relative to competitors and relative to what customers actually value. An operational strength that customers do not care about is not a strategic strength.
The most useful output of a SWOT is the cross-analysis: which strengths can be used to capture which opportunities, which weaknesses need to be addressed before which threats become critical. This is where strategy starts to form. Most teams never get there because they treat the SWOT as the output rather than as an input to a harder conversation.
The Market Context Section: What Belongs Here and What Doesn’t
Market context is the external environment section of a situation analysis. It covers the forces that will shape the market during the planning period, regardless of what any individual business does. This is where macro trends, regulatory changes, technology shifts, and category dynamics belong.
The trap in this section is comprehensiveness. Teams list every trend they can find and then fail to connect any of them to strategic implications. A trend that does not affect your customers, your competitors, or your cost structure in a meaningful way during the planning period does not belong in a situation analysis. It belongs in a future-gazing document that serves a different purpose.
The filter to apply is: does this trend change what we should do in the next 12 to 18 months? If the answer is no, cut it. If the answer is yes, be specific about how. A technology shift that is changing how customers search for products in your category is relevant. A geopolitical development that affects raw material costs for a business in your supply chain is relevant if it affects your pricing. Vague references to “digital transformation” are not relevant to anything.
Early in my career, before agency leadership, I learned quickly that the difference between useful market analysis and impressive-looking noise was specificity. I was building a website from scratch at a time when most businesses in that sector did not have one, partly because I had taught myself to code when the budget for a professional build was not available. The market context that mattered was not “the internet is growing” in the abstract. It was “customers in this category are starting to search online before they buy, and nobody in our competitive set has a credible web presence.” That was actionable. Everything else was background.
From Analysis to Strategic Implication: The Step Most Teams Skip
The most common failure mode in situation analysis is producing a thorough, well-researched document that has no visible effect on the strategy that follows. The plan looks more or less the same as last year’s plan. The budget allocation follows the same logic. The target audience is defined in the same terms. The situation analysis sits in a folder somewhere and gets referenced in presentations as evidence that the team did the work.
This happens because teams treat the analysis as a compliance exercise rather than a decision-making tool. The question that should follow every section of a situation analysis is: given what we have just established, what should we do differently? If the answer is nothing, either the analysis was not honest enough or the strategy is already optimal, and the latter is rarely true.
The synthesis section of a situation analysis should produce a short list of strategic implications. Not recommendations, not tactics, but implications. Things that the evidence suggests are true about the market, the customer, and the competitive environment that have consequences for how the business should compete. Three to five clear implications, each grounded in the analysis, is more valuable than a 60-page report with no clear conclusions.
I have managed significant ad spend across a wide range of industries and the campaigns that performed best were almost always the ones where the brief was grounded in a clear-eyed view of the market. When I ran a paid search campaign at lastminute.com for a music festival, the reason it worked was not sophisticated campaign architecture. It was that we understood exactly who was searching, what they needed to hear, and what would make them book. That understanding came from analysis, not instinct.
How Long a Situation Analysis Should Take
There is no universal answer, but there is a useful heuristic: a situation analysis should take as long as it takes to change your mind about something. If you complete the process with exactly the same views you started with, either you were right about everything before you started, which is possible but unlikely, or the process was not rigorous enough.
For most businesses running annual planning cycles, a situation analysis that takes more than three to four weeks is probably expanding to fill the time available rather than producing proportionally better output. The research phase, internal data review, competitive mapping, and synthesis can be completed in that window if the scope is kept tight and the team is focused on implications rather than comprehensiveness.
For smaller businesses or teams with limited resources, a compressed version covering the five core components in a structured half-day workshop, with pre-work assigned beforehand, can produce a working situation analysis that is genuinely useful. The small business planning principles discussed at Copyblogger make a related point: rigour does not require scale. A small team with clear thinking can outplan a large team going through the motions.
The output should be a document short enough to actually influence decisions. Two to four pages of structured findings and implications is more useful than a comprehensive report that gets read once and archived. If the people making budget and strategy decisions cannot summarise the key findings from memory, the situation analysis has not done its job.
For teams building out their broader research and intelligence capability, the Market Research and Competitive Intel hub covers the methods, frameworks, and tools that make situation analysis a repeatable process rather than a one-off exercise.
Common Mistakes That Undermine the Whole Process
Starting with the SWOT. The SWOT should come last, not first. When teams begin with a SWOT brainstorm, they are working from memory and opinion rather than evidence. The SWOT should be a synthesis of the analysis, not a substitute for it.
Using outdated data. A situation analysis built on market research that is two or three years old is describing a market that may no longer exist. Customer behaviour, competitive positioning, and channel dynamics can shift significantly in that window. The analysis needs to reflect current conditions, not historical ones.
Confusing activity with insight. Listing 12 competitors with their social media follower counts and website traffic estimates is activity. Identifying that three of those competitors are all competing for the same mid-market segment while the premium end is underserved is insight. The situation analysis should produce the latter.
Treating it as a solo exercise. The situation analysis benefits from multiple perspectives. Sales teams know things about customer objections that marketing teams do not. Finance teams know things about margin and cost structure that inform which segments are worth pursuing. Product teams know things about capability gaps that affect what can be promised in market. A situation analysis that draws only on marketing department knowledge is systematically incomplete.
Skipping the “so what.” Every section of a situation analysis should end with a clear implication. Not “the market is growing” but “the market is growing in the SME segment while enterprise is flat, which means our current enterprise-focused positioning is misaligned with where the demand is.” The difference between those two statements is the difference between analysis and strategy.
About the Author
Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.
