Give a new colleague someone to turn to

What we found in the news

The Department of Health’s 2015 announcement of the Care Certificate (opens in a new tab) described knowledge, skills, and behavior expected in particular care roles. Its examples included:

“caring with privacy and dignity”

— Care Certificate launch announcement, March 25, 2015

We are looking at this historical announcement as a reminder that beginning a role involves more than receiving information. It is not a statement of current training requirements or a complete induction plan for every organization.

Why this matters to us

A new colleague can read the welcome folder and still be unsure whom to ask when the day changes.

Consider a hypothetical coordinator starting at a community program. They know where to find the timetable. They are less certain how to respond when a participant wants to arrive early, or which details may be discussed at the public reception desk.

Those questions become real in the work. At genus, we want a new colleague to have support at that moment, as well as material to read beforehand.

A capable person may be unfamiliar with a particular organization’s way of working. Treating every question as a knowledge deficit misses that distinction.

Plan the first useful conversations

Identify the people a newcomer will need to work with and make the introductions purposeful. Explain what each colleague handles, when they are available, and what to do when they are away.

A named buddy can help, provided the role is agreed and time is available. A name in a folder is less useful when that person is covering another service all week.

In our hypothetical program, the coordinator might walk through a first-arrival scenario with an experienced colleague. Where can they discuss a private question? Who can confirm a changed arrangement? What needs recording, and where?

Use fictional examples for practice. A learning conversation should not depend on spreading a participant’s personal information beyond the people who need it.

Let the newcomer see the task and try it with support

Showing a process once does not establish that it is understood. Give the colleague a suitable chance to explain the next step and practice within the responsibilities they have been assigned.

Ask where the written guidance differs from what they see. Sometimes a document is out of date. Sometimes an experienced person is using a shortcut that needs examination. The newcomer’s question can reveal something the organization should clarify.

Keep the scope realistic. Someone should know which decisions they can make and which require another person’s review. Avoid treating confidence as a substitute for competence, or silence as evidence that everything is clear.

Make essential guidance easy to find during the task. A long folder may remain useful as a reference, but the first shift also needs a manageable way to locate the answer that matters now.

Return after the first few ordinary days

Arrange a check-in that happens after the colleague has encountered the work, rather than only before it begins. Ask which situations were straightforward, which required help, and what they could not find.

Review the support arrangements too. Was the named contact available? Did the newcomer know how to reach someone else? Were colleagues expecting to provide help?

An unanswered question may reflect a gap in the process rather than a reluctance to learn. Make room to say that something still needs explaining.

When the role changes, revisit the relevant preparation. Being experienced in one part of a service does not automatically prepare someone for different systems, responsibilities, or people.

What this means for the people you serve

A participant should not have to guess whether a new colleague can help with a particular request. Introductions can make roles clear while keeping the person’s own preferences central. Invite participants to explain what helps them feel understood, without making them responsible for training the entire workforce.

The genus connection

Today, configured genus staff tools include training and help resources for supported workflows. The Partner Portal can bring relevant participant context and operational tasks into the authorized staff workspace.

Availability depends on the modules and permissions agreed with the organization. A resource, demonstration, or completed learning activity does not by itself establish competence. We see the tools as part of an induction arrangement that also needs experienced people, practice, and review.

One question for your next team meeting

If a new colleague encounters an unfamiliar situation tomorrow, do they know who can help at that time?