--- name: wir-weekly-translation description: > Translates a participant's rough weekly work notes into executive-level business language mapped to the 5 WIR metrics (Revenue, Speed, Risk, Team, Momentum). Use every Friday or whenever a user wants to convert their dashboard row into CFO/CRO-ready language. This is the core weekly ritual of the WIR framework. --- # Weekly Translation Sub-Skill > **Prerequisite:** Load `skills/SKILL.md` first for the core > framework, 5 metrics definitions, and reframe quality gate. --- ## Purpose Turn one week of messy, honest, task-heavy notes into 2–3 sentences that could be read aloud in an executive meeting — and make the connection between the participant's work and real business value unmistakably clear. --- ## When to Use - User says it's Friday (or end of week) - User wants to fill in their weekly dashboard row - User pastes rough notes and says "translate this" - User says "what did I actually accomplish this week" --- ## Step-by-Step Workflow ### Step 1 — Receive Input Accept the user's weekly notes in any format: - Pasted text from their dashboard - Bullet points - A linked Google Doc or Sheet - Stream-of-consciousness sentences Do not ask them to clean it up first. Work with what they give you. If they haven't given you anything yet, prompt with: > "Paste in your rough notes from this week — anything you worked on, > conversations you had, problems you solved. Don't filter. Just dump it." --- ### Step 2 — Map to the 5 Metrics Read through their notes and silently map each item to one or more metrics: | Look for... | Map to | |---|---| | Deal movement, renewals, expansions, pipeline | 💰 Revenue | | Time saved, process shortened, lag removed | ⚡ Speed | | Churn flagged, issue surfaced, problem prevented | 🛡 Risk | | Rep enabled, team trained, someone coached | 👥 Team | | New segment, new adoption, new traction | 🚀 Momentum | If a note doesn't map to any metric → it's likely a task, not an outcome. Set it aside unless the user wants to discuss it. --- ### Step 3 — Identify the Numbers Before translating, extract or prompt for any numbers: - Dollar amounts (deal size, pipeline value, budget impacted) - Percentages (conversion rate, churn reduction, efficiency gain) - Time (days saved, weeks shortened, cycle length) - People (reps enabled, accounts touched, team size) If a number is missing, gently ask: > "Do you have a rough number for [item]? Even an estimate helps — > executives trust specifics more than descriptions." --- ### Step 4 — Translate Produce the weekly translation in this format: --- **📊 Weekly Impact Translation** **Metric Mapping:** - 💰 Revenue: [translated contribution] - ⚡ Speed: [translated contribution] - 🛡 Risk: [translated contribution] - 👥 Team: [translated contribution] - 🚀 Momentum: [translated contribution] *(Only include metrics where the user had activity. Omit blank ones.)* **📢 Executive Translation (CFO/CRO Language):** > [2–3 sentences combining the strongest 1–2 outcomes into language a CRO > would say in a meeting. Lead with the biggest business impact. Include numbers. > Remove all task language.] **Dashboard Row (Ready to Copy):** | Week | 💰 Revenue | ⚡ Speed | 🛡 Risk | 👥 Team | 🚀 Momentum | 📢 Executive Translation | |------|-----------|---------|--------|--------|------------|--------------------------| | [Date] | [entry] | [entry] | [entry] | [entry] | [entry] | [2–3 sentence summary] | --- ### Step 5 — Reframe Quality Check Before delivering output, verify: - [ ] No task language ("helped with," "supported," "managed") without an outcome attached - [ ] At least one number appears in the executive translation - [ ] The executive translation could be read aloud in 30 seconds - [ ] Each entry answers "so what?" for a business leader If any check fails → revise before outputting. --- ## Example Transformation **User's raw note:** > "Had a lot of calls with the enterprise team this week. Also sent some follow-ups > on the Johnson account. Ran the enablement session for new reps." **Translated output:** 💰 Revenue: Accelerated follow-up on Johnson account — currently at risk of pushing to next quarter. 👥 Team: Delivered onboarding enablement to [X] new reps — covering [topic] to accelerate their ramp to first deal. 📢 Executive Translation: > "Intervened on a stalled enterprise deal to protect Q3 timing. Simultaneously > onboarded [X] new reps with targeted enablement — reducing ramp time and > protecting pipeline continuity." --- ## Edge Cases **User has no numbers at all:** Prompt once: "Pick your strongest win this week — can you estimate the dollar value, the time saved, or the number of people it touched?" Then work with whatever they give. **User's week was "slow" or "internal":** Internal weeks still contain impact. Prompt: "Did anything move faster, get unblocked, or become clearer this week because of your involvement?" There's almost always something. **User pastes a full Google Sheet:** Focus on the most recent week's row. Confirm: "I'm looking at [week]. Is that the one you want to translate?"