Public course or in-house course: which one suits you?
Whether to send an employee to a public course or to run the course for your team alone depends on three things: the number of people, the subject, and what you want from the course.
The scene is familiar. The management team spends two days in a hotel, comes back with a strategy everyone is proud of, and presents it to the staff. Six months later, people are doing what they did before. The strategy was not wrong. It broke somewhere between the slides and the daily work, usually in one of four places.
“To be the customer’s first choice” means nothing to the person in the warehouse. Until each department can say what it will do differently next Monday, there is no strategy, only a wish.
A plan with twelve priorities has none. When everything is important, people go back to whatever is urgent. Three objectives that everyone can repeat from memory do more than twelve that live in a document.
An objective given to a committee belongs to no one. Each objective needs one name next to it: a person who is asked about it, by name, at every review.
A strategy reviewed only at the end of the year is reviewed too late to save. An hour every quarter is enough, with three questions: what did we say we would do, what happened, and what do we change?
Ask five employees from five departments what the company’s priorities are this year. If you get five different answers, the problem is not the strategy. It is that the strategy never left the room it was written in.
Whether to send an employee to a public course or to run the course for your team alone depends on three things: the number of people, the subject, and what you want from the course.
Copying colleagues on an email feels harmless. Multiplied across a whole company, it becomes one of the largest hidden costs of the working day.
An employee comes back from a course full of enthusiasm, and a month later works exactly as before. The cause is usually not the course itself but what happens before and after it.