THIS IS YOUR DIRECT LINE TO IMPROVEMENT. No surveys. No forms. No "we'll consider it." Just: Tell us what needs to change. We'll fix it or explain why we can't. HOW THIS WORKS: 📅 Weekly Check (Every Friday): I'll comment below asking: "What needs to improve THIS WEEK?" 📆 Monthly Review (First Monday of each month): I'll comment asking: "What should we prioritize THIS MONTH?" ⚡ Ongoing: Comment anytime with feedback. If it's good, it gets implemented fast. WHAT WE WANT FROM YOU: ❌ NOT THIS (Too Generic): - "The community is great!" - "More content please" - "I wish there was more engagement" - "Can you add more features?" ✅ THIS (Specific & Actionable): - "The 7-day experiment template is confusing in Step 3. Can you add an example?" - "Pillar 5 frameworks feel too similar to Pillar 6. Consider merging or clarifying the difference." - "I can't find past framework discussions easily. Add a search tag system?" - "Friday deadlines for experiments don't work for my schedule. Can we make it flexible?" See the difference? Generic = We can't act on it. Specific = We can fix it in 48 hours/Give you exact timeline to incorporate the changes FEEDBACK CATEGORIES: Use these tags when commenting: #Content - Frameworks, lessons, case studies, book extractions #Structure - Categories, navigation, organization #Features - Tools, resources, templates missing #Community - Engagement, culture, member behavior #Pricing - Tier value, what you're getting vs paying #Tech - Bugs, broken links, access issues #Other - Anything else WHAT HAPPENS NEXT: If your feedback is: ✅ Immediately actionable (fix a broken link, clarify a confusing lesson) → We fix it within 48 hours and reply to confirm 🔄 Requires discussion (big structural change, new feature) → We'll respond explaining if/when/how we'll address it ❌ Not aligned with community vision (conflicts with core principles) → We'll explain why we're not implementing it YOU WILL GET A RESPONSE. Always. No feedback goes ignored. Even if we disagree, we'll tell you why.

WHEN YOU FINISH A 7-DAY EXPERIMENT, POST IT HERE. This is the heartbeat of the community. Your experiments teach the rest of us what works (and what doesn't). USE THIS EXACT TEMPLATE: (Copy-paste this and fill it in) 🧪 EXPERIMENT: [Framework Name] 📊 BUSINESS CONTEXT: ▸ What I'm building: [Product/service] ▸ Current revenue: $[X]/month ▸ Team size: [Solo/2-5/5+] 🎯 CHALLENGE APPLIED TO: [Specific problem or decision - be detailed] 💡 HYPOTHESIS: [What I was testing - "If I do X, then Y will happen because Z"] 🛠️ SETUP (Day 0): [What I prepared before starting the experiment] 📅 DAILY ACTIONS: ▸ Day 1: [Brief summary] ▸ Day 2: [Brief summary] ▸ Day 3: [Brief summary] ▸ Day 4: [Brief summary] ▸ Day 5: [Brief summary] 📊 RESULTS: ▸ Quantitative: [Numbers/data - revenue change, time saved, conversion rates, etc.] ▸ Qualitative: [What changed that's harder to measure - clarity, confidence, team alignment] ✅ SUCCESS CRITERIA MET? [Yes/No/Partial - reference the success criteria from the framework lesson] 💎 KEY INSIGHT: [The ONE thing I learned that I'll carry forward] 🔄 WHAT I'M DOING DIFFERENTLY NOW: [Specific change in how I operate my business] 👍 WOULD I RECOMMEND THIS FRAMEWORK? [Yes/No + why in 1-2 sentences] 🏷️ TAGS: #[FrameworkName] #[PillarNumber] REAL EXAMPLE: 🧪 EXPERIMENT: First Principles Thinking 📊 BUSINESS CONTEXT: ▸ What I'm building: Email marketing SaaS for e-commerce ▸ Current revenue: $8K/month ▸ Team size: Solo + 1 VA 🎯 CHALLENGE APPLIED TO: Stuck on pricing. Competitors charge $99-299/month. Not sure if I should match, undercut, or go premium. Been overthinking this for 3 weeks. 💡 HYPOTHESIS: If I break down pricing to first principles (actual value delivered vs market comparisons), then I'll find a defensible price point that's not just "what competitors charge minus 20%." 🛠️ SETUP (Day 0): ▸ Listed all assumptions about pricing (must be cheaper than Klaviyo, must be <$200, e-com stores won't pay more, etc.)

This is where we celebrate execution. Big wins. Small wins. Revenue wins. Clarity wins. Time-saved wins. All wins count if they came from running an experiment. USE THIS TEMPLATE: 🎉 WIN: [What happened - be specific] 🧪 Framework Used: [Which framework from TBL] 📊 Impact: ▸ Revenue: [$ increase or N/A] ▸ Time: [Hours saved or N/A] ▸ Clarity: [Decision made or problem solved] ▸ Other: [Any other measurable impact] 💡 What Made It Work: [The key insight or action that drove the result] 📅 Timeframe: [How long from starting framework to seeing result] REAL EXAMPLES: EXAMPLE 1: Revenue Win 🎉 WIN: Closed $12K client using BATNA framework 🧪 Framework Used: BATNA (Best Alternative to Negotiated Agreement) 📊 Impact: ▸ Revenue: +$12K (was going to accept $8K) ▸ Time: Saved 2 weeks of back-and-forth negotiation ▸ Clarity: Knew my walk-away point, stopped second-guessing 💡 What Made It Work: Before negotiation, I listed my BATNA (3 other qualified leads worth $6-8K each). Realized I had leverage. Client wanted 40% discount. I held firm at 20% because I had alternatives. They accepted. 📅 Timeframe: 7 days (ran experiment Mon-Fri, negotiation happened Friday) EXAMPLE 2: Time Win 🎉 WIN: Cut my weekly task list from 47 items to 9 using 80/20 🧪 Framework Used: 80/20 Rule (Pareto Principle) 📊 Impact: ▸ Revenue: No direct change yet ▸ Time: Freed up 12 hours/week (was working 60, now 48) ▸ Clarity: Know exactly what drives results vs busywork 💡 What Made It Work: Tracked every task for a week. Discovered 80% of my revenue came from 3 activities: sales calls, customer onboarding, and fixing critical bugs. Everything else was noise. Cut the noise, doubled down on the 3. 📅 Timeframe: 14 days (1 week tracking, 1 week executing new schedule) EXAMPLE 3: Clarity Win 🎉 WIN: Finally decided to kill my side project using Kill Your Darlings 🧪 Framework Used: Kill Your Darlings 📊 Impact: ▸ Revenue: N/A ▸ Time: Freed up 8 hours/week I was wasting on a dead project

🧪 EXPERIMENT: Getting Eyeballs 📊 BUSINESS CONTEXT: ▸ What I'm building: Prosperous Affiliate Pirates skool group ▸ Current revenue: $0/month ▸ Team size: Solo 🎯 CHALLENGE APPLIED TO: It's completely new. Nobody knows it exists. 💡 HYPOTHESIS: If I connect with with people in other skool groups every day, they will go to my profile, find my group and join it. 🛠️ SETUP (Day 0): Skool group is set up. First posts are up. 📅 DAILY ACTION PLAN: ▸ Day 1: Connect with people in at least three groups. ▸ Day 2: Connect with people in at least three groups. Create a lead magnet for the group. ▸ Day 3: Connect with people in at least three groups. ▸ Day 4: Connect with people in at least three groups. ▸ Day 5: Connect with people in at least three groups.

THE BASICS: Q: Do I need to test every framework? A: No. Pick ones relevant to your current challenges. Quality > quantity. You'll get more value testing 10 frameworks deeply than skimming 80 frameworks shallowly. Q: What if I miss a week? A: No problem. Frameworks stay in categories forever. Test at your own pace. But: The weekly rhythm creates accountability. Miss 3+ weeks in a row = you're not executing, just consuming. Q: Can I test multiple frameworks at once? A: Not recommended. One per week lets you isolate what's working. Testing 3 frameworks simultaneously means you won't know which one drove the result. Exception: Meta-frameworks explicitly teach you to stack frameworks. Do those when instructed. Q: What if my experiment fails? A: Post it anyway. Failed experiments with data are MORE valuable than "it worked perfectly." We learn as much from "I tried First Principles on pricing and it didn't help because X, Y, Z" as from success stories. Failures are wins if you learned something. Q: How long are 7-day experiments? A: Literally 7 days. - Day 0 (Sunday or whenever): Setup - Days 1-5 (Mon-Fri): Execute daily actions - Day 6-7: Synthesize results, post by Friday Don't overthink it. 7 days. One framework. Post results. CONTENT & FRAMEWORKS: Q: When do new frameworks release? A: Every Monday. One framework per week, rotating through all 8 pillars. Check 📅 Weekly Framework Release category. Q: How do I request a framework? A: Post in 🎤 Live Sessions & Feedback → "Framework Request Thread" Be specific: "Jobs to Be Done for SaaS pricing" not "more marketing stuff." Most requested frameworks get prioritized. Q: What if I don't understand a framework? A: Ask in the framework's discussion thread or tag it #Question in 🧪 Active Experiments. Community will help. That's what we're here for. COMMUNITY & ENGAGEMENT: Q: What if I can't commit to weekly experiments? A: You'll get less value. This community rewards execution, not passive reading. Reality check: