Riding Sequence: More Knowledge Creates Less Skill

Fullness of the First Month
A new employee finishes the first week with six LMS modules completed, dozens of policy documents, mandatory compliance training, product documentation, several internal program presentations, and a calendar full of onboarding meetings. By all legal measures, the process appears to have been successful.
Then the first real job comes. Instead of applying what he has learned, the employee hesitates, flips through old notes, or asks a co-worker to follow a procedure put together a few days earlier. The problem is rarely encouraged. Often, riding asks people to acquire more information than they can turn into actionable information.
Many organizations take the first month as an opportunity to educate new hires on everything they may need to know. Effective onboarding follows a different principle: people learn best when information arrives when they are ready to use it. That difference often determines whether new employees are productive quickly or spend their first weeks piecing together disconnected facts.
Why More Information Produces Less Learning
The sentiment behind many ride-hailing programs is understandable. If new employees need to be productive quickly, giving them more information early seems to be the fastest route there. Psychology suggests the opposite.
John Sweller’s cognitive load theory explains why. Working memory has a limited capacity, especially if everything is unusual. Every new program, policy, product, process, and summary competes for the same mental resources. Once that ability has passed, people stop organizing information into long-term memory and start trying to keep up.
For L&D teams, the definition applies. Time spent reading a policy that won’t apply in another month is time not spent building confidence in the jobs employees will face tomorrow. A well-designed ride prioritizes the importance of volume. Employees remember more when each piece of information comes closer to the time they need it.
This idea is also consistent with the training framework of Baldwin and Ford. Learning during training is only the first phase. Whether employees apply that learning on the job depends on what happens after the course, including whether they have opportunities to apply the new knowledge before it begins to fade.
Learning Should Follow the Work, Not the Org Chart
Reducing the cognitive load is part of the solution. The next question is how to decide what belongs in the first week of a hire, what can wait until the third week, and what doesn’t come up until much later.
David Merrill’s original teaching principles provide a useful way to think about that series. His research argues that people learn more effectively when teaching is structured around real activities rather than around topics or categories of information. Information is easier to understand if it helps someone solve an immediate problem than if it prepares them for every situation they may eventually face.
Most boarding programs do the opposite. They model the organizational structure instead of the first weeks of work at work. New hires don’t need to understand every department or policy right away. They need enough knowledge to successfully complete today’s work.
Seen through this lens, riding begins with a different question. Instead of asking, “What should every employee know by day 30?”, it’s more helpful to ask, “What does this person need before completing their first freelance job?” That change often produces a different onboarding plan—one built around the employee’s actual responsibilities rather than the organization’s structure.
3-Step Framework for the First 30 Days
Rather than treating the first month as one long onboarding phase, it’s helpful to think of it as three distinct phases of learning. Each section supports a different goal, and presenting the information in that order gives new hires a better chance of applying what they learn instead of just memorizing it long enough to pass the quiz.
Section 1. Learn Enough to Get Started (Days 1–5)
The first week should answer one question: “How do I do my real job effectively?” That means prioritizing the information workers need to start working safely and confidently. Critical workflows, immediate team expectations, critical systems, and a number of high-risk errors are all here—for example, security issues, customer-facing errors, or legal violations.
Phase 2. Making Decisions (Weeks 2–3)
When routine tasks become more familiar, employees have enough insight to understand why those tasks are performed in a certain way. That creates room for comprehensive processes, standard deviations, customer scenarios, and decision thinking. Instead of simply following instructions, employees began to develop judgment in less unexpected situations.
Section 3. Expand Context (Weeks 3–4)
Different processes, long-term strategies, advanced systems, and unusual situations become more meaningful when employees have practical experience to relate to them. The information presented in this section has a much stronger chance of retention because it now has a real workplace context.
A Different Approach to the First Month
A healthcare technology company encountered a common onboarding problem. New customer success professionals complete every required module in their first two weeks and regularly pass knowledge checks. However, managers have noticed a similar pattern when employees begin to personally handle customer conversations. They knew where to find information, but they questioned whenever a client asked an unexpected question or a situation fell outside the examples presented during training.
A closer look at the boarding schedule revealed the issue. In the first week, new hires were expected to absorb product information, internal systems, compliance requirements, company history, reporting procedures, and customer contact standards—all before handling a single customer contact. The information itself was accurate, but much of it arrived long before workers had any context to use it.
The problem was the point the workers encountered. The riding sequence was redesigned around the real working crew. The first week focuses only on the information needed to support basic customer conversations. Extensive procedures, edge cases, and various workflows moved into the following weeks, after employees had become familiar with common scenarios.
In the first month, management reported a noticeable change. New hires began handling direct customer requests with greater confidence, relying less on senior team colleagues for routine inquiries, and achieving independent productivity quickly. The management did not expand the boarding program or introduce additional content. They just change when the workers experience it.
Questions to Ask Before Adding Anything in Week One
Before adding new content in the first week of onboarding, ask:
- Do employees need this before completing their first freelance job?
- Can this be learned effectively after actual work experience?
- Does this reduce uncertainty, or simply increase knowledge?
- If we remove this in the first week, will the work performance really suffer?
The First Month Is About Consistency, Not Speed
Organizations often judge onboarding by how quickly employees complete it. A more useful question is how quickly they can work independently. Completing a ride and being competent at work are related outcomes, but not the same outcome. Presentation of completion steps. Competence measures whether learning transfers to practice.
The first month shapes new hire performance more than most organizations realize. Employees don’t need every policy, procedure, and exception right away. They need enough knowledge to succeed in today’s work, followed by context that helps them face tomorrow’s. For L&D teams, success is measured less by how quickly onboarding is done and more by how employees begin to work confidently and independently.
References:


