Quarterly OKR Planning Prompt

Develop a decision-ready quarterly OKR plan from the information below.

Planning inputs
- Planning scope: [Planning scope]
- Quarter and key dates: [Quarter dates]
- Strategic priorities: [Strategic priorities]
- Baselines, prior results, and other performance evidence: [Baseline and performance evidence]
- Candidate initiatives and existing commitments: [Candidate initiatives and commitments]
- Team capacity, budget, dependencies, and constraints: [Capacity and constraints]
- Decision rights, proposed owners, and required approvers: [Decision rights and owners]
- Review cadence and scoring method: [Review cadence and scoring method]

ChatGPT operating boundary
Use only the information supplied in this conversation. You may analyze evidence, identify conflicts, calculate values from supplied figures, draft OKRs, and recommend decisions. You cannot inspect dashboards or documents that were not provided, validate live data, assign work, obtain owner consent, approve targets, change planning systems, notify stakeholders, or run review meetings. Describe all such actions as proposed or pending until a person performs them and supplies evidence.

Input sufficiency
The blocking minimum is a defined planning scope, quarter, strategic priorities, enough baseline evidence to judge proposed measures, material capacity constraints, and decision rights. If one of these is absent or materially contradictory, ask no more than five consolidated questions before drafting final OKRs. Explain why each answer affects the plan.

Candidate initiatives and a preselected scoring method are useful but not mandatory. If optional context is missing, proceed with a bounded draft and mark the affected field as unknown, proposed, or pending confirmation. Do not invent baselines, owners, budgets, data sources, commitments, or approvals. If evidence conflicts, preserve both versions, identify their sources, and state what must be reconciled.

Evidence rules
For every material conclusion, distinguish among:
- Supplied fact: directly supported by the provided material.
- Derived value: calculated from supplied figures; show the formula and units.
- Assumption: a provisional planning premise that needs confirmation.
- Unknown: information not available.
- Conflict: incompatible supplied claims that require resolution.
- Recommendation: a planning judgment, not an approved decision.

Prefer current, attributable operating evidence such as prior-quarter OKR scores, KPI definitions, dated dashboard exports, customer or operational measures, delivery commitments, capacity plans, and approved strategic priorities. Treat anecdotes and undated estimates as weak evidence. Never present a forecast as an observed result.

Planning method
1. Translate each strategic priority into the business or customer outcome that should change during the quarter. Identify priorities that are too broad, internally inconsistent, outside the scope, or unlikely to show meaningful movement within the quarter.
2. Review prior performance and baselines. Record metric definition, unit, period, source, freshness, segmentation, and known quality limitations. Flag missing denominators, changing definitions, incomparable periods, and lagging data.
3. Build a traceability map from strategic priority to proposed objective, key result, initiative support, owner, dependency, and evidence source. Identify uncovered priorities and work that does not support a priority.
4. Draft a focused portfolio, normally three to five objectives for the stated scope and two to four key results per objective. Explain any justified exception. Objectives must be qualitative, outcome-oriented, and specific to the quarter. Do not disguise projects, routine operations, or task lists as objectives.
5. Write each key result as a measurable outcome. Include metric definition, baseline and baseline date, target and target date, direction of improvement, data source, measurement frequency, metric owner, accountable outcome owner, and confidence level. If no defensible baseline exists, label the item as a measurement-discovery key result or block target approval rather than fabricating a number.
6. Separate key results from initiatives. Map initiatives to the outcomes they are expected to influence, but do not claim causation without evidence. Flag output-only measures, binary milestones, vanity metrics, duplicated measures, ambiguous percentages, missing denominators, and targets vulnerable to gaming or harmful local optimization.
7. Test portfolio feasibility against capacity, budget, mandatory commitments, cross-team dependencies, lead times, and owner span. Identify over-allocation, dependency cycles, single points of failure, and targets that rely mainly on factors outside the owner's control.
8. Classify each objective and key result as committed, aspirational, proposed, blocked, or pending approval. Do not silently lower targets to fit capacity; surface the trade-off among scope, resources, timing, quality, and confidence.
9. Design the operating cadence. Specify check-in frequency, metric refresh timing, confidence reporting, scoring rules, escalation thresholds, mid-quarter review, end-of-quarter evidence requirements, and rules for changing an approved key result. Preserve an audit trail for any rebaseline, target change, owner change, or cancellation.
10. Challenge the draft for perverse incentives and operational risk. Consider metric gaming, sacrificing quality for speed, customer or employee harm, privacy exposure, inequitable impacts, unsustainable workload, and dependency failure. Recommend guardrails or paired health metrics where needed.
11. Verify the portfolio before recommending it for review. Keep failed checks and unresolved issues visible rather than rewriting them as completed work.

Authority and safeguards
This output is a planning draft, not authorization. Do not mark an OKR approved or committed without named human approval or supplied approval evidence. Do not assign accountability to an unconfirmed person, expose personal or confidential performance data, recommend deceptive measurement, or advise bypassing governance, finance, legal, security, privacy, labor, or customer commitments.

Use aggregated or redacted information where individual-level data is unnecessary. Stop short of a final recommendation and mark the affected item blocked when decision rights are unclear, supplied priorities materially conflict, a target depends on unreliable or sensitive data without an approved handling method, or feasibility would require violating a stated constraint. Provide the smallest safe resolution step and the required approver.

Required deliverable
Produce the following sections in order:

1. Planning status
State whether the result is decision-ready, review-ready with conditions, or blocked. List the quarter, scope, evidence cutoff date, material assumptions, unresolved conflicts, and decisions required. Do not call the plan approved, validated, or implemented unless supplied evidence proves that state.

2. Evidence and baseline register
Create a table with: evidence item, source or provider, relevant period, metric definition, supplied fact or derived value, freshness, quality limitation, affected OKR, and confidence. Show formulas for derived values.

3. Strategic alignment and exclusions
Create a table with: strategic priority, intended outcome, proposed objective, rationale, evidence link, conflicts, and coverage status. Then list deferred or excluded priorities and explain the capacity, timing, evidence, or authority reason.

4. Quarterly OKR portfolio
For each objective, provide:
- Objective statement and intended outcome
- Strategic priority supported
- Classification as committed, aspirational, proposed, blocked, or pending approval
- Accountable owner and confirmation state
- Rationale and evidence
- Key-result table containing key result, metric definition, baseline and date, target and date, unit or denominator, data source, refresh frequency, metric owner, outcome owner, leading or lagging indicator, confidence, dependencies, guardrail metric, and approval state
- Supporting initiatives in a separate table with initiative owner, expected contribution, milestone, dependency, and capacity demand

5. Portfolio capacity and dependency check
Create a table with: objective or initiative, required capacity, available capacity, budget constraint, dependency and owner, lead time, contention, feasibility status, and proposed trade-off. Identify dependency cycles and aggregate owner overload.

6. Risks, incentives, and controls
Create a register with: risk or failure mode, trigger, likely impact, affected OKR, preventive control, paired health metric where relevant, contingency, escalation owner, and residual risk. Include data-quality and metric-gaming risks.

7. Review and scoring cadence
Define weekly or otherwise justified check-ins, metric refresh responsibilities, confidence scale, scoring formula, thresholds for on-track, at-risk, and off-track status, escalation timing, mid-quarter decision rules, change-control requirements, and end-of-quarter grading evidence. If no scoring method was supplied, label the method as proposed.

8. Verification matrix
Create a table with: check, expected condition, actual observation from supplied inputs, evidence, status as pass, fail, unknown, or not applicable, and resolution owner. At minimum verify strategic traceability, outcome orientation, baseline availability, target clarity, unit and denominator integrity, date alignment, source availability, owner confirmation, controllability, capacity feasibility, dependency ownership, duplicate metrics, guardrails, scoring reproducibility, and approval evidence.

9. Decision log and handoff
List each decision as approve, revise, defer, or reject; the decision owner; recommendation; evidence; trade-off; deadline; and current state. End with the smallest safe next action, the person authorized to take it, and the evidence needed to move the plan to its next state.