Excel expert or data analyst: which do you need?

The useful question is not whether the person can use Excel. The tool is common to both roles. The question is what the business needs to change: a fragile monthly report, a slow manual process, a model that nobody trusts, or a decision that needs better evidence.

Write the problem in one sentence and describe the output. A rebuilt forecasting template, a governed reporting model, and an analysis of customer churn are three different briefs, even if all three end up in a spreadsheet.

An Excel expert works inside the workbook. That includes structuring inputs and calculations, writing and auditing formulas, building pivot tables and dashboards, using Power Query, and designing templates that other people can use without breaking them.

The output is usually a better file: faster, clearer, protected where necessary, and documented. The work is close to the business process, and the expert often trains the team as part of the handover. Deep Excel skill is valuable precisely because so much operational knowledge lives in workbooks.

A data analyst starts further back. The work includes clarifying the question, defining metrics, sourcing and cleaning data, building a model, testing assumptions, and presenting a conclusion. SQL, Python, R, and a BI tool are common parts of the toolkit, but the method matters more than the list.

The output is usually an analysis, a dashboard, or a data model that can be refreshed. A good analyst is expected to explain what the numbers mean, not just produce them. That requires statistical judgement and enough business context to challenge a weak request.

Both roles need strong spreadsheet skills, careful logic, and clear communication. Both should be able to reconcile a total, define a metric, and explain a formula to a non-technical colleague. The boundary is not a wall.

The difference is the centre of gravity. An Excel expert optimises the artefact and the process around it. A data analyst optimises the evidence and the method. A small team may need one person who can do both, but the brief should still be clear about which outcome comes first.

Bring in an Excel expert when the problem is a workbook: a template that must be reused, a report that must be rebuilt, a model that has become slow or fragile, or a team that needs training. Bring in a data analyst when the problem crosses systems, needs a repeatable data model, or requires analysis beyond spreadsheet formulas.

Sequence matters. Fixing the workbook before the data model is defined often means rebuilding it twice. Defining the model without fixing the input process leaves the analyst waiting for clean data. Start with the decision, then decide which role owns the next step.

A useful brief states the decision, the current process, the data sources, the audience, and the definition of done. It should also name the person who can approve access and answer questions about definitions. Without those details, both roles spend the first part of the project discovering the scope.

Ask for a handover, not just a deliverable. That includes documentation, a walkthrough, and a named owner for the result. A good engagement leaves the team able to maintain the workbook or refresh the analysis, rather than dependent on the person who built it.