Swot Prioritisation

Purpose

45ck ae6f6a8 1.2 KB Updated

File contents

Purpose

Map strengths, weaknesses, opportunities, and threats, then prioritise the few that matter most.

Use when

  • a SWOT is explicitly requested
  • you need a compact strategic diagnosis
  • you need to transition from broad analysis to focused action

Inputs

  • problem context
  • available evidence and constraints
  • known stakeholders or actors
  • desired output format

Procedure

  1. Clarify the decision or deliverable.
  2. State assumptions before analysis.
  3. Apply the technique explicitly rather than implicitly.
  4. Capture findings in a structured table or list.
  5. Separate facts, inferences, and unknowns.
  6. End with implications for next actions.

Outputs

  • prioritised SWOT matrix
  • rationale for each priority
  • strategic implications
  • suggested responses

Guardrails

  • Do not present the technique as the answer; use it to inform a decision.
  • Flag missing evidence and weak assumptions.
  • Keep terminology consistent with the project glossary.
  • Where tradeoffs exist, rank them explicitly.

Completion criteria

  • technique applied correctly
  • assumptions visible
  • findings actionable
  • next step clear

45ck/business-analysis-skills/tree/main/atomic/swot-prioritisation commit ae6f6a8ddf

Frequently asked questions

npx skillmds@latest add 45ck/swot-prioritisation