Learning in public: creating content while you are still learning

Many would-be membership owners stall on one worry: “Who am I to teach this? I am not the ultimate expert.” Others push ahead but feel like impostors, padding their content with confident claims they are not sure about. Neither is necessary. There is an honest middle path, often called learning in public, where you share what you are figuring out as you figure it out, and invite members along for the journey.

Done well, it can be one of the most relatable forms of membership content there is. Members who are a few steps behind you often learn more from someone who remembers being confused than from an expert who has long forgotten what confusion felt like. The key is to be clear about what you are offering, careful about accuracy and generous with what you discover.

What learning in public is, and what it is not

Learning in public means documenting your own progress on a skill or subject and turning each lesson you learn into something useful for others. It is not pretending to have mastered something you have not, and it is not a diary about your feelings. The value for members comes from three things:

• Recency. You remember the stumbling blocks because you hit them last month.
• Filtering. You read the long manuals, sat through the confusing tutorials and can pass on the parts that mattered.
• Company. Members feel less alone when someone they trust is openly working through the same challenges.

Picture a hypothetical membership for electric bike owners who want to do their own maintenance. The founder, Dev, is not a professional mechanic. He is a keen rider who spent two years learning to service his own bike and now shares each repair he tackles, including the ones that went wrong.

Be upfront about where you stand

Honesty about your level is what makes this approach trustworthy rather than shaky. Say it once, clearly, on your about page and sales page, and repeat it where it matters. Something like:

I am not a professional mechanic. I am a rider who got tired of waiting two weeks for simple repairs and taught myself to do them. Everything here is something I have done on my own bike, explained the way I wish someone had explained it to me. For anything involving the battery or motor electronics, I will always point you to a qualified technician.

That statement sets expectations, tells the right members they are in the right place and draws a firm line around what you will and will not teach.

Formats that suit someone still learning

Some content formats play to the strengths of learning in public:

• Project logs: “I replaced my brake pads for the first time. Here is exactly what I did, what confused me and what I would do differently.”
• Mistake write-ups: an honest account of something that went wrong and how you fixed it. These are often the most valued pieces of all.
• Study notes: a clear summary of a dense manual, guide or course, with your own plain-language explanations.
• Experiments: trying two methods side by side and reporting what happened, clearly labeled as your own small trial rather than a proven result.
• Expert conversations: bringing in people who know more than you and asking the questions your members would ask. Your beginner's curiosity becomes an asset; the planning tips in interviews as member content apply.

Stay accurate when you are not the authority

The risk in learning in public is passing on something wrong with confidence. A few habits protect you and your members:

1. Separate what you did from what is generally true. “This worked on my bike” is honest. “This is the right way” may not be.
2. Check against reliable sources before publishing anything technical, and say where your information comes from.
3. Know your safety limits. Where a mistake could hurt someone or cost them money, send members to a qualified professional instead of improvising.
4. Invite correction. End pieces with a line such as, “If you know a better way, tell me and I will update this.”
5. Correct openly. When you learn you were wrong, update the piece and add a short note saying what changed. This builds far more trust than quietly editing.

Turn your progress into structured lessons

A stream of project logs is interesting, but members eventually want something organized. Every few months, look back at what you have shared and turn it into structure. Dev might group his logs into a path: basic cleaning and checks, then brakes, then gears, then tires and punctures. Each log becomes a lesson, tidied up with what he has learned since.

Your own mistakes also make excellent teaching material once you step back from them. The structure in teaching with case studies and real examples works well for turning a messy repair into a clear lesson with a question for the reader in the middle.

A before-and-after of the same piece

Here is how a learning-in-public piece can go wrong, and how to fix it:

Before: Adjusting your gears is easy. Just turn the barrel adjuster until the chain runs smoothly. Any rider can do it in two minutes.

After: The first time I adjusted my gears, it took me forty minutes and I made it worse before I made it better. Here is what finally worked on my bike: small quarter-turns of the barrel adjuster, testing each gear after every turn. If your chain still skips after ten minutes of this, stop. The problem may be a bent part, and that is a job for a shop.

The second version is longer, but it is honest about difficulty, specific about method and clear about its limits. Members trust it more precisely because it does not oversell.

Your first steps

1. Write a two- or three-sentence statement of where you stand and what you will not teach, and add it to your about page.
2. List five things you learned recently that tripped you up at first.
3. Write one of them up as a project log or mistake write-up, separating what you did from what is generally true.
4. Add an invitation to correct you at the end of each piece.
5. Line up one conversation with someone more experienced than you, built around your members' questions.
6. Every few months, reorganize your logs into a structured path.

You do not need to know everything to be useful. You need to be honest, careful and a few steps ahead, and willing to bring members with you.