## Overview A structured, repeatable framework for improving business processes, performance, and profitability. It works by translating goals into measurable rituals, tracking effort and results, and running weekly improvement cycles. Applicable at the company, department, or individual level, with typical turnaround timelines of 3–6 months. --- ## Key Concepts - **Goal Statement** – a time-bound declaration of what will be achieved and by when - **Potential Difficulty** – anticipated obstacles that block goal achievement - **Potential Possibility** – specific solutions mapped to each identified difficulty - **Success Ritual** – a recurring, non-negotiable rule or habit derived from each possibility - **Effort Score** – a measure of input activities (e.g., number of calls made) - **Result Score** – a measure of output outcomes (e.g., revenue generated) - **Improvement Cycle** – a weekly review loop based on the PDCA model --- ## Detailed Notes ### Step 1: Write a Goal Statement - Convert aspirations into a **concrete, time-bound goal** - Keep the horizon short: **1–6 months** (more effective than long-term targets) - Format: **"What [entity] will achieve by [date]"** - Can be written at three levels: | Level | Goal Statement Format | |---|---| | **Company** | "What the company will achieve by [date]" | | **Department** | "What the department will achieve by [date]" | | **Individual** | "What the individual will achieve by [date]" | - Avoid indefinite planning — commit to a decision and move forward --- ### Step 2: Identify Potential Difficulties - List **all anticipated obstacles** preventing goal achievement - Be specific — vague difficulties produce vague solutions - This step forces honest assessment of what stands in the way --- ### Step 3: Map Potential Possibilities - For **each difficulty** listed in Step 2, write a **corresponding specific solution** - Every difficulty must have at least one possibility - Possibilities should be actionable, not aspirational --- ### Step 4: Convert Possibilities into Success Rituals - Transform each possibility into a **fixed rule, routine, or ritual** - Rituals protect against inconsistency caused by **mood swings or motivation dips** - When communicated as rules, teams are more likely to follow them consistently - **Example:** If the possibility is "exercise daily," the ritual becomes → *"06:00–07:00 is non-negotiable exercise time"* --- ### Step 5: Measure the Success - Track two distinct scores for each ritual: | Score Type | What It Measures | Example | |---|---|---| | **Effort Score** | Input/activity volume | Number of sales calls per day | | **Result Score** | Output/outcome achieved | Revenue generated per day | - Set **expected scores** in advance, then track **actual scores** - Both scores together reveal whether performance gaps are caused by **effort deficiency** or **effectiveness deficiency** --- ### Step 6: Review Steps 4 and 5 - Compare **expected vs. actual** for both effort and result scores - Calculate achievement percentage: | Metric | 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 | Target revenue | 80% of target | 80% achieved | | Result Score | Target revenue | 120% of target | 120% achieved | - Optionally rate on a **1–10 scale** - Use review data to build **Management Information System (MIS) reports** - Review data informs decisions on: - **Rewards, recognition, and compensation** for individuals - **Product performance** across categories - **Regional or segment performance** across territories - **Review frequency:** weekly (minimum) — daily monitoring preferred to catch direction errors early --- ### Step 7: Improvement Cycle (Action Plan) - Conduct a **weekly review** (suggested: start of each work week) - Evaluate three dimensions: | Dimension | Timeframe | Action | |---|---|---| | **What went well** | Previous week | **Repeat** these actions | | **What went wrong** | Previous week | **Improve** these areas | | **What could be improved** | Coming week | **Plan** new actions | - Start reviews with **revenue-linked departments** first, then move to support departments - Dual focus: **increase revenue streams** while simultaneously **reducing costs** - The "what could be improved" element drives all iterative change --- ### Linking the Improvement Cycle Back to the Framework - When improvements are identified, **loop back to earlier steps** as needed: - New difficulties? → return to **Step 2** - New solutions? → return to **Step 3** - New habits needed? → return to **Step 4** - Root causes may shift over time — common progression: 1. **Skill gap** → solve with training and development 2. **Data integrity issue** → solve with verification and accountability 3. **Motivation/will issue** → solve with incentives, leadership behaviour, and culture - The framework is **self-correcting** — each cycle narrows the gap between current and desired performance --- ### PDCA Model (Embedded in the Improvement Cycle) - **Plan** – design the specific improvements - **Do** – implement the improvements - **Check** – verify whether implementation was successful - **Act** – refine and improve further based on results --- ## Mermaid Diagrams ### Full 7-Step Framework Flow ```mermaid flowchart TD A[Step 1: Goal Statement] --> B[Step 2: Potential Difficulties] B --> C[Step 3: Potential Possibilities] C --> D[Step 4: Success Rituals] D --> E[Step 5: Measure Success] E --> F[Step 6: Review Effort & Result Scores] F --> G[Step 7: Improvement Cycle] G -->|What could be improved| D G -->|Root cause shift| B ``` ### Weekly Improvement Cycle ```mermaid flowchart LR A[Review Previous Week] --> B{What went well?} A --> C{What went wrong?} B --> D[Repeat] C --> E[Improve] A --> F{What could be improved?} F --> G[Plan for Next Week] G --> H[Execute] H --> A ``` ### PDCA Cycle ```mermaid flowchart TD P[Plan] --> D[Do] D --> C[Check] C --> A[Act] A --> P ``` ### Root Cause Escalation Path ```mermaid flowchart TD A[Revenue Not Increasing] --> B{Is effort sufficient?} B -->|No| C[Address Effort: Rituals & Accountability] B -->|Yes| D{Is skill sufficient?} D -->|No| E[Address Skill: Training & Development] D -->|Yes| F{Is data accurate?} F -->|No| G[Address Integrity: Verification Systems] F -->|Yes| H[Address Will: Incentives, Leadership, Culture] ``` --- ## Key Terms - **Goal Statement** – a short-term, time-bound declaration of intended achievement - **Success Ritual** – a fixed, recurring rule that operationalises a solution - **Effort Score** – quantified measure of input activities - **Result Score** – quantified measure of output outcomes - **MIS Report** – Management Information System report aggregating performance data - **PDCA** – Plan, Do, Check, Act — a continuous improvement cycle - **Improvement Cycle** – weekly structured review to identify what to repeat, fix, or enhance --- ## Quick Revision - Set **short-term (1–6 month) goal statements** at company, department, or individual level - List all **difficulties** blocking the goal, then map a **specific solution** to each - Convert every solution into a **non-negotiable ritual or rule** - Track both **effort scores** (inputs) and **result scores** (outputs) against expectations - **Review weekly** — compare expected vs. actual, build MIS reports - Use three questions: **what went well → repeat**, **what went wrong → improve**, **what could be improved → plan** - Start with **revenue-generating departments**, then extend to support functions - When results stall, **loop back** through the framework to find shifted root causes (skill → data → motivation) - The framework embeds a **PDCA cycle** for continuous, compounding improvement - Expect measurable transformation within **3–6 months** of consistent application