Skip to main content

Product SWOT & Product Scorecard

Audience: Product Manager, Strategy Manager
Page Type: How-To Guide
Phase: Cross-Phase
Duration: 45-60 minutes

Product SWOT​

What It Is​

Product SWOT in COS uses the same SWOT engine with product scope. Each analysis is linked to:

  • Product
  • Strategic cycle
  • Org unit

Record Model​

SWOT entries are stored as:

  • Category: STRENGTH, WEAKNESS, OPPORTUNITY, THREAT
  • Summary: required
  • Detail: optional
  • Risk fields (optional, same record):
    • isRisk
    • riskPrimaryCategories (multi-select)
    • riskSecondaryTags (multi-select)
    • riskLevel (0..1)
    • riskProbability (0..1)
    • on-the-fly score: riskLevel * riskProbability

Basic Flow​

  1. Go to Synthesis → Product SWOT
  2. Create analysis (product + cycle + org unit + name)
  3. Add SWOT entries by category
  4. Optionally mark entries as risk and fill risk fields inline
  5. Update or remove entries as needed

Risk behavior:

  • If risk is unchecked, risk fields are cleared automatically.
  • If risk is checked, at least one primary category and level/probability are required.

Integration with Findings​

Product SWOT entries are not listed in Findings → Analysis Inputs.

Findings import scope is limited to PESTLE, Porter, and VRIO analysis inputs.
Product SWOT remains a synthesis artifact and is managed inside the Product SWOT module itself.

Product Scorecard​

What It Is​

Product Scorecard tracks product-level KPIs per strategic cycle.

Scorecard/KPI Model​

  • Scorecard is tied to product + strategic cycle
  • KPI fields include:
    • title
    • category (FINANCIAL, CUSTOMER, OPERATIONAL, GROWTH, QUALITY)
    • unit
    • betterDirection
    • isActive, order

betterDirection values are:

  • HIGHER_IS_BETTER
  • LOWER_IS_BETTER

Adding KPIs​

  1. Open scorecard detail
  2. Add KPI from Product KPI Library (or create/maintain in library first)
  3. Review category and betterDirection

Measurement Model​

Each KPI measurement uses:

  • periodStart, periodEnd, periodicity
  • target, actual, forecast (optional)
  • statusNote (optional)

Tips​

  • Keep SWOT entry text short and decision-focused
  • Do not mix KPI meaning and KPI target in the title; keep title stable
  • Use one consistent periodicity per KPI where possible for cleaner trend tracking