Universal Accessibility
Every organisation has Excel. No installation barriers, no licensing debates, no security reviews.
Excel remains foundational despite newer platforms. This guide covers advanced techniques BAs actually use in requirements analysis, data validation, and stakeholder reporting.
Despite the proliferation of specialized analytics platforms, Excel persists as the universal language of business data. Every stakeholder knows it, IT departments don't block it, and it requires no infrastructure investment or approval process. As a BA, Excel proficiency enables independence in data analysis, quick prototyping of calculations and visualizations, and stakeholder communication in familiar formats.
Every organisation has Excel. No installation barriers, no licensing debates, no security reviews.
Executives understand Excel. Analysts trust it. Subject matter experts can collaborate directly.
Test calculations, validate data models, create quick dashboards before investing in formal tools.
Pivot tables transform flat data into multidimensional insights without formulas. BAs use them for requirements analysis (How many users requested feature X by department?), data validation (Do stakeholder estimates align with system data?), and impact analysis (Which business units would be affected by this change?).
Requirements Analysis — Analyse requirements by priority, stakeholder, business unit. Identify patterns: "80% of Must-Have requirements come from Finance."
Data Validation — Cross-check stakeholder estimates against system data. Validate completeness: "We have user stories for 6 of 8 identified workflows."
Impact Analysis — Summarise transaction volumes by department, process, time period to quantify change impact.
Stakeholder Reporting — Create executive summaries: requirements status by priority, test coverage by module, issues by severity.
Business analysts constantly combine data from multiple sources: requirements from documentation, user counts from databases, cost estimates from finance. Lookup functions automate this matching without manual copy-paste.
Syntax:
=VLOOKUP(lookup_value, table_array, col_index_num, [range_lookup])
When to Use: Simple lookups where match column is leftmost in table. Quick for basic tasks.
Limitations:
Example:
=VLOOKUP(A2, Requirements!A:D, 3, FALSE)
Look up requirement ID in A2, return priority from column 3.
Syntax:
=INDEX(return_range, MATCH(lookup_value, lookup_range, 0))
When to Use: Professional BA work. More flexible and robust than VLOOKUP.
Advantages:
Example:
=INDEX(Requirements!C:C, MATCH(A2, Requirements!A:A, 0))
Match A2 in Requirements column A, return corresponding value from column C.
Syntax:
=XLOOKUP(lookup_value, lookup_array, return_array, [if_not_found])
When to Use: Excel 365/2021+. Simplifies syntax while retaining INDEX-MATCH power.
Advantages:
Example:
=XLOOKUP(A2, Requirements!A:A, Requirements!C:C, "Not Found")
Look up A2 in Requirements column A, return column C, show "Not Found" if no match.
Scenario: You have requirements documented in one sheet with Requirement IDs. User research data in another sheet also references Requirement IDs. You need to combine them for stakeholder review.
Solution with INDEX-MATCH:
=INDEX(UserData!D:D, MATCH([@[Req ID]], UserData!A:A, 0))
This formula in your requirements table looks up each Req ID in the UserData sheet and returns the corresponding user count from column D. As requirements are added/removed, the formula automatically adjusts.
Conditional formatting transforms spreadsheets from data dumps into decision-support tools. BAs use it to highlight exceptions (requirements without test coverage), show trends (increasing defect rates), and create visual dashboards (red/yellow/green status indicators).
Requirements Traceability — Highlight requirements without linked test cases in red. Instant gap identification.
Rule: =ISBLANK(TestCaseID) → Fill Red
Priority Visualisation — Colour-code by MoSCoW priority: Must Have (red), Should Have (orange), Could Have (yellow), Won't Have (gray).
Status Dashboards — Icon sets for approval status: ✓ (Approved), ⚠ (In Review), ✗ (Rejected), ⏸ (Pending).
Outlier Detection — Highlight effort estimates > 2 standard deviations from mean for review.
Home → Conditional Formatting → New Rule → Use a formula to determine which cells to format
Example: Highlight overdue requirements
=AND([@Status]<>"Complete", [@DueDate]<TODAY())
Applies formatting when status isn't "Complete" AND due date has passed.
Power Query (Data → Get & Transform Data) enables BAs to clean, reshape, and combine data through a visual interface instead of complex formulas. Once configured, queries refresh with one click, automating repetitive data preparation.
Requirements Import Automation — Connect to Jira/Azure DevOps exports. Transform JSON/CSV into analysis-ready tables. Refresh weekly for status tracking.
Multi-Source Data Combination — Merge user feedback from surveys, usage data from databases, and requirements from documentation into single analysis view.
Data Quality Validation — Filter for blank fields, duplicate IDs, invalid formats. Generate data quality report showing completeness.
Stakeholder Reporting — Shape system exports into executive-friendly formats. Remove technical fields, rename columns, add calculated KPIs.
Data → From Table/Range (or From Text/CSV, From Web, From Database)
Clean, reshape, combine using visual interface
Home → Close & Load (creates refreshable connection)
Data → Refresh All (updates with latest source data)
Macros automate repetitive multi-step tasks. BAs don't need to become VBA programmers — recording macros handles 80% of automation needs. Use for formatting reports, generating weekly status summaries, or preparing data for stakeholder review.
Start Recording — View → Macros → Record Macro. Give descriptive name (no spaces). Assign shortcut key if desired.
Perform Actions — Execute the steps you want automated. Excel records every action (formatting, sorting, filtering, calculations).
Stop Recording — View → Macros → Stop Recording. Macro saved for reuse.
Run Macro — View → Macros → View Macros → Select macro → Run. Or use assigned shortcut key.
Macros can pose security risks if from untrusted sources. Organisations often disable macros by default.
Coming soon: Sample BA datasets with exercises covering pivot tables, lookup functions, conditional formatting, and Power Query transformations.
Practice with realistic requirements data, stakeholder analysis examples, and status reporting templates.