Iterative Learning: The Feedback Loop That Accelerates Skill Acquisition [Part 2]

You’ve chosen your real project. You’re building consistently, one hour every day. You’re learning just what you need, exactly when you need it.

This will get you functional. But it won’t make you a master.

The first three steps create the foundation. The next three steps create the multiplier effect – the difference between someone who can do something adequately and someone who’s genuinely skilled.

These are the steps that accelerate your learning exponentially rather than linearly. They’re what separate hobbyists from professionals, beginners from experts.

Let’s get into them.

If you have no idea what I’m talking about here, you probably haven’t read the first two articles yet, so here they are:

1. Why Learning by Doing Beats Traditional Education (And How Schools Keep Us Unprepared)
2. The Only Learning By Doing Framework You Need To Master Any Skill [Part 1]

Step 4: Share Publicly and Get Real Feedback

Fourth step – share your project publicly, get feedback. Feedback is the key step. After building part of the project, even incomplete, there’s a term MVP (Minimum Viable Product) – a product with the minimum set of functions for use. It’s imperfect, without all the planned functions, but acceptable enough to try, touch, and give feedback.

This is important, the most effective way to advance as a person. You get real data from the real world, not fantasies. Fantasies let you down, the brain protects you, deceives you that you’re doing everything right. You can imagine how great everything is, but real light will show something different. Don’t delay with feedback, no matter how uncomfortable it is.

I recommend reading Mark Manson’s book “The Subtle Art of Not Giving a F*ck” – it will help you not care about others’ opinions. Post online, build in public, get feedback, like I do. I write articles, posts, sometimes it’s cringe, but people like them, comment, the material resonates with someone. This gives information about where to move. If material doesn’t get feedback, that’s also information – you’re doing something wrong. Set up a feedback loop, a cycle of feedback with the external world and people, to understand how the project works.

Studies And Data On Sharing Progress

A comprehensive analysis by researcher John Hattie found feedback had an effect size around 0.7-0.79, placing it among the top influences on student achievement. Immediate, specific feedback helps learners correct mistakes and refine techniques more efficiently.

In workplace or practical projects, feedback from users or mentors enables iterative refinement. An early prototype receives criticism, and the creator learns and improves it. The principle of public sharing also has evidence: a 2013 study found that people sharing weight-loss progress on Twitter (back then) lost more weight than those who kept progress private. In that study, every 10 tweets posted corresponded to an additional 0.5% weight loss, indicating social feedback and support improved outcomes.

The principle carries to skill learning: sharing progress publicly can provide encouragement, accountability pressure, and access to feedback from a community. Productivity research noted that declaring goals publicly makes individuals four times more likely to follow through, primarily due to accountability and social reinforcement.

Without feedback, you’re flying blind. You might be practicing the wrong things. You might be reinforcing bad habits. You might be solving problems that don’t actually matter.

Feedback gives you course correction. It tells you what’s working and what isn’t. It shows you the gap between what you think you’re doing and what you’re actually doing.

The discomfort you feel when sharing imperfect work is a feature, not a bug. That discomfort means you care. It means the stakes are real. It means you’re learning for real, not just playing at learning.

Step 5: Iterate and Improve

“I have not failed. I’ve just found 10,000 ways that won’t work.”

— Thomas A. Edison (20th century, American inventor)

Fifth stage – iterative improvement. The first version of the project is only the beginning. If you’re making a program, code for others, improve it iteratively – make a second, third version. If it’s content, improve the content itself. In my first publications I see what doesn’t satisfy me, I try to improve it, not by rewriting the old, but by creating new with changes in mind. You become better, you transform the content, improving part of it each time.

We iteratively improve feedback, the product, the project in gradual steps. Imagine what will happen in a year of active improvement – you’ll become experienced, projects will turn out well.

The first version of my product ANTIghostwriter was not as good as I wanted it to be. But I published it and started selling. The very first sale was a disaster, because I received feedback (step 4 btw) with some mean words about my speaking in videos. I’m not a native English speaker and recording such types of videos (screencasts) was new for me. So I rewrote the scripts for every video in the product, reshot all of them, additionally checked all the grammar with AI, and published a new version of it. But this time with confidence, because it was a huge quality improvement.

ANTIghostwriter btw is my content creation system that can help you consistently create a lot of content, and with the power of AI repurpose it for different platforms. If you’re building your personal or corporate brand, check it out, it will save you thousands of dollars on copywriting and days of precious time.

Kaizen & Mastery

The notion of continuous improvement is a cornerstone of skill mastery. Anders Ericsson’s research on expertise found that deliberate practice – which involves constant feedback and refinement – is what separates elite performers from others. Iteratively improving a project is essentially a form of deliberate practice: each iteration targets weaknesses from the previous attempt. Over time, these cycles produce significant skill gains.

This aligns with the concept of “kaizen” (continuous improvement) in professional domains. There’s abundant qualitative evidence: writers produce multiple drafts to improve clarity, and each new draft incorporates lessons from the last. Software engineers release iterative versions (v1.0, v2.0, v.342.869453.974906857345) and in the process become more proficient.

The key insight is this: your first version teaches you what your second version should be. Your second version teaches you what your third version should be. Each iteration builds on the lessons of the previous one.

This is how expertise develops. Not through one perfect attempt, but through many imperfect attempts that gradually get better.

Most people never get good at anything because they never get past version one. They build something once, decide it’s “good enough,” and move on. Or worse, they abandon it because it’s not perfect.

Don’t do that.

Commit to iteration. Commit to making each version better than the last. Not perfect – just better.

After a year of this approach, you’ll look back at your early work and barely recognize it. The gap between where you started and where you are will be enormous. That’s not because you had some breakthrough moment. It’s because you improved a little bit, consistently, over and over again.

Step 6: Teach Others to Cement Your Knowledge

Sixth point – teach, transfer knowledge and skills. There’s no better way to learn than by teaching someone else. You condense information, present it as a structure so another person can apply it and do a project. This is the best way to learn.

There might be impostor syndrome, but these are psychological aspects. Manson’s book helps partially, but it’s better to work on your psyche. Life is a big experiment, a project. All people, successful or not, initially don’t understand what they’re doing, but over time they get data, information, improve skills iteratively, gradually. Then they teach others, while you stand still. Teach, it’s a useful final step.

This is a well-known phenomenon sometimes called “the protégé effect.” Educational psychology experiments have confirmed that students who tutor or prepare to teach others show higher understanding and retention. In a controlled study, participants who expected to teach the material later recalled more and organized their knowledge better than those who expected only a test.

The act of teaching forces you to clarify and structure knowledge, identifying any gaps. As far back as Seneca, educators observed “while we teach, we learn,” and modern research validates this folk wisdom. A 2014 study published in Memory & Cognition found that simply anticipating having to teach led students to adopt more effective learning strategies and remember more.

Furthermore, a 2018 meta-analysis of learning-by-teaching methods found significant benefits for the learner-turned-teacher in terms of mastery of the content. Teaching works because it combines practice, retrieval, and organization, which are all excellent learning strategies.

How Does Teaching Work

When you teach, you can’t hide behind vague understanding. You have to make things clear and concrete. You have to anticipate questions. You have to organize information in a logical sequence.

This process reveals all the gaps in your own knowledge. Every time you struggle to explain something, you’ve found something you don’t actually understand as well as you thought. And now you know exactly what to go learn more deeply.

Teaching also forces you to think about the subject from different angles. Different students have different questions, different confusions, different ways of thinking. Addressing those differences deepens your own understanding.

And there’s a bonus: teaching builds your reputation and network. When you help others learn, they remember you, they value you, they want to work with you, learn from you, collaborate with you.

You don’t need to be a world expert to teach. You just need to be one step ahead of the person you’re teaching. If you’ve spent a month learning something, you can teach someone who’s just starting. If you’ve spent a year, you can teach someone who’s spent a month.

Start small. Write a blog post explaining something you just learned. Answer questions in online forums. Create a tutorial. Make a video. Help a friend who’s trying to learn what you know.

The act of teaching will make you better at the thing you’re teaching. Guaranteed.

The Complete Learning By Doing Framework

Let me pull back and show you how all six steps work together as a system.

1. Step 1: You choose a real project. This gives you direction and purpose.
2. Step 2: You build consistently. This creates momentum and compounds your learning.
3. Step 3: You learn just-in-time. This makes your learning efficient and contextual.
4. Step 4: You get feedback. This shows you what’s working and what needs to change.
5. Step 5: You iterate. This turns feedback into actual improvement.
6. Step 6: You teach. This cements everything you’ve learned and reveals gaps.

Then you loop back. You start a new project, or a new version of the same project. You build on what you learned, you seek new feedback, you iterate again, you teach more.

Each cycle through this framework makes you more capable, builds on the previous one, and compounds your skills.

This is how mastery develops. Not through one heroic effort, but through many small cycles of building, feedback, and improvement.

And the beauty of this system is that it works for virtually any skill. Programming, writing, design, marketing, music, art, public speaking – the framework is the same.

Real project, consistent building, just-in-time learning, public feedback, iterative improvement, teaching others.

Do this for six months and you’ll be competent, do it for a year and you’ll be skilled, do it for several years and you’ll be an expert.

Real-World Examples of This Framework in Action

Consider Elon Musk. He learned rocket science not through formal schooling but by reading textbooks and immediately applying knowledge to design rockets. His approach with SpaceX involved rapid prototyping – build rockets, test them (sometimes to failure), learn from the errors, and iterate. Musk has said that “you can learn anything you need to know for free on the internet.” His case demonstrates how iterative practical experiments sped up his acquisition of expertise.

Look at High Tech High, a network of public charter schools in California known for project-based learning. Students learn through interdisciplinary projects – building underwater remotely operated vehicles in marine biology class or writing and publishing books in humanities. There are no AP exams or rote lectures; instead, students present their projects in public exhibitions. The result has been high levels of student engagement and strong college admission rates.

Or consider the medical residency system, which is essentially “learn by doing.” After medical school, resident doctors spend years practicing in hospitals under supervision, gradually taking on more responsibility. The apprenticeship model is grounded in the belief that only hands-on experience with real patients can truly develop a doctor’s skills. Studies show that residents improve through repeated practice with feedback from attending physicians. The mantra is “see one, do one, teach one” – exactly this framework in action.

These examples span different fields, different contexts, different skill levels. But they all follow the same pattern: real projects, consistent practice, feedback, iteration, teaching.

What Holds Most People Back

Now let me address the elephant in the room. Most people won’t actually do this.

They’ll read this article, think “this makes sense,” and might even start a project. But they won’t finish, won’t iterate, won’t share publicly, won’t teach.

Why not?

Usually, it comes down to one of three fears:

Fear of judgment

• What if people think my work is bad?
• What if they criticize me?
• What if I look stupid?

This is where Manson’s book helps. You need to not care about the opinions of people who aren’t in the arena with you. The only feedback that matters is from people who are actually doing the thing, or from the users who need what you’re building.

Everyone else’s opinion is just noise. Ignore it.

Fear of failure

• What if I can’t do it?
• What if I’m not talented enough?
• What if I waste all this time and don’t get good?

Here’s the truth: you will fail. Your first versions will be bad. You will waste time on approaches that don’t work.

That’s not a possibility. That’s a guarantee.

But that’s also how learning works. Every failure teaches you something. Every bad version shows you what good versions need. Every wasted hour builds pattern recognition that makes future hours more efficient.

Life is a big experiment, a project. All people, successful or not, initially don’t understand what they’re doing. But over time they gather data, information, improve skills iteratively, gradually.

Failure isn’t the opposite of success, but it’s the path to success.

Fear of commitment

• What if I start this and then can’t finish?
• What if I get bored?
• What if something else comes up?

This is actually the most reasonable fear. You should be thoughtful about what you commit to. Your time and attention are finite.

But here’s the thing: you don’t need to commit forever. You just need to commit to the next cycle. One project, one iteration, one teaching moment.

After that, you can decide if you want to continue or pivot to something else.

The framework doesn’t trap you. It gives you a structured way to learn quickly, so you can decide if this is something you want to pursue further.

The Truth About Mastery

“The essence of knowledge is, having it, to apply it; not having it, to confess your ignorance.”

— Confucius (c. 5th century BC, Chinese philosopher, from the Analects)

Let me end with this: there’s no secret to mastery, there’s no shortcut or hack that lets you skip the work.

But there is a path. A clear, proven path that works for virtually any skill.

1. Real project.
2. Consistent building.
3. Just-in-time learning.
4. Public feedback.
5. Iterative improvement.
6. Teaching others.

Six steps. Not complicated. But they require commitment.

Every day you follow this framework, you get better, every cycle makes you more capable, every iteration builds on the last.

And unlike traditional education, where you spend years studying before you can do anything useful, this framework lets you create value from day one. Your projects matter. Your learning has immediate application. Your skills develop in the context of real use.

That’s the difference. That’s why this works when traditional approaches fail.

So stop waiting, stop preparing, stop looking for the perfect course or the perfect moment.

Choose your project. Block your hour. Start building.

The world doesn’t need more people who know things in theory. It needs people who can actually build, create, and solve real problems.

Become one of those people.