The Home Depot Canada Business Analyst gathers and documents the requirements behind website, mobile app and retail channel enhancements, and works as a key contact between end users, business units, IT and Product Management. That handoff is where enhancements succeed or fail — and it is the work below: business functions and processes defined from the floor up, redesigned against measured outcomes, specified so both sides build from the same page, and accepted before rollout.
Read closely, this is a translation role with a paper trail: turn what the business needs and what end users actually do into requirements, functional specifications and test cases that IT can build against — then write the procedures and training that make the change hold after launch. It rewards an analyst who has stood on every side of the handoff: the retail floor where processes land, the enterprise platform team where requirements are negotiated, and the builder’s desk where specifications become shipped systems. That combination is rare because most analysts only ever sit in one chair. I have sat in all three.
Information gathering starts with end users, not with the request form. Document current operational procedures as they actually happen — the workarounds are requirements too.
Business Requirements Docs, use cases, process diagrams and functional specifications that end users and IT read the same way — with changes tracked and design rulings recorded, not remembered.
Test cases and user acceptance testing are defined up front, and the end-user procedures and training are written before go-live — so the enhancement holds after the launch meeting ends.
Defined and documented the business functions and processes behind service and repairs, then carried the operational change: Geek Squad repair turnaround cut from ∼5 business days to under 48 hours. The two teams I led (18 people) held first place in NPS rankings every month from November 2022 through February 2024, with performance analysis run on Power BI and Titan dashboards.
Requirements-vs-delivery analysis at scale: test cases defined against 32 live production deployments, 247 exchanges scored against the rubric, and the findings consolidated into one published, decision-grade report — research consolidated for decision-making, in public.
Embedded at a Philip Morris International affiliate: information gathering and requirements synthesis across Digital, Commercial, Enablement and IT for the platform retail field teams run on — navigation, AI-driven search, guided flows, contextual help — plus Microsoft 365 Copilot prototypes and a 90-day integration roadmap, inside a regulated enterprise.
A complete product specification (v1.3) written before any build: feasibility worked through in the open, five design rulings recorded with their reasoning, scope and constraints explicit. Requirements discipline as a reviewable record — the document is the deliverable.
A document-heavy legal process analyzed and re-specified as guided intake: input and output requirements defined for non-expert users, current procedures mapped from a coded corpus of real complaints, and the future-state flow built, shipped and measured in users’ hands.
End-user procedures and training designed for people who will never read a manual: a live education product whose scam-safety module (Bob the Bouncer) shipped with a presenter briefing and pamphlet prepared for a Toronto Public Library session — recognition before reading, teach-the-teachers structure.
An enhancement succeeds or fails in the handoff — between what the business meant and what the system got. The analyst’s job is to make the handoff hold.
Document the enhancement intake as it actually flows, the operational procedures end users actually follow, and the documentation set Product Management decides from — a baseline the whole team can point at.
Requirements, functional specifications, test case definition, user acceptance testing, procedures and training — one live enhancement carried through the full cycle, with end users, IT and Product Management in the same loop.
Codify the worked cycle as the documentation standard — BRD and use-case shapes, change tracking, acceptance checklists — so the pattern outlives the contract and the team that stays owns it.