Let me preface with, I am fairly new here and really appreciate this community! The organization of ICM is what finally helped me start to grasp AI. Before that, I was working with PARA (projects, areas, resources, archive) as my way of organizing files for AI. For those familiar with PARA, how would you compare/contrast it with ICM? How do I use them together? Or is that not a thing?

Hi everyone, I have just reached level 2 and would like to make a first post of my own. I have always been interested in technology, economics, and human behavior, but only recently started writing about how they connect. How AI is used inside our systems is the focus here. It is what brought me here, and why ICM makes sense to me. I also like to explore how we humans behave with these systems. I am sharing an essay I originally wrote in Portuguese and translated into English for this community. It explores the social cost of asking another person for help, and how AI changes that choice. Asking a machine can spare us the embarrassment of admitting what we do not know, or the judgment that sometimes comes with an answer. I look at how that changes whom we turn to, what we trust, and how we relate to one another.

Do folders need to be numbered sequentially, as the ICM states, or is it okay to have a mix of numbered and descriptive folder names? At the moment, the workflow stage folders are mostly numbered, but resourcing has a 01a stage and the final handoff stages jump from 04 to 06. Client, template and record folders use descriptive names without numbers. Is that setup wrong, or is it okay as it is?

Hey everyone, I’m building an ICM workspace for my recruitment work and I’ve been thinking about how to keep it structured without making it too rigid. I like the idea of numbered stages because they create a clear order and help Codex find the right instructions. But in practice, my work doesn’t always start at the beginning or follow the same path. For example, I might add a new company and vacancy, work through the vacancy preparation, and then assess a candidate’s CV. That feels like a nice, ordered process. But the next day I might get another CV for that same vacancy. Ideally, I’d want Codex to pick up the existing vacancy information and go straight to the new candidate’s assessment, without repeating all the earlier steps. Other times, I might get a CV before I have a vacancy, or I might just want to format a CV without going through the full recruitment process at all. I’d like the workspace to flag anything useful that’s missing, but also let me decide whether to do it or skip it and move on when it isn’t essential. I’m trying to understand how best to make those entry points and optional steps clear in the folder structure and instructions. Am I overthinking this? Has anyone else run into this when their work doesn’t always follow a clear, step-by-step process? How have you structured your ICM so it stays organised while still letting you jump in at different points and reuse work you’ve already done? Would love to hear how others have approached it!