What I’ve Learned About Leading People Who Learn Differently

One of the mistakes I made early in leadership was assuming that a clear explanation should work the same way for everyone.

Some people understand a process after hearing it once. Others need to see it, practice it, write it down, or ask questions after they have had time to think. That difference does not tell me who cares more. It tells me that people process information differently.

Over time, I have learned that leadership is less about explaining something once and more about creating enough structure for people to use it well.

Understanding a Process Is Only the Beginning

A team member can follow an explanation in a meeting and still struggle to carry it out during a busy day. I have seen this with clinical handoffs, scheduling protocols, digital workflows, and patient communication.

The person may understand the idea but still be unsure what a strong result looks like in practice. That is where leaders often become frustrated. We think, “We already covered this,” while the team member may still be trying to connect the explanation to the actual work.

Another general reminder rarely closes that gap. More specific teaching usually does.

Sometimes that means demonstrating the process, watching the person try it, correcting one step, and repeating the cycle. A new scanning workflow may need a written checklist, a live example, practice time, and review after several cases.

A difficult patient conversation may need something different: a script, observation, repetition, and feedback. The standard stays the same, but the path toward it becomes clearer.

Repetition and Feedback Build Consistency

I used to worry that repetition meant I had not explained something well enough. Now I see it as part of building a shared way of working.

Teams do not become consistent because they attended one meeting. Expectations have to be reinforced enough to hold up during full schedules, emergencies, staffing changes, and complicated cases.

That reinforcement should not feel like the same speech delivered over and over. It can come through practice, observation, real examples, and feedback people can actually use.

General feedback rarely creates much movement. “Be more careful” leaves the person to guess what should change. “Good job” feels encouraging but may not show them what to repeat.

Specific feedback gives them something concrete. Instead of saying a handoff was weak, I might explain that the clinical information was accurate but the next action was unclear. Instead of offering general praise, I might point out that the team member slowed down, checked the patient’s understanding, and confirmed the next step before the patient left.

When people know exactly what worked or what needs to change, they can improve with more independence.

Leadership Requires Observation Before Assumption

I have also learned to be careful about labeling every performance issue as an attitude problem.

Sometimes the expectation was unclear. Sometimes training moved too quickly. Different leaders may have given conflicting directions, or the team member may not have had enough practice to become confident.

Before deciding what the problem is, I try to look at what actually happened. Was the expectation clear? Did the person see a strong example? Were they given time to practice? Was the same standard reinforced across the team?

I also try to determine whether I am looking at a knowledge gap, a skill gap, or a willingness issue. That distinction changes the response.

Someone who needs more training should be coached differently from someone who understands the standard and repeatedly chooses not to follow it. Both situations require leadership, but they do not require the same kind.

Leading people who learn differently has made me more patient, but it has also made me more precise. I think more carefully about how expectations are taught, practiced, observed, and reinforced.

The standard can remain consistent while the support around it changes.