Why I track EVERY changes in my community (and how I can do it better)
I'm getting a bit known around here and on Skool for advocating MVP, feedback loops and all ^^ Mind me, after 15+ in the startup world, that became a second nature :) Running a Skool community is also a process of trial and error. I rewrite my about page, adjust my VSL (this is what I hate the most btw), or change up my onboarding or DM script, then check how it works. And if I'm not tracking what you change and why, i'm just guessing. And guessing in business is a no-go zone. So I track (not efficiently enough, more on that later) everything I change or tweak and try to see my community as a living system. Every update I make could have a effect, so I track (on Notion) all versions of: - My bio - My communities descriptions - My communities about pages - My welcoming questions - My Auto-DMs - My follow-ups OK this is where I stop to highlight that, the mechanic's car always being broken, I don't track as efficiently as I should. Because I should have a sh*t ton of tracked metrics on how many calls I took, my conversion rate, and so on. (which is dumb because I love analyzing data ๐คท) I version every change I make, but I still rely on my memory to know how many members I had, where I stood out in discovery, what my conversion rate was (that one being a 7-day rolling window it's a bit tricky anyway), etc.. So, don't be like me, don't do things halfway! Please, keep track of: - What did you change? (be specific) - Why did you change it? (what were you trying to improve?) - What happened next? (better? Worse? No changes?) The point is always to test, learn and adapt (the famous Deming's wheel, Plan, Do, Check, Act) To stop making random changes and start learning what works. The Deming's wheel and the whole agility methodology is made to "capitalize on experience". When something works, you can replicate it. When it doesnโt, youโll know why. I'm starting tracking my data impacts better, (better late than never, even if IRL that can cost you a LOT), with a database linking the changes to Skool's main KPIs.