Your Team Knew Before You Did

Most problems reach a leader late, once they show up in a number, even though people on the team saw them coming. That gap between what the team knows and what reaches you is where a lot of avoidable damage happens, and it isn't closed by asking people to communicate more. It's closed by building the paths that feedback travels. Feedback Loops is that system, and here's how it works.

Your team knew before you did

The client who'd been frustrated for weeks, the process that broke two teams ago, the risk three people saw coming: in almost every case, someone on your team knew first, and what they knew took too long to reach you. The same issues keep surfacing, because nothing in the business is built to move them while they're still small and cheap to fix.

This is rarely a people problem. It's the absence of a system, and the absence has a specific shape you can fix.

Why telling people to speak up doesn't work

You've probably already tried the obvious fix: told people to bring you problems early, added a couple of meetings, asked for more transparency. The important things still reach you late, because asking people to speak up does nothing on its own until they can see where an issue goes once they raise it, who acts on it, and what happens next.

When that's unclear, people hold what they know, because speaking up with no idea what will come of it feels both risky and pointless. Feedback fails for one plain reason: the business never built a way for what people know to reach the people who can act on it.

Feedback needs three directions

Feedback Loops is the system you design so that when someone sees something, they know exactly where it goes and what happens next. It runs in three directions, and most businesses build only the first.

Upward, from the team to you

Information, risks, and ideas reach you early and in the open, through structures like an open feedback forum where the team brings problems paired with recommendations, a short anonymous pulse survey, or a skip-level session where you hear from people beyond your direct reports.

Downward, from you back to the team

You close the loop by naming what you heard and what you're doing about it, through a what-we-heard update, a town hall, or a simple closing-the-loop message, so people can see their feedback was heard and used.

Across, between teams

Teams surface and resolve the issues between them directly, through a cross-functional review, a project retrospective, or a handoff review, so a problem between two teams gets handled by those teams and stops coming back to you.

Most businesses build only the upward direction, and even that half-heartedly, so feedback goes up and nothing visible comes back, and the issues between teams keep coming to you instead of getting solved where they happen. Building all three is what gets you the truth in time to use it.

Make it safe, and give every issue the same shape

A path tells people where feedback goes; safety decides whether they use it. People hold what they know when they expect to be blamed for it, judged for it, or have it held against them later. So before you run any of these structures, agree with the team on how you'll protect that safety: focus on the problem and its impact more than the person who raised it, agree what stays private, treat an early warning as doing the job well so it's never held against anyone, and make sure whatever gets raised gets a response.

Safety gets people to speak, and a shared format makes what they say easy to act on. Ask everyone to bring an issue in the same three parts: the problem, its impact, and a recommendation. In that shape, "onboarding is a mess" becomes "onboarding emails go out two days after a client signs, so new clients hit their first task with no guidance and week-one tickets are up, and we should trigger the emails off the signed contract instead." The same issue now arrives ready to act on.

Close the loop, or it goes quiet

Getting the information is only half the work, and closing the loop is the half most leaders skip. Closing a loop means showing the person that what they raised was heard and acted on, whether you follow up with them directly, write up what changed and send it to everyone it affects, or point to the thing that's different now because they spoke up. When people see that happen, they bring you the next thing. When they never hear back, they read it as talk and stop raising things.

There's a simple test for whether a loop is closed: can people name something that changed because they spoke up? If they can't, the loop is still open, no matter how much was said.

Where Feedback Loops fit

Feedback Loops is one of the operational tools of the Leadership Operating Flywheel, the four-stage system your team runs on. It's how the Collect stage works in practice, the part where what's really happening reaches you early instead of late. It works best alongside the others: a team that shares one direction, knows how decisions get made, and learns from the work as it goes. Each of those tools strengthens the rest, and together they're what lets the team run without you in every decision. On its own, a feedback system that works well is the difference between hearing about problems in time to act and hearing about them once they've already cost you.

Download the free Feedback Loops Blueprint

We put the whole system into the Feedback Loops Blueprint. It has the three directions with a menu of structures to choose from, the safety agreement to set first, the three-part format for issues, the four ways to close a loop, and a worksheet to design one structure in each direction this week.

→ Download the free blueprint: loyaltyops.com/feedback-loops

If you want to build these paths alongside a room of other leaders working on the same thing, that's part of the work inside the Leaders Mastermind.

FAQ

What are feedback loops in a business?

They're the built paths that carry information between people, so problems and ideas reach whoever can act on them. In a healthy business, feedback runs in three directions: upward from the team to the leader, downward from the leader back to the team, and across between teams.

What are the three directions of feedback?

Upward (the team raises risks and ideas to leadership), downward (leadership names what it heard and what it's doing about it), and across (teams resolve the issues between them directly). Most businesses build only the upward direction, which is why feedback often goes up and nothing comes back.

How do I build a feedback culture?

Build the paths, not just the encouragement. Set up two or three upward structures, two or three downward, and one or two across; agree on a safety standard first; ask for issues in a problem/impact/recommendation format; and close every loop so people see that raising something leads to a response.

Why does feedback stop after a while?

Usually because the loop never gets closed. When people raise things and never hear what happened, they read it as talk and go quiet. The fix is to visibly show what changed because someone spoke up, which is what keeps people bringing the next thing.

How is this different from just running surveys?

A survey is one upward structure. On its own, it collects information without a path back or a way to resolve cross-team issues, so it often goes quiet. Feedback Loops builds all three directions and, most importantly, closes the loop, which is what makes any single structure keep working.