Scope and map the employee journey · Lesson 1

From a vague experience request to an executable brief

6 min read

Lesson objectives

  • Draft a brief specifying population, journey point, evidence, decision owner, output and authority boundary.
Reading tools

An employee experience specialist may receive a request to “increase engagement this quarter.” That expresses an ambition, but identifies neither whose experience should change, nor the moment in the work journey, nor the decision the evidence will support. Employee experience spans interactions such as joining, gaining tools, speaking with a manager and moving between roles. Engagement concerns the employee's relationship with work conditions and the ability to influence them; it is not interchangeable with satisfaction with a single event. The specialist names a testable problem before choosing a survey or an activity. The role can improve evidence gathering and facilitate an authorized decision, but cannot promise a change to staffing or compensation policy without its owner.

An operational brief has seven linked fields. First, define the population, for example recent joiners in a service team since the start of a quarter, rather than “all employees.” Second, identify a journey point, such as receiving system access in week one, rather than undefined “culture.” Third, state the observed symptom and its source, keeping a service log distinct from one person's account. Fourth, state a hypothesis to test: delayed access might postpone productive work. A hypothesis is not an established cause. Fifth, specify the specialist's deliverable, such as an access request map and an improvement recommendation. Sixth, name the decision owner and the person who can change the step. Seventh, state the data limits, deadline and acceptance check. Missing case counts or dates should remain unverified until suitable records are obtained.

Select a measure after defining the decision. If the issue is delay, elapsed time from an approved access request to confirmed activation may fit that touchpoint, provided the start and end are defined and cancelled requests are handled transparently. An overall engagement score alone cannot locate the failed access step. An employee account of the impact can be considered alongside the service record to examine the sequence; the coincidence does not prove that delay caused lower engagement. Keep individual records with authorized custodians and share a summary that does not expose a person or comment in a small group. Privacy rules vary by location and organization, so route questions about legal basis and retention to the responsible function.

Test the draft brief with three questions. Could a colleague identify the information to collect without inventing it? Could the process owner accept or reject the deliverable using a stated check? Is any proposed decision outside the specialist's authority and therefore in need of escalation? Repair a field when the answer is no. “Run a companywide survey and then launch a recognition event” is a weak brief when the friction point is still unknown. So is a promise of a higher engagement percentage without a baseline or verification path. A useful brief is a small work contract linking the employee need, the evidence and the decision while keeping inference limits visible. It is short enough to use, but sufficiently precise to expose who must act next.

Lesson summary

Draft a brief specifying population, journey point, evidence, decision owner, output and authority boundary. an eight field brief and one escalation line.