Scroll any PM resume and you'll find it: "supported cross-functional initiatives," "supported senior leadership," "supported delivery." The word sounds like involvement — it doesn't prove it. Here are 15 verbs that do.

15 stronger ways to say 'supported' on a resume

Synonym What it signals Resume bullet
Enabled Cleared the path so execution could happen Enabled on-time Q3 launch by resolving 3 vendor dependencies 2 weeks before ship date
Facilitated Guided a process toward its outcome Facilitated weekly cross-functional standups across 5 teams, cutting blocker resolution time by 40%
Championed Advocated publicly with stake in the outcome Championed JIRA adoption across 4 departments, reducing sprint-planning prep by 6 hours/week
Reinforced Strengthened existing structures or standards Reinforced SDLC documentation across 2 engineering pods, improving onboarding ramp time by 30%
Bolstered Added capacity that moved the needle Bolstered vendor negotiations by surfacing 18 months of delivery data, locking in a 12% SLA improvement
Backed Committed resources or decisions to an outcome Backed $240K reallocation toward highest-ROI sprints, cutting project overhead by 18%
Underpinned Served as the structural foundation Underpinned a $1.2M product launch by owning the risk register and escalation protocols for a 7-week sprint
Advanced Pushed something meaningfully forward Advanced OKR adoption across 3 business units, raising quarterly goal-completion rate from 54% to 79%
Accelerated Shortened timelines through deliberate action Accelerated release cadence from 6-week to 3-week sprints by rolling out async standup tooling for a 22-person team
Empowered Gave others what they needed to act Empowered junior PMs to own sprint ceremonies for 4 squads, freeing 8 hours/week for strategic roadmap planning
Elevated Raised quality or performance Elevated retrospective quality across 6 consecutive sprints by introducing structured outcome tracking; velocity improved 23%
Sustained Kept something alive under pressure Sustained 98% on-time delivery rate across 14 sprints despite 2 mid-cycle headcount reductions
Coordinated Aligned people and resources toward a shared goal Coordinated 11-stakeholder review cycle for $3.4M infrastructure migration, delivering on schedule
Anchored Held moving parts together under ambiguity Anchored 9-month roadmap for 4 product lines, maintaining scope integrity through 2 executive priority shifts
Drove Created forward motion with clear ownership Drove dependency-mapping process that surfaced 6 critical blockers 3 sprints before impact

Three rewrites

Before: Supported senior stakeholders during quarterly planning. After: Anchored quarterly OKR review for 8 executives, synthesizing 14 product roadmaps into a single 6-page exec brief. "Supported" is attendee language. "Anchored" owns the session.

Before: Supported the engineering team on a product migration. After: Coordinated 3-team, 11-week platform migration from Jira Server to Jira Cloud, achieving zero-downtime cutover for a 26-person eng org. The swap names the scope and commits to an outcome a recruiter can actually evaluate.

Before: Supported risk management process for new feature launches. After: Drove risk-register process across 4 concurrent launches, surfacing 9 blockers and resolving 7 before code freeze. "Drove" signals you owned the process. The numbers prove it worked.

Once your bullets are tight, make sure your email when sending a resume carries the same direct tone — vague verbs in the email body undercut sharp bullets in the attachment.

When 'supported' is genuinely the right word

You were explicitly a support function — loaned to a project without delivery ownership, serving as a PM advisor to another team's decision-maker, or backfilling a gap rather than leading a workstream.

The role title itself uses "support" — if the JD says "Support PM" or "Program Support Specialist," mirroring that language helps ATS matching and keeps your resume honest.

You're contextualizing a team win before claiming your slice — "Supported delivery of a $6M infrastructure overhaul; personally owned the vendor-onboarding workstream for 3 partner integrations" is fine because the second clause does the real work.

The long-tail verb problem

Rare verbs like "orchestrated," "catalyzed," and "synthesized" read as aspirational when the outcome underneath is ordinary. A PM bullet that says "orchestrated cross-functional alignment" but lists no stakeholder count, no conflict resolved, no deadline cleared — the fancy verb makes it worse, not better. Recruiters flag the mismatch. The rule is proportionality: your verb tier should match your outcome tier. "Organized" on a 40-person sprint review is underselling. "Orchestrated" on a 4-person standup is reaching. Project managers are especially prone to this because PM vocabulary is already abstract — the temptation is to elevate the verb where a number should go. Fill it with the number instead. A plain verb and a sharp number outperforms a rare verb every time.

40 free swipes a day. Sorce applies, you swipe.

For more: reduced synonym, solved synonym, trained synonym, accomplished synonym, anticipated synonym