Who helps the team use this well?

What we found in the news

A November 2025 WHO/Europe release (opens in a new tab) introduced a regional report on readiness for AI in health systems. Among the priorities it described was the need to:

“invest in an AI-ready workforce”

— WHO Regional Office for Europe

The underlying survey concerned national approaches across the region, rather than the performance of one product or staff team. Its workforce focus prompts a local question: who helps people use a new tool well after the launch session is over?

Why this matters to us

A colleague may understand a tool during a demonstration and still need help the first time an unusual question appears during a busy shift.

Imagine a community service introducing assistance with finding approved resources. During handover, an experienced colleague practices one ordinary task with someone who will cover the next shift. A participant adds that the earlier answer did not explain which entrance to use.

The practice now has a real purpose. It connects the tool’s operation with the information people need and the staff member who can resolve a gap.

At genus, readiness includes that everyday support around the technology. A login and a presentation do not tell us whether the next colleague knows what to do.

Teach the task in its actual setting

Choose a realistic example and use the configuration staff will encounter. Show where the information comes from and which details need checking.

Let colleagues practice the parts that require judgment. They may need to recognize an incomplete answer, explain uncertainty, or choose another route when the tool cannot help.

In our imagined handover, the newer colleague tries the resource question while the experienced colleague observes. The participant’s entrance question gives the team something specific to verify.

Use fictional details where private information would otherwise be involved. Practice should build understanding without exposing records that are unnecessary for learning the task.

Give questions an owner

Name the person or team responsible for different kinds of help. A content correction may need the program owner, while a permission problem may need a service administrator or supplier.

Make the route easy to find during ordinary work. A simple contact guide should say what information helps the receiving colleague investigate and what should stay out of a general message.

Agree what staff should do while waiting for an answer. They need an appropriate way to continue the service without guessing about the tool’s behavior or offering a promise they cannot keep.

Ensure the arrangement covers absences and occasional staff. The service should not depend entirely on the colleague who happened to attend every planning meeting.

Use the questions to improve the setup

A repeated question is useful evidence. It may reveal a missing resource, unclear wording, or a function that does not fit the expected workflow.

Bring those observations together at a proportionate review point. Separate issues that can be corrected locally from matters requiring supplier or leadership decisions.

Tell colleagues what changed and why. When the entrance information is corrected in our example, the team can update the resource and the relevant guidance, then ask whether the next person can find it.

Revisit training when the configuration changes. A familiar label may now lead to a different action, and staff who were previously confident may need another opportunity to practice.

Make it acceptable to ask again. Reliable use grows through clear explanations and supported experience, with uncertainty raised early enough for someone to respond.

What this means for the people you serve

People benefit from staff who can explain the tool’s role, recognize a limit, and find the right help. They can also contribute to the team’s learning by pointing out missing or confusing information. Their experience should inform the support material used by the next colleague.

The genus connection

Today, genus partner-portal workflows are configured around staff roles, content, and enabled functions. Preparing a useful setup includes confirming who can do what and who reviews the information being shared.

We would connect that configuration with practical onboarding and a clear route for ongoing questions. Start with the task staff need to perform, prepare realistic examples, and keep the help current as the service evolves. The team’s ability to use the tool is part of delivering the intended experience.

One question to take away

Who will help the colleague on the next shift when the task does not look like the demonstration?