Most career advice will tell you that your resume will get great through action verbs:
Lead. Manage. Spearhead. Optimize.
And yes, strong verbs matter. But after 15 years of writing resumes and helping more than 10,000 job seekers tell their professional stories, the three words I consider most important are some you've likely never considered.
These three words, or some variation of them, appear in every single resume I write. They’re the key to transforming a flat list of tasks into a compelling narrative about who you are as a professional and what you're capable of contributing. Let me show you what I mean.
I've literally read thousands of resumes (no pun intended). Within the first few seconds, I can usually tell what's wrong. It's not a lack of action verbs, or formatting, or font size. It's that the bullets sound like a job description instead of a story. Check this one out:
Managed a team of social workers providing case management.
It's not wrong, but it doesn't tell me much. Who were the clients? How big was the team? What was the organization trying to accomplish? What changed because of your work?
Now look what happens when we apply "on behalf of" thinking:
Managed team of 12 social workers on behalf of federally funded workforce development program serving 800 participants annually, increasing placement rates by 34% during tenure.
Two bullets about the same person doing the same job, but they tell a totally different story. The second version doesn't just tell me what they did. It tells me the scale they operated at, the mission they were part of, and the transformation they helped create.
When I sit down with a client - or when our AI platform walks a job seeker through the resume building process - the first question isn’t "what did you do?" Instead, the process starts with deeper questions, each connecting back to our three magic words.
1. Tell me about the setting you were working in.
Before we talk about your responsibilities, I want to know about the organization you were part of. How large was it? What was its annual budget? How many people did it serve? What population or market was it focused on?
These details matter because they immediately communicate your professional context. There's a difference between managing a program at a 10-person nonprofit and managing a program at a city agency with a $50 million budget. Both are valuable. But a hiring manager needs to understand the environment you were operating in to appreciate what you brought to it, and how it relates to their world.
Think of it this way: "on behalf of" lets you borrow the impressiveness of your organization and attach it to your own story.
2. What problem were you addressing?
Every job in the world exists because something needed to happen. A gap needed to be closed. A population needed to be served. A system needed to be built or fixed or scaled. As you describe this problem, you’re giving your work meaning and stakes.
Instead, most resumes describe activities without ever explaining why those activities mattered. "Developed training curriculum" is an activity. "Developed training curriculum to address 40% turnover rate among frontline staff" implies that the person fixed a real organizational challenge.
3. What collaborative impact did you help achieve?
Notice I said "help achieve.” You don't have to claim sole credit for an outcome to include it on your resume. In fact, the most credible accomplishments acknowledge that results happen through collective effort.
"On behalf of" gives you permission to claim association with outcomes that were bigger than you. If you were part of a team that doubled revenue, you can say that. If you contributed to a department-wide initiative that reduced patient wait times, you can say that too. The key is to frame it honestly: you helped make it happen. You can absolutely share what your specific contribution looked like within that larger effort.
Some people take to this shift right away. They hear 'on behalf of' and immediately start connecting the dots between their work and the bigger picture. But others push back. Sometimes it's because they've been conditioned to stay small, to not take credit, to describe their work in the most modest terms possible. Or they've internalized the idea that their work wasn't significant enough to attach to a bigger outcome. I see this especially with people who have spent years in direct service roles, where the work is enormous but the recognition is minimal. 'On behalf of' isn't about inflating what you did. It's about telling the truth about the environment you did it in and the impact it contributed to. What I find interesting is that the people who resist this framework tend to be the ones who need it the most.
One of the things I love about this framework is that it scales. It works whether you're writing a resume for an entry-level case manager or a C-suite executive.
For someone early in their career, "on behalf of" might sound like: "Provided intake and enrollment support on behalf of a community health center serving 5,000 low-income families across three boroughs."
For a director, it might sound like: "Oversaw a $2.4 million grant portfolio on behalf of a national workforce development organization, supporting 15 regional partners in meeting Department of Labor performance benchmarks."
When I built RS Works, I didn't just want to help people format their resumes. I wanted to change the way they think about communicating their experience. We trained our AI platform to ask the same questions I ask in a one-on-one coaching session. Instead of prompting users to list their duties, it asks them to describe the organization they worked for, the challenges they were addressing, and the results they contributed to.
It's "on behalf of" thinking, built into every step of the process. We've seen it transform the way job seekers talk about themselves, not just on paper but in interviews, networking conversations, and beyond.
The next time you sit down to update your resume, try this exercise: Pick one role, your current one or your most recent, and before you write a single bullet point, answer these questions:
What organization was I working on behalf of?
Is the organization similar to the types of orgs I want to work with, in terms of size, mission, customer base?
What problem or challenge was I, my team, or department trying to address?
What measurable or meaningful change did I contribute to as part of that effort?
Remember, you weren't just doing a job. You were doing it somewhere, for someone, and something changed because of it. Don’t be too humble to put that on the page.
Liked this post?
Share via LinkedIn | Share via Email