# Goals ## **Getting Started with the Goals Dashboard** **Organization level:** Applies to the entire company. Choose Scope = Organization when creating the goal. Use this for broad outcomes like reliability, delivery speed, or quality across all teams. **Team level:** Applies to one team. Choose Scope = Team, then select the specific team. Use this to drive improvements or delivery targets for that team. **Contributor level:** Applies to one or more individuals. Choose Scope = Contributor, then select the contributor(s). Use this for personal development, review turnaround, or similar metrics. ## **Upload Goals & Key Results** If you don’t want to add goals manually, use the Upload Goal or Upload Key Results buttons. A preview template appears when you click Upload—use it to understand the exact columns and formats required. Once your file matches the template, upload to create goals and key results in bulk.\ Below are the images how goal dashboard looks like when it is created
## **Organization-Level Goal – Setup Guide** ### **A) Goal Details (must be completed first)** Goal Name 🏷️\ Plain language, outcome‑style.\ Examples:\ • “Improve Organization Delivery Quality”\ • “Strengthen Release Reliability” **Goal Description** 📝\ **Goal Name 🏷️** Plain language, outcome‑style. **Examples:** • “Improve Organization Delivery Quality”\ • “Strengthen Release Reliability” **Goal Description 📝** 1–2 lines of context so anyone understands what success looks like.\ Example: “Reduce change failure rate and speed up safe deployments across all teams.” **Scope** Choose Organization (applies to all teams). If you pick anything else, it’s not an org‑level goal. **Timeframe ⏳** Choose one: Weekly, Monthly, or Quarterly. **Minimum duration rule** • Weekly: at least 30 days between start and end\ • Monthly: at least 90 days between start and end\ • Quarterly: at least 180 days between start and end\ If the span is too short, you’ll see a validation pop‑up and cannot continue. **Start Date & End Date 📅** Pick dates that meet the rule for the timeframe you selected.\ Valid examples:\ • Weekly: 1 Jul → 5 Aug (35 days, OK)\ • Monthly: 1 Jul → 1 Oct (92 days, OK)\ • Quarterly: 1 Jan → 30 Jun (181 days, OK)\ ✅ When all five items above are valid, the Key Results section becomes available. ### **B) Key Results (add one or more; weights must total 100)** For each Key Result, fill these fields in order: * Key Result – Short, specific outcome for this metric. * Weight – Contribution of this KR to the overall goal (in %). All KR weights must sum to 100. * Select Metric – Choose the metric to track. * Condition – More Than / Less Than / Between. * Count – Target value(s). ⚠️ If anything is incompatible (e.g., wrong type for the metric, missing range for “Between”), you’ll get a pop‑up and the KR won’t save until corrected. ### **Weight rule (must equal 100)** You can add as many KRs as you like, but the sum of all KR weights must be exactly 100. Once the total is 100 and every KR is valid, the Update Key Results button becomes enabled. ### **C) Finish & Save** * Click Update Key Results (enabled when all KRs are valid and total Weight = 100). * Review the summary. * Click Save Goal. ### **D) Concrete Examples** Example 1 — Delivery Quality (Quarterly) | Field | Example Entry | | ----------- | -------------------------------------------------------------------------------------------------------- | | Goal Name | Improve Organization Delivery Quality | | Description | Reduce change failures and speed up safe releases across all teams. | | Scope | Organization | | Timeframe | Quarterly | | Dates | 1 Jan → 30 Jun | | KR 1 | Reduce CFR – W: 40, Metric: Change Failure Rate, Condition: Less Than, Count: 10% | | KR 2 | Increase Deployment Frequency – W: 30, Metric: Deployment Frequency, Condition: More Than, Count: 5/week | | KR 3 | Improve Cycle Time – W: 30, Metric: Cycle Time, Condition: Less Than, Count: 3 days | Example 2 — Weekly Monitor (needs ≥ 30‑day span) | Field | Example Entry | | ----------- | -------------------------------------------------------------------------------------------------------- | | Goal Name | Stabilize Weekly Release Health | | Description | Keep weekly releases healthy across org. | | Scope | Organization | | Timeframe | Weekly | | Dates | 1 Jul → 5 Aug | | KR 1 | Reduce CFR – W: 50, Metric: Change Failure Rate, Condition: Less Than, Count: 12% | | KR 2 | Increase Deployment Frequency – W: 25, Metric: Deployment Frequency, Condition: More Than, Count: 4/week | | KR 3 | Cycle Time Guardrail – W: 25, Metric: Cycle Time, Condition: Between, Count: 2 and 4 days | ### **E) Common Validation Pop‑ups & Fixes** * “Timeframe dates are too short” – Ensure dates meet minimum span. * “Weights must add up to 100” – Adjust KR weights until total is exactly 100. * “Invalid condition for metric” – Match condition to metric type. * “Key Results can’t be updated yet” – One or more KR fields incomplete/invalid or weights ≠ 100. ### **F) Tips for first‑time users how we can set goal Organization-Level:**
* Keep KRs simple and measurable. * For count metrics, avoid double‑counting by using distinct IDs. * Review progress regularly and adjust future goals. ## **Team-Level Goal – Setup Guide** Main difference from Organization level: Scope = Team. You must select the specific team. ### **A) Goal Details** * Goal Name 🏷️ – Specific to the team. * Goal Description 📝 – Context for the team’s objective. * Scope – Select Team. * Select Team 👥 – Choose which team this goal applies to. * Timeframe ⏳ – Weekly ≥ 30 days, Monthly ≥ 90 days, Quarterly ≥ 180 days. * Start Date & End Date 📅 – Must meet timeframe rules. ### **B) Key Results** Same order, validations, and weight rules as Organization level. ### **C) Example – Team Level** | Field | Example Entry | | ---------------- | ----------------------------------------------------------------------------------------------- | | Goal Name | Reduce Cycle Time – Backend Team | | Goal Description | Cut average cycle time by 25% for Backend Team | | Scope | Team | | Selected Team | Backend | | Timeframe | Quarterly | | Dates | 01 Jan → 30 Jun | | KR 1 | Cycle Time Reduction – W: 50, Metric: Cycle Time, Condition: Less Than, Count: 3 days | | KR 2 | PR Review Time – W: 30, Metric: PR Review Time, Condition: Less Than, Count: 1 day | | KR 3 | Deployment Frequency – W: 20, Metric: Deployment Frequency, Condition: More Than, Count: 4/week | Below are the steps how we can set goal Team level:
## **Contributor-Level Goal – Setup Guide** Main difference from Organization level: Scope = Contributor. You can select one or multiple contributors. ### **A) Goal Details** * Goal Name 🏷️ – Specific to contributor(s). * Goal Description 📝 – Context for the contributor’s objective. * Scope – Select Contributor. * Select Contributor(s) 👤 – Choose one or more contributors. * Timeframe ⏳ – Weekly ≥ 30 days, Monthly ≥ 90 days, Quarterly ≥ 180 days. * Start Date & End Date 📅 – Must meet timeframe rules. ### **B) Key Results** Same order, validations, and weight rules as Organization and Team levels. ### **C) Example – Contributor Level** | Field | Example Entry | | -------------------- | ---------------------------------------------------------------------------------- | | Goal Name | Improve PR Review Turnaround – John Doe | | Goal Description | Reduce PR review time and improve test coverage | | Scope | Contributor | | Selected Contributor | John Doe | | Timeframe | Monthly | | Dates | 01 Jul → 30 Sep | | KR 1 | PR Review Time – W: 60, Metric: PR Review Time, Condition: Less Than, Count: 1 day | | KR 2 | Test Coverage – W: 40, Metric: t Test Coverage, Condition: More Than, Count: 80% | Below are the steps how we can set goal Contributor level: