Effort Impact Matrix

Use this skill to run Effort Impact Matrix as a practical consulting method, not as a generic framework explanation.

Method Notes

• Normalize items so each one is an executable action.
• Use quick wins, major bets, fill-ins, and deprioritize/defer.

Required Inputs

Collect or infer these inputs before execution:

• candidate actions
• impact estimate
• effort estimate
• time or resource constraints

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use when impact and effort cannot be estimated on a comparable basis or when hard dependencies determine the sequence. This is a relative triage tool, not a full investment case.

Adjacent Methods

• rice-scoring: prioritize a backlog using Reach, Impact, Confidence, and Effort.
• wsjf-prioritization: sequence work using Cost of Delay divided by Job Size.
• decision-matrix: make a one-time option choice using explicit weighted criteria.

Step-by-Step Execution

Output Template

### 1. Scope And Anchors
Decision horizon:
Impact definition:
Effort definition:
High/low boundary or medium / boundary-item handling:
Constraints:

### 2. Action Scores
| Action | Impact | Effort | Evidence / assumption | Confidence |
|---|---|---|---|---|
|  |  |  |  |  |

### 3. Quadrant Map
| Quadrant | Actions | Why |
|---|---|---|
|  |  |  |

### 4. Sequence
| Order | Action | Owner | Timing | Expected signal | Stop condition |
|---|---|---|---|---|---|
|  |  |  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Quality Gate

• Produce the method-specific outputs for Scope And Anchors, Action Scores, Quadrant Map; do not substitute a generic framework summary.
• Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
• Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
• Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
• State missing inputs and the smallest validation action instead of inventing precision.
• Keep wording professional and plain enough that a smart non-specialist can use the output directly.