Andrea prescribes XYZ attribution bullets

Promotion docs are a writing problem pretending to be a performance problem. That’s the point Andrea Barghigiani is making. The work may be real. The impact may be real. But if your bullet reads like “improved search feature,” the people deciding your level can’t see what was hard, what was yours, or why it mattered. Her fix is simple — use XYZ bullets that force all three onto the page. (careercraft.ing)ce: accomplished X as measured by Y by doing Z. Barghigiani points to the version Google popularized internally, then applies it to engineering promotion docs and brag documents. The structure is doing more than making bullets prettier. It makes you name the outcome, quantify it, and explain the mechanism. That last part matters because a naked metric can still leave room for someone to shrug and think the fix was obvious. (careercraft.ing) ### Why do vague bullets fail? Because they describe activity, not leverage. “Improved search feature” tells a teammate something happened. It tells a calibration panel almost nothing. Panels are usually reading quickly, outside your project context, and with limited patience for reconstructing your contribution from scraps. If the bullet doesn’t say what changed, how much, and what you specifically did, the reader fills in the blanks — and those blanks usually get filled with doubt. (careercraft.ing) ### What kind of doubt? Barghigiani’s phrase is basically promotion pathology. One version is “the work was too easy.” Another is “the whole team contributed.” Another is “what has she done lately?” None of those attacks necessarily mean the work was weak. They mean the write-up failed to defend it. A clean solution often looks trivial after the fact. Team wins often erase the person who found the bottleneck, drove the decision, or stitched the rollout together. (careercraft.ing) ### So what changes in the bullet? The bullet starts naming the hidden labor. One of her examples turns “Reduced API response time 40% by implementing Redis caching” into a stronger version that says the engineer identified cache invalidation bottlenecks through distributed tracing and prevented a $200K infrastructure scaling decision. Same project, but now the reader can see diagnosis, judgment, and business consequence — not just tool usage. That’(careercraft.ing) problem other people missed.” (careercraft.ing) ### Why does the “how” matter so much? Because attribution fights are really causality fights. If you only show the result, reviewers can credit circumstance, team momentum, or low-hanging fruit. If you show the path — found the drop-off, traced the bottleneck, led the implementation, mentored juniors, prevented the bad spend — you make your contribution legible. Basically, you are leaving a receipt for your judgment. (careercraft.ing) No — Barghigiani is aiming it at internal promotion packets too. She argues engineers already write clearly for peers in PRs and docs, but management needs a different translation layer. The audience isn’t asking whether the code was elegant. The audience is asking whether the person operated at the next level. XYZ bullets help because they package technical work in business language without flattening the technical substance. (careercraft.ing) ### Why is this landing now? Because more companies are formalizing calibration and expecting evidence that survives secondhand review. Barghigiani even says teams at places like Dropbox, GitLab, and high-growth startups now expect this style in reviews and resumes. Whether or not every company names it “XYZ,” the underlying demand is the same — quantified impact plus visible ownership. (careercraft.ing), then rewrite them before review season. Don’t just store outputs. Store the mess — the ambiguity, the dead ends, the bottleneck you found, the tradeoff you made, the cost you avoided. That’s the material reviewers need in order to see seniority. A polished launch is good. A polished launch with the hidden difficulty exposed is what gets defended in the room. (careercraft.ing)ghigiani isn’t really prescribing a bullet template. She’s prescribing a way to preempt attribution doubt. The metric gets attention. The action gets credit. The combination is what keeps your work from turning anonymous the moment it leaves your team.