When you sit down to write your self-evaluation or update your resume, two frameworks come up more than any others: Google's XYZ formula and the STAR method.
People often ask which one they should use. The short answer is that they solve two different length problems:
- The XYZ formula compresses a win into one punchy bullet point (15–30 words).
- The STAR method unpacks a complex win into a short, checkable story (3–5 sentences).
Below is how each formula works, side-by-side examples of the exact same work written both ways, and how to combine them in your next performance review without inventing fake numbers.
Quick comparison: XYZ formula vs. STAR method
| XYZ Formula | STAR Method | |
|---|---|---|
| Structure | Accomplished [X] as measured by [Y], by doing [Z] | Situation, Task, Action, Result |
| Ideal length | 1 sentence (a single bullet point) | 3–5 sentences (a short paragraph or 4 bullets) |
| Best used for | Brag sheets, resumes, weekly updates, and secondary review wins | Top 2–3 flagship review examples, promotion packets, and interviews |
| Main strength | Easy to skim in five seconds | Shows obstacles, trade-offs, and your specific ownership |
Side-by-side examples: the same work in XYZ vs. STAR
Here is how the exact same real-world work looks in both formats across four different roles. Notice how neither version invents a fake percentage.
1. Operations: fixing a slow approval workflow
Written as an XYZ bullet (for a resume or summary list):
Cut vendor invoice approval time from ~6 days to ~2 days (X & Y) by replacing three separate email inboxes with one shared intake sheet and a weekly finance triage (Z).
Written as a STAR story (for a deep-dive self-evaluation question):
- Situation: Vendor invoices needed sign-off from three teams and frequently stalled in scattered email threads ahead of month-end close.
- Task: I took ownership of making approvals predictable before Q3 close.
- Action: I mapped where requests got stuck, built a single shared intake sheet with clear owners and due dates, and ran a 15-minute weekly triage with finance and procurement.
- Result: Finance stopped chasing approvals by email, and average turnaround time dropped from roughly six days to two days.
2. Project / Product Management: navigating a late change
Written as an XYZ bullet:
Shipped the Q3 pricing page relaunch on the original target date (X) with zero post-launch compliance issues (Y) by re-sequencing design reviews and running daily 15-minute check-ins after late legal copy changes (Z).
Written as a STAR story:
- Situation: Two weeks before our planned pricing page relaunch, legal requested copy changes across the comparison table.
- Task: Keep our committed launch date without skipping compliance sign-off.
- Action: I re-sequenced the remaining design work, set up a daily 15-minute check-in for the final two weeks, and had legal review each section as it finished instead of waiting for one final pass.
- Result: We launched on the planned date with full legal approval and no last-minute fire drills.
3. Finance / Accounting: preventing late month-end closes
Written as an XYZ bullet:
Eliminated late month-end closes (X), going from three late closes last year to zero this year (Y), by building a standardized close checklist with cutoff reminders and backup owners (Z).
Written as a STAR story:
- Situation: Last year our team missed the month-end close deadline three times when key reconciliations waited on late departmental handoffs.
- Task: Make our monthly close predictable and remove single-person bottlenecks.
- Action: I built a shared close checklist with explicit cutoff dates for each department, automated our two slowest reconciliation templates, and cross-trained a backup reviewer.
- Result: We completed every month-end close on schedule this year—going from three late closes to zero—even during team PTO.
4. Engineering / Support: stopping a recurring failure
Written as an XYZ bullet:
Eliminated manual reruns of the nightly customer export job (X & Y) by tracing intermittent failures to a timezone filter bug, shipping the fix, and adding a regression test (Z).
Written as a STAR story:
- Situation: Our nightly export job failed two or three times a week, forcing whoever was on call to rerun it by hand in the morning.
- Task: Find the root cause and stop the recurring manual work.
- Action: I audited the failure logs, traced the issue to a timezone boundary bug in the date filter, patched the query, and added an automated regression test.
- Result: The export job has run cleanly every night since the fix with zero manual reruns.
How to use XYZ when you don't have a hard metric for "Y"
A common frustration with "Accomplished X as measured by Y, by doing Z" is feeling stuck when you don't have a revenue or conversion percentage for Y.
In non-sales roles, Y doesn't have to be a percentage. Use a concrete operational change instead:
- Before vs. after time: "...as measured by cutting setup time from three weeks to eight days, by..."
- Before vs. after count: "...reducing stuck contract requests from 40 to 0 in six weeks, by..."
- Adoption proof: "...adopted by all 15 stakeholders as the standard department template, by..."
- Zero-defect proof: "...passing the annual audit with zero findings, by..."
(For more examples like this, see our guide on how to write a self-evaluation without metrics.)
How to combine both in your self-evaluation form
When you fill out your performance review, don't write ten long STAR paragraphs (your manager will get tired of reading) and don't write only one-line bullets (your biggest wins will lack context). Combine them like this:
Top Accomplishments — [Review Period]
Flagship Outcomes (2-3 STAR stories for your biggest projects):
1. [Project / Initiative Name]
- Situation & Task: [1 sentence on the problem and your goal]
- Action: [1-2 sentences on what YOU specifically did]
- Result: [1 sentence on what changed, with real numbers or before/after proof]
2. [Second Flagship Project]
- ...
Additional Wins & Operational Impact (3-5 XYZ bullets):
- [Outcome X] ([proof or before/after Y]) by [specific action Z].
- [Outcome X] ([proof or before/after Y]) by [specific action Z].
- [Outcome X] ([proof or before/after Y]) by [specific action Z].
Generate both from a single rough note
Notice that whether you write an XYZ bullet or a STAR method story, both require the exact same raw memory: what was broken, what you did, and what changed.
If you keep a two-line Friday note in a work brag sheet or send a weekly status update, you already have the raw material for both formats.
Want to test it on one of your own notes right now? Paste a sentence or two into our free STAR method generator (no sign-up)—it gives you both a structured STAR story and a concise one-line bullet using only the facts you wrote.
And if you want to log your week in a minute and have your weekly updates, categorized brag sheet, and STAR stories ready automatically at review time, start free on WinStash.