The article should be my text output rather than a file write, per the generation format. Here it is:

A new person walks into your business on their first day and, for a few short weeks, they can see something you cannot. They notice the double handling in your quoting process. They wonder why the price list lives in three different spreadsheets. They watch a customer interaction go slightly sideways and think, quietly, that seems avoidable. Then the weeks pass, they learn the ropes, and that outsider view quietly disappears. They stop noticing, because now it is just how things are done here.

I have hired plenty of people across seventeen years in electrical wholesale, and for most of that time I treated onboarding as a one-way street. I told the new person how we did things. It took me far too long to work out that the traffic should run both ways. The most valuable thing a new hire brings is not on their CV. It is the fact that, for a brief window, they have not yet been trained to accept your blind spots. This article is about how to capture that, cheaply and deliberately, with a structured conversation at the 30-day mark that I have come to think of as the fresh eyes debrief.

Why the window closes so fast

The whole reason this needs to be scheduled rather than left to chance is that the useful perspective has a short shelf life. New hires normalise to existing processes within roughly the first month or two. They adapt, because adapting is what you want a new employee to do. The trouble is that adaptation and forgetting are the same process viewed from two angles. Once someone has queued at the broken printer forty times, they stop seeing it as broken. It becomes background noise, the same way it did for you.

This is why I am firm about the timing. If you wait until the three-month review to ask what felt clunky, you have missed it. By then your new hire has been quietly worn smooth by your existing habits, and the honest answer you will get is a shrug. Thirty days is roughly the sweet spot. Long enough that they have seen the real work, not just the induction slideshow, but early enough that the contrast between your business and wherever they came from is still sharp in their mind.

The idea of a fresh eyes report is not something I invented. It has been kicking around in larger organisations for a while, and there are ready-made templates for running one as part of induction Klaxoon (n.d.). The problem is that those versions assume a formal HR function, a template library, and a culture team to process the output. If you run a business with eight people and you are also on the floor doing the work, that scaffolding is not just unnecessary, it is a barrier. What follows is a lighter version built for the way small businesses actually operate.

What the existing resources get wrong for small business

Most of what is written about feedback and new employees comes at the problem from the wrong direction for an owner-operator. The bulk of it is about the feedback managers give to new hires: how to run a good first review, how to phrase constructive criticism, how to set expectations. There are entire libraries of example phrases for exactly that Frankli (n.d.). That is useful in its own right, but it is the opposite of what I am talking about. The fresh eyes debrief flips the direction. You are not assessing the new hire. You are asking the new hire to assess the business.

The other thing the big-organisation material assumes is infrastructure you do not have. It assumes a survey platform, an anonymity threshold that works because you have hundreds of staff, and a people-ops person to close the loop afterwards. In a small team none of that holds. Feedback happens in the ute, at the counter, in the ten quiet minutes before opening. So the format has to suit that reality. No portal, no template the new person has to fill in on their own time, just a proper conversation you have deliberately set aside time for and prepared for.

Set the tone before you ask a single question

Here is the part people skip, and it is the part that decides whether the whole exercise works. A new hire at 30 days is nervous. They do not yet know if they have the job for good. They badly do not want to come across as critical, ungrateful, or as someone who turned up and immediately started telling the boss what is wrong. So if you sit them down and say, “Any feedback for me?”, you will get politeness and nothing else. That is not because they have noticed nothing. It is because the risk of speaking up feels higher than the reward.

This is a psychological safety problem, and it does not go away just because your team is small. If anything it is sharper, because in a small business the mistakes are personal and the boss is right there. The research on this is clear that people only speak candidly when they believe it is safe to do so, a point Amy Edmondson has spent a career making Edmondson, via Harvard Business School (2023). I have written more about what that looks like in a small team over on psychological safety in a small business team, because it underpins almost everything about getting honest input.

The practical fix is to say the quiet part out loud. I frame it something like this: “I am asking because your outsider view is genuinely valuable to me, and it has a use-by date. In a couple of months you will be as blind to our quirks as I am. Nothing is wrong with you, and nothing you say here counts against you. I want the stuff that made you go, huh, that is odd.” Naming the purpose does two things. It gives the person permission to be honest, and it makes clear you are asking about the business, not fishing for reassurance.

The four areas worth covering

I keep the debrief anchored to four areas. Ranging too wide gives you mush. These four consistently surface the useful stuff.

The first is processes that seemed inefficient or confusing. This is where the double handling lives, the approvals that make no sense, the steps everyone does out of habit that nobody can explain.

The second is information that was hard to find. Where did they get stuck? What did they have to ask three people about because it was not written down anywhere? A new hire is essentially a live audit of your documentation, and the gaps they hit are the same gaps every future hire will hit.

The third is customer interactions that felt awkward or inconsistent. A new person watching your team serve customers with fresh eyes will notice when two staff members handle the same situation two different ways, or when a script feels off. They have often just come from another business and have a direct comparison in their head.

The fourth is anything they assumed would exist but did not. This one is gold. It catches the tool you never bought, the checklist you never wrote, the handover step that lives only in your head. When someone says, “Oh, I figured there would be a shared calendar for that,” they have just handed you a small, specific, fixable gap.

Specific questions beat an open invitation

A vague “share anything you like” puts the whole burden on the new hire and usually produces very little. A tight set of six to eight questions works far better, because specificity is what gives someone permission to be honest. A pointed question feels like answering a fair request. An open-ended one feels like volunteering a complaint, and most people will decline.

Here is a set I would actually use:

Notice that none of these are yes or no. Each one points at a specific corner of the business and gives the person a concrete thing to react to. The last two, in particular, tend to unlock the honest stuff once the earlier questions have warmed the conversation up.

The Fair Work backdrop

There is a compliance layer worth being aware of, and it quietly reinforces why tone matters. At the 30-day mark, most award-covered employees are still inside their minimum employment period, the window that shapes unfair dismissal eligibility. The Fair Work Ombudsman sets out the framework around hiring and the early stages of employment Fair Work Ombudsman (n.d.). I am not a lawyer and this is not legal advice, so check your specific award and circumstances.

The point for our purposes is not the legal detail. It is that the fresh eyes debrief lands at a moment when the relationship is still being decided by both parties. The new hire is working out whether this is a place worth committing to, just as much as you are. A debrief where you genuinely listen, and then act, tells them this is a two-way street. That signal, sent early, is worth a great deal for retention. It is a far better use of the probation window than a one-sided assessment.

Close the loop or do not bother

This is the rule that makes or breaks the whole thing. The output of the debrief should be a short written summary that you write, not the new hire. It is not their homework. You take fifteen minutes afterwards and jot down what came up and what you plan to do about it. Then, and this is the non-negotiable bit, at least one thing on that list becomes a visible change.

The reason is simple. If a new person tells you the price list being in three spreadsheets is a nightmare, and a month later it is still in three spreadsheets, you have taught them that speaking up is pointless. They will not do it again, and neither will the next person who watches them learn that lesson. Closing the loop is what makes every future round of feedback credible. It is the same principle whether the feedback comes from a new hire, a five-year veteran, or a customer, and I have argued elsewhere that acting on input is the whole game when you have no HR function to lean on, over at acting on staff feedback with no HR team. The evidence on feedback culture consistently points the same way: input that visibly changes nothing trains people to stop giving it Formbricks (2026).

You do not have to fix everything. You cannot. Some of what surfaces will be things you already know and cannot afford to change yet. That is fine, and saying so honestly is itself respectful. What you cannot do is take the feedback, nod, and let all of it evaporate. Pick one thing, do it, and tell the person you did it because they raised it.

From one-off event to ongoing habit

The debrief is a single event, and on its own it is worth doing. But the instinct it builds is the more valuable thing. Once you have run one, you start to notice how much useful operational detail is sitting in the heads of your staff, going uncaptured, every single day. New hires have the sharpest version of that view, but everyone on your team has some of it.

The natural next step is a lightweight, ongoing way to gather that input without the one-off conversation being the only channel. That is the gap I built Business Review 360 to fill: a simple, recurring way for a small team to capture ideas and concerns as they come up, so the good ones do not get lost between the counter and the end of the shift. It is not an enterprise survey platform, and it is not meant to be. It is designed for the owner who has just discovered, via a fresh-eyes debrief, that their team can see things they cannot, and who wants to keep that channel open rather than close it after 30 days.

Start with the debrief. It costs you an hour and a bit of humility. If it works the way it has for me, you will find yourself wanting a way to do it all year round.

References

Edmondson, A., via Harvard Business School Online. (2023). How to build psychological safety in the workplace. Retrieved from https://online.hbs.edu/blog/post/psychological-safety-in-the-workplace

Fair Work Ombudsman. (n.d.). Hiring employees. Retrieved from https://www.fairwork.gov.au/starting-employment/hiring-employees

Formbricks. (2026). Closing the feedback loop: Definition, 5 steps and examples. Retrieved from https://formbricks.com/blog/closing-the-feedback-loop

Frankli. (n.d.). Giving feedback to new employees: 56 examples for managers. Retrieved from https://getfrankli.com/knowledge-centre/giving-feedback-to-new-employees-examples

Klaxoon. (n.d.). Fresh eyes report: A valuable new employee induction tool you can use to identify possible improvements within the company. Retrieved from https://klaxoon.com/community-content/fresh-eyes-report-a-valuable-new-employee-induction-tool-you-can-use-to-identify-possible-improvements-within-the-company/

FAQ

When exactly should I run the fresh eyes debrief?

Aim for around the 30-day mark. That gives the new hire enough time to have seen the real work rather than just the induction, while their outsider perspective is still sharp. New employees normalise to existing processes within the first month or two, so if you wait until a three-month review, the most useful observations have usually already faded into background noise for them.

What if a new hire says nothing is wrong?

That almost always means the setup was off, not that there is nothing to find. Most new people are wary of looking critical or ungrateful so early on. Reframe the conversation explicitly as asking for their outsider view because it is valuable and has a use-by date, make clear nothing counts against them, and lean on specific questions rather than an open “any feedback?” A pointed question about one corner of the business is far easier to answer honestly than a blank invitation.

Do I need special software to run this?

No. The debrief is a prepared conversation and a short written summary you author yourself, so a notebook and half an hour is enough to start. Software becomes useful later, once you decide you want an ongoing way to capture ideas and concerns from the whole team rather than relying on one-off conversations. At that point a lightweight tool built for small teams helps, but it is not a prerequisite for the debrief itself.

Should casual and part-time new hires get a debrief too?

Yes, and arguably they see even more, because they often work across different shifts and settings than you do. The main adjustment is timing: for someone working two shifts a week, thirty calendar days may only be a handful of actual shifts, so gauge readiness by how much work they have actually seen rather than the date on the calendar.

What do I do with the feedback afterwards?

Write a short summary yourself, pick at least one thing you can realistically change, and make that change visible. Then tell the person you did it because they raised it. Acting on even one item is what makes the exercise credible; feedback that visibly changes nothing quietly teaches people to stop offering it, which is worse than never having asked.