Overcoming Scheduling Conflicts in Training

40 people registered. 12 showed up. My client's first instinct: send a stronger reminder next time. Maybe make it mandatory. Maybe add calendar holds earlier... . I wanted to know why 28 people voted with their feet. So I called a few of them. Not to guilt them. To listen. What I heard: "I didn't think it was relevant to my actual work." "My manager didn't mention it, so I figured it wasn't a priority." "I've been to three workshops this quarter and nothing changed after any of them." one person said "I forgot." That last answer stuck with me. "Nothing changed after any of them." This wasn't a scheduling problem or a communication gap. It was a trust problem. People had learned that attending training didn't lead anywhere. Brinkerhoff's research backs this up. When only 15% of training transfers to behavior, people notice. They may not know the statistic, but they feel it. They learn that showing up doesn't matter because the system around them won't support whatever they learn. No-shows are not a compliance failure. They're the most honest feedback your learning culture will ever produce. Before you fix the reminder email, ask yourself: Do people believe that attending will change anything? Does their manager know the training exists? Is there any follow-up after the session? If the answer to those is no, better reminders won't help. When was the last time you treated low attendance as data instead of a problem to fix? #LearningCulture #LandD #PeopleAndCulture

Here's how I cut 80% of scheduling headaches with one AI Agent. For years, booking a 30-minute call meant fifteen emails back and forth. Double-bookings I'd catch too late. Meetings scattered across time zones that left me starting some days at 6am. Scheduling is one of the first things we hand off inside the Lab—because it's low-stakes enough to learn on, and high-frequency enough that you feel the relief immediately. Here's the framework: 𝟭. 𝗗𝗲𝗳𝗶𝗻𝗲 𝘆𝗼𝘂𝗿 𝗿𝘂𝗹𝗲𝘀 𝗳𝗶𝗿𝘀𝘁. Before you touch tools, decide how you 𝘸𝘢𝘯𝘵 your calendar to run. Which days for discovery calls? When's deep work protected? Do existing clients get priority access? These rules become the agent's instructions. Without them, you're just building a faster version of chaos. 𝟮. 𝗠𝗮𝗽 𝘆𝗼𝘂𝗿 𝘀𝘁𝗮𝗰𝗸. Where does scheduling actually happen for you? Calendly, Google Calendar, Zoom, Slack DMs? The agent needs to connect wherever requests come in—not just where you want them to come in. 𝟯. 𝗣𝗶𝗰𝗸 𝗮 𝗯𝘂𝗶𝗹𝗱𝗲𝗿 𝘁𝗵𝗮𝘁 𝗺𝗮𝘁𝗰𝗵𝗲𝘀 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆. Lindy, Make, Relay—plenty of options. The key: don't overbuild. If you're a solo founder with one calendar, you don't need enterprise-grade orchestration. Start simple. Add complexity when you hit real limits. 𝟰. 𝗗𝗲𝗽𝗹𝗼𝘆 𝗮𝗻𝗱 𝗺𝗼𝗻𝗶𝘁𝗼𝗿 𝗹𝗶𝗸𝗲 𝗮 𝗻𝗲𝘄 𝗵𝗶𝗿𝗲. Run it live, but watch it for a week. Edge cases will surface—weird timezone requests, double-booking conflicts, that one client who always replies to the wrong email thread. Once it's dialed in, you've got an assistant that manages requests, protects your focus time, and handles the back-and-forth you used to dread. But here's what actually matters: it's not about scheduling. It's about what you do with those hours back. For me, it meant finally having mornings free for the strategic work that was always getting pushed to "next week." If you're a solo founder looking to reclaim 10-20 hours a week to focus on growth instead of operations: https://lnkd.in/gz8ZwFpa

It's hard to be in two places at one time. So what do you do when you’ve signed up for a class and something else comes up? When choosing between an urgent task or a class, most people choose work over their own growth.😢 Why? Development is IMPORTANT. But tasks that are IMPORTANT and URGENT derail participation every time. It’s a good choice, as long as those tasks are actually IMPORTANT and URGENT.😏 But, if I had a dime for every time someone skipped a class because: ❌ They prioritized a task that could’ve waited ❌ Their manager called right when they were about to leave for class ❌ They considered a class as just another meeting and decided another meeting mattered more It adds up to missed opportunities - not just for the employee, but for the team and the organization. So how do you help people make an optimal choice when content needs to be learned in a class setting? For employees: 👉 Before you skip a class, ask yourself: Do I really have to choose? What other options exist for accomplishing the work? For my participation? 👉 Before assuming you can’t attend, communicate. Let your manager or facilitator know what’s going on. A quick conversation can lead to clarity and/or a creative solution. For managers: 🗝️ When you discuss an employee’s development plan and agree on the courses they’ll take, don’t stop there. Empower them to own their development. 🗝️ Make it clear that learning is part of the job. Support them in prioritizing their growth – and offer to help when the work feels too urgent to attend. 🗝️ Better yet, help them plan their time to avoid these conflicts altogether. Training is an investment - in your employees, your team, and your business. What strategies do you use to ensure learning is a priority on your team? 👇