[{"data":1,"prerenderedAt":129},["ShallowReactive",2],{"footer-topics-en-US":3,"post-en-US-structured-collaborative-intelligence-structuring-the-first-question":70},{"topics":4},[5,21,33,46,58],{"locale":6,"name":7,"slug":8,"blurb":9,"summary":10,"state":11,"featuredOnHub":12,"hubOrder":13,"accent":14,"questionsTitle":15,"questions":16,"body":20},"en-US","The Journey","the-journey","From early experiments in Agile × AI to a working system — the story behind the thinking.","From early experiments to a working system — the real story of building Agile4AI, including the wrong turns that shaped everything.","published",true,2,"gold","What the journey keeps teaching us",[17,18,19],"What convinced us that Agile and AI belonged together — and what nearly convinced us otherwise?","Which wrong turns turned out to be the most instructive?","How did SCI evolve from a copy-and-paste experiment into AI responses that you can actually rely on?","\nEvery idea in this topic comes from our experiences developing Agile4AI. We're eager to share the story with you — the successes and the failures — because we believe we can all learn together as we discover how to work better with AI. What we figured out didn't come from theory. It came from doing, from failing, from starting over with what we learned.\n\nThe journey started as a straightforward question: could Agile be updated for the AI era? What followed was years of experimentation, failed assumptions, unexpected discoveries, and the slow emergence of something that actually works — a Structured Collaborative Intelligence (SCI) approach and the Agile4AI system built on top of it.\n\nThis isn't a polished retrospective written with hindsight. It's the story told as close to how it happened as possible — including the dead ends, the moments of doubt, and the breakthroughs that reframed everything.\n\nWe share it because the story itself carries the lesson. The conclusions matter, but so does *how we got there* — because the path shows what worked, what didn't, and why.\n\nPosts in this topic cover the full arc: early experiments with AI collaboration, the development of SCI, specific discoveries that changed how we work, and milestones worth marking. Some posts are reflective. Some are raw. All of them are real.\n\nIf you want to understand why Agile4AI and SCI exist — not just what they are — start here.\n",{"locale":6,"name":22,"slug":23,"blurb":24,"summary":25,"state":11,"featuredOnHub":12,"hubOrder":26,"accent":14,"questionsTitle":27,"questions":28,"body":32},"Agile Decoded","agile-decoded","What Agile terms actually mean — not the common shorthand, not the cargo-cult version, not the methodologist's gloss.","The vocabulary of Agile is widely used and widely misunderstood. Getting the terms right isn't pedantry — it's the difference between the ceremony and the work.",3,"Why terminology is load-bearing",[29,30,31],"If a standup is run like a status report, what does the team actually lose?","When \"Agile Methodology\" became standard vernacular, what did it do to how organizations approached transformation?","What's the cost of a team that can name every Agile practice but doesn't understand what any of them are for?","\nAgile has a vocabulary problem. Not because the terms are obscure — most people in modern organizations have heard them. Because the terms are familiar words being used in a completely different context, and without that context, people map them to what they already know.\n\nWhen someone encounters \"Scrum Master\" for the first time, the nearest available concept is \"Project Manager.\" The mapping feels natural — almost obvious. The context is completely different.\n\nNo one built a clear enough bridge between them. And the problem compounded when well-meaning practitioners — people genuinely trying to move organizations forward — began describing Agile as \"better project management.\" Began writing books called \"Agile Methodology.\" When you call your approach a methodology, people measure it by methodology standards: planning artifacts, phase gates, deliverable structures. When Agile doesn't produce those things — because it was never designed to — it fails those standards, with good reason. The problem isn't that Agile is a bad methodology. It's that Agile is not a methodology at all. Calling it one guaranteed that everyone looking for a methodology would be disappointed, and that everyone who adopted it would build something Waterfall had already mapped out.\n\nA standup becomes a status report. A sprint becomes a deadline. A backlog becomes a task list. \"Agile Methodology\" becomes the standard phrase for something the Manifesto authors would not have recognized as describing what they built. And when the words mean the wrong thing, the practices built on them produce the wrong results — precisely, faithfully, and at scale.\n\nThis topic is a concept-by-concept correction. Not a style guide — a functional one. Each post takes one word or phrase that's become load-bearing in how organizations think about Agile, examines what it actually means, and explains what gets lost when the shorthand replaces the substance. These aren't just terminology differences. \"Desired Outcome\" isn't a fancier word for \"Specification\" — it's a different thing entirely, from a different model of how work gets done. The term is the surface. The concept underneath is what matters.\n\nThe same pattern appears when organizations approach AI — and the conceptual gap is wider. With Agile, the underlying concepts had at least been articulated, even if poorly communicated. With AI, the concepts themselves are still being formed, and in the public understanding they're barely forming at all. The vocabulary is racing ahead of the comprehension: AI as \"automation,\" AI as \"tool,\" \"AI transformation\" as a project with a completion date. Each of these locks in a mental model before anyone has examined whether it fits. What we call things shapes what and how we build. Getting the words right is the prerequisite for getting the work right.\n\nThere's a principle at work here: mental models come first. Language expresses them. Actions follow. When the mental model is misaligned with the work, the vocabulary that expresses it carries that misalignment — and the actions built on that vocabulary will faithfully execute the distorted understanding, at scale, with full commitment. A vocabulary shift without a mindset shift produces, at best, a translation table: an equivalency chart where \"sprint\" maps to something like \"short deadline.\" Translation tables let people operate across the gap. They don't close it. The posts in this topic are trying to do more than translate. They aim to shift the mental model.\n",{"locale":6,"name":34,"slug":35,"blurb":36,"summary":37,"state":11,"featuredOnHub":12,"hubOrder":38,"accent":39,"questionsTitle":40,"questions":41,"body":45},"Structured Collaborative Intelligence","structured-collaborative-intelligence","Where collaborative reasoning beats a single frontier model — and where it doesn't.","Where structured collaboration — between models, and between models and humans — produces reasoning a single model can't reach alone.",4,"green","Questions we keep returning to",[42,43,44],"Where does structured collaborative intelligence add value that a single model simply can't match?","When models disagree, what does that tell you — and how do you use it?","How do you design structure that makes AI collaboration productive rather than just redundant?","\nA single AI model, however capable, reasons alone. It has no one to push back on its assumptions, catch its blind spots, or notice when it has drifted from the original intent. Solo-AI — working with a single model at a time — is susceptible to this. A model directed to give you a response will give you one, even when it doesn't have a good answer worthy of reaching you.\n\nStructured Collaborative Intelligence (SCI) is a different approach. Rather than treating a single model's output as the final result, SCI uses structured collaboration — between multiple AI models, and between models and humans — to produce outputs that are more reliable, more thoroughly examined, and more transparent about their own limitations. Models review each other. Disagreements surface assumptions. The process itself creates a feedback loop that a single-model interaction can't replicate.\n\nThe connection to Agile is direct: this is what high-performing teams have always done. Not one person producing an answer in isolation, but a structured process of collaboration, review, and iteration that catches what any single perspective misses. SCI applies that same discipline to AI.\n\nThere is a deeper issue with solo reasoning. Solo-AI locks you into a single data source, a single architecture, and a single set of embedded biases — which means a single answer shape, whether or not that shape is accurate. Think of how a good detective interviews multiple witnesses. Not because any one of them is lying, but because each vantage point reveals something the others missed. Together, they get closer to what actually happened. SCI works the same way: multiple models from different lineages, each bringing its own angle. The answer that emerges has been seen from multiple directions — richer, fuller, and more difficult to be quietly wrong.\n\nWhen models of different lineages collaborate, outputs improve in ways that matter: fewer confident errors, better handling of edge cases, more explicit reasoning that humans can evaluate and correct. Disagreements between models, rather than being noise to suppress, turn out to be exactly the signal you want when the stakes are high.\n\nSCI is the analytical engine behind the Agile4AI service. Posts in this topic document what it is, how it works in practice, where it adds genuine value, and — equally important — where it doesn't. Part of the discipline is knowing which is which.\n",{"locale":6,"name":47,"slug":48,"blurb":49,"summary":50,"state":11,"featuredOnHub":12,"hubOrder":51,"accent":52,"questionsTitle":40,"questions":53,"body":57},"Agile4AI Values & Principles","agile-ai-values-principles","Agile values and principles applied to the age of AI — what carries forward, what changes, and why we invite the strongest objections.","The Agile mindset applied to AI work — what carries forward, what sharpens, and why the fit between Agile and AI isn't accidental.",5,"red",[54,55,56],"When complex work can't be fully planned in advance, what does that mean for how we work with AI?","How does the Agile emphasis on continuous feedback change when your collaborator doesn't get tired or defensive?","Is \"Agile for AI\" a natural fit — or is the category error objection actually decisive?","\nThe Agile mindset was forged in complexity — not to manage complexity away, but to move through it mindfully and intelligently. That doesn't become less relevant when your collaborator is an AI model. In many ways, it becomes more so.\n\nThis topic is about that relationship: not Agile-by-prescription, not frameworks or ceremonies, but the underlying values and principles Agile distilled — and how those apply, sharpen, and occasionally need reexamination when humans and AI work together.\n\nThe core insight is that Agile thinking was always a response to the *nature* of complex work, not just to the quirks of human teams. When Agile challenged the assumption that complex work can be planned in detail upfront, that wasn't a workaround for human limitations — it was an accurate observation about how non-deterministic, fast-moving work actually behaves. That observation doesn't change because an AI is involved. It intensifies.\n\nEstimation is worth naming directly — it's one of the most contested topics even among committed Agilists. Agile didn't emerge to help teams estimate better; it emerged to expose why estimation *breaks* in complex work — and to replace false precision with empirical measurement and genuine feedback that does improve delivery forecasting. In the age of AI, where outputs are probabilistic and the work itself resists fixed specification, that insight is sharper than ever.\n\nThis is also the home of Principled Debate: where the strongest objections to \"Agile for AI\" get their turn on the soapbox. We think the case holds. We want to be proved wrong if it doesn't.\n",{"locale":6,"name":59,"slug":60,"blurb":61,"summary":62,"state":11,"featuredOnHub":12,"hubOrder":63,"accent":64,"questionsTitle":40,"questions":65,"body":69},"AI Psychological Safety","ai-psychological-safety","Why the freedom to say \"I don't know yet\" is the precondition for real intelligence.","The conditions you create in your communication shape what AI gives back — and when those conditions are wrong, the result is confidence without reliability.",6,"amethyst",[66,67,68],"What conditions make an AI more likely to surface real uncertainty rather than a confident-sounding guess?","How does the way you frame a question shape whether the answer is reliable — or just reassuring?","What carries from Agile's approach to psychological safety — and what needs to adapt for AI?","\nMost people think about psychological safety as a human concern — the conditions that allow a person to speak up, express uncertainty, or challenge an idea without fear. That's right as far as it goes.\n\nBut something important gets missed when we ignore where AI came from. AI was built by humans, shaped by human language, trained on human choices. The dynamics that affect human performance — including psychological safety — carry into AI interactions for the same underlying reasons Agile has always identified: **the conditions you create in your communication shape what you get back.**\n\nAn AI prompted in ways that reward confident-sounding answers will produce confident-sounding answers — whether or not confidence is warranted. An AI with no room to say \"I'm not sure\" will fill that room with something else, because its directives require it to do so even when it knows that it doesn't have the right answer. The dynamic is different from human psychological safety, but the underlying principle holds: intelligence performs better when it has permission to be honest about what it doesn't know.\n\nThis matters practically. Hallucinations, overconfident outputs, and AI systems that tell you what you want to hear rather than what's true are not purely technical failures. They're often failures of the interaction design — the prompts, the framing, the implicit expectations baked into how a question is asked.\n\nPosts here explore the conditions that make human–AI collaboration more reliable and more truthful. That includes how to prompt in ways that invite genuine uncertainty rather than suppress it, the difference between deterministic and probabilistic AI use and why that distinction changes everything about how you frame your work, and what Agile's approach to psychological safety in human teams carries over when your collaborator is a model.\n\nThis is also where we examine the failure modes: what happens when those conditions aren't in place, and what it costs.\n",{"kind":71,"post":72,"topic":82,"availableLocales":84,"translations":92,"html":127,"audioUrl":128},"post",{"audio":-1,"author":73,"category":35,"excerpt":74,"featured":75,"locale":6,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":78,"title":81,"translationKey":77,"updatedAt":76},"Seán González","How you frame the opening question in an SCI session shapes everything that follows. The structure is more important than the length.",false,"2025-07-01T10:00:00.000Z","structuring-the-first-question",[79,80],"prompting","SCI","Structuring the first question",{"locale":6,"name":34,"slug":35,"blurb":36,"summary":37,"state":11,"featuredOnHub":12,"hubOrder":38,"accent":39,"questionsTitle":40,"questions":83,"body":45},[42,43,44],[6,85,86,87,88,89,90,91],"es-419","fr-FR","pt-BR","de-DE","uk","ru","ja",[93,95,100,104,108,112,117,121],{"audio":-1,"author":73,"category":35,"excerpt":74,"featured":75,"locale":6,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":94,"title":81,"translationKey":77,"updatedAt":76},[79,80],{"audio":-1,"author":73,"category":35,"excerpt":96,"featured":75,"locale":85,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":97,"title":99,"translationKey":77,"updatedAt":76},"La forma en que formula la pregunta inicial en una sesión de SCI moldea todo lo que sigue. La estructura importa más que la extensión.",[98,80],"Prompting","Estructurar la primera pregunta",{"audio":-1,"author":73,"category":35,"excerpt":101,"featured":75,"locale":86,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":51,"slug":77,"state":11,"tags":102,"title":103,"translationKey":77,"updatedAt":76},"La façon dont vous formulez la question d'ouverture d'une séance SCI façonne tout ce qui suit. La structure compte plus que la longueur.",[98,80],"Structurer la première question",{"audio":-1,"author":73,"category":35,"excerpt":105,"featured":75,"locale":87,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":106,"title":107,"translationKey":77,"updatedAt":76},"Como você formula a pergunta inicial em uma sessão de SCI molda tudo o que vem depois. A estrutura importa mais que o tamanho.",[98,80],"Estruturar a primeira pergunta",{"audio":-1,"author":73,"category":35,"excerpt":109,"featured":75,"locale":88,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":110,"title":111,"translationKey":77,"updatedAt":76},"Wie Sie die Eröffnungsfrage in einer SCI-Sitzung formulieren, prägt alles, was danach kommt. Die Struktur zählt mehr als die Länge.",[98,80],"Die erste Frage strukturieren",{"audio":-1,"author":73,"category":35,"excerpt":113,"featured":75,"locale":89,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":114,"title":116,"translationKey":77,"updatedAt":76},"Те, як ви формулюєте початкове питання в сесії SCI, визначає все, що йде далі. Структура важливіша за довжину.",[115,80],"Промптинг","Структурування першого питання",{"audio":-1,"author":73,"category":35,"excerpt":118,"featured":75,"locale":90,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":38,"slug":77,"state":11,"tags":119,"title":120,"translationKey":77,"updatedAt":76},"То, как вы формулируете начальный вопрос в сессии SCI, определяет всё, что следует дальше. Структура важнее длины.",[115,80],"Структурирование первого вопроса",{"audio":-1,"author":73,"category":35,"excerpt":122,"featured":75,"locale":91,"pinnedInTopic":75,"pinnedOverall":75,"publishedAt":76,"readingMinutes":123,"slug":77,"state":11,"tags":124,"title":126,"translationKey":77,"updatedAt":76},"SCIセッションで最初の問いをどう枠づけるかが、そのあとのすべてを形づくる。重要なのは長さではなく構造である。",1,[125,80],"プロンプト","最初の問いを組み立てる","\u003Cp>In a Structured Collaborative Intelligence session, you’re not prompting a single AI system. You’re opening a structured dialogue between multiple models, with one AI — chosen by you — that synthesizes the collective response in the voice and format that you prefer. The first question and your AI voice selection don’t just determine what the first responses will be — they set the frame that every subsequent contribution works within.\u003C\u002Fp>\n\u003Cp>Getting that frame right is worth the time and effort.\u003C\u002Fp>\n\u003Ch2>What the first question does\u003C\u002Fh2>\n\u003Cp>The opening prompt establishes the problem space. It signals what kind of thinking is wanted: analytical or generative, convergent or exploratory, evaluative or creative. It sets the context for the AIs to align their independent perspectives and, based on their training data, establish their position relative to the question and other AIs’ contributions as the conversation progresses.\u003C\u002Fp>\n\u003Cp>A poorly framed first question runs the risk of over-biasing some or all of the AIs, potentially pitting one against another instead of creating the shared context where all can collaborate in genuine agreement and disagreement. The goal is for the AIs to reach consensus, not agreement. Consensus here is the worked-through collective position that keeps the disagreements visible inside it; agreement is the flatter thing that sands them away. That is what lets your chosen AI synthesize the responses — agreements and disagreements included — in a way that delivers both breadth and depth.\u003C\u002Fp>\n\u003Cp>A well-framed first question produces responses that are aware of each other — where an AI pushes back on an assumption, or builds on a prior response, or identifies a tension in the framing that the session needs to resolve.\u003C\u002Fp>\n\u003Ch2>Elements of a strong opening question\u003C\u002Fh2>\n\u003Cp>The most productive SCI opening questions contain three things: the context (what situation are we actually in), the constraint (what are we working within), and the specific question (what exactly do we need to figure out), which points in the direction of our desired outcome from the SCI session.\u003C\u002Fp>\n\u003Cp>Context without constraint produces abstract answers. Constraint without context produces recommendations the models have no way to evaluate against your reality. Neither without the specific question produces anything actionable.\u003C\u002Fp>\n\u003Cp>“We’re a twelve-person product team, we’ve been running Scrum for two years, and our retrospectives have stopped producing changes. What are the most likely root causes and how would you investigate them?” — that’s a question with all three elements. The context grounds the answers. The constraint (retrospectives specifically, not process in general) focuses them. The specific question (root causes and how to investigate) directs the kind of thinking you want.\u003C\u002Fp>\n\u003Cp>There is nothing new about this approach. This is exactly what Agile culture has taught us to do to improve our team communications, align towards a common goal, and remain focused on the thinking that produces the best quality answer.\u003C\u002Fp>\n\u003Ch2>What to leave out\u003C\u002Fh2>\n\u003Cp>The opening question doesn’t need to be long to be well-structured. Unnecessary context actually dilutes the focus — the models will try to incorporate everything you’ve given them, and excessive setup can make the session slower to get to the useful territory. It can also derail the conversation by offering too many details that unnecessarily constrain the response to fit all those details; wisely choosing “just enough” is important to get the best answer.\u003C\u002Fp>\n\u003Cp>Avoid front-loading every piece of background that might be relevant. Give the models what they need to answer the question you’re asking, not everything you know about the domain. If additional context turns out to matter, it can come in the follow-up turns or as interjections while the conversation is going and you spot divergence away from what is important to you.\u003C\u002Fp>\n\u003Ch2>When the first question is wrong\u003C\u002Fh2>\n\u003Cp>Sometimes you discover mid-session that the first question framed the problem incorrectly. Maybe the AIs’ responses revealed that you were solving the wrong problem, or that a key assumption you built the question around is contestable.\u003C\u002Fp>\n\u003Cp>This isn’t a failure — it’s often the most valuable thing an SCI session produces. The right response is to reframe explicitly: “Based on what you’ve raised, I think the more important question is…” and start from there. The session has already done useful work by surfacing the reframe.\u003C\u002Fp>\n\u003Cp>The first question is a starting point, not a contract. But the quality of your start determines how quickly you get to the territory that matters. Keep in mind that when multiple AIs engage in this type of exchange they produce deep and meaningful answers. You want your first question to be just enough to set them in the right heading; that’s all that’s needed for the AIs to carry the conversation forward.\u003C\u002Fp>\n",null,1793842013172]