Let's say I challenged you to get good at something you've never done before. One option is shooting free throws. The other is hiring new employees. Which do you think you'd pick up quicker?
Free throws, obviously. And the reason is mostly the feedback loop.
Shoot a free throw and you know within a second whether it went in. You adjust and try again. Hire a manager and it might take months - or years - before you figure out whether you got it right. Even then, half the time you still can't tell how much was the hire vs. the team they inherited, the market, luck, whatever else was going on.
You improve at the speed of your feedback. More precisely, at the speed and quality of it. Once you start noticing that, a lot of skills and decisions start looking less like talent problems and more like loop problems.
Short loops compress learning
Short feedback loops give you more reps, and you usually catch mistakes sooner - before they compound. That compresses the learning curve. It's also why some domains get so competitive (sports especially). Everybody else is getting those same reps, and they're getting them constantly.
Coding is a clean example. You write something, run it, watch what happens, change it, repeat - usually within a few minutes. Changing a company culture, raising a child, picking an executive: you might wait years before you know if your judgment was any good.
Short loop
Long loop
Same cycle either way - act, observe, update. What changes is how long you wait, how clear the signal is, and whether you can actually connect the result back to what you did.
Easy environments and hard ones
Some environments make this almost unfair. Clear rules, repeatable situations, quick accurate feedback - golf, chess, a lot of crafts. You get a huge number of attempts and you know pretty quickly how you did.
Other environments are the opposite. Business, investing, leadership, hiring. Feedback shows up late, noisy, or just wrong. You don't get clean reps. And most of the work that actually matters lives here, which means "just practice more" isn't really a strategy. You have to get better at learning from worse information.
Know your loop
The useful habit is looking at a skill or decision and asking what the feedback loop actually looks like. A few concrete properties matter more than the rest:
Latency - how long until feedback arrives? Seconds, weeks, years?
Frequency - how many repetitions do you actually get? You can shoot hundreds of free throws in an afternoon. Finding the right investor happens a handful of times in a career, if that.
Fidelity - does the feedback measure what you care about, or are you tracking a proxy that only vaguely relates to the real goal?
Attribution - can you connect the result to a given decision? Revenue went up after a reorg. Was it the reorg, or the product launch that shipped the same quarter?
Cost - how expensive is each attempt? Cheap attempts invite experimentation. Expensive ones make people freeze, or overfit to one data point. Would SpaceX have made it with half the capital?
Reversibility - can you recover after being wrong? Shipping a feature behind a flag is reversible. Signing a five-year contract, or making a very public bet, often isn't.
These properties sit on different parts of the loop:
Latency is the wait between action and feedback. Fidelity and attribution are about the signal - is it clean, and does it clearly point back to what you did? Reversibility is whether the update can actually change the next action, or whether you're locked in. Cost and frequency are more about the cycle as a whole: how often you get to go around, and what each lap costs.
Look at things this way for a while and you'll start noticing where a loop is weak. That's usually where you're stuck.
Manufacture shorter loops
People who get good at long-feedback work usually aren't just more patient. They're building shorter loops inside the long one.
They don't wait five years to learn whether a strategy worked. They create intermediate signals along the way. In practice that tends to look like:
Make smaller bets. A pilot, a prototype, a limited rollout. Same direction as the big decision, but cheaper and faster to learn from.
Track leading indicators, not just the final outcome. Usage, retention, hiring pipeline quality - whatever tends to move before the thing you actually care about.
Write predictions down beforehand. "I think this will do X by Y date, because Z." When the result finally shows up, you have something to compare against. Without that, it's too easy to rewrite history into a story where you basically knew all along.
Review the decision separately from the outcome. A good process can produce a bad result. A bad process can get lucky. Grade yourself only on outcomes and you may just be amplifying noise.
Update before you're certain. Waiting for the final result often means waiting too long. Adjust as intermediate signals come in.
Long loop
Versus the same strategy with a manufactured loop you can run many times before the final outcome arrives:
Manufactured loop
When feedback is slow, patience alone doesn't cut it. You have to find ways to learn before the final result arrives.
Fast feedback can still teach the wrong lesson
Short loops aren't automatically good. A tighter loop makes you improve quickly at whatever it rewards (anyone who's trained an LLM has seen this). That doesn't mean it rewards the right thing.
Social media, gambling, click-through rates, short-term revenue - all of these give you immediate feedback that can feel positive at first. They're also excellent at training you to optimize the proxy until the proxy is the goal. More likes, more clicks, more bookings this quarter... and somehow less of what you actually wanted.
There's a related problem with local maxima. When the loop is fast and the current approach seems to be working, you keep doing the same thing. You stop trying anything structurally different, because the short loop keeps telling you you're on the right track. Until you plateau.
Speed isn't the only lever. If the signal is fast but wrong, you'll get worse at the thing that counts while getting better at the thing that doesn't.
Learning when the world is slow
Anyone can improve when the result is immediate. Free throws, code, games with clear scores - the loop does a lot of the work for you.
The harder part is improving when consequences show up months or years later. Which, inconveniently, is most of the decisions that matter - who you hire, what you build, which strategy you commit to, or how you raise your kids.
Know the loop you're in, and which parts of it are working against you. When the real feedback is far away, manufacture something shorter in the meantime. And don't confuse a fast proxy with the thing you actually care about.
Good judgment is keeping learning even when the world is slow to tell you whether you were right.