Most people hear from their manager a handful of times a year, and almost always at the worst possible moment: the annual review. By the time it arrives, it is not feedback anymore. It is a verdict. Nothing in it is a surprise to the manager and everything in it is a surprise to the employee, which is exactly backwards.
Feedback fails for two separate reasons, and most advice only addresses one of them. The first is that there is no relationship strong enough to hold it, so even accurate feedback lands as an attack. The second is that there is no system to make it happen, so it defaults to once a year whether anyone means it to or not. You need both. A good relationship with no system produces warmth and no growth. A good system with no relationship produces resentment. This guide is about building the two together, and it leans on two people at Trainual who have quietly turned feedback into their edge: Jami Hartman, our VP of marketing, and Mallory, our director of marketing, who started as a community manager and now runs a team of her own.
What employee feedback really is
It helps to be precise, because "feedback" gets used for four different things that need different handling.
Employee feedback is specific, timely information about how someone is performing, shared to help them adjust or keep going. That is it. It is not the same as praise, which affirms a person but does not tell them what to change. It is not coaching, which develops a skill over time through practice and questions. And it is not a performance review, which formally evaluates someone against expectations over a set period. Feedback is the small, frequent input that lives in between all of those, the running commentary that makes the review a formality instead of a shock.
Naming those distinctions matters, because most "feedback problems" are really category errors: a manager who thinks weekly praise counts as feedback, or who saves all their real input for a review that comes twice a year.
Why most feedback doesn't land
When feedback fails, it usually fails in one of four familiar ways. It arrives too late, weeks after the moment it refers to, when nobody can act on it. It is too vague to use, some version of "be more strategic" with no example attached. It only travels one direction, from manager down, so the employee never learns to ask for it or give it back. Or it comes from someone the person does not trust yet, which turns even fair feedback into a threat. Fix the timing and the specifics and you have solved the mechanics. Fix the trust and the direction and you have solved the harder half. The rest of this guide takes them in that order: relationship first, then system.
Part one: the relationship comes first
There is a phrase worth stealing from sales, connect before you correct. You cannot give hard feedback to someone who does not believe you are on their side, and belief like that is not built in the conversation where you deliver the feedback. It is built in all the ordinary moments before it.
Jami puts the relationship at the center of everything. "Your relationship with your direct reports is the most important thing," she says, "your ability to communicate with them through tough times, pivots, unexpected things." The important word there is communicate, in both directions, long before anything goes wrong.
The catch is that the relationship does not build itself. Rapport is scheduled, not spontaneous. It comes from dedicated time, regular check-ins, and skip-level conversations that a manager puts on the calendar and protects. Jami takes every member of her team seriously as a person first, which is what makes them comfortable enough to hear the hard thing later.
Transparency is what earns the benefit of the doubt. When a team knows their manager is consistently straight with them, they extend trust automatically, because they know the feedback is coming from an honest place rather than a political one. "If your team knows that you are transparent with them," Jami says, "they are inherently going to trust you." That trust is the interest you earn on a hundred small honest moments, and it is what lets a piece of tough feedback land as help instead of ambush.
Then there is the part most managers skip: knowing what genuinely motivates each person, so feedback connects to something they want. Not what you assume motivates them, what truly does. Jami's method is simple and worth copying. First, ask. Most high performers will tell you their north star is impact, but underneath that, some are driven by comp, some by title, some by influence, some by the chance to work on a different part of the company. Then, watch. If someone says they want to grow into data work but never picks up the data projects you hand them, their actions are telling you something their words are not. Feedback that connects to what a person genuinely wants stops being a correction and becomes a path to the thing they are already chasing.
The new-manager trap
Here is where good intentions do the most damage. New managers tend to over-protect. They soften the message, they withhold the stretch project, they avoid the clear feedback because they do not want to overwhelm someone. It feels like kindness. It is the opposite.
"One thing that new managers do is they will try and protect their team a little bit too much," Jami says, "not give the clear feedback, or they won't give them a certain project because they don't want to overwhelm them." The problem is that high performers want to be pushed. Protecting them from the stretch is protecting them from the growth, and they feel the ceiling immediately. If you manage people for the first time, the instinct to shield your best people is the instinct to distrust.
The bigger unlock behind all of this is where a manager spends their attention. Early on, Jami did what most of us do: she obsessed over her lowest performers, worried about them on weekends, poured her hours into moving them from struggling to adequate. The math on that is bad. "Taking someone that's an underperformer to meeting expectations, that's real and that's great," she says, "but taking someone who's great and making them exceptional has exponential gains." When she flipped her time toward her highest performers, the whole team leveled up, and, in her words, it got a lot more fun. If you take one thing from Jami, take this: your feedback should follow your best people, not just your struggling ones.
Part two: the system that makes it consistent
Relationship gets feedback heard. A system gets it to happen at all. And Jami's system is almost aggressively simple, which is exactly why it works.
Every month, every direct report gets written feedback from her. No exceptions. It is two sections: where you're shining and where to dig in. It is bullets, not paragraphs. And it is specific, a project she is unclear on the status of, a moment in a meeting where someone could have shown up better, a metric worth chasing next. That is the entire format. "Every month all of my direct reports get feedback from me," she says. "It's all bullets. It's two sections. Here's where you're shining and here's where to dig in."
The origin story is the best argument for it. Jami did not always do this. She started because Mallory asked her to. Mallory, a self-described feedback lover, came to her and said she would love regular monthly feedback. Jami's honest first reaction was that she did not have time to write feedback for everyone every month. And then Mallory said the thing that unlocked it: just bullets. Make it easy. "I can do bullets once a month," Jami decided, and the impact was immediate enough that it became non-negotiable. She now protects it fiercely. She tells a story about almost skipping it right before a holiday break, thinking nobody would need it that week, and then catching herself: no, Mallory will want it, keep going.
What the monthly note buys you is the thing every manager wants: reviews stop being about course-correction and start being about upleveling. "When performance cycles or reviews come around, they know exactly where they stand," Jami says. Nobody is blindsided, because you have been telling them the truth in small doses all year. The formal review becomes a summary of a conversation you have already been having, which is how it is supposed to work.
If you want the one-word version of why this matters, Jami's answer is accountability. High performers cannot stand working alongside people who are not accountable, and consistent feedback is how accountability gets made visible and even across a team. The monthly note is not busywork. It is the mechanism that keeps a high-performing team high-performing.
How to give feedback in the moment
The monthly note is the system. In-the-moment feedback is the reflex, and the cleanest structure for it is SBI: Situation, Behavior, Impact. Name the situation ("in this morning's client call"), describe the specific behavior without judgment ("you jumped in before the client finished their question twice"), and state the impact ("it read as impatient, and they went quiet after"). No labels, no character assessment, just the sequence. SBI works because it is specific and hard to argue with, and because it separates what happened from what it meant.
A few rules of thumb around it. Give it close to the moment, while it is still real. Praise in public, correct in private, always. And when a conversation goes sideways, when someone gets defensive, stop selling your point and get curious instead. Ask what they were seeing that you might be missing. Defensiveness usually means the person feels unsafe, not that they disagree, and the fastest way through it is to lower the stakes rather than raise them.
How to receive and request feedback
Here is the half of the conversation almost nobody teaches: feedback is a two-way street, and the employee owns their side of it. The single highest-leverage move an individual can make is to ask for feedback on something specific, rather than waiting for it to arrive. "How did that presentation land?" gets you something useful. "Any feedback for me?" gets you "you're doing great."
Mallory is the proof. The entire monthly-feedback system that Jami now considers her edge exists because Mallory asked for it. One person, asking for something specific, changed how her manager manages, and by extension how an entire team operates. That is the leverage hiding in a simple request. If you report to someone, do not wait for the system to reach you. Build your own by asking.
This is also the part of feedback that has been hardest to make consistent, because asking depends on the employee remembering to ask and the manager remembering to respond. It is exactly the kind of thing that should live in a system rather than in good intentions, which is a large part of what we have been building toward with Performance suite, our forthcoming tool for making feedback, requests, and review cycles one connected practice instead of three disconnected ones. More on that at the end. You can join the waitlist if you want to be early.
Feedback across generations
One more relationship variable worth naming: people across different generations often want feedback delivered differently, in tone, in channel, in frequency, and a manager who flexes to that gets heard by more of their team. Jami sees the range of perspectives on her team as a strength rather than a friction, and the skill is reading what each person needs rather than defaulting to how you like to receive it yourself. We go deeper on this in [our guide to coaching across generations]([LINK: multigenerational coaching piece, confirm slug]).
Feedback templates you can steal
These are built to copy and paste. Keep them short; the brevity is the point.
The monthly note (Jami's two-section format)
Where you're shining
- [Specific win, with the project or moment named. "Your handling of the X launch, especially the way you caught the tracking issue before it shipped."]
Where to dig in
- [Specific, themed area with one example. "Meeting presence: in the Y review you had the right answer but waited to be asked. Bring it earlier."]
In-the-moment praise (SBI)
- In [situation], you [specific behavior], and the impact was [result]. That is exactly the standard. Keep doing it.
In-the-moment correction (SBI)
- In [situation], I noticed [specific behavior]. The impact was [result]. Here is what I'd try next time: [adjustment]. What did you see from where you sat?
Requesting feedback (for the employee)
- I've been working on [specific skill or project]. Where did it land for you, and what is one thing you'd have me do differently next time?
How to train your managers to do this
Here is the uncomfortable part. Everything above works beautifully for Jami, and it will keep working right up until Trainual has more managers than Jamis. A practice that lives in one exceptional manager's head is not a system. It is a single point of failure. The whole thing only scales if it is written down, taught, and expected, rather than left to whichever managers happen to be naturally good at it.
That is a documentation-and-training problem, and it is the one Trainual was built for. Write the feedback practice down as an actual process, the monthly cadence, the two-section format, the SBI structure, and assign it as training to every manager, tied to their role, so it is part of what managing here means rather than a suggestion. Jami herself credits documented, shared expectations as one of the most powerful things a company can give its people. Feedback is no different. Make the standard explicit, and you stop depending on getting lucky with hires. [Start from a feedback training template]([LINK: feedback training process template, confirm URL]) if you want a running start.
Feedback, reviews, and career paths are one system
The reason feedback breaks in most companies is that it is treated as three separate things, the offhand comment, the annual review, and the vague conversation about someone's future, run on three separate schedules by three separate levels of intention. They are not three things. They are one system. Monthly feedback feeds the review. The review feeds the career path. The career path gives the feedback something to aim at. When they connect, growth stops being an event and becomes a default.
That connected system is what we are building with Performance suite, and this article is the first time we are talking about it publicly. It is not out yet, and we are not putting a date on it. But if the way Jami and Mallory work sounds like the way you want your team to work, we would love to have you in early.
Want to be first to see it?
👉 Join the Performance suite waitlist and we'll reach out the moment it's ready.
Want to build the habit now?
👉 See how teams document and train the way they run so good management scales past a few great managers.
