TOWS Matrix: Turn SWOT Findings into an Action Plan

A TOWS matrix turns a SWOT analysis into strategic options. It pairs internal strengths and weaknesses with external opportunities and threats, then asks what the organization should do. In Japanese business writing, this is often called cross-SWOT analysis.

The useful output is a decision, not a full set of boxes. Give each option an evidence base, an owner, a resource requirement and a review date. The following example shows how to move from observations to a small, testable plan.

What the four TOWS strategies mean

Strategy	Pairing	Decision question
SO	Strengths and opportunities	Which opportunity can we pursue using an existing capability?
ST	Strengths and threats	How can a capability reduce exposure to an external threat?
WO	Weaknesses and opportunities	What gap must we address to make an opportunity usable?
WT	Weaknesses and threats	What should we limit, redesign or avoid to reduce downside?

An ST strategy need not be an aggressive response to a competitor. It might involve diversifying supply or clarifying a service promise. A WT strategy need not mean closing a business. Narrowing a project’s scope can also reduce exposure. Make each proposal specific enough for someone to act on it.

A worked example: a small software business

Aoba Tools is a fictional Japanese software company serving small manufacturers. Its planning goal is to generate qualified sales conversations over the next 90 days. Every condition, cost and action below is illustrative, not a reported result or industry benchmark.

Factor	Working assumption	Evidence to collect in a real business
S1	Staff have experience supporting factory implementations	Support records and customer interviews
W1	Setup guidance is fragmented and assistance takes too long	Support categories and time logs
O1	An industry association has asked about a workshop	The request, audience needs and attendance criteria
T1	A competitor is offering a lower-priced plan	Published pricing and documented loss reasons

SO pairs the implementation capability with the workshop opportunity: run one practical workshop for the association. ST uses the same capability to clarify implementation support and responsibilities, giving buyers a basis for comparison beyond headline price. WO creates a setup guide for the workshop and tests whether it also reduces repeated support questions. WT reviews the scope and terms of projects that consume more support than their margin can cover.

Record the factor codes beside each proposal. This makes it possible to revisit an option when its assumptions change. If the association’s request is uncertain, verify demand before producing a sales forecast.

Compare options before committing resources

Option	Illustrative resource requirement	First uncertainty to test	Initial decision
SO: run one workshop	JPY 100,000 and 20 staff hours	Will the intended audience attend and raise relevant needs?	Pilot
WO: create a setup guide	JPY 50,000 and 15 hours	Can customers and staff follow it successfully?	Develop alongside the pilot
ST: expand a supported plan	JPY 300,000 and 60 hours	Will buyers pay enough to cover delivery?	Interview customers first

These are Japanese-yen examples, not recommended budgets. A scoring system can help compare alternatives, but a score is not a probability of success. Separate mandatory constraints from preferences: a contractual problem or a cash shortage should not disappear because an option receives a high growth score. Break expensive, uncertain proposals into smaller evidence-gathering steps.

Turn the decision into a 90-day plan

Period	Work	Owner	Review question
Days 1–30	Validate customer problems, set attendance criteria and draft the guide	Sales and implementation staff	Are we addressing a real, shared problem?
Days 31–60	Run one workshop and record follow-up requests	Marketing	How many relevant conversations occurred, and what did delivery cost?
Days 61–90	Review opportunity progress and support effort	Sales manager	Continue, change the offer or stop?

Define a qualified conversation before launch. A registration alone may not meet that definition. For a long sales cycle, report open opportunities separately from revenue and realized profit. Do not count all future contract value as cash earned within the pilot period.

Also record other changes that could affect results, including pricing, seasonality and existing sales activity. An improvement after a workshop does not by itself establish that the workshop caused it. Reporting helps organize evidence; it does not remove the need for an appropriate evaluation design.

A reusable decision template

Objective, customer segment and planning horizon: ____
Internal factor, external factor and dated evidence: ____
Proposed action and expected mechanism: ____
Required budget, staff time and constraints: ____
Unverified assumptions and how to test them: ____
Accountable owner, deadline and first deliverable: ____
Conditions for continuing, changing or stopping: ____

Review the matrix when evidence changes, a competitor changes its offer or a pilot contradicts a key assumption. Keep the original reasoning alongside the updated decision. This turns TOWS into a practical record of choices rather than a one-off workshop exercise.

Review your results consistently

For ongoing data aggregation, comparison and reporting, review NeX-Ray’s integrations and features. Check the plan requirements for your analysis, then start for free.

Sources and verification

Public documentation checked on October 1, 2026. Availability and interface details can vary by account and market; check the linked documentation before configuring a campaign.