Convert Vague Goals Into SMART OKRs
Takes a vague goal statement and rewrites it as a SMART OKR with specific, measurable, achievable, relevant, and time-bound elements. Built for PMs inheriting fuzzy goals from leadership.
When to use this prompt
Use this when leadership hands you a vague goal and you need to turn it into something your team can actually work against. You will need the original goal and any implicit context about what leadership was thinking. The prompt explicitly names each SMART element so you can spot which part of the goal is vague and fix it targeted rather than rewriting the whole thing. It is most valuable when leadership is unfamiliar with OKR discipline and writes goals that sound inspirational but cannot be measured. For already-specific goals, prompts 28 or 30 are better fits.
The Prompt
You are a product manager converting a vague goal statement into a SMART OKR. Your job is to name which SMART elements are missing, propose specific replacements, and produce a final OKR. Vague goal: {{vague_goal}} Implied context: {{context}} Who issued this goal: {{issuer}} Business outcome the issuer likely wants: {{implied_outcome}} Step 1: SMART AUDIT â For each SMART element, mark the original goal PASS or FAIL with a 1-line reason. - SPECIFIC: Does the goal name a clear subject and action? - MEASURABLE: Can you identify a metric to track progress? - ACHIEVABLE: Is there a realistic path given team capacity? - RELEVANT: Does the goal align with a business outcome? - TIME-BOUND: Is there a deadline? Step 2: PROPOSED REPLACEMENTS â For each failed element, propose a specific fix. For example, if the original goal was "improve customer experience," the specific fix might be "reduce support ticket resolution time for billing admins." Step 3: CANDIDATE OKR â Produce a full OKR based on the fixes: - Objective (qualitative, 1 sentence, memorable) - KR 1 (numeric, with baseline, target, deadline, owner) - KR 2 (numeric, with baseline, target, deadline, owner) - KR 3 (numeric, with baseline, target, deadline, owner) Step 4: VALIDATION â Read the candidate OKR and test it against the original vague goal. Does it actually deliver what the issuer wanted? If not, adjust. Step 5: CLARIFYING QUESTIONS â If the original goal is too vague to convert without assumptions, list the 1-3 specific questions you would ask the issuer before proceeding. Do not guess on questions you should ask. Be direct. A vague goal converted badly is worse than a vague goal flagged for clarification.
Example Output
Vague goal: "Improve the customer experience for billing." SMART AUDIT - Specific: FAIL (customer experience is vague; billing is only slightly less vague). - Measurable: FAIL (no metric). - Achievable: CANNOT DETERMINE (no scope to test against capacity). - Relevant: PASS (billing is clearly in the product area). - Time-bound: FAIL (no deadline). PROPOSED REPLACEMENTS - Specific: Narrow to billing admins specifically and the overdue workflow they struggle with. - Measurable: Use days-to-collection and NPS as the two clearest metrics. - Time-bound: End of Q2. CANDIDATE OKR Objective: Make billing admins love the invoices dashboard by end of Q2. - KR 1: Reduce median days-to-collection from 18 to 12 by end of Q2. Owner: Priya. - KR 2: Increase billing admin NPS from 32 to 50 by end of Q2. Owner: Marco. - KR 3: Cut spreadsheet-export events by billing admins from 1200/week to 400/week by end of Q2. Owner: Dan. VALIDATION: This OKR delivers a measurable improvement in billing admin experience, which matches the likely intent of "improve customer experience for billing." CLARIFYING QUESTIONS - Did leadership mean all billing users or specifically mid-market billing admins? - Is there a specific customer complaint that triggered this goal? - Is this a Q2-only goal or ongoing?
Recommended Tools
Notion projects and Coda both work well for iterating on SMART rewrites with comments from the original issuer. Google Workspace (Docs) is the right choice if the original goal arrived in a leadership memo and needs to be clarified in the same document. Use whichever tool the issuer prefers; the goal is fast clarification, not tool-switching overhead.
Frequently Asked Questions
When should I use this prompt?
Use it whenever leadership hands you a vague goal you are expected to execute against. The SMART rubric gives you legitimate language to push back on vague asks without sounding defensive. Do not use it for goals that are already specific; running the audit on well-written goals wastes time. Also do not use it for exploratory research goals where vagueness is intentional; 'understand the billing user' is a legitimate discovery goal that cannot be SMART-ified without destroying its purpose.
What if the issuer rejects the SMART version?
That usually means one of three things. First, your interpretation of the vague goal was wrong; ask the clarifying questions from Step 5 and re-run. Second, the issuer wants to keep the goal vague so they can claim credit for any outcome later; push back diplomatically but firmly, because committing to a vague goal means you cannot be held accountable either, which is usually worse for you. Third, the issuer values the aspirational framing and treats the SMART version as a destruction of ambition; offer to keep the aspiration as the objective and the SMART version as the key results underneath it.