The Action-Skill-Result Bullet: A Cleaner Formula Than STAR

"Responsible for managing team tasks and delivering projects on time."

That line is on roughly half the resumes in any applicant pool. It says nothing about what you actually did, what skills you used, or what changed because you were there. A hiring manager skimming at 7 seconds per resume will skip it entirely. An ATS will parse it fine -- it's clean text -- but no metric, no keyword context, and no result means no differentiation.

The problem isn't that people can't write. It's that the most commonly taught resume framework, STAR, was designed for interview prep, not bullets.

STAR Was Built for Conversations, Not Bullets

STAR (Situation, Task, Action, Result) was created by the UK National Careers Service and adopted broadly by career coaches as a way to structure verbal answers in behavioral interviews. In a spoken answer, you need setup: the interviewer has no context, so the Situation and Task orient them before you get to what you actually did.

On a resume, your section headers already supply most of that context. "Software Engineer at Acme Corp, 2023-2025" tells the reader the situation. They don't need you to restate it in each bullet. So STAR on paper becomes redundant -- you're writing four clauses to communicate what two can handle.

Resume coaches themselves will say it outright: STAR is "a bit much for a resume" and works better for spoken interview answers. The framework that survives compression is the one that starts with the verb and ends with the number.

The Three Formulas, Explained

1. Action-Skill-Result (ASR)

University career centers at Yale, Wellesley, and UTSA all teach a variation of this -- also called CAR (Context-Action-Result) or PAR (Problem-Action-Result). The structure:

[Strong verb] + [what you did / which skills] + [concrete outcome]

Fill-in-the-blank: [Verb]ed [X] using [skill/method/tool], [result with number].

2. XYZ (Accomplished X as measured by Y by doing Z)

Popularized by former Google SVP Laszlo Bock, this formula forces you to lead with the metric and then explain how you got there. Google recruiters explicitly endorse it because it front-loads the result -- the most important piece of information -- before the reader's attention drops.

[Outcome + metric] + by doing [action + skill]

Fill-in-the-blank: [Verb]ed [metric] by [method/tool/approach] for [scope].

3. STAR (Situation-Task-Action-Result)

Keep STAR as a drafting tool, not a writing template. Write out the full four-part story when planning a bullet. Then cut the Situation and Task, because your job title and dates already imply them. What remains is an ASR or XYZ bullet.

The practical workflow:

1. Draft with STAR to make sure you haven't forgotten context or the result
2. Compress to ASR or XYZ for the actual line
3. Add a number -- percentage, count, timeframe, revenue figure, anything concrete

Yale's career office puts it directly: a concise, results-focused structure usually works better than fully writing out STAR, which is better kept as a planning framework.

A Note on ATS

Before anyone argues that one formula ranks better in applicant tracking systems: ATS doesn't detect or score bullet formulas. It treats each bullet as a text line and scans for keywords. It does not know if you used STAR, XYZ, or a haiku. What matters for ATS is that you use plain text bullets (hyphens or bullet characters, no icons, no nested indentation) and include the right keywords from the job description. This is a human readability question, not a machine ranking question.

Before and After

The same experience, written three ways:

	School Counsellor	SaaS / Product Role
Weak	Responsible for counselling students about academic and personal issues.	Managed a web app for resume building.
ASR	Counselled 120+ secondary students using solution-focused brief therapy techniques, reducing repeat crisis visits by 35% within one term.	Built and iterated a resume-builder SaaS using Next.js and Supabase, increasing trial-to-paid conversion from 8% to 18% over six months.
XYZ	Reduced repeat student crisis visits by 35% by implementing solution-focused brief therapy and structured follow-up plans for 120+ secondary students.	Increased trial-to-paid conversion from 8% to 18% by running A/B tests on pricing, onboarding flow, and resume templates in a Next.js/Supabase resume-builder SaaS.

Notice what happens in each case. The weak version describes a job. The ASR version describes a person doing a job well. The XYZ version leads with proof that the person succeeded.

Neither ASR nor XYZ is strictly "better." ASR reads more naturally as a sentence. XYZ is more aggressive about putting the metric first, which is useful when the metric is impressive and you want it in the first three words. Use whichever fits the bullet.

The Workflow, Step by Step

1. Write STAR in a scratch doc. Situation: what was the context? Task: what were you supposed to do? Action: what did you actually do, and which skills or tools did it involve? Result: what changed, measured how?
2. Drop Situation and Task. Your job title and company cover that.
3. Choose ASR or XYZ. If the result is the best part, use XYZ. If the action is more interesting (novel method, rare skill), use ASR.
4. Add a number. Percentage, count, timeframe, dollar amount. If you don't have an exact figure, use a range or an approximation you can defend.
5. Check the opening verb. Avoid "Responsible for," "Helped," "Worked on." Use specific action verbs: Counselled, Reduced, Built, Increased, Designed, Negotiated, Deployed.

The Tailoring Problem

Here's where most people stop short. You can write a perfect ASR bullet, and it still undersells you on a specific job, because the skill emphasis is wrong.

A counsellor bullet that foregrounds "solution-focused brief therapy" lands differently on a clinical role than it does on a school wellness coordinator role. The action and the metric stay the same. The skill you emphasize in the middle changes based on which keyword the job description uses.

Doing that across 20-30 applications manually is where the formula breaks down in practice -- not because it's a bad formula, but because rewriting the skill layer for each role is tedious enough that most people skip it. That's the step where BulkResumes does the heavy lifting: the structure of your bullets stays yours, but the skill emphasis in each line gets matched to the specific job description you're applying to.

The formula is the foundation. Tailoring it per role is what gets you past the first filter.