Hey everyone, I've been running an ICM folder system for my own reporting workflow and it's genuinely changed how I stay on top of everything. Now I want to roll it out to my immediate team first, then the wider company, but I want to do it in small increments rather than dropping it on everyone at once. Has anyone gone through this? Taking this system and actually getting a team or business to adopt it without it dying in week two? I'm thinking start with just my team, let them get used to the structure, then bring in other departments once there's some proof of life. But I'd love to hear from someone who's already been through the rollout side of things. What worked, what didn't, what you'd skip if you were starting again. Also, is there a video on here I should have watched already? If there's something that covers this and I've missed it, please just point me at it. Happy to do the homework first. Thanks

I explain the details about it on today's high tea . I built a Claude skill that turns a process, an idea, or a messy folder into an ICM workspace. The folder structure does the orchestration. Numbered folders carry the order, the hierarchy scopes context, and plain markdown files hold state. One agent walks the right files at the right time and does the work a multi-agent setup would. Repo: github.com/RinDig/icm-architect 📦 What it does Two modes. 🔨 Build. You describe your work and it pulls out the structure already sitting in how you talk about it. The stages, the points where you stop and check, what stays the same every run versus what is new. Then it picks one of five proven forms and scaffolds the smallest workspace that carries the job. ♻️ Restructure. Point it at a folder, repo, or vault you already have. It reads every file, sorts each one by role, shows you a migration map, waits for your yes, then moves and checks the result. 🧩 The five forms Pipeline, umbrella, record library, knowledge bundle, context map. They mix and nest, so most real workspaces use more than one. ✅ The walk test Every result gets checked cold. An agent with no memory has to open the root, find its way, act, and report status from the files alone. If it can't, the structure gets fixed until it can. ⚙️ How to use it You can honestly just tell claude to download it from the link, but if you're using codex or something else it will just have to restructure the claude.md to agents.md Or if you want to do more Hands-On install Claude Code: drop the folder in ~/.claude/skills/icm-architect/, then say "ICM this" or "build me a workspace for X." Claude apps: zip the folder and upload it under Settings, then Capabilities. Fork it, break it, tell me what you built. 👇

🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.