The First Fortnight Is the Real Feedback Form

The end-of-session feedback form has a lot to answer for. It is easy to run, easy to count and almost always kind. People tick 'good' or 'very good', write 'really useful' in the comments box, then head back to the desk where the real test begins. By the following Monday, the training is a memory and the inbox is not.

That is not a reason to scrap feedback. It is a reason to stop treating it as the final word. A better question for UK teams is simpler and far more revealing: when did someone actually use the new skill on real work? Not in the practice activity. Not in the role-play. On the job, with a customer, a spreadsheet, a colleague or a deadline.

The smiley sheet flatters everyone

Happy sheets measure the temperature of the room, not the temperature of the work. They tell you whether the trainer was engaging, whether the biscuits were adequate and whether people felt good about giving up a morning. All useful in their place. None of it proves that the skill has moved from the training room to the desk.

The first use matters because it is the moment training becomes behaviour. It is also the point where problems show up early enough to fix them. If someone learns a new handover process and does not use it within a fortnight, something is already getting in the way. Better to find that out while the session is still fresh than in a review six months later.

What counts as a first use?

Keep the definition deliberately unglamorous. A first use is a real task where the learner applies the new approach, even partly, without being led through it. It might be using a new briefing structure in a team meeting. It might be asking a customer a different opening question. It might be updating a project tracker in the way the session described.

It does not need to be perfect. In fact, a slightly wobbly first attempt is often a good sign. It means the person has tried the skill in the messy real world rather than waiting until they feel ready. Waiting for ready is how training ends up as a PDF in a folder called 'resources'.

Before the session ends, ask each learner to complete a first-use sentence: 'By the end of next week, I will use this when...' It takes two minutes and gives everyone something concrete to look for.

Track it without building a monster

You do not need a dashboard the size of a bus. A simple shared log is enough: name, skill, first-use date and a one-line note about where it happened. Add a column for what helped or hindered. Keep it visible to the learner and their line manager, not to a central team who will turn it into a league table.

Managers do not need to become auditors. A short prompt is enough. Within 48 hours: 'What is the one thing you will try?' At day seven: 'Where did it land, and what felt awkward?' At day 14: 'What would make the next use easier?' These are conversations, not compliance checks.

The point is to make first use normal and expected. If someone has not used the skill by day 14, treat that as information. It might mean the opportunity has not come up. It might mean the process does not allow it. It might mean the learner is not confident yet. All three are fixable. None of them are revealed by a happy sheet.

The 30-day stuck review

If nobody in the group has used the training within 30 days, pause and look at the barriers. Do it without blame. The learner turned up. The trainer delivered. Something between the room and the desk is not joining up.

Ask a few plain questions. Was there a real task to use it on? Did the line manager know what was coming? Did the team's existing process contradict the new approach? Was there time to practise? Did people understand what good looked like? Were they worried about looking foolish?

The answers usually point to one of a handful of things: workload, opportunity, permission, confidence or system design. Only one of those is really about the learner. The rest are about the environment around them. That is why the 30-day review is so useful. It moves the conversation from 'did they like it?' to 'what would make it stick?'

Make first use the story you tell

Numbers help, but stories travel further. In team meetings, ask for a quick first-use example. Not a polished case study, just a sentence: 'I tried the new agenda and the meeting finished ten minutes early.' That does more for credibility than a slide of average scores.

Keep the measurement light. Pick one or two skills per programme rather than trying to track everything. Celebrate the awkward first attempts as much as the smooth ones. And give managers a simple role: create a chance, ask a question, notice the attempt.

Happy sheets can stay for logistics and trainer feedback. Just do not let them sign off the learning. The real feedback form is the first fortnight. Ask who used the skill, where, and what got in the way. If the answer is 'not yet', you have not failed. You have found the next piece of work.