What The Unbreakable Core Actually Means In Practice
I first ran into this concept last year when a partner studio reached out about a joint product launch. They kept referring to something called the unbreakable core and I had no idea what they were talking about. After digging through threads on a few collaboration forums and reading an early whitepaper from Jonathan Bailey's team, I finally understood what it is and more importantly how to actually implement it. At its simplest, the unbreakable core is a framework for coordinating cross-organizational teams around shared objectives without collapsing into endless meeting loops and misaligned deliverables. Bailey and Steelere developed it after several high-profile project failures in the creative technology space where multiple teams kept shipping work that didn't actually integrate. The framework has three layers: the anchor, the flow, and the feedback loop. You need all three working together or the whole thing falls apart. The anchor is the single most important element. It is a concise written document that every participant must agree on before any real work begins. I learned this the hard way on a project where we skipped the anchor because everyone was too excited to start building. Three weeks in, we had four different versions of the same feature and nobody could figure out which one to ship. That took us another six weeks to clean up.
Here is how I structure the anchor. One page maximum. It covers three things: what problem we are solving, who owns which decisions, and what success looks like in measurable terms. No decorative language. No mission statement fluff. Just clear boundaries and clear outcomes. When I first started using this, my anchors were around two pages because I kept adding context. Now they average about 400 words and the projects move faster.
Setting Up The Flow Layer
The flow layer handles how work moves between teams. This is where most collaborations fail because nobody defines the handoff points. I usually set up a shared board with three columns per team: waiting, doing, and delivered. Each column has specific entry and exit criteria written directly in the card descriptions. When a card says delivered, it means it has passed the receiving team's acceptance checklist, not just the sender's. I encountered a specific problem with this setup on a project involving a design team and an engineering team across different time zones. The design team would mark items as delivered late in their evening, the engineering team would review them early the next morning, and by the time they flagged issues, the designers were already offline for the day. This created a two day waiting cycle on everything. The workaround was simple: I added a required synchronous check-in window of 90 minutes each day where at least one person from each team had to be available. We rotated the time slot so it wasn't always inconvenient for the same group. This cut our average cycle time from four days down to two and a half. The feedback loop is the third layer and it is usually the one people skip. It is a structured review that happens at predetermined intervals, not when someone feels like it. I run these every two weeks on a fifteen minute call with a very specific agenda. First five minutes: what did we ship. Next five minutes: what blocked us. Last five minutes: what changes for the next cycle. That is it. No broader project updates. No status reports. The feedback loop only addresses coordination friction.
Get the Full Details
One counter-intuitive thing I learned: the framework actually works less well in small teams of three or fewer people. The structure adds overhead that outweighs its benefits at that scale. I've found it shines with teams of six to twenty people spread across two or more organizations. Below six people, a shared document and a weekly sync covers it. Above twenty, you need to break the group into sub-teams that each use the framework internally while sharing anchors at the top level. There are also scenarios where this approach breaks down completely. If any participant team does not have the authority to make decisions independently, the framework stalls. I worked with a client who brought this system to a partnership with a large enterprise division that required executive approval for every change. Nothing moved. The unbreakable core assumes decision-making autonomy at the team level. When that is not present, you need a different model, usually something closer to a standard gated process with defined approval chains. For downloading or accessing the original materials, the core framework documents are available through Bailey's published resources online. Steelere has contributed case studies and variations through her own channels. The basic framework is free to use. The certified training and templates come through their official website at a paid tier if you want the full toolkit.
I will say this plainly: the unbreakable core is not a magic solution for bad collaboration. It will not fix a team that lacks basic communication skills or an organization that refuses to delegate authority. What it does is give you a repeatable structure that prevents the most common and expensive failure modes in multi-team projects. The anchor keeps everyone aligned, the flow makes work visible, and the feedback loop catches drift before it becomes a crisis. That is all it promises and that is more than most frameworks deliver.
