“Dear L&D” is a reflective letter-style series where learning leaders address the profession directly, giving voice to the lessons, challenges and opportunities shaping the future of learning and development (L&D).

Dear L&D,

The email arrives.

“Hi. We need training on this.”

Maybe it’s sales preparing for a new pitch. Maybe it’s a product launch of something new. Maybe it’s compliance reacting to a regulation that showed up yesterday afternoon, and suddenly everyone’s a little nervous.

Either way, the request is familiar. Someone wants a course.

If you’ve worked in learning and development (L&D) for a while, you’ve probably heard the advice: Slow down. Diagnose the problem. Ask what behavior needs to change before agreeing that training is the answer.

And yes, that’s solid advice. But in the real world, especially at the beginning of a relationship, things rarely unfold that neatly. Because when someone sends their first training request, they’re not only asking for a course. They’re deciding whether they trust you.

Push back too hard in that first conversation, and something subtle can happen. The stakeholder may start to feel like the project is being challenged before it even begins. From their perspective, the request seems reasonable. They have a deadline, pressure from leadership and a belief that training will help move things forward.

In other words, they’re trying to solve a problem the best way they know how. What they’re really looking for at that moment is a partner who can help. Not someone who immediately turns the meeting into a cross-examination.

Many experienced learning professionals recognize this dynamic. In our work at IDLance, where we collaborate with organizations and a community of over 2,000 freelance instructional designers, we see this pattern all the time. Instead of turning the request into a debate, experienced practitioners focus on delivering value.

Build the course. Do it well. Ask thoughtful questions along the way. No drama. No lecture. Just good work.

Something interesting usually happens after that first project.

The next request comes in. And the tone shifts a little.

“Hey, could you take a look at this and tell us what you think?”

Now the learning team is no longer just the group that builds the course. They’re the people stakeholders start asking for perspective.

• What should we prioritize?
• Would employees actually use this?
• Is training even the best way to approach it?

Those questions rarely show up in the first meeting. They show up after the learning team proves something simple. They understand the business. They meet deadlines. And the work they produce really helps people do their jobs a little better.

Trust changes the conversation. At that point, it becomes easier to ask a bigger question: What do you want people to do differently after this?

Now the discussion moves beyond the course itself. Stakeholders start talking about outcomes, performance and what success looks like. The learning team is no longer just building training. They’re helping solve problems.

And if we’re being honest, this is the part many learning professionals enjoy the most. Not just building content but helping teams think through what noticeably moves the needle.

It’s also the moment when the learning team begins to earn a different kind of seat at the table. Not just as course builders, but as trusted partners who understand how work gets done inside the organization.

That shift rarely happens during the first request. It happens after credibility is earned.

Most L&D advice focuses on the ideal process: diagnose first, design second. But influence inside organizations doesn’t always work in that order. Sometimes the most practical move is to deliver excellent work on the first request and use that credibility to shape the next one.

That doesn’t mean ignoring the real problem. It means recognizing that trust is often the door that leads to solving it. And trust takes a little time. Because the first training request may not solve the entire issue. But it can open the door to solving the right ones.