Give Feedback to Early Hires: Early, Specific, Two Ways
How to give feedback to early hires: say the small thing in week three, be specific, and ask for the new person's honest view of your company in return.
To give feedback to early hires well, say it early, make it specific and ask for feedback in return. The most common failure is silence: something is noticed in week three, left unsaid, and raised in month four when it has become a pattern.
That failure is easy to understand. The person is new, the issue feels minor and the founder has a dozen other demands. Saying nothing seems kind. In practice it stores up a harder conversation for later, and it deprives the person of the information they need to improve while improving is still easy.
How to give feedback to early hires while it is still small
Timing is most of the skill. A comment in week three is small, specific and easy for both of you. The same observation in month four has hardened into a pattern, carries the weight of everything that went unsaid and feels like a judgement on the person and not on a piece of work.
| Week three | Month four | |
|---|---|---|
| Size of the issue | A single, small thing | A pattern |
| Difficulty of the conversation | Easy for both | Difficult, with history behind it |
| What the person hears | A note about the work | A verdict on them |
| Chance to improve quickly | High | Lower |
The left column is almost always the better deal for everyone. The only thing standing between you and it is the small discomfort of speaking up now.
Say the small thing
You do not need to wait for a formal moment. If you notice something in the third week, say it in the third week, in a sentence or two. The aim is not to hold a review. It is to keep the gap between noticing and saying as short as you can.
A useful private rule is that nothing significant should be saved up for later. If you are carrying something around and rehearsing how to bring it up, it has probably already waited too long.
Be specific, and point at the document
General feedback is easy to give and hard to use. A remark about attitude or quality leaves the person guessing what to change. Specific feedback names the thing, says what you expected and, where possible, ties it to something agreed in advance.
That is where the ninety-day outcome document earns its place. Because the expectations were written down and shared on day one, you can refer to them. Feedback becomes a comparison with something both of you have seen, not a clash between two private impressions. The earlier post on how to write a ninety day role outcome explains how to create that reference.
Specific and general compared
| General | Specific |
|---|---|
| Says something is not good enough | Names the piece of work and what was expected |
| Describes the person | Describes the work or the behaviour |
| Leaves the next step unclear | Makes the next step obvious |
| Cannot be compared with anything | Refers back to what was agreed |
The value of specificity is that it is both kinder and clearer. The person knows exactly what is being asked, and you know exactly what you are asking for.
Include the good, with the same precision
Feedback is not only for problems. When something goes well, say what and why, with the same level of detail. Specific praise tells the person what to repeat. It also keeps the relationship in balance, so that a conversation with you is not always the one that carries bad news.
A new person who hears only from you when something is wrong will start to dread the conversations. A new person who hears about what worked, and what to adjust, learns that talking to you is useful.
Ask for feedback in return
Feedback has to run in both directions. A new person sees your company with clear eyes for about a month, before it starts to seem normal to them. What they notice in that window is information you cannot obtain any other way.
Ask for it directly and early. Ask what they have noticed, what confused them and what they would change. Because you are asking while their view is fresh, you will hear things that will not be visible to them in a few months, and that you can no longer see yourself.
- Ask what they noticed in the first weeks.
- Ask what was unclear or took longer than it should have.
- Listen without defending the way things are.
- Act on at least something, and tell them you did.
The last point matters most. If a person offers an honest observation and nothing happens, they learn not to offer another. If they see a change, they learn that their view counts.
A feedback checklist for the first weeks
Each line below is a box you can either tick or not. If you cannot tick it, that is your next task.
| Check | Why it matters |
|---|---|
| Small, specific feedback has been given within the first three weeks | It keeps the gap between noticing and saying short |
| I have asked what they noticed while their eyes were still fresh | It captures a view that fades quickly |
| An honest review against the ninety-day outcomes is scheduled | It prevents drift |
| Nothing significant is being saved up for later | It prevents the month four conversation |
Run through the list at the end of the third week. It takes a minute and it catches the silence before it sets.
Preparing a comment so that it lands
You do not need a script, but a little preparation helps. Before you speak, decide the one thing you want the person to take away. State what you saw, say what you expected, and then listen. The conversation should leave them clear about what to do next.
It also helps to separate the work from the person. A remark about a particular piece of output is something they can change. A remark about who they are is not, and it invites defence. Staying on the work keeps the conversation useful and keeps the relationship intact.
Finally, choose the moment. A short word soon after the event usually serves better than a large conversation scheduled for later, because the details are still fresh for both of you and the stakes feel lower.
Receiving feedback without defending
When you ask a new person what they have noticed, the hardest part is hearing the answer. Some of it will concern habits you have stopped seeing, and some may touch things you care about. Thank them, ask a follow-up question and resist the urge to explain why things are as they are.
Explaining is tempting and costly. It tells the person that candour leads to a lecture, and they will soon stop offering it. Listening, by contrast, shows that you take the view seriously, whether or not you act on every point.
The same openness underlies the delegation point raised earlier in this series. A new person is often the first to see where you keep decisions that should be theirs. If they tell you, that is useful, and acting on it is the proof that you meant it when you said you wanted people who take things off your plate.
Keep a scheduled, honest review
Alongside the small, frequent comments, put a review against the ninety-day outcomes in the calendar. It is the place where the larger picture is discussed, and because the small things were said as they came up, nothing in it should be a surprise.
The review also guards against drift. Without a date, it is easy to let the period pass and arrive at a decision point with nothing agreed. For the first weeks that set up this process, see how to onboard your first employees.
What this does for the team
Early hires watch how feedback is handled. When a founder addresses issues promptly and kindly, the rest of the team learns that standards are real and that problems are raised openly. When issues are ignored, strong people notice and quietly recalibrate.
That is one reason delay is costly. A weak situation left alone affects the people who are doing well, because they are watching to see whether you will address it. Part of what you are doing when you give feedback early is protecting them.
When feedback does not change anything
Sometimes the comment is given, understood and nothing shifts. Then the next step is a clearer conversation, not a longer wait. The reasoning is in how to tell a hire is not working, which sets out why acting quickly is better for everyone.
Common mistakes
- Silence. Saying nothing in week three and raising it in month four.
- Vagueness. Remarks the person cannot act on.
- One direction only. Giving feedback and never asking for it.
- Saving it up. Waiting for a formal review to say things that could have been said sooner.
- Asking and ignoring. Collecting views and changing nothing.
Frequently asked questions
How soon should I give feedback to a new hire?
As soon as you notice something, which for many issues means within the first three weeks. Small and specific comments are easier for both of you than a late conversation about a pattern.
What if the issue feels too minor to mention?
That is the reason to mention it now. A minor issue left unsaid tends to become a pattern, and a pattern is much harder to discuss.
Why ask a new hire for feedback about my company?
Because they see it with clear eyes before it becomes normal to them, and what they notice cannot be obtained any other way.
Should feedback refer to the role document?
Yes. A document agreed in advance gives feedback something concrete to point to, so it is a comparison and not a disagreement about impressions.
The full method, with the checklists, is in The First Ten Hires Playbook, a free 33-page playbook.