Looking at the numbers in this group got me thinking about how we measure engagement around here. Coming from the hair industry, social media analytics are basically life or death for us to keep our chairs full, so I always notice this stuff. We have like 39,000 people in this group, but the highest response I saw on a survey was around 7,000. I think a lot of people see that gap and think it's bad news, but honestly a 17% engagement rate on a single post is kind of insane. From what I've had to learn about marketing just to run my own business, you are usually lucky to even get 1% or 2% of your audience to wake up and click a button on regular platforms. But at the same time, it does feel like the daily comments come down to the same 20 or 30 people, and a massive chunk of the group is still sitting at Level 1. They probably just jump in to grab the classes and then ghost the social side completely. In my line of work you learn that there are always tons of people who are getting value from what you do but they just stay quiet. They don't have the social energy or the confidence to post. Especially in a tech heavy group like this, it is so easy for a beginner to scroll through, feel some major imposter syndrome, and just decide to stay quiet. I'm super curious, for anyone who actually made it past Level 1, what finally broke the ice for you? Was it wanting to rank up in the levels, or did you just wait until you had something cool to share?

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)