What should business analyst resume bullets prove?

Business analyst resume bullets should prove that a change happened because of your analysis. Each line traces part of one path: the problem you studied, the people you asked, the option you recommended and whether it worked after launch. A list of meetings and documents shows activity. A finished path shows results.

The International Institute of Business Analysis defines the work in its page on what business analysis is. IIBA calls it "the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders." That definition is a useful test for a bullet. Does the line name a need, a solution or the value delivered?

The Bureau of Labor Statistics has no profile for the title business analyst. The nearest is management analysts, and BLS sums up that job in one line: "Management analysts recommend ways to improve an organization's efficiency."

Which O*NET profile matches your business analyst job?

Business analyst appears as a reported job title in two O*NET profiles, and the right one depends on your work. Process and requirements analysts match management analysts. Analysts who build reports and dashboards match business intelligence analysts. Pick the profile closest to your last two jobs and write bullets from its tasks.

The O*NET profile for management analysts (13-1111.00) lists Business Analyst among its reported titles. Its tasks start with fieldwork: "Interview personnel and conduct on-site observation to ascertain unit functions, work performed, and methods, equipment, and personnel used." The O*NET profile for business intelligence analysts (15-2051.01) lists Business Analyst too. Its first task is to "Generate standard or custom reports summarizing business, financial, or economic data for review by executives, managers, clients, and other stakeholders."

Many jobs mix both. In that case, lead with the side the posting asks for. Put the other side lower in the same job.

Which business analyst duties turn into strong bullets?

Business analyst duties turn into strong bullets when the line reaches past the document to its effect. The table takes six O*NET tasks from the two profiles. Each gets a weak bullet, a fixed bullet and the facts you replace. All fixed bullets are made-up examples with brackets for your own numbers.

O*NET taskWeak bulletFixed bullet (made up)Facts you swap in
Interview personnel and conduct on-site observationGathered requirements.Interviewed [N] staff in [N] teams and observed [process] for [N] days, producing [N] requirements signed off by [sponsor].Interview count, teams, sign-off
Analyze data gathered and develop solutionsAnalyzed data.Analyzed [N] months of [order] data and proposed [fix], cutting cycle time from [X] to [Y] days.Data period, the fix, before and after
Document findings and prepare recommendationsWrote reports.Wrote the recommendation for [new system], approved by [steering group] with a $[X] budget.Who approved, budget
Confer with personnel on newly implemented systemsSupported go-live.Held [N] check-ins with [team] after [system] went live, closing [N] of [N] reported issues in [N] weeks.Issues found and closed, weeks
Prepare manuals and train workersTrained users.Wrote the [system] guide and trained [N] staff in [N] sessions; tickets about [form] fell from [X] to [Y] a month.Staff trained, ticket change
Generate reports for executives (BI)Made dashboards.Built a weekly [metric] dashboard for [N] managers, replacing [N] manual spreadsheets.Audience, what it replaced

What do example business analyst bullets look like?

Example business analyst bullets below are grouped by the stage of a project they prove. Every line is made up. Replace each bracket with a fact you can source from your own project records. If you only contributed to a stage, say what your part was, and cut the line if you had none.

Discovery and requirements

  • Ran [N] workshops with [team] to map the [process] as it runs today, finding [N] manual hand-offs.
  • Turned [N] stakeholder interviews into [N] user stories with acceptance criteria, approved before build began.

Analysis and recommendation

  • Compared [N] options for [problem] on cost and effort; the chosen option saved $[X] a year over the next best.
  • Reviewed [N] forms with their users and removed [N] unused fields, cutting completion time by [X] minutes.

Rollout and adoption

  • Wrote [N] test scenarios and ran acceptance testing with [N] users before the [system] launch.
  • Tracked use of the new [procedure] for [N] weeks and reported adoption by [X] of [Y] teams to [sponsor].

Reporting and BI

  • Documented specs for [N] reports with [team], cutting rework requests from [X] to [Y] per release.
  • Combined [industry] trend data into a [N]-page brief that supported the decision to [action].

The review line comes from an O*NET task: "Review forms and reports and confer with management and users about format, distribution, and purpose, identifying problems and improvements." BLS lists the follow-through step as well: "Confer with managers to ensure changes are working". Rollout bullets are where most analysts stop too early.

What should a business analyst cut from resume bullets?

Business analyst resumes often spend their best lines on artifacts. A requirements document, a process map or a status report matters only for what it changed. Cut or rewrite these lines first, since a hiring manager can assume every analyst produced them.

  • "Liaised between business and IT" with no project named.
  • Counts of documents, meetings or tickets with no outcome attached.
  • Method names alone, such as [modelling technique], without the problem they solved.
  • Results the whole programme owned, unless you can say which part was yours.

How do you check a business analyst bullet before you send it?

A business analyst bullet passes when your project sponsor would agree with it. Read each line and ask three questions. Could you name the source of the number, and would the sponsor describe your part the same way? Does the line match a requirement in the posting?

IIBA notes that business analysis covers many titles. Its list includes business systems analyst, process analyst and product owner. If your title was one of those, keep the real title. Let the bullets show the analysis.

The resume bullet points guide covers the base formula, and the XYZ resume formula helps when a result needs a baseline. The free resume optimizer rewrites the lines that matter for a posting and keeps your facts. For the interview that follows, see business analyst interview questions.

Sibling pages cover bullets for a product manager, whose work overlaps on requirements, a financial analyst, a marketing manager and a sales representative.