SWOT Analysis
Menu: Situation Analysis → SWOT Analysis
SWOT collects strengths, weaknesses, opportunities and threats for a strategic cycle. Company/unit and product scopes are selected on the same SWOT page, with access checked separately for each.
Create an analysis
- Select the company and strategic cycle.
- Open Situation Analysis → SWOT Analysis.
- Select company/unit or product scope.
- With creation permission, add an analysis and select its name and relevant unit/product.
- Save and open the details.
Matrix
| Category | What belongs here? | Example |
|---|---|---|
| Strength | Internal advantage | Experienced product team |
| Weakness | Internal limitation | Manual quality checks |
| Opportunity | Positive external factor | New customer segment |
| Threat | Negative external factor | Increasing substitute competition |
Open the add action in a category and enter the category, short summary and optional details. For entries marked as risk, complete risk categories, tags, level and probability. Risk score is calculated from level and probability, rather than a separate textual High/Medium/Low impact field.
The Matrix tab is this four-category view.
Focus areas
Use Focus Areas to review and, with permission, manage links between SWOT entries and strategic priorities. Tracing which priority an entry supports connects analysis with objectives and KPI tracking.
You may use SO/WO/ST/WT as a workshop method: strength + opportunity for growth, weakness + opportunity for development, strength + threat for defense and weakness + threat for risk reduction. These are not automatically generated strategy records in the application.
KPIs
The KPIs tab uses records from the KPI Register. Add KPI can create a KPI from a library or use an existing register KPI, another report or a previous cycle. Measurements and criteria belong to the KPI; weight belongs to the report usage.
Product SWOT can use the same flow with the product library. See KPI Tracking.
Findings
Use Findings to review relevant cycle findings and those already promoted to SWOT. With permission, promote a finding into the appropriate SWOT category. Keeping that link preserves traceability instead of entering the same fact again.
The Findings guide explains analysis-input import and risk links.
Permissions and cycle state
Reading follows company scope; writing follows role and unit scope. Team Leads write in their led subtree; company-level analysis writing requires root-unit leadership. Closed strategic cycles lock writes, and the KPI section shows its closing snapshot.
Role and access scope determine visibility.