A 3-Step Rule to Stop Repeating Instructions to New Hires

1. A Checklist to Assess Knowledge Levels

Seniors often mistakenly assume that new hires naturally understand what they know. This cognitive bias is the primary cause of misaligned task instructions. A new hire who nods is more likely sending a "fake signal" because they are afraid to ask questions, rather than because they truly understand.

When assigning tasks, ensure you include the following three elements in your documentation:

Specify the trainee's level based on the Dreyfus model: Clearly state whether they fall into one of the four stages: novice, advanced beginner, competent, or proficient.
Provide level-specific guidelines: For the first stage, provide a segmented checklist; for the third stage, delegate based on milestones.
Request a self-assessment of difficulty: Have the person receiving the task write down a numerical value for the task's difficulty; this allows you to immediately identify discrepancies in expectations.

Following this process alone will cut the number of unnecessary re-instructions in half.

2. Mandatory Construction of an Internal Technical Glossary

Complex technical jargon slows down learning and frustrates managers. GitLab enforces a "handbook-first" policy to centralize all knowledge and deletes Slack conversation history after 90 days to force users to search the wiki. This has reduced the onboarding period for new hires by 70%.

Utilize Notion's database properties to build a glossary:

Organize technical terms, examples of how to translate them into plain language, and real-world application cases into a single table.
Whenever a new term arises, do not explain it personally; record it in this table once and then share the link.
Incorporate a step into the business process that requires looking up this dictionary.

Save the energy you spend answering the same questions over and over and create an environment where new hires can look things up for themselves.

3. Introducing a Teach-Back Protocol for Re-explanation

Instead of asking if they understand, have the trainee explain the execution flow back to you. This is a "teach-back" technique used in medical settings to prevent safety accidents.

Change your conversation routine with these three rules:

Before asking, state the purpose of the conversation: "I want to make sure my explanation was clear, so please repeat back what you just heard in your own words."
Have the trainee recount the steps and priorities of the task.
If the explanation is off-base, do not re-explain verbally; change the stimulus visually by drawing a diagram or providing code examples.

Applying this routine at the end of meetings eliminates the cost of rework caused by misunderstandings. Instructions should be delivered through systems, not just verbally, to protect the manager's own deep work time.

1. A Checklist to Assess Knowledge Levels

When assigning tasks, ensure you include the following three elements in your documentation:

Specify the trainee's level based on the Dreyfus model: Clearly state whether they fall into one of the four stages: novice, advanced beginner, competent, or proficient.

Provide level-specific guidelines: For the first stage, provide a segmented checklist; for the third stage, delegate based on milestones.

Request a self-assessment of difficulty: Have the person receiving the task write down a numerical value for the task's difficulty; this allows you to immediately identify discrepancies in expectations.

Following this process alone will cut the number of unnecessary re-instructions in half.

2. Mandatory Construction of an Internal Technical Glossary

Utilize Notion's database properties to build a glossary:

Organize technical terms, examples of how to translate them into plain language, and real-world application cases into a single table.

Whenever a new term arises, do not explain it personally; record it in this table once and then share the link.

Incorporate a step into the business process that requires looking up this dictionary.

Save the energy you spend answering the same questions over and over and create an environment where new hires can look things up for themselves.

3. Introducing a Teach-Back Protocol for Re-explanation

Instead of asking if they understand, have the trainee explain the execution flow back to you. This is a "teach-back" technique used in medical settings to prevent safety accidents.

Change your conversation routine with these three rules:

Before asking, state the purpose of the conversation: "I want to make sure my explanation was clear, so please repeat back what you just heard in your own words."

Have the trainee recount the steps and priorities of the task.

If the explanation is off-base, do not re-explain verbally; change the stimulus visually by drawing a diagram or providing code examples.

A 3-Step Rule to Stop Repeating Instructions to New Hires

Related Video

How to Explain Anything To Anyone (Even If It's Complex!)

A 3-Step Rule to Stop Repeating Instructions to New Hires

1. A Checklist to Assess Knowledge Levels

2. Mandatory Construction of an Internal Technical Glossary

3. Introducing a Teach-Back Protocol for Re-explanation

Comments (0)

A 3-Step Rule to Stop Repeating Instructions to New Hires

1. A Checklist to Assess Knowledge Levels

2. Mandatory Construction of an Internal Technical Glossary

3. Introducing a Teach-Back Protocol for Re-explanation