Business analysts and data analysts run into a familiar problem during performance reviews. If you write "Built 12 dashboards and answered 100 ad-hoc data requests," you sound like a ticket queue. If you claim "Increased company revenue by 20%," it feels dishonest because product, sales, or operations actually executed the change.
The strongest analyst self-evaluations focus on the bridge between data and action: the messy requirement you clarified, the blind spot you uncovered in the numbers, the manual spreadsheet you automated, or the bad data you caught before leadership made a wrong call.
Below are before-and-after rewrites, copy-and-paste examples across five core analyst areas, and a fill-in template. Replace every detail with your own work and only use numbers you can back up.
Before and after: from ticket taker to decision partner
| Weak (lists outputs only) | Strong (shows decision, reliability, or time saved) |
|---|---|
| Built several dashboards for the sales and ops teams. | Built one shared pipeline dashboard for sales and ops that replaced three conflicting weekly spreadsheets and became the source for Monday forecast calls. |
| Wrote requirements docs for the ERP project. | Mapped the current invoice workflow across finance and procurement and wrote the business requirements for the ERP handoff, catching two missing approval states before development started. |
| Answered a lot of ad-hoc data questions. | Noticed the same three cohort questions coming up every week, built a self-serve filter view, and walked the team through it so they no longer needed manual SQL pulls. |
| Fixed data bugs in the reporting tables. | Traced a discrepancy in monthly churn numbers to duplicate refund records, fixed the logic with data engineering, and documented the definition so finance and product numbers matched. |
Self-evaluation examples by category
1. Insights and decisions influenced
- "Investigated why trial-to-paid conversion dropped in Q2, found that most drop-offs happened at the team-invite step, and shared the breakdown with product—which led to simplifying the setup flow in Q3."
- "Analyzed support ticket volume by feature area ahead of H2 planning, giving product and engineering the evidence to prioritize export reliability over two lower-impact requests."
- "Built a cost-per-vendor breakdown with procurement that identified four overlapping software contracts prior to Q4 renewals."
2. Business requirements and process mapping (BA focus)
- "Interviewed six stakeholders across finance, legal, and sales ops to document the end-to-end contract approval workflow, turning conflicting requests into one signed-off requirements spec."
- "Wrote clear acceptance criteria and edge-case scenarios for the billing migration, which helped QA and engineering catch a proration issue in staging before launch."
- "Facilitated the trade-off review when engineering flagged a timeline constraint on the reporting portal, helping stakeholders agree on a phased release without slipping the go-live date."
3. Reporting automation and self-serve enablement
- "Replaced a manual Monday morning Excel export with an automated scheduled report, saving roughly two hours of manual copy-pasting each week and eliminating formula errors."
- "Created a 'metrics dictionary' page defining our 15 most-used KPIs (active accounts, net retention, resolution time) so marketing, finance, and leadership stopped bringing different numbers to quarterly reviews."
- "Ran two 30-minute office-hour sessions to teach Customer Success leads how to filter the account health dashboard themselves, reducing routine data requests in our queue."
4. Data quality and reliability
- "Caught an upstream tracking gap after the checkout update that was undercounting mobile sign-ups, alerted engineering the same day, and backfilled the missing week of reporting."
- "Added sanity checks to our monthly close queries so row-count drops or null spikes are flagged before leadership receives the monthly deck."
- "Audited our legacy Looker/Tableau folders and archived 20+ outdated dashboards so stakeholders stopped pulling numbers from deprecated tables."
5. Areas for improvement (honest examples for analysts)
- "In the first half of the year, I sometimes delivered raw tables in response to stakeholder questions without stating what I thought the numbers meant. Since Q3, I've started every analysis readout with a three-bullet 'so what' summary and a recommended next step."
- "I said yes to too many quick Slack data pulls earlier in the year, which interrupted deeper project work. I now ask requesters what decision the number is for and route non-urgent pulls through our intake form."
(Need more options for the growth box? See our full guide on areas for improvement examples for self-evaluations.)
Fill-in template for Business & Data Analysts
Role: [Business Analyst / Data Analyst]
Review period: [Start] to [End]
1. Decisions & insights:
- Investigated [question or problem], found [key insight], which led [team/stakeholder] to [decision or action taken].
2. Requirements & process clarity:
- Mapped [workflow or system] across [teams], clarified [edge case or conflict], and delivered [spec / rollout] on schedule.
3. Automation & self-serve:
- Replaced [manual report / recurring ad-hoc request] with [automated dashboard / workflow], saving [time or manual steps] for [who].
4. Data quality & reliability:
- Identified and fixed [discrepancy, tracking gap, or broken definition] in [dataset/report] before it affected [review/close/launch].
5. Goals for next period:
- [1-3 concrete goals—see our performance review goals guide]
Don't let ad-hoc wins vanish into Slack history
Analysts have a unique memory problem at review time: your biggest project sits in Jira, but much of your actual value happened in Slack threads, quick SQL checks, requirement clarifications, and fires you prevented before a meeting. By November, those threads are impossible to dig up.
The fix takes two minutes on a Friday: jot down the question you answered, the discrepancy you caught, or the requirement you unblocked in a running brag sheet or a weekly status update.
Looking for adjacent role examples? Check our guides for Operations, Product Managers, and Project Managers, or read how to write a self-evaluation without flashy revenue metrics.
To turn a rough note about an analysis or project into a clean story right now, try the free STAR method generator. To log your weekly wins in a minute and generate your brag sheet and STAR stories at review time—with nothing made up—start free on WinStash.