50 Performance Review Phrases for Business Intelligence Analysts

Self Assessment Phrases - Achievements

• I built a dashboard for [team] that gave stakeholders clearer visibility into performance without needing manual reports.
• I worked with stakeholders to define the metrics that actually mattered for their decisions, rather than defaulting to what was easy to pull.
• I cleaned and restructured a messy dataset that made downstream analysis significantly more reliable.
• I identified a discrepancy in reported figures and traced it back to an issue in how data was being aggregated.
• I automated a recurring report that had previously been compiled manually each week.
• I presented findings to stakeholders in a way that made the implications clear, not just the numbers.
• I documented data definitions and business logic so dashboards were interpreted consistently across teams.
• I collaborated with data engineers to improve the underlying pipelines feeding my reports.
• I trained stakeholders on how to use self-service dashboards, which reduced ad hoc reporting requests.
• I flagged a trend in the data early enough for the business to adjust its approach before it became a bigger issue.

Self Assessment Phrases - Growth and Development

• I want to get better at understanding the business context behind a request before building the report.
• I sometimes build dashboards that are technically correct but not as intuitive as they could be for the end user.
• I need to push back more when a stakeholder asks for a metric that won't actually answer their underlying question.
• I want to improve how I validate data before presenting it, rather than assuming the source is correct.
• I could do more to follow up after delivering a report to see whether it's actually being used.
• I want to develop stronger skills in a wider range of visualisation techniques rather than defaulting to familiar chart types.
• I need to work on documenting my analysis process so others can reproduce or extend it.
• I want to get more comfortable challenging a stakeholder's assumptions when the data suggests something different.
• I could improve how I prioritise competing reporting requests when everything is marked urgent.
• I want to build stronger habits around checking dashboards for accuracy after underlying data changes.

Peer Review Phrases

• They ask good questions before building a report, which saves time later when requirements would otherwise shift.
• They catch data inconsistencies that others miss, and they trace them back to the actual source.
• They build dashboards that are genuinely easy for non-technical stakeholders to use.
• They document their analysis clearly enough that someone else could pick it up and understand the logic.
• They present findings in a way that focuses on what the business should do, not just what the numbers show.
• They are responsive when stakeholders need something urgently, without cutting corners on accuracy.
• They collaborate well with data engineering to flag issues with underlying pipelines.
• They push back constructively when a requested metric wouldn't actually answer the real question.
• They stay organised across multiple reporting requests without letting details slip.
• They are generous about helping other analysts get unstuck on a tricky data problem.

Manager Review Phrases - Strengths

• You ask the right questions before building a report, which means fewer surprises when requirements shift later.
• You catch data quality issues that others miss and trace them back to the source.
• You build dashboards that stakeholders can genuinely use on their own, which reduces the volume of ad hoc requests.
• You handled [project] well, balancing a tight deadline with the need for accurate data.
• You present findings clearly, focusing on what the business should do rather than just listing numbers.
• You are responsive to urgent requests without compromising on the accuracy of your work.
• You collaborate effectively with data engineering to flag issues with the pipelines feeding your reports.
• You push back constructively when a stakeholder's request wouldn't actually answer their real question.
• You document your analysis clearly, which makes your work easy for others to pick up.
• You stay organised across multiple competing reporting requests without letting details slip.

Manager Review Phrases - Areas to Develop

• Try to dig into the business context behind a request before starting to build the report.
• Work on making dashboards more intuitive for non-technical stakeholders, not just technically accurate.
• Push back sooner when a requested metric won't actually answer the underlying question.
• Build in a validation step for data before presenting it, rather than assuming the source is correct.
• Follow up after delivering a report to see whether it's actually being used as intended.
• Broaden your range of visualisation approaches rather than defaulting to the same chart types.
• Document your analysis process more thoroughly so others can reproduce or extend your work.
• Get more comfortable challenging a stakeholder's assumptions when the data points somewhere different.
• Work on prioritising competing requests more clearly when several are marked urgent at once.
• Check dashboards for accuracy more consistently after underlying data or logic changes.

How to use these phrases

Don't paste these in verbatim. Pick the two or three closest to what you actually did, then make them specific: swap the generic claim for your own project, metric, or outcome. Use the rest as a checklist of themes worth covering in a Business Intelligence Analyst review, and see the Perform Review blog for guides on structuring the full review.

Phrases for related roles

• Data Analyst performance review phrases
• Data Engineer performance review phrases
• AI Engineer performance review phrases
• Machine Learning Engineer performance review phrases
• Data Scientist performance review phrases