Most teams do SWOT the same way. They book a half-day offsite, put four boxes on a whiteboard, and spend the morning arguing about whether "strong brand" belongs in Strengths or whether "economic uncertainty" counts as a Threat. By noon they have a full grid. By Friday, it's filed somewhere and nobody's opened it since.
The framework itself isn't the problem. SWOT is genuinely useful: it maps where you are before you plan where to go. The problem is what happens after the workshop. Most organisations treat the output as an endpoint rather than a starting point.
This article covers how to run a SWOT analysis properly, including where the data for each quadrant should actually come from, and how to connect the output to a strategy your team will execute on.
What is SWOT analysis?
SWOT is a structured framework for assessing an organisation's current strategic position. It examines four dimensions: Strengths and Weaknesses (internal factors the organisation controls) and Opportunities and Threats (external factors it responds to).
The framework was developed at Stanford in the 1960s and has become one of the most widely used tools in strategic planning. Its longevity comes from its simplicity: four clear categories, easy to facilitate, accessible to people without a strategy background.
ℹ️ SWOT does not produce a strategy. It produces the situational awareness you need before you can make strategy decisions.
The SWOT framework: internal factors (top) versus external factors (bottom), helpful versus harmful.
The four quadrants
.png)
Strengths
Strengths are internal capabilities or resources that give the organisation a competitive edge. The key test is whether the strength is genuine and specific, not a feel-good statement. "Our people are great" is not a strength. "Our customer success team achieves 95% retention in a market where the average is 80%" is a strength.
Weaknesses
Weaknesses are internal gaps or limitations that put the organisation at a disadvantage. This is the quadrant people most commonly soften or avoid. A weakness is only useful in a SWOT if it's honest. "We're still building our marketing capability" is more useful than leaving the box empty.
Opportunities
Opportunities are external conditions the organisation could exploit. New market segments, technology shifts, competitor missteps, regulatory changes. Opportunities aren't things you create; they're things you position to take advantage of. The question is whether you have the strengths to pursue them.
Threats
Threats are external factors that could harm the organisation's position. Competitor moves, market shifts, economic conditions, platform dependency. A threat is not automatically a problem: some threats are manageable, some are irrelevant depending on your position. The value of listing them is choosing which ones to actively defend against.
The workshop trap: why most SWOTs are built on vibes
Here's the real problem with how most teams run SWOT: they fill in the grid based on opinion. Leadership gets in a room and surfaces what people feel to be true. The loudest voices dominate. Uncomfortable truths get smoothed over. Aspirational thinking creeps into the Strengths column.
The result is a SWOT that reflects the group's shared narrative rather than the organisation's actual situation. It confirms what everyone already believed, which makes it useless for making genuine strategic decisions.
A data-driven SWOT replaces gut feel with evidence. Before the workshop, you pull the data. What do your retention metrics actually look like? Where have your OKRs been consistently green, and where do check-ins keep showing amber? What have customers said in recent surveys? What deals are you losing and why?
If your team has been tracking goals in a tool like Tability, that historical check-in data is the raw material for an honest SWOT. Two quarters of missed delivery time targets is a documented weakness. A consistent streak of overachieving new logo targets is a real strength, not just a feeling.
How to run a SWOT analysis: five steps
Step 1. Gather evidence before the workshop.
Pull performance data, customer feedback, and goal tracking history before anyone enters the room. Assign sections: one person pulls win/loss data, another reviews operational metrics, another summarises customer satisfaction trends. Walk into the workshop with facts, not a blank canvas.
Step 2. Fill each quadrant with specifics, not generalities.
Every item in the grid should be specific enough to act on. "Good technology" fails the test. "Proprietary data processing pipeline that processes 10x faster than off-the-shelf solutions" passes it. If you can't attach evidence or a number to a claim, it probably doesn't belong in the grid.
Step 3. Challenge the Strengths column hardest.
Teams are naturally optimistic about their strengths and pessimistic about their weaknesses. In practice, the most important work happens in the Strengths column: stress-testing whether an apparent advantage is actually defensible. Ask: would a new competitor with no legacy constraints be able to replicate this in 18 months? If yes, it's a competitive requirement, not a strength.
Step 4. Map Opportunities against Strengths.
Not every Opportunity is worth pursuing. The right Opportunities are those where your Strengths give you a genuine edge over everyone else chasing the same opening. A useful exercise: draw lines from Opportunities to the Strengths that would allow you to pursue them. If an Opportunity has no corresponding Strength, it belongs in the "wishlist" column, not the strategy.
Step 5. Close the loop: turn findings into commitments.
The SWOT ends when each key finding is assigned to a next step. Not a recommendation, not a suggestion. An owner, a deadline, and a measurable outcome. This is where most SWOT sessions fail, and it's the step this article returns to below.
Using Tability to gather the data your SWOT needs
The quality of a SWOT analysis is determined almost entirely by the quality of the data that goes into it. This is where most teams fall short: they run the workshop from memory and consensus rather than from a record of what has actually happened.
If your team has been using Tability to track goals, you already have the primary data source for an honest internal assessment. Here is how to use it.
For Strengths: look at consistent overachievement
In Tability, pull your goal progress history across the last two to three planning cycles. Look for outcomes where check-ins have consistently shown green, and where teams have hit or exceeded targets across multiple periods. Consistent overachievement in a specific area is a documented strength, not a workshop opinion. Pay particular attention to metrics that matter competitively: customer retention, time to close, delivery reliability.
For Weaknesses: find the persistent amber and red
The check-in history is equally useful for identifying weaknesses. Outcomes that repeatedly show amber or red across planning cycles are not isolated misses: they are a pattern. If your team has checked in on "improve enterprise NPS" for three quarters and the needle hasn't moved, that is a documented weakness. Tability's reporting makes this pattern visible without requiring anyone to admit it in a room.
The AI-powered insights in Tability can also surface these patterns automatically. Rather than manually reviewing every check-in, you can ask Tability to identify which areas have seen the most consistent underperformance, and use that as the starting point for your Weaknesses quadrant.
For Opportunities and Threats: use reporting to challenge assumptions
External factors require external data, so Tability won't fill in the Opportunities and Threats quadrants directly. But it can help you challenge the assumptions people bring into the room. If someone claims "our biggest threat is slow delivery times," the check-in data either supports or contradicts that. If delivery OKRs have been consistently green, the threat may be overstated. If they've been red, the data confirms what the gut already suspected.
💡 Before your next SWOT session: run a Tability report on the last two to three cycles and export the goal progress summary. Walk into the workshop with that report instead of a blank whiteboard.
From SWOT analysis to action: the missing step
A SWOT analysis tells you where you are. It doesn't tell you where to go or how to get there. The gap between the two is where strategy dies.
The translation works like this. Each quadrant produces a different type of strategic input:
Strengths become the foundation of your strategic pillars: the two or three focus areas where your strategy is concentrated. A company with a genuine strength in customer data should have a strategic pillar around data product development. A company whose culture is a documented differentiator should have a pillar around talent.
Opportunities and Threats become OKRs: specific objectives with measurable key results that tell you whether you're actually pursuing the opportunity or successfully defending the threat. Without this step, a SWOT is a diagnosis without a prescription.
Weaknesses require honest improvement objectives. Not "we'll invest in this area" but "by end of Q2, our NPS in the enterprise segment will move from 34 to 45." The measurable target is what converts a weakness into a commitment.
💡 The question to ask at the end of every SWOT session: what is each person in this room going to measure differently as a result of what we found?
SWOT vs VRIO: which framework to use
SWOT and VRIO are complementary, not competing. They answer different questions and work best in sequence.
SWOT is the broader scan. It covers both internal and external factors, surfaces issues quickly, and is accessible to a wide range of participants. It works well at the start of a strategic planning cycle to map the landscape before narrowing focus.
VRIO is a deeper internal analysis. It takes the Strengths quadrant of a SWOT and subjects it to rigorous scrutiny: which of these strengths are actually hard to copy? VRIO separates genuine competitive advantages from strengths that look good on paper but provide no lasting protection.
The practical sequence: use SWOT to open the strategic conversation and identify priorities. Then use VRIO to pressure-test whether your apparent strengths are genuinely defensible. The combination gives you both breadth and depth.
What data should go into your SWOT
The quality of a SWOT is entirely dependent on the quality of the inputs. Here is where each quadrant's evidence should come from:
- Strengths: goal tracking data (where have teams consistently overachieved?), customer retention metrics, win rates in competitive deals, employee engagement scores, product usage data.
- Weaknesses: missed targets from the last two to three planning cycles, NPS data by segment, operational bottleneck analysis, skills gap assessments, customer churn reasons.
- Opportunities: market research, customer interview themes, competitor pricing and product gaps, technology trends, regulatory pipeline.
- Threats: competitor announcements and product launches, customer churn reasons, market share data, supply chain or dependency risks, talent market dynamics.
Teams using Tability have an advantage here: the check-in history and goal progress data provides a continuous record of what the organisation is actually achieving versus what it planned. That record becomes the evidence base for an honest internal assessment, rather than a workshop where the loudest voice wins.
Common SWOT mistakes
- Filling the grid with generalities. Every item should be specific enough to act on.
- Skipping the external research. Opportunities and Threats should come from evidence, not inference.
- Running SWOT in isolation. The output is only useful if it connects to a planning process that produces commitments.
- Not revisiting it. SWOT is most useful when run at the start of each planning cycle, not as a one-off exercise.
- Treating all four quadrants equally. Strengths are the foundation of strategy. The SWOT lives or dies on how honest and specific that quadrant is.
Turn your SWOT findings into goals your team actually tracks
Tability gives you two things SWOT analysis needs most: the historical goal data to run an honest internal assessment, and the OKR tracking to act on what you find. Your check-in history tells you where you're genuinely strong and where you're not. Your OKRs turn the findings into commitments teams measure every week.
Using Tability's AI-mode or MCP server, you can quickly get answers to any questions you may have regarding your next business opportunities. When running your SWOT analysis, getting quick answers is invaluable.
Try Tability free and build your first strategic plan from your SWOT output, or book a demo to see how other teams use Tability to close the strategy-to-execution gap.
.png)
.jpg)
