# 7-Step Performance Turnaround Framework ## Overview This framework provides a structured, repeatable 7-step process for improving organisational performance, speed, and scale. It converts vague ambitions into measurable rituals, tracks effort and results, and uses a weekly improvement cycle (PDCA) to drive continuous progress. It is applicable at the company, department, or individual level. --- ## Key Concepts - **Goal Statement** – a short-term, time-bound declaration of what will be achieved and by when - **Potential Difficulty** – anticipated obstacles that may prevent goal achievement - **Potential Possibility** – specific solutions mapped to each identified difficulty - **Success Ritual** – a repeatable rule or habit created from each possibility to ensure consistent action - **Effort Score** – a measure of whether the required activities (inputs) are being completed - **Result Score** – a measure of whether the desired outcomes (outputs) are being achieved - **PDCA Cycle** – Plan, Do, Check, Act — a continuous improvement loop applied weekly --- ## Detailed Notes ### Step 1: Write a Goal Statement - Convert broad ambitions into a **specific, written goal statement** - Time-bound to **1–6 months** (short-term goals are more actionable) - Format: **"What will be done, by when"** - Can be written at three levels: - **Company level** – overall business targets - **Department level** – functional team targets - **Individual level** – personal performance targets - Avoid indefinite dreaming; the act of writing forces commitment and decision-making ### Step 2: Identify Potential Difficulties - List **all foreseeable obstacles** that could prevent achievement of the goal - This step explains why previous goals may have failed - Be honest and specific — vague difficulties lead to vague solutions ### Step 3: Map Potential Possibilities - For **each difficulty** identified in Step 2, write a **specific corresponding solution** - Every difficulty has at least one possibility - Possibilities must be **clear and actionable**, not abstract ### Step 4: Create Success Rituals - Convert each possibility into a **ritual (rule or routine)** - Rituals protect progress from being disrupted by mood, motivation, or inconsistency - A ritual includes **what to do and when to do it** - Example: If the possibility is "exercise daily," the ritual becomes "exercise from 6:00 AM to 7:00 AM every day" - Rituals apply to teams as well — when a ritual is mandated, compliance increases ### Step 5: Measure Success - Track two types of scores: - **Effort Score** – measures whether the ritual (activity/input) was performed - **Result Score** – measures the outcome produced by that effort - Compare **expected vs. actual** for both scores | Score Type | Expected | Actual | Review | |---|---|---|---| | **Effort Score** | 50 calls/day | 40 calls/day | 80% achieved | | **Effort Score** | 50 calls/day | 60 calls/day | 120% achieved | | **Result Score** | Revenue target X | Actual revenue 0.8X | 80% achieved | | **Result Score** | Revenue target X | Actual revenue 1.2X | 120% achieved | - Scores can also be rated on a **1–10 scale** - Use this data to build **Management Information System (MIS) reports** - Data informs decisions on **rewards, recognition, increments**, and identifying underperformance ### Step 6: Review Steps 4 and 5 - Compare effort scores and result scores **weekly** - Identify which products, teams, or regions are performing well or poorly - Without regular review, teams can drift off course without leadership noticing - Daily or weekly review ensures **course correction happens early** ### Step 7: Improvement Cycle (Action Plan) - Conduct a **weekly review** with three questions: 1. **What went well?** (previous period) 2. **What went wrong?** (previous period) 3. **What could be improved?** (next period) - Actions from the review: - **Repeat** what went well - **Improve** what went wrong - The "what could be improved" element drives all meaningful change - Consistent application over **3–6 months** produces significant organisational improvement --- ### Applying the Framework: Implementation Guidelines - Run the framework **weekly, department by department** - Allocate **30 minutes to 2 hours** per department per cycle - Start with **revenue-linked departments** first, then move to support functions - Prioritise revenue generation before cost reduction (or do both simultaneously in smaller organisations) - Build additional revenue streams using the framework as a discovery tool ### Iterative Problem-Solving Within the Framework - If the "what could be improved" review reveals deeper issues, **loop back** to earlier steps - Common iteration paths: - Results not improving → revisit **Step 4** (rituals may need changing) - Rituals are followed but outcomes are poor → revisit **Step 2** (the identified difficulty may be wrong) - Effort data appears inflated → investigate **data integrity and motivation issues** - Team underperforming despite effort → check **training gaps, management behaviour, or incentive structures** --- ### PDCA Continuous Improvement Cycle - **Plan** – design the improvements needed - **Do** – implement the planned changes - **Check** – verify whether the implementation was successful - **Act** – refine further based on results --- ## Tables ### Framework Steps at a Glance | Step | Action | Key Output | |---|---|---| | 1. Goal Statement | Define what will be achieved and by when | Written, time-bound goal | | 2. Potential Difficulty | List all obstacles to goal achievement | Obstacle register | | 3. Potential Possibility | Map a specific solution to each difficulty | Solution map | | 4. Success Ritual | Convert possibilities into repeatable rules | Ritual schedule | | 5. Measure Success | Track effort scores and result scores | Performance data | | 6. Review | Compare expected vs. actual performance | Review report | | 7. Improvement Cycle | Identify what went well, wrong, and can improve | Action plan for next cycle | ### Effort Score vs. Result Score | Dimension | Effort Score | Result Score | |---|---|---| | **Measures** | Input / activity completion | Output / outcome achievement | | **Example** | Number of calls made per day | Revenue generated per day | | **Purpose** | Ensures rituals are being followed | Ensures rituals are producing results | | **Gap Diagnosis** | Low effort = discipline/compliance issue | Low result despite high effort = strategy/skill issue | --- ## Diagrams ### 7-Step Framework Process Flow ```mermaid flowchart TD A[Step 1: Write Goal Statement] --> B[Step 2: Identify Potential Difficulties] B --> C[Step 3: Map Potential Possibilities] C --> D[Step 4: Create Success Rituals] D --> E[Step 5: Measure Success - Effort & Result Scores] E --> F[Step 6: Review Steps 4 & 5] F --> G[Step 7: Improvement Cycle] G -->|What could be improved?| D G -->|Deeper issue found?| B ``` ### PDCA Continuous Improvement Cycle ```mermaid flowchart LR P[Plan] --> D[Do] D --> C[Check] C --> A[Act] A --> P ``` ### Iterative Problem-Solving Logic ```mermaid flowchart TD R[Weekly Review] --> Q1{Results Improving?} Q1 -->|Yes| REPEAT[Repeat What Works] Q1 -->|No| Q2{Are Rituals Being Followed?} Q2 -->|No| FIX_DISCIPLINE[Address Discipline / Motivation] Q2 -->|Yes| Q3{Is the Difficulty Correct?} Q3 -->|No| REVISE_DIFF[Revisit Step 2: Redefine Difficulty] Q3 -->|Yes| Q4{Training or Skill Gap?} Q4 -->|Yes| TRAIN[Provide Training & Re-measure] Q4 -->|No| INVESTIGATE[Investigate Data Integrity / Management Issues] ``` --- ## Key Terms - **Goal Statement** – a written, time-bound commitment defining what will be achieved and by when - **Potential Difficulty** – a forecasted barrier to goal achievement - **Potential Possibility** – a specific, actionable solution paired to each difficulty - **Success Ritual** – a repeatable rule or scheduled habit that operationalises a possibility - **Effort Score** – a metric tracking whether the required activities (inputs) are being completed as expected - **Result Score** – a metric tracking whether the desired outcomes (outputs) are being produced - **MIS Report** – Management Information System report; a data-driven summary of organisational performance - **PDCA** – Plan, Do, Check, Act; a four-stage continuous improvement methodology - **Improvement Cycle** – a weekly review process asking what went well, what went wrong, and what could be improved --- ## Quick Revision 1. The **7-step framework** converts ambitions into measurable, repeatable processes that drive performance improvement over 3–6 months. 2. **Step 1** requires writing a specific, time-bound goal statement at the company, department, or individual level. 3. **Steps 2–3** pair every anticipated difficulty with a concrete, actionable possibility (solution). 4. **Step 4** converts possibilities into **success rituals** — scheduled, rule-based habits that remove reliance on motivation. 5. **Step 5** tracks both **effort scores** (input compliance) and **result scores** (output achievement) against expected targets. 6. **Step 6** reviews performance data weekly to detect drift and inform decisions on rewards, training, and course correction. 7. **Step 7** uses a three-question improvement cycle: what went well, what went wrong, and what could be improved. 8. The framework is **iterative** — if results don't improve, loop back to earlier steps to redefine difficulties, possibilities, or rituals. 9. **PDCA (Plan, Do, Check, Act)** underpins the entire improvement cycle as a continuous refinement methodology. 10. Start implementation with **revenue-linked departments** first, then expand to supporting functions.