Academy / Candidate experience, onboarding and retention

LESSON 1 OF 6 · BEGINNER

Map the candidate journey

List every point where a person waits, supplies information or makes a decision. Identify which steps provide useful evidence and which create avoidable effort. Ask how a candidate knows the status and how to request help. A journey map should include people who withdraw or are declined, not only successful hires.

Learning objective

Map six journey steps with candidate effort, owner and update expectation.

About 2 minutes reading + 12 minutes practice. Take longer when needed.

Apply the method

Map the candidate journey from first awareness through closure and the start of employment. For each step, record what the candidate must do, what they learn, what decision evidence the employer gains, who owns it and when an update is due. Include withdrawals and rejections. Identify duplicated effort, unexplained waits and difficult access points. Ask which steps can be simplified without losing necessary evidence. A journey map is useful when it leads to a concrete repair and a review, not when it is only a visually attractive process diagram.

A worked application

Fictional example: A local service business asks applicants to re-enter the same job history after uploading it. The review finds one entry supports an essential internal process while another is redundant. The team removes the unnecessary repetition and explains the remaining request. A hospital employer may have different credentialing needs, so the map must distinguish genuine requirements from avoidable burden.

Common mistake to avoid

Do not remove a necessary verification solely to shorten the process. Explain its purpose and improve how candidates complete it.

Work through the case

FICTIONAL SCENARIO

An applicant repeats the same work history in three systems. A process owner can assess whether all three entries are necessary and provide clearer instructions.

Make it practical

Map six journey steps with candidate effort, owner and update expectation.

Compare your reasoning with a worked response

Look for duplicate requests and unexplained waits. Prioritize an improvement that reduces burden without removing necessary evaluation.

Takeaway

Use the method to explain your decision, identify what you still need to verify and choose an accountable next step.

Treat the response as a model for reasoning, not the only possible wording. Adapt it to the role, evidence and appropriate organizational guidance.

Next lesson →

Sources for this course