Rethinking Employee Training

Lately, I have been rethinking how we train new team members.

This did not come from reading a management book or trying to redesign everything from theory. It came from practical observation. Over time, my partner Ashley and I kept noticing the same pattern: some new hires were not learning as smoothly as we hoped, even when we thought the training content itself was logical and complete.

That made me step back and ask a more basic question.

Maybe the issue was not only what we were teaching. Maybe it was also how we expected people to learn.

The Shape of Our Usual Thinking

For a long time, my natural tendency was to explain things from the top down.

I like starting with the big picture. I want to explain the context, the logic, the categories, the purpose, and the structure first. In my mind, once someone understands the overall map, the smaller details become easier to place. It feels efficient. It feels clean. It feels like the "smart" way to teach.

In practice, that often means starting with questions like these:

• Who is the customer?
• What kind of business are they running?
• What problems do they face?
• What systems do we have?
• Which product solves which problem?

From there, the rest is supposed to connect naturally.

For someone who learns this way, it makes sense. I still think there is value in it. But what I slowly realized is that this learning style may be more personal than universal.

A Mismatch, Not a Deficiency

One thing I have had to unlearn is the quiet assumption that if something is logically explained, it should already be easy to absorb.

In reality, many of the people we hire are not naturally trained in abstract thinking, conceptual grouping, or learning from frameworks first. Their strengths may come from a more practical background. They may learn more through direct contact, repetition, observation, and doing.

When I looked at it this way, the problem started to feel different.

It was no longer, "Why are they not getting it?"

It became, "Are we asking them to learn in a way that does not match how they naturally build understanding?"

That shift matters. It changes the tone of training. It makes it less about judging the learner and more about examining the design.

Concrete Before Concept

The more I thought about it, the more I felt that many people do not begin with abstraction. They begin with concrete experience.

They need to see the thing. Touch the thing. Compare the thing. Use the thing. Repeat the thing.

Only after enough exposure do they slowly form a deeper understanding of what the thing is, how it works, and why it matters.

This made me rethink the sequence of learning.

Instead of always starting with why, then moving to how, and finally to what, I started wondering whether, for some roles, the more natural sequence might be:

What → How → Why

Not because "why" is unimportant, but because sometimes understanding needs raw material first.

Recognition Before Explanation

In our context, this became especially relevant when thinking about customer service training for ShopTech products.

Traditionally, it is tempting to begin with business context, use cases, system categories, and product logic. But now I am leaning toward a simpler first step: let new hires first become familiar with what is physically in front of them.

Before expecting them to explain products, maybe they should first recognize them.

What does this device look like? How is it different from another model? What parts does it have? What happens when it is powered on? What feels similar, and what feels different?

At this stage, the goal is not mastery. It is familiarity.

There is something important about being able to say, "I have seen this before. I have held it. I know roughly what it is."

That kind of recognition may sound basic, but it gives the mind something stable to build on.

Familiarity Reduces Cognitive Load

One reason I find this approach meaningful is that learning often becomes easier on the second encounter, not the first.

If someone sees a product for the first time while also trying to understand its function, troubleshooting logic, use case, and configuration steps, that is a lot happening at once. Even if they look like they are following, it may still feel mentally crowded.

But if the first encounter is just about recognition and exposure, then the second encounter can focus on operation.

Now the product is no longer completely foreign. There is already a visual memory, a tactile memory, a small sense of orientation. That changes the learning experience.

The person is no longer trying to understand everything from zero at the same time.

Learning Through Contact

The heart of this shift is not just a new sequence. It is a different view of how understanding grows.

I used to assume that if structure is given clearly enough, understanding will follow.

Now I think that for many kinds of learners, understanding often grows after enough contact with reality.

That contact may look simple from the outside:

seeing products, handling them, switching them on, noticing differences, trying things repeatedly, getting used to their presence.

But beneath that simplicity, something important is happening. The learner is collecting raw data. And with enough raw data, abstraction becomes much more possible.

In that sense, some forms of learning are not "explained into existence." They are built from accumulated contact.

Slow at the Start, Smoother Later

One trade-off of this approach is that it may look slower in the beginning.

A more top-down training style can cover a lot of scope quickly. You can explain the whole landscape in a short time. On paper, it looks efficient.

But speed at the beginning does not always mean ease over the full journey.

Sometimes people hear everything, but do not truly digest it. They may hesitate to ask questions. They may feel lost without knowing how to describe it. They may appear to understand, while still carrying confusion underneath.

That kind of training looks fast, but the friction shows up later.

A more bottom-up path may feel slower at first, because the early stage involves exposure, repetition, and patience. But it may create less hidden resistance. And over time, that may actually become the more efficient route.

Not faster in appearance, but smoother in absorption.

Not Only for Slower Learners

Another thing I have been reconsidering is whether this kind of approach is only useful for people who struggle academically or abstractly.

I do not think so.

Some people are quick to understand concepts. They can listen to an explanation and repeat it back well. But even then, there is a difference between understanding a conclusion and building one from firsthand experience.

Without enough hands-on exposure, people can become fluent in explanation without being grounded in reality. They know the summary, but not the texture. They know the answer, but not the material behind it.

That is not a criticism. It is just a reminder that speed of understanding and depth of understanding are not always the same thing.

So while the concrete-first approach may be especially helpful for some learners, it may still be useful more broadly than I first assumed.

Capability Over Information

What this has changed for me is not only how I think about training flow, but how I think about the purpose of training itself.

Sometimes training is treated as information transfer.

But in real work, especially operational work, the goal is usually not just to help someone remember information. The goal is to help someone build capability.

Those two things are related, but they are not identical.

A person may remember a framework and still freeze in front of a real case. A person may not speak in polished concepts, but may handle the real situation well because they have built familiarity, pattern recognition, and practical confidence.

That distinction has become more important to me over time.

A Wider Management Reflection

What started as a small question about onboarding has slowly become a broader management reflection.

As founders or managers, it is very easy to teach from our own mental habits. We naturally explain things in the way that makes the most sense to us. That is normal. But it can also create blind spots.

Sometimes what feels clear to the teacher is still too abstract for the learner. Sometimes what feels efficient to the manager creates invisible pressure for the trainee. Sometimes what looks like weak learning is actually a mismatch in teaching order.

I do not think this means top-down teaching is wrong. It still has a place. In fact, for some people and some situations, it may still be the better method.

But I am becoming more careful about assuming that a method is universally effective just because it feels natural to me.

Beginning of an Experiment

At this stage, I still see this as a hypothesis rather than a conclusion. It has not been fully validated in practice yet. But at least to me, the logic feels sound enough that it is worth testing seriously.

One reminder I am taking for myself is that in training, I should think more from the learner's point of view. In this context, the "user" is the employee. That means the question is not only whether the training makes sense to me, but whether it makes sense from where they are entering it. Maybe that requires more observation, more listening, and more willingness to question the status quo instead of simply repeating how things have always been done.

For now, I want to treat this as the beginning of an experiment. We will see how it rolls out in practice, what holds up, what needs adjustment, and what surprises show up along the way. I hope to share more updates as we learn from it.