<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Asbjorn Bjaanes on Medium]]></title>
        <description><![CDATA[Stories by Asbjorn Bjaanes on Medium]]></description>
        <link>https://medium.com/@asbjorn_17696?source=rss-a659414b9495------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tnOfl4jZb3UFJAh1</url>
            <title>Stories by Asbjorn Bjaanes on Medium</title>
            <link>https://medium.com/@asbjorn_17696?source=rss-a659414b9495------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:04:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@asbjorn_17696/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Stand-up Isn’t Going Away. The Room Is.]]></title>
            <link>https://medium.com/@asbjorn_17696/the-stand-up-isnt-going-away-the-room-is-1872d808db2d?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/1872d808db2d</guid>
            <category><![CDATA[aidlc]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 15:55:26 GMT</pubDate>
            <atom:updated>2026-11-06T15:55:26.262Z</atom:updated>
            <content:encoded><![CDATA[<p>Nov 6, 2026 · <a href="https://medium.com/u/a659414b9495?source=post_page---user_mention--0a60e1d3a88f-----------------------------------------">Asbjorn Bjaanes</a></p><figure><img alt="The Stand-up Isn’t Going Away. The Room Is." src="https://cdn-images-1.medium.com/max/1024/1*HafuawaXZDHKenPDAEvpkA.jpeg" /></figure><p>Many organisations hear AI-native development and conclude that the stand-up, and most other agile ceremonies, are on their way out. The agents do the building. The spec holds the truth. A small mob has everyone it needs. Why meet?</p><p>For some teams, that is true. For most organisations, it is the opposite. AI does not remove the need to work together. It shortens the time we can afford to wait. When the economics of execution change, the economics of coordination change with them.</p><p>In “<a href="https://medium.com/@asbjorn_17696/the-spec-is-not-the-handover-intent-ai-dlc-and-the-return-of-the-room-f9903e9c9f81">The Spec Is Not the Handover</a>”, I argued that the daily stand-up is how product gets back into the room. This article follows that thought further.</p><h3>A blocker, found the same day</h3><p>In one of our recent bolts, a short and focused AI-DLC cycle, the work stopped. The AI had raised questions nobody in the bolt could answer, and the answers sat with product, in a different calendar and a different focus.</p><p>We had kept our stand-ups. So the blocker surfaced the very same day. The right people heard it, we saw what was stopping the flow, and we made the decisions from there.</p><p>Without that touchpoint, the bolt would likely have waited for days before anyone noticed. With AI, that is a long time. The build itself might only take hours. When building gets that fast, waiting becomes the most expensive part of the work.</p><h3>When the ceremonies really can go</h3><p>It is worth being honest about where the belief comes from.</p><p>If your whole product is one mob, two or three people working on one thing together, then everyone who holds the intent is already in the room. You communicate with those involved, and that is it. Heavy ceremonies would only add noise.</p><p>Many organisations can also move closer to this. With AI-DLC, a Kanban flow where small mobs of two or more people swarm one item at a time becomes a natural way of working. Work flows, blockers surface when they appear, and the ceremony load can be light.</p><p>So there is no single right answer. Being truly agile means fitting the process to the reality of the organisation, not copying a framework by the book.</p><h3>The twist of going fully AI native</h3><p>Now follow the idea to its end. If you want to be truly AI native, everything becomes spec-driven, including the small work items. Living specs that result in code.</p><p>A small spec-driven item can be a one-person job. In the language of bolts and mobs, that is a one-person mob. And when many one-person mobs run side by side inside a sprint or a Kanban flow, you are back to something very familiar: individuals working in parallel, each holding a piece of the picture. Only faster.</p><p>I am stretching the word on purpose. AI makes individual execution more powerful, and that can make collective understanding more fragile. The coordination problem has not disappeared. It has come back faster.</p><h3>Why larger organisations need the ceremonies more</h3><p>Teams working on larger applications still need to produce multiple things in parallel. Many will still run Scrum, or a scaled agile approach. And for them, the ceremonies do not lose their purpose. They gain urgency.</p><p>They do two jobs that AI cannot do on its own.</p><p><strong>They keep tacit knowledge at the front of the room.</strong> In AI-native development, the AI asks the questions, and tacit knowledge is what answers them: why something matters, what the customer really meant, which part of the system tends to break. Each answer is captured in the living spec, so the spec grows with what the people know. A ceremony is where that knowledge comes forward, and where new knowledge forms, before it fades. As I wrote in “<a href="https://medium.com/@asbjorn_17696/the-moat-is-moving-what-is-left-to-protect-when-code-becomes-a-commodity-0a60e1d3a88f">The Moat Is Moving</a>”, tacit knowledge is a flow, not a stock.</p><p>Google’s <a href="https://opensource.googleblog.com/2026/10/introducing-elephant-goldfish-model-plugin.html">Elephant-Goldfish Model</a> makes this visible. The elephant holds the project context and drafts the spec. The goldfish reads it with no context at all, and probes for the gaps and unstated assumptions. In other words, the goldfish is designed to find exactly what nobody wrote down. The gaps go back to the elephant to be resolved. But the elephant only knows what has been written down and discussed. AI can expose an assumption. It cannot tell whether that assumption reflects the actual intent. That knowledge sits with people, and that is why the room matters more, not less.</p><p><strong>They resolve bottlenecks fast enough to keep up.</strong> In the past, we accepted waiting weeks for decisions. Agile pushed us to shorten the feedback loops to days. AI-native work needs them shorter still. What used to be days is now hours.</p><h3>Present, but not in the room</h3><p>There is a quieter reason the room matters. Even when people sit together, AI creates wait time. While the agents work, attention drifts to other things. People are physically present, but their attention is somewhere else.</p><p>In the 1970s, Thomas Allen at MIT showed that communication between engineers drops sharply with physical distance. Shared attention research adds the other half: two people can sit a metre apart, and if their attention is not on the same thing, the distance reappears.</p><p>Being present is not the same as sharing understanding. Shared attention creates collective sense-making, and collective sense-making is what makes decisions fast. This is why the stand-up is not overhead. It is one of the few moments where attention is shared by design. It brings the room back together, for a few minutes, around the same intent.</p><p>I have written about the habit itself in “<a href="https://medium.com/@asbjorn_17696/the-15-minute-daily-habit-that-connects-every-team-to-a-shared-truth-2cb66ae04346">The 15-Minute Daily Habit That Connects Every Team to a Shared Truth</a>”, and about noticing where attention goes in “<a href="https://medium.com/@asbjorn_17696/how-the-best-leaders-read-the-room-and-why-you-can-learn-it-too-f931f3acb50f">How the Best Leaders Read the Room</a>”.</p><h3>Fit the ceremonies to the shape of your work</h3><p>The question is not whether to keep your ceremonies. It is which shape your AI-DLC takes, and what that shape needs.</p><ul><li><strong>A standalone mob of two or three:</strong> keep it light. Talk when you need to.</li><li><strong>Kanban with small mobs:</strong> a short daily touchpoint to surface blockers and dependencies the moment they appear.</li><li><strong>Many parallel bolts on a larger application:</strong> keep the stand-up and the review, and tighten them. The review is a learning system, not a demo, as I wrote in “<a href="https://medium.com/@asbjorn_17696/the-sprint-review-is-not-a-demo-meeting-it-is-a-learning-system-67a159780876">The Sprint Review Is Not a Demo Meeting</a>”. They are how intent travels and how decisions keep pace.</li></ul><h3>For sponsors and executives</h3><p>If you are investing in AI-DLC to get 10x, the ceremonies are part of how you protect that investment. The agents can only build as fast as the decisions behind them. A team that waits three days for an answer loses more now than before, because everything else got faster.</p><h3>Try this in your next stand-up</h3><p>Ask one question:</p><p><strong>What is the AI asking that nobody here can answer?</strong></p><p>Then notice who should have been in the room, and how long that answer would have taken without the meeting.</p><p>Then measure it. Track <strong>decision latency</strong>: the time from the moment a question is raised to the moment someone answers it. In many organisations this used to be days, sometimes weeks. In an AI-native pipeline, aim for hours. If the number grows, the bottleneck is not the agents. It is the room.</p><p>AI is making execution cheaper and faster. It is also making the cost of waiting more visible. The stand-up is not going away. The room simply has less time to catch up with the work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1872d808db2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Moat Is Moving: What Is Left to Protect When Code Becomes a Commodity]]></title>
            <link>https://medium.com/@asbjorn_17696/the-moat-is-moving-what-is-left-to-protect-when-code-becomes-a-commodity-0a60e1d3a88f?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a60e1d3a88f</guid>
            <category><![CDATA[acquired]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ssd]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 16:50:56 GMT</pubDate>
            <atom:updated>2026-11-02T16:50:56.055Z</atom:updated>
            <content:encoded><![CDATA[<p>Nov 1, 2026 · <a href="https://medium.com/u/a659414b9495">Asbjorn Bjaanes</a></p><figure><img alt="The Moat Is Moving: What Is Left to Protect When Code Becomes a Commodity" src="https://cdn-images-1.medium.com/max/1024/1*sRJGr2oeNyrthiASqdG6dQ.jpeg" /></figure><p>There is something your organization has built that you are proud of. A product, a platform, software that took years to get right. Ask what makes it yours, and the answer probably comes quickly: the code, the architecture, the algorithms nobody else figured out.</p><p>That was my answer for most of my career. Exploring AI-DLC and spec-driven development has made it less solid. AWS has released its frameworks, Google talks about the elephant and the goldfish, and the cost of turning an idea into working software keeps falling. We are commoditizing the coding part of software development.</p><p>I don’t have a finished answer to what that means. This is a reflection, written while I am still working it out.</p><h3>Intent is the new source code</h3><p>We have been here before. Compilers commoditized assembly, cloud commoditized infrastructure, and each time value moved one level up. Now it is moving from writing code to knowing what is worth building and why.</p><p>In <em>The Spec Is Not the Handover</em> I described the spec as something a team builds together in the room, around the intent product brings. Follow that one step further. If AI can produce the code from a good spec, the code becomes the compiled output, and <strong>intent becomes the new source code.</strong></p><p>It is a small thought, but it quietly rearranges what we point at when someone asks what protects the business.</p><h3>The copy</h3><p>Imagine, for a moment, that you are on another team. You are capable, you have the same AI tools, and you are looking at that product someone else is proud of. Within weeks you have something that looks and behaves the same. It feels like a shortcut, and in a way it is.</p><p>Then the market shifts, and you have to decide what to change. Which parts were essential? Which were accidents along the way? Nobody on your team knows, because you never made those choices. You hold <strong>a result without a history.</strong> Lippman and Rumelt called this causal ambiguity: when it is unclear, sometimes even to the owner, how the pieces produce the result, imitation falls short. A copy answers yesterday’s question. It has no way of reaching tomorrow’s.</p><h3>What the copy is missing</h3><p>Picture yourself as a product manager visiting a customer. Nothing dramatic is said, but you notice something nobody asked for: every Monday, their operations lead exports the weekly report to a spreadsheet and rebuilds it by hand. In the next planning session you mention it, half unsure it matters. The team asks why, and the real need surfaces. The customer doesn’t want a better report. They want to see which deliveries are at risk before the week starts. That becomes the intent, and with AI the first version ships within days.</p><p>Six months later, a competitor copies the feature screen by screen. They get the dashboard. They don’t get the Monday spreadsheet behind it, or the conversation that turned it into intent, so they can’t tell what to change when the customer’s needs move on.</p><p>What you carried out of that meeting was not in any ticket or repository. Polanyi called it tacit knowledge: we know more than we can tell. The engineer who just knows which part of the system will break next carries the same kind of knowing. No competitor can download it.</p><p>The advantage now lies in turning that kind of knowing into intent AI can build on. Once captured, though, it becomes explicit, and explicit knowledge spreads: through models, through people changing jobs, through competitors studying what gets shipped. What keeps the advantage alive is that people create new tacit knowledge every time they meet a customer. <strong>Tacit knowledge is a flow, not a stock.</strong></p><p>Think about what could have happened to the Monday spreadsheet instead. If it waits a week, much of it will be gone; Ebbinghaus showed in the 1880s how quickly memory fades unless it is revisited or used. If it passes through three layers and a handover, it arrives without its nuance. And if speaking up feels risky, it may never be shared at all. Amy Edmondson’s research on psychological safety, later echoed by Google’s Project Aristotle, found that people offer doubts and half-formed insights only when it feels safe to do so.</p><h3>Two organizations</h3><p>Step back now, far enough to see two organizations in the same domain, with the same tools and equally talented people. Code does not separate them.</p><p>In one, the Monday spreadsheet travels through layers before it shapes anything. In the other, the people who sensed it are in the room when intent is set. Over time, one keeps building on a slightly sharper truth than the other. The difference lies in what they keep doing, not in what they own.</p><p>In the Meta Model from NLP, a noun like <em>moat</em> would be called a nominalization, a process frozen into a thing. Seen from here, it thaws back into something moving: sensing, learning, shaping intent, deciding. <strong>The moat becomes a verb.</strong> What an organization produced yesterday can be copied. What it keeps doing is far harder to reach.</p><p>From this distance you also notice what has quietly accumulated in the second organization: a history of decisions and the reasons behind them. Pre-mortems, retrospectives and post-mortems, kept close to where the next decision is made, turn those reasons into guardrails. In <em>The Compass You Never Handed Out</em> intent was the direction; the whys mark the edges of the road. As long as someone keeps questioning them, they stay firm rather than hard.</p><p>People move through that organization differently too. Someone new plugs in and draws on the accumulated context within weeks. When someone leaves, much of what they knew is already in the system. And as AI takes on more of the building, the people doing the sensing matter more, not less.</p><h3>What makes it yours</h3><p>Go back to the thing you were proud of. It may still be valuable. But perhaps what makes it yours is how your people notice, decide and learn, and the reasons behind the choices that brought you here.</p><p>Perhaps ownership is shifting from possession to stewardship. A steward never owned the estate they looked after; their job was to care for it, make it thrive and hand it on in better shape than they found it. That may be the relationship knowledge now asks of us: less about stopping others from getting it, more about keeping it alive and growing.</p><p>It also puts strategy back at the centre. When anyone can build anything, choices set organizations apart: who they serve, what they say no to, and why. As I wrote in <a href="https://medium.com/@asbjorn_17696/build-organizations-to-behave-strategically-418ad0c08f70"><em>Build Organizations to Behave Strategically</em></a>, you don’t have a strategy problem, you have an identity problem.</p><p>Shifts like this are hard for a reason. Research on predictive processing, from Karl Friston, Lisa Feldman Barrett and others, describes the brain as predicting from internal models and updating them mainly when reality surprises it. Our maps of what protects a business were drawn in another era, and they change only when we notice where they no longer fit. I am still updating mine, with a few questions that keep coming back:</p><ul><li>If our code were copied tomorrow, what would we still have?</li><li>How long does it take an insight from a customer to shape what gets built?</li><li>Which past decisions could the team still explain the why of today?</li><li>If the best people left, how much of what they know would stay?</li><li>What are we continually getting better at doing?</li></ul><p><em>Maybe the moat is no longer something we own. Maybe it is something we keep doing.</em></p><h3>References</h3><ul><li>Lippman, S. A. and Rumelt, R. P. (1982). Uncertain imitability. <em>Bell Journal of Economics</em>.</li><li>Polanyi, M. (1966). <em>The Tacit Dimension</em>.</li><li>Ebbinghaus, H. (1885). <em>Memory: A Contribution to Experimental Psychology</em>.</li><li>Edmondson, A. (1999). Psychological safety and learning behavior in work teams. <em>Administrative Science Quarterly</em>.</li><li>Friston, K. (2010). The free-energy principle. <em>Nature Reviews Neuroscience</em>; Barrett, L. F. (2017). <em>How Emotions Are Made</em>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a60e1d3a88f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How the Best Leaders Read the Room, You Can Learn It Too]]></title>
            <link>https://medium.com/@asbjorn_17696/how-the-best-leaders-read-the-room-and-why-you-can-learn-it-too-f931f3acb50f?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/f931f3acb50f</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[acquired]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 14:28:32 GMT</pubDate>
            <atom:updated>2026-10-25T14:30:46.082Z</atom:updated>
            <content:encoded><![CDATA[<p>By Asbjorn Bjaanes</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LsAjHz97rpofNDUoLkpa3A.jpeg" /></figure><p>Most expensive mistakes in organisations do not come from a lack of effort. They come from solving the wrong problem with great focus.</p><p>A roadmap fills with features nobody needed. A specification is delivered to the letter and still misses the point. A steering meeting ends with a decision that three people in the room quietly doubted. Rework, scope creep and decision debt follow. In every case, the information that would have changed the outcome was in the room. Nobody was positioned to see it.</p><p>We tend to call the people who do see it intuitive, as if it were a gift. I think it is a skill. And it starts with something very simple: learning to use your peripheral perspective.</p><h3>The content is not where the information is</h3><p>Many coaching disciplines share one principle: pay attention to the process, not the content. The content is the agenda, the slide, the ticket, the request. The process is everything around it. Who goes quiet. Where the energy drops. Which question someone asks twice. Who looks at whom before answering.</p><p>Most leaders are trained to master the content. The decisions, though, are shaped by the process.</p><h3>Ohno’s circle</h3><p>Lean thinking has a beautiful illustration of this. Taiichi Ohno, one of the architects of the Toyota Production System, is known for drawing a chalk circle on the factory floor and asking a manager to stand in it and observe. No agenda, no fixing, just watching.</p><p>At first the manager sees details and wants to act on them. After a while, often after becoming quite bored, something shifts. They stop judging what they see and stop jumping to solutions. That is when the system appears: the flow, the waiting, the workarounds, the relationships between the moving parts.</p><p>The circle moves a person from doer to observer. That shift is exactly what most meetings lack.</p><h3>What the brain does under pressure</h3><p>There is a reason busy rooms miss the obvious. Under stress and pressure, attention narrows. Psychologists have long observed that arousal reduces the range of cues we take in. We get tunnel vision, quite literally, and fix on fewer and fewer details.</p><p>The relationship also seems to work the other way. Wide, panoramic vision is associated with a calmer, less aroused state, and researchers are exploring how deliberately widening your gaze can help settle the stress response. It is an emerging field, but the direction is consistent: narrow focus and pressure feed each other, and widening your view helps break the loop.</p><p>The research on insight points the same way. John Kounios and Mark Beeman found that moments of insight are more likely when attention is broad and relaxed than when it is tightly focused. What we call intuition looks a lot like a brain that has been allowed to take in more of the picture.</p><h3>Try it now</h3><p>Before reading further, try this. It takes about a minute.</p><p>Lift your eyes from the screen and rest them on one spot in front of you. Without moving your eyes, let your vision soften until you take in the whole space around you, the edges as well as the centre. Do not focus on anything.</p><p>Now, still without focusing, notice three things in your field of view. Do not study them. Just let them be there. Then two. Then one.</p><p>Now do the same with sound. Take in everything you can hear without attaching to any single sound. Then notice three sounds, then two, then one.</p><p>Finally, notice three things you can feel, the chair, your feet on the floor, your breath. Then two. Then one.</p><p>Notice how you feel now compared to a minute ago. Most people describe it as calmer, more spacious, more present. That state is where reading the room begins.</p><p>This sequence is adapted from a technique developed by Betty Erickson. I use it to train myself, and I use it in meetings when I notice I have been pulled into the details.</p><h3>The view from above</h3><p>None of this is new. Marcus Aurelius, writing to himself as Roman emperor, practised what is often called the view from above: imagining himself rising up and looking down on the whole scene, the people, their busyness, their concerns, from a height. Throughout the Meditations he also returns to the idea of separating what happens from the judgement we add to it.</p><p>That is Ohno’s circle in Stoic form. Step back, see the whole, and let go of the judgement long enough to see what is actually there.</p><h3>Zoom in, zoom out</h3><p>The wide view alone is not enough. The skill that makes the difference is moving between the wide view and the detail on purpose.</p><p>Machiavelli captured this in the dedication of The Prince. Landscape painters, he wrote, go down onto the plain to study the mountains, and climb the mountains to study the plain. To understand one view, you have to stand in the other.</p><p>In a meeting, it looks like this. I start in the wide view, taking in the room. Then I zoom in on one perspective and ask a powerful question about it. Then I return to the wide view, so I do not get stuck inside one person’s story. Then I zoom in on the next perspective, and out again.</p><p>Wide view tells you where to look. Curiosity tells you what to ask. One is how you notice, the other is how you act on what you notice.</p><h3>Proof from the floor</h3><p>Recently I took part in a leadership gathering where teams competed in two challenges. The first was the classic marshmallow challenge: build the tallest structure you can from spaghetti and marshmallows. The second gave us straws, cups, tape and a ping pong ball, with the goal of keeping the ball rolling for as long as possible.</p><p>Our team won both. Not because we were cleverer, but because we worked differently. Most teams saw the problem and became laser focused on the result. They turned into doers, doing the next obvious thing, forcing the piece into the hole without stepping back to see the shape of the hole.</p><p>We stepped back. We observed what was actually happening, adjusted as we went, and ran small tests early instead of betting everything on one big build at the end. Tom Wujec’s research on the marshmallow challenge shows the same pattern: kindergartners often beat business school graduates, because the children test as they go while the graduates plan, build and add the marshmallow at the very end, when the tower collapses.</p><p>For engineering and agile teams, this is shifting left. The wide view is what makes small, early tests feel obvious rather than slow.</p><h3>Where it pays off</h3><p><strong>In the executive room.</strong> Decisions are rarely made on the slides alone. Reading the room lets you see where alignment is real and where it is only polite, before the decision turns into debt.</p><p><strong>In product.</strong> Every PRD, RFP and RFI is content. The need behind it is the process. There is a line often attributed to Henry Ford: if I had asked people what they wanted, they would have said a faster horse. Whether or not he said it, the point stands. A faster horse is a request. More effective transportation is the need. You only see the need when you stop staring at the request.</p><p><strong>In engineering and delivery.</strong> Teams under deadline pressure narrow. A leader who holds the wide view can see where the team is stuck, where dependencies are hiding and where a small test would save a large rework.</p><h3>Know when you have been pulled in</h3><p>Nobody stays in the wide view all the time. The skill is noticing when you have left it. These are the signals I have trained myself to catch:</p><ul><li>My attention starts to fluctuate.</li><li>I turn inwards and start internalising.</li><li>I notice I have been triggered by an opinion.</li><li>I feel the urge to force my view onto the conversation.</li><li>I feel the urge to add value.</li></ul><p>That last one surprises people. Wanting to add value sounds like a good thing. Very often, though, it is the moment I have stepped out of observing and into my own agenda.</p><p>When I catch one of these signals, I have tools to lift myself back out, such as the moccasin walk, where you deliberately step into another person’s perspective, and moving between associated and dissociated states. Those deserve articles of their own.</p><h3>Your next meeting</h3><p>You do not need any of the deeper tools to start.</p><p>In your next steering meeting, refinement session or customer call, take a few moments to literally widen your view. Instead of focusing on one person or one screen, soften your gaze and let the whole room in, everything within it, without capturing the details.</p><p>Then notice what happens. Who has gone quiet. Where the energy shifts. Which question is not being asked.</p><p>A few seconds of wide vision. Most people feel the difference the first time. Practised regularly, it becomes what others will call your intuition.</p><p><em>I teach this, along with the deeper tools behind it, in my NLP programmes and in work with leadership, product and engineering teams. If you want to bring it to yourself or your team, feel free to reach out.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f931f3acb50f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Spec Is Not the Handover: Intent, AI-DLC and the Return of the Room]]></title>
            <link>https://medium.com/@asbjorn_17696/the-spec-is-not-the-handover-intent-ai-dlc-and-the-return-of-the-room-f9903e9c9f81?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9903e9c9f81</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 17:18:01 GMT</pubDate>
            <atom:updated>2026-10-24T17:18:01.235Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HaAW1SkwMlkukB2Q64yhRQ.jpeg" /></figure><p>In <a href="https://medium.com/@asbjorn_17696/the-compass-you-never-handed-out-why-intent-is-the-real-cure-for-scope-creep-1e600bbc809b">The Compass You Never Handed Out</a>, I made the case that scope creep is rarely a scope problem. It is a compass problem. Teams ask for more detail when what they are missing is intent.</p><p>The same mistake is now happening at AI speed. This time it is called spec-driven development.</p><h3>Spec-driven does not mean waterfall</h3><p>Many organisations hear spec-driven development and picture a familiar sequence. Product writes a complete, detailed specification. It gets handed over. Development builds it.</p><p>That is waterfall with a new label, and it misses the point of AI-DLC entirely. The intent behind AI-DLC is to put people together, shift product and domain expertise left, and have them work side by side every day.</p><p>The reason is human. We make sense of the world in a linear way, step by step, assuming a predefined plan leads to a predictable outcome. Much of business and leadership still runs on that mindset. Spec-driven sounds like it confirms it.</p><p>In reality, AI-DLC does the opposite. When people, agents and decisions connect in tighter circuits, speed increases until the work is no longer linear. At a quantum level, there is no distinction between past and future. Something similar happens in a bolt. Specifying, deciding and building no longer sit in separate phases. They happen in the same moment. The linear mindset is not wrong, it is simply too slow for what is now possible.</p><p>Look at what spec-driven actually means. Instead of working in code files, people work in the spec. It becomes the source of truth, and the agents turn it into code. If the spec is where the work happens, it cannot be a document that is finished and passed on. It has to stay alive for as long as the work does.</p><p>The spec is not a gateway between product and development. It is a shared artefact that evolves around the intent brought into the room.</p><h3>The principles still hold</h3><p>The Agile Manifesto turns 25 this year. Individuals and interactions over processes and tools. Customer collaboration over contract negotiation. Responding to change over following a plan.</p><p>AI-DLC does not replace any of this. It changes the cost of building. When building becomes fast and cheap, the bottleneck moves to how clear and how shared the intent is.</p><p>AI does not change the principles. It removes the excuses. Get intent wrong, and AI will help you build the wrong thing faster than ever.</p><h3>What teams really need from product</h3><p>Teams often say they depend on product for detailed specifications. They do not. They depend on intent. When the why is clear, the detail can be shaped by the people doing the work.</p><p>Product’s job does not change. Discovery stays the same. Product still explores, talks to users, understands the problem and matures a PRD, often in collaboration.</p><p>What changes is the purpose of the PRD. It is not there to answer every question in advance. It exists to carry three things into the room:</p><ul><li><strong>The intent.</strong> Why are we doing this?</li><li><strong>The preferred outcome.</strong> What does success look like?</li><li><strong>The workflows users will be working within.</strong> How do they move through the problem?</li></ul><p>A PRD should carry <a href="https://medium.com/@asbjorn_17696/how-i-apply-nlp-to-shift-the-way-prds-and-specifications-influence-outcomes-6214b8045b09">mental models, not instructions</a>, and <a href="https://medium.com/@asbjorn_17696/from-features-to-transformation-using-nlps-well-formed-outcomes-in-product-development-26d64cb7532f">well-formed outcomes</a> let a team model success before building begins. In AI-DLC, both become essential.</p><p>Intent is not owned by product alone. Engineering and design must bring intent around the technical architecture and the design. Everyone who holds a piece of the picture is responsible for bringing it.</p><h3>Who asks and who decides</h3><p>A bolt in AI-DLC is a short, focused cycle, typically one to three people working with AI agents.</p><p>In Scrum, the team breaks work into stories as tickets, separate from the code. In a bolt, stories become markdown files in the repository, next to the code, ready for the agents to build from.</p><p>The common mistake is to believe humans must now write every detail so the AI can execute. That is backwards. The AI asks the questions, based on the intent. The people in the bolt answer them and make the decisions. The AI surfaces the ambiguity. Humans own the judgement.</p><p>The spec is not an input to the collaboration. It is a record of it, growing with every question answered and every decision made.</p><p>Google’s recently open-sourced <a href="https://github.com/google/elephant-goldfish-model">Elephant-Goldfish Model</a> for spec-driven development makes the same point from another angle.</p><p>The elephant is a deep-context agent. It remembers the history, the architecture and the user journeys, and it drafts the spec.</p><p>The goldfish remembers nothing. It reads only the spec and the code, and tests whether the design holds up.</p><p>A goldfish is the perfect test of whether intent travelled. If a reader with no context cannot find the why, the intent stayed trapped with whoever wrote it.</p><p>This is not only true for agents. In every organisation, many people work like goldfish, acting on what is written and said. The question is whether we hand them the compass.</p><h3>Where product gets back into the room</h3><p>A popular belief says AI makes Agile ceremonies obsolete. No more daily stand-ups. The opposite is true.</p><p>Bolts start features that depend on other features, and those dependencies must be resolved. Product cannot sit in every bolt. In practice, product prepares with their own agents, often on the first day, and then the people are no longer in the same room.</p><p>The idea that product, with every decision, is always in the room is wishful thinking.</p><p>Science has known this for decades. In the 1970s, Thomas Allen at MIT showed that communication between engineers drops sharply with physical distance. Beyond roughly 50 metres, regular communication almost stops. This became known as the Allen curve. Distance does not have to be large to break the flow of intent. A different floor, a different calendar, a different bolt, or simply a different focus of attention is often enough.</p><p>Neuroscience adds another layer. Shared attention, people attending to the same thing at the same time, is increasingly recognised as a foundation for focus and collective performance. Which means the distance is not only physical. Two people can sit a metre apart, and if their attention is not shared, the distance reappears. The Allen curve applies to the mind as much as to the floor plan. Mental distance breaks the flow of intent just as surely as physical distance does. The stand-up is one of the few moments where attention is shared by design.</p><p>The daily stand-up is how product gets back into the room. It keeps decisions down to hours, not the weeks we accepted before Agile and again under scaled Agile. The AI raises the questions, the stand-up brings them to whoever holds the intent, and the decision flows back into the spec the same day.</p><p>This is not theory. It is a pattern that shows up quickly once bolts start running. The AI raises questions about edge cases and dependencies, and no one can answer them. Not because the detail is missing, but because the intent was never worked through before the bolt began.</p><p>When that happens, the stand-up is what prevents a full stall. It is where the gap becomes visible, and where the decision is made to pivot and replan the bolt. Without that daily touchpoint, teams keep building in the wrong direction, or keep waiting. Either way, time is lost.</p><h3>Fit the process to the reality</h3><p>There is no single right way to run AI-DLC, and there should not be.</p><p>Being truly agile means adjusting the process to the reality of the organisation. For some, bolts within sprints are the right fit. For others, a Kanban way of working serves better, where work flows continuously and blockers surface the moment they appear.</p><p>The deciding factor is what supports the business and its daily processes. Copying a framework by the book is not agility.</p><p>For leaders and executives, this means adjusting expectations. AI-DLC is not a way to remove people from the room. It is the reason the room matters more. The human factor, the communication and the mindset are what make it work.</p><h3>Bring the compass into the room</h3><p>The mindset that must go is the belief that everything can be specified perfectly before work begins.</p><p>Product must still have explored. Product, engineering and design must still bring intent around the problem, the architecture and the design. But the spec is not where the conversation ends. It is where it begins.</p><p>The next time a bolt starts, look at what is brought into the room. A stack of detail, or a compass? Then look at what the AI asks, and who is there to answer.</p><p>The spec was never meant to be the handover. It is the conversation, written down.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9903e9c9f81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Compass You Never Handed Out: Why Intent Is the Real Cure for Scope Creep]]></title>
            <link>https://medium.com/@asbjorn_17696/the-compass-you-never-handed-out-why-intent-is-the-real-cure-for-scope-creep-1e600bbc809b?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e600bbc809b</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[acquired]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 20:53:54 GMT</pubDate>
            <atom:updated>2026-10-23T20:53:54.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1iauSfDI2OXWlT--ZF3JVA.jpeg" /></figure><p>I keep seeing the same pattern. Teams keep pushing. Deadlines are missed. And when you ask what success looks like, nobody can really answer. Not because they disagree, but because no one ever described what success looked like.</p><p>This came back to me recently in discussions about roadmaps, and in projects where I watched the scope grow and grow. It shows up in all kinds of projects, but especially in software. And every time, the root is the same. There is no intent.</p><h3>Pushing pieces through a hole you cannot see</h3><p>Imagine being handed a box of shapes and a hole. You do not know whether the hole is square, round or triangular. So you push. One shape does not fit, so you try another. Someone gives feedback, so you try a third. Every attempt adds something new to the work.</p><p>That is what scope creep looks like from the inside. It is not that people are lazy or that customers are unreasonable. It is that the team is reacting, passing things through without ever stepping back to ask what shape they are trying to fit.</p><p>Now imagine the same situation with intent. The intent is to match the shape. Suddenly the behaviour changes. You stop pushing and start looking. You use your peripheral vision. You navigate, you sense, you adjust.</p><h3>Intent is the compass</h3><p>Intent is the compass for whatever you are trying to achieve. It does not tell you every step. It tells you which way is north.</p><p>Without a compass, every piece of feedback feels like a new destination. With a compass, feedback becomes course correction. That single difference is what separates a team that converges from a team that drifts.</p><h3>Two scenarios, one outcome</h3><p>In my experience there are two different ways a team ends up without intent.</p><p>The first is <strong>absent intent</strong>. It is missing all the way through the stack. Leadership has not described it, product has not described it, and the team has not asked for it. Everyone is reactive, and everyone is busy.</p><p>The second is <strong>trapped intent</strong>. This is common in micromanaged teams. The intent actually exists. It sits with whoever is defining the goal, the scope and the target. It just never reaches the team. The team receives tasks without the why.</p><p>Two different causes. A very similar outcome. A team pushing pieces without knowing the shape.</p><p>It is worth pausing here and asking yourself: which one am I in?</p><h3>A belief worth letting go of</h3><p>Some people believe that feeling micromanaged is a sign of growth. I do not buy that. Of course, the feeling can be misread. Sometimes what feels like micromanagement is really someone asking for traction, and that is a fair ask. But being handed tasks without intent is not growth. It is a team being kept away from the compass.</p><p>So if it feels like micromanagement, pause before you react. Notice whether it is an ask for traction or actual micromanagement. The test is intent. If there is an intent behind the ask, it is about traction, and you still have room to choose how you get there. If there are only tasks and check-ins and no why, that is micromanagement. And if you cannot see the intent, ask for it before you decide. It might simply be trapped somewhere above you.</p><p>Intent is shared. It can be a leadership gap, but it can also be a team gap. Anyone, at any level, can be the one who stops and asks: what does success look like?</p><h3>The detail illusion</h3><p>There is another belief I see often. The belief that to hit the target, you need a lot of detail.</p><p>It is the opposite. When you have the intent, you need less detail. A team that knows why can fill the gaps themselves, and they will make good calls in places no specification ever anticipated.</p><p>So when I see people asking for more and more detail, I treat it as a symptom. The ask for detail is very often a signal that intent is missing.</p><h3>What to do about it</h3><p>When the ask comes to me, I answer with the why instead. More often than not, the question changes, or disappears.</p><p>When I am advising on a project and see the symptom, I help surface the intent using whatever fits the context. Sometimes that is OKRs, where the objective carries the intent and the key results describe what success looks like. I have written about how OKRs lose their power when they become structure without direction in <a href="https://medium.com/@asbjorn_17696/the-okr-illusion-why-structure-without-direction-is-just-noise-09b12e325626">The OKR Illusion, Why Structure Without Direction Is Just Noise</a>.</p><p>Other times it is about making the roadmap or backlog tell a story, so the why is visible in the work itself. More on that in <a href="https://medium.com/@asbjorn_17696/telling-the-story-through-your-sprint-backlog-making-agile-transparent-again-27e01d6975f1">Telling the Story Through your Sprint Backlog</a>, and <a href="https://medium.com/@asbjorn_17696/the-backlog-illusion-when-one-story-leads-to-four-realities-1cc6fd2a0bfa">The Backlog Illusion</a>.</p><p>And sometimes it is about how we write initiatives and specifications, so they carry intent rather than just requirements. See <a href="https://medium.com/@asbjorn_17696/how-i-apply-nlp-to-shift-the-way-prds-and-specifications-influence-outcomes-6214b8045b09">How I Apply NLP to shift the way PRDs and specifications Influence Outcomes</a>, and <a href="https://medium.com/@asbjorn_17696/from-features-to-transformation-using-nlps-well-formed-outcomes-in-product-development-26d64cb7532f">From Features to Transformation</a>.</p><h3>Hand out the compass</h3><p>Scope creep is rarely a scope problem. It is a compass problem.</p><p>So here is my invitation. The next time someone asks you for more detail, pause. Offer the why first. Then notice what happens. You might find that the shape of the hole was never the mystery. Nobody had simply described it yet.</p><h3>Hand out the compass</h3><p>Scope creep is rarely a scope problem. It is a compass problem.</p><p>So here is my invitation. The next time someone asks you for more detail, pause. Offer the why first. Then notice what happens. You might find that the shape of the hole was never the mystery. Nobody had simply described it yet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e600bbc809b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If You Keep Prioritizing the Urgent, You Will Never Get to the Important]]></title>
            <link>https://medium.com/@asbjorn_17696/if-you-keep-prioritizing-the-urgent-you-will-never-get-to-the-important-1ed7478ed1c4?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ed7478ed1c4</guid>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[business-development]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Wed, 29 Jul 2026 09:48:02 GMT</pubDate>
            <atom:updated>2026-08-16T18:51:54.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OmE7cDS7dGq5xLCmgznOMw.jpeg" /></figure><p>Many of you will recognize the story of the teacher and the jar. He filled it with sand, then pebbles, then tried to force in big marbles, and of course they wouldn’t fit. So he started over, marbles first, then pebbles, then sand, and everything settled into place perfectly. The marbles are the important things. The sand and pebbles are the urgent, lower value things that expand to fill whatever space we give them.</p><p>This is exactly what happens in software and product development. Most teams I’ve worked with start from a place where urgent work consumes everything, and more urgent work keeps arriving. Ask why, and the answer is always the same, we don’t have time, we need more resources. But if you only ever serve the urgent, you never reach the important, the genuinely value adding work. The problem is, more resources rarely fix this, because urgent work has a way of expanding to consume whatever capacity you give it. The problem usually isn’t a lack of hands, it’s a lack of protected space.</p><h3>Start with honest allocation</h3><p>Start with deliberate capacity allocation. Split your team’s time into three buckets: value added work, housekeeping (things like refactoring, maintenance, and performance improvements), and genuinely urgent work (critical defects and time sensitive fixes).</p><p>But don’t assume some ideal ratio, like eighty percent value and twenty percent everything else, is where you should start. If an organization is carrying heavy technical debt or a large backlog of urgent commitments, treat this like a financial recovery plan. Just as someone in debt might need a larger down payment for a while before they can increase spending again, a team may need to allocate more capacity to urgent work and debt burn down at first, gradually shifting the balance toward value as the pressure eases.</p><p>Action point: before you touch your backlog, get honest about how deep the hole is, and set your starting ratio accordingly, not aspirationally.</p><h3>Making it stick requires courage</h3><p>Leaders need to be told upfront, before the work even begins, that there will be a painful period where the urgent pile hasn’t shrunk yet even though you’ve already pulled capacity away from it. That’s precisely the moment discipline matters most, because the instinct will be to abandon the plan and go back to firefighting.</p><p>Action point: agree on the plan and the expected pain, before you start, so that when the dip comes, everyone can point back to what was agreed rather than negotiating fresh in a moment of panic.</p><h3>Build a shield</h3><p>This is also why strong middle management, or Scrum Masters if you’re using that framework, matter so much. They act as a shield, absorbing pressure from stakeholders and customers so engineers aren’t pulled directly into the chaos and pushed off the plan. If leadership or customers have direct, unfiltered access to engineers during this period, the whole thing tends to collapse.</p><p>Action point: invest deliberately in that middle layer, train them, back them publicly, and make it clear that redirecting urgent requests through the process is their job, not a failure of responsiveness.</p><p>But be honest about the precondition here. This shield only holds if senior leadership has visibly committed to defending it in the specific moment someone tries to go around it, not just in principle, in the room, when a VP escalates past the Scrum Master to lean on an engineer directly. In organizations without much cross departmental trust, this is often the hardest part of the whole approach, harder than the framework, harder than the math. If a Scrum Master says no once and gets overruled, everyone learns instantly that the shield was theater, and the old habits come rushing back. So this isn’t a one time investment, it’s a standing commitment that has to be tested and honored repeatedly before people believe it’s real.</p><h3>Two audiences, two kinds of proof</h3><p>Belief doesn’t change through good intentions alone, especially among executives who are measured quarter to quarter. When the pain hits, and it will, customer satisfaction or delivery numbers may dip for a period, and the people closest to that pain, team leads, engineers, need real coaching and change management support to hold steady. Senior leadership, further from daily operations, needs something different, constant transparency and a steady stream of small, tangible wins translated into language they trust, reduced churn, cost savings, measurable delivery gains.</p><p>Action point: set up a lightweight, recurring update, weekly or biweekly, that shows leadership one or two hard numbers moving in the right direction, even if they’re small. Momentum, made visible, is what buys you the runway to keep going.</p><h3>Nest your frameworks inside the allocation</h3><p>Underneath all of this sits a simple mechanical truth, the eighty-twenty rule. Most value comes from a small fraction of effort, so protecting that fraction is what allows the marbles story to compound over time into genuinely excellent products and durable customer loyalty.</p><p>Once you have your buckets, nest your prioritization frameworks inside each one rather than applying one framework across everything. Use something like RICE or weighted shortest job first within the value bucket, and a simpler, lighter framework within the housekeeping and urgent buckets. This way nothing urgent can sneak into the value lane just because it shouted the loudest, everything has to compete on its own turf, within its own allocation.</p><p>Action point: this is a very practical thing any team can implement this quarter, without waiting for organizational buy-in on the whole philosophy first.</p><h3>What success actually looks like</h3><p>The payoff, when it finally arrives, shows up in two places at once. In the numbers: rising velocity, falling defect rates, faster time to resolution. And in the people, a spark returning in teams who had lost motivation, now rediscovering the satisfaction of building something properly instead of endlessly patching what’s broken.</p><h3>A few questions worth sitting with</h3><p>Consider these questions instead:</p><p>How much technical debt is your organization actually carrying, honestly, not optimistically?</p><p>Who in your organization is currently absorbing the pressure that should be hitting a process instead?</p><p>What’s the one small, visible win you could surface to leadership this month to buy yourself a little more runway?</p><p><em>Put the marbles in first. The sand will always find a way to fit around them.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ed7478ed1c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emotional Engineering, How the Feeling Has to Travel]]></title>
            <link>https://medium.com/@asbjorn_17696/emotional-engineering-how-the-feeling-has-to-travel-19ba39ec3571?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/19ba39ec3571</guid>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[business-development]]></category>
            <category><![CDATA[behavioral-psychology]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Sun, 26 Jul 2026 11:52:13 GMT</pubDate>
            <atom:updated>2026-07-29T07:45:19.624Z</atom:updated>
            <content:encoded><![CDATA[<h2>You are Not Pitching a Product or Idea, You are Selling a Feeling That Has to Travel</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bvK0wNGHrIILaNrLm3Y3GQ.jpeg" /></figure><p>Every decision anyone ever makes is emotional first and logical second. We like to think we buy, invest, hire, or say yes because of spreadsheets and pros and cons lists, but underneath all of that is a much simpler mechanism. People make decisions to feel good, and everything else, the reasoning, the justification, the business case, is just the costume that feeling wears so it can go out in public.</p><p>Here’s the distinction worth sitting with. Sometimes people want something and then go looking for reasons to justify it. That justification is a kind of fiction, a story built after the fact to satisfy what we imagine the outside world expects of us. Other times, there’s no need for justification at all, the good feeling is the whole point. Nobody needs a spreadsheet to justify a moment of joy or comfort. But most decisions live somewhere in between, a mix of wanting to feel good and needing a story that makes the feeling look reasonable.</p><p>This means the real job, whether you’re pitching a product, closing a sale, or just meeting someone at a networking event, is to make the other person feel good. Confident, valued, curious, at ease. That’s the actual transaction happening underneath the visible one.</p><p>Most of us secretly believe the pitch is the moment of truth. We prepare for it, rehearse for it, obsess over the room, the slide, the handshake, as if that’s where the decision actually gets made. But it isn’t. The real moment of truth happens later, alone, in someone else’s head, in a kitchen or a boardroom you’re not invited to, when the feeling you gave them has to survive without you there to protect it.</p><p>This is the belief worth ripping the Band-Aid off. If you think your job ends when they nod and say yes, you’ve mistaken the spark for the fire. The spark happens in the room, with your energy and timing working in your favor. The fire is what happens after, when your buyer is alone with your absence, and the feeling either turns into a story that spreads, or an itch of doubt.</p><p>So the work isn’t generating a good feeling once. It’s engineering a version of that feeling sturdy enough to survive being retold by someone else, in a conversation you’re not even in.</p><p>That gives us a rough shape for how this plays out. First, the spark, the initial contact, where the only job is generating an authentic positive feeling. Second, the story, handing them the justification, the logical packaging their feeling can wear when it travels. Third, the wobble, planning proactive check ins that recharge the original feeling before doubt wins. Fourth, the translation, arming them explicitly with the language and proof points the next person will respond to. And fifth, the afterglow, where the product or relationship has to outperform the feeling that sold it in the first place.</p><p>The same mechanism shows up anywhere someone has to carry a feeling forward without you present, a user clicking through a product alone, or an employee advocating for change to skeptical colleagues in a room you’re not in.</p><p>Which brings us to the real craft. Feelings themselves can’t travel, only the packaging around them can. So the actual work of emotional engineering is compression, taking something as private as a feeling and turning it into a phrase, a story, a proof point, portable enough that a stranger can pick it up and feel a version of what the original person felt, even secondhand.</p><p>Business, at its core, is the discipline of making people feel good, and then engineering that feeling well enough that it survives the trip to everyone who wasn’t in the room.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19ba39ec3571" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your estimates are not done yet, shift your model]]></title>
            <link>https://medium.com/@asbjorn_17696/your-estimates-are-not-done-yet-shift-your-model-d2c89d95d849?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2c89d95d849</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 22:40:09 GMT</pubDate>
            <atom:updated>2026-08-12T13:21:38.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFmewccDtkLLT8VN3cZFgg.png" /></figure><p>There is a conversation that happens in almost every product organisation at some point. A customer asks about the roadmap. A stakeholder wants to understand where things stand. And someone pulls up a list of stories, points at completion percentages, and hopes the numbers tell the story.</p><p>They never do.</p><p>Progress visibility is not a reporting problem. It is a structural problem. And until you address the structure, no dashboard, no metric, and no velocity chart will fix it.</p><h3>The Misconception That Slows Everything Down</h3><p>The most common belief I encounter is this: to show accurate progress, you need maximum detail. Break everything down, estimate every story, map every dependency, and then you will finally have a true picture of where things stand.</p><p>This belief feels logical. It is also wrong.</p><p>Detail without context is noise. And detail applied too early does something far more damaging than noise. It turns a team focused on solving problems into a team focused on following instructions. The moment you fully specify work that is six months away, you have stopped building toward an outcome. You have started building toward compliance.</p><p>The team’s energy shifts. Instead of asking “what is the right thing to build?” they ask “have we ticked all the boxes?” The stories become the goal, not the solution. And when the context changes, as it always does — nobody questions the stories, because the stories were the plan.</p><h3>Roadmaps Are Not Contracts. They Are Bets.</h3><p>The language we use around roadmaps matters enormously. When we call something an estimate, we imply a level of precision we rarely possess. When we call it a commitment, we create a contract. And contracts shift the team’s energy from solving to complying.</p><p>The honest framing is different. A roadmap is a series of progressively refined bets. Each bet is placed with the best information available at that moment, at the right level of confidence for that stage of the work. As new information arrives, the bet is updated.</p><p>This is not vagueness dressed up as methodology. It is how every credible forecasting system in the world operates. Weather forecasters don’t give you a single point on a map where a hurricane will make landfall. They show you a cone of uncertainty, all possible paths, with the most likely path in the centre. The wider the cone, the greater the uncertainty.</p><p>A roadmap should work exactly the same way. Wide at the initiative level. Narrowing at the epic level. Tight at the story level, where the work is imminent and the context is real.</p><h3>The Science of Probabilistic Refinement</h3><p>This is what makes a roadmap credible, not the volume of detail, but the honesty of the probability distribution at each layer, and the discipline with which it is updated as evidence arrives.</p><p>This is precisely what Bayes’ Theorem describes. You start with a prior belief — your initial bet on the size and timing of an initiative. As evidence accumulates; completed stories, spike results, velocity patterns, you update that belief to form a posterior probability. The posterior is not more accurate because you planned better upfront. It is more accurate because it is informed by real data from inside the work.</p><p>This has a critical implication for how teams should think about estimation. Writing 40 stories for an epic before the work begins does not produce evidence. It produces assumptions dressed as detail. The cone does not narrow because you specified more. It narrows because you learned more. And the only way to learn is to start.</p><p>Instead of providing single-point estimates, teams can use probabilistic forecasting to communicate ranges of possible outcomes. A team might determine there is a 50% chance they will complete an epic in 8 sprints, a 70% chance in 10 sprints, and a 90% chance in 12 sprints. That is not imprecision. That is an honest model of reality that customers and stakeholders can actually plan around.</p><p>The research confirms why the alternative fails. Average time overruns in software development increased from 63% to 82% between 2000 and 2007, a period when detailed upfront planning was standard practice. The planning fallacy arises from optimistic bias and over-reliance on best-case internal scenarios, failing to account for switching costs, typical delays, and unanticipated complexities. Writing more stories does not fix optimism bias. It embeds it deeper into a structure nobody then wants to challenge.</p><p>Probabilistic forecasting embraces variation and says: we know there is uncertainty, let us model it rather than pretend it does not exist. That shift, from false certainty to honest probability, is what builds durable trust with customers and stakeholders.</p><p>Feeding a prediction model with unearned detail does not reduce uncertainty. It hides it, until reality forces it back into the open.</p><h3>The Abstraction Ladder</h3><p>The initiative → epic → story hierarchy exists for a reason. Each layer carries a different confidence level, and that confidence is earned through learning, not declared through planning.</p><p>An initiative is a wide bet. Strategic direction, rough size, high uncertainty. It does not need stories yet because the data to justify them does not exist yet.</p><p>As the initiative matures into epics, spikes sharpen the probability distribution. A spike is not delivery work — it is learning work. It answers the questions that make the next bet tighter. Each spike is a Bayesian update. The cone narrows.</p><p>As epics move toward sprints, stories emerge progressively from work that is actually imminent. An epic estimated at 300 hours might have 150 hours broken into active stories and 150 hours deliberately left as a rough band. As the first stories close, the remaining band adjusts — tighter, more honest, more credible.</p><p>That adjustment is the progress signal. The posterior is more accurate than the prior. The cone is visibly narrowing. That is not a planning failure. That is the system working exactly as it should.</p><h3>Progress Visibility</h3><p>Three things make progress genuinely visible across the hierarchy.</p><p>Initiatives must be tied to measurable outcomes. “Reduce time-to-value for new customers” shows progress. “New onboarding flow” does not.</p><p>Epics must carry honest probability ranges, updated as spikes and completed stories narrow the cone. The recalibration is the signal, not a failure to be explained away.</p><p>Story-level work belongs in the sprint, not on the roadmap. When customers ask about progress, they are asking at the initiative or epic level. Showing them stories is like answering “how is the journey going?” with a list of left turns.</p><p>Show the direction. Show the narrowing cone. Show what you have learned and how it has tightened the picture.</p><p>That is a roadmap customers can trust. Not because it promises certainty. Because it is honest about uncertainty, and visibly reducing it, sprint by sprint, bet by bet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2c89d95d849" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 15-Minute Daily Habit That Connects Every Team to a Shared Truth]]></title>
            <link>https://medium.com/@asbjorn_17696/the-15-minute-daily-habit-that-connects-every-team-to-a-shared-truth-2cb66ae04346?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cb66ae04346</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Mon, 20 Apr 2026 07:24:29 GMT</pubDate>
            <atom:updated>2026-04-20T07:24:29.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BMhM_Zl8h-4zg-5_Yrqbg.jpeg" /></figure><p>Most organisations that scale Agile do one of two things. They either import a heavyweight framework and spend six months configuring it, or they let teams run independently and discover, too late, that no one is rowing in the same direction. There is a third path, and it is surprisingly simple.</p><p>It is called the Scrum of Scrums, and when you run it well, it becomes what practitioners often refer to as the Boardwalk.</p><h3>What Is the Boardwalk and Scrum of Scrums?</h3><p>The Boardwalk is a daily coordination event where one representative from each Scrum team meets with representatives from all other teams. It runs every single day and takes no more than 15 minutes. Think of it less as a meeting and more as a pulse check, a shared heartbeat across multiple teams working toward a common product or goal.</p><p>Where a single team has its Daily Scrum to synchronise within itself, the Boardwalk is the mechanism that synchronises across teams. It answers three essential questions:</p><ul><li>What did my team complete that other teams need to know about?</li><li>What is my team working on next that may affect other teams?</li><li>What is blocking my team that someone in this room might be able to remove?</li></ul><p>The name “Boardwalk” captures the intent well. You are not sitting in a conference room reviewing slide decks. You are walking the board, moving across the shared landscape of work in progress, spotting the connections and collisions before they become expensive.</p><h3>The Burndown Chart as a Shared Truth</h3><p>One of the most powerful elements you bring into a Boardwalk session is a shared burndown chart at program level, one that aggregates the progress of all participating teams toward a release or milestone.</p><p>A burndown chart answers a deceptively simple question: are we on track?</p><p>The vertical axis shows the work remaining, typically in story points or feature units. The horizontal axis is time. The ideal burn is a straight diagonal line from the total scope at the start to zero at the end. Reality rarely follows the ideal. That gap between where the line is and where it should be is your most honest conversation starter.</p><p>In a Boardwalk context, the burndown does something beyond tracking progress. It makes cross-team dependencies visible in a way that words rarely can. If Team A is running ahead while Team B is stalling on a shared integration, the chart reveals the asymmetry instantly. Without it, both teams might spend weeks believing the problem belongs to someone else.</p><p>Because the Boardwalk happens every day, the burndown is reviewed every day. Course corrections happen in hours, not weeks. That is the entire point.</p><h3>Short Feedback Loops as a Competitive Advantage</h3><p>The deepest value of the Boardwalk is not the event itself. It is the daily cadence it creates.</p><p>When teams meet every day to synchronise, the feedback loop between action and awareness shrinks to its minimum. An impediment raised on Monday gets visibility on Tuesday. A scope change discovered on Wednesday gets communicated before it derails Thursday’s work. The cost of a miscommunication drops by an order of magnitude simply because the gap between the mistake and the correction is measured in hours.</p><p>This is the often-overlooked competitive advantage that scaling frameworks miss when they add ceremony in the name of coordination. The goal is not more meetings. The goal is faster signal. The Boardwalk, at 15 minutes per day, is a signal amplifier with almost no overhead.</p><p>Short feedback loops also serve the people involved. Teams that operate inside tight information cycles feel less isolated. They understand how their work connects to a larger outcome. That is not just a morale benefit. It is a performance driver. People perform differently when they can see the impact of what they are building in near real time.</p><h3>Making the Boardwalk Work in Practice</h3><p>A few principles separate a Boardwalk that creates real value from one that becomes another coordination tax.</p><p><strong>Daily, without exception.</strong> The power of the Boardwalk is in its consistency. Skipping a day breaks the rhythm and lets small misalignments grow into real problems overnight.</p><p><strong>15 minutes is the ceiling, not the target.</strong> If a conversation needs to go deeper, it becomes a sidebar after the session, not a detour inside it. Protect the time boundary and people will respect the format.</p><p><strong>Send the right representative.</strong> The Boardwalk representative should be someone with enough technical and delivery context to speak for their team meaningfully. This is not always the Scrum Master. Sometimes it is a lead developer or a product owner.</p><p><strong>Use the board, not the report.</strong> A visible board or live burndown on screen is far more effective than a verbal status update. Make the data the centrepiece, not the talking head.</p><p><strong>Treat impediments as design flaws, not complaints.</strong> When a team surfaces a blocker at the Boardwalk, the response should not be sympathy. It should be ownership. Who in this group has the ability to remove or escalate this today?</p><h3>The Transformation Waiting Inside the Practice</h3><p>What looks like a 15-minute coordination ritual on the surface is actually something more significant. The Boardwalk, run daily and consistently, gradually shifts how teams think about ownership and accountability. Teams stop optimising for their own sprint and start optimising for the collective release. They start caring about the team next to them because they see, every morning on a shared burndown, that their success is directly connected.</p><p>That is not just an Agile practice. That is a cultural shift toward collective performance and shared responsibility. And in organisations where that shift takes hold, the burndown chart stops being a reporting tool and starts being what it was always meant to be: a shared truth that keeps everyone aligned and moving forward together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cb66ae04346" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything You Think Makes Sprint Planning Work, Is Slowing Your Team Down!]]></title>
            <link>https://medium.com/@asbjorn_17696/everything-you-think-makes-sprint-planning-work-is-slowing-your-team-down-8643f6d1ba54?source=rss-a659414b9495------2</link>
            <guid isPermaLink="false">https://medium.com/p/8643f6d1ba54</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Asbjorn Bjaanes]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 18:11:54 GMT</pubDate>
            <atom:updated>2026-03-28T18:11:54.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDFEHG7sj8JP9l8zVAXrnQ.jpeg" /></figure><p>You have probably sat in a sprint planning session that felt productive.</p><p>Stories were discussed. Estimates were given. The team left with a plan.</p><p>And then the sprint unfolded the same way it always does. Work piled up mid-week. Commitments slipped. The review felt like damage control.</p><p>The planning was not the problem you thought it was.</p><p>The beliefs running underneath it were.</p><h3>You assigned the work. That is where it went wrong.</h3><p>If you lead a team, you have probably assigned stories in planning.</p><p>It feels like the responsible thing to do. You know the priorities. You know who is best suited for what. Letting the team figure it out feels slow, even risky. So you point at the work and tell people what to pick up.</p><p>The team nods. Planning finishes on time.</p><p>What you have just done, without intending to, is removed the one thing that makes people perform well under pressure: the sense that the work is theirs.</p><p>One of the most consistent patterns in human behavior is that people act differently depending on where they believe the source of control sits. When the source is internal, when you chose this, when this belongs to you, people self-correct. They stay engaged when it gets difficult. They make decisions without waiting to be told. When the source is external, when this was handed to you, the relationship to the work changes entirely. You execute. You report. You wait.</p><p>The developer who chose the story and the developer who was assigned the story are not the same developer in the sprint.</p><p>One owns the outcome. The other owns the task.</p><p>You built a compliant team. Then you wondered why nobody showed initiative.</p><p>The people closest to the code know which stories need a conversation before they start. They know what is actually small and what is deceptively large. They know where the risks are hiding. That knowledge does not exist at the level where assignment decisions are made.</p><p>Let the team use it.</p><h3>Estimation is not about accuracy</h3><p>Most teams treat estimation as a forecasting exercise. The point is to get the number right. If the number is wrong, the estimate was bad. If estimates are consistently wrong, either the team is not trying hard enough or the stories are not well-defined enough.</p><p>This belief produces a very specific behavior. Teams learn to converge quickly on a number that feels safe. Disagreement is inefficiency. A long estimation discussion means something went wrong.</p><p>So people learn to read the room and anchor to the first number that sounds reasonable.</p><p>And they carry all their unspoken assumptions directly into the sprint.</p><p>Here is what estimation is actually for. When one developer puts up a 2 and another puts up an 8, they are not both guessing at the same thing. They have built different internal pictures of the work. One of them has a model that includes a dependency, a technical constraint, or a layer of complexity the other has not seen yet.</p><p>That gap is not a problem. That gap is information.</p><p>Planning poker asks everyone to reveal cards simultaneously for exactly this reason. It protects each person’s independent model before the group converges. The moment someone says “I’m thinking a 5, what does everyone else think,” the anchoring has already happened. Estimates that follow are no longer independent. They are reactions.</p><p>The conversation that surfaces when two people see the work differently is where alignment is built. Assumptions are named. Ambiguity is resolved before it becomes a mid-sprint misunderstanding. The story becomes the same story in everyone’s mind.</p><p>A five-minute disagreement in planning is the cheapest version of that conversation. The alternative is a three-day misunderstanding mid-sprint.</p><p>If your estimation sessions feel fast and smooth, ask yourself what is not being said.</p><h3>You may think staying involved keeps things on track</h3><p>Mid-sprint, a priority shifts. A stakeholder flags something urgent. You have a request that will only take a day.</p><p>So you bring it to the team. You are not demanding they drop everything. You are just raising it. Surely they can absorb one small addition.</p><p>What the team hears is different from what you said.</p><p>They hear: your commitment was conditional. Your judgment about what fits in a sprint is subject to revision. The plan you made in planning was a starting point, not an agreement.</p><p>People are consistent with their stated commitments. When a team publicly commits to a set of work, that commitment shapes behavior across the entire sprint. It guides decisions at the end of a long day. It creates a frame for saying no to distractions. The moment the sprint backlog becomes negotiable from the outside, that frame dissolves.</p><p>Teams do not stop committing because they are disengaged. They stop committing because they have learned, sprint after sprint, that commitments do not hold. So they stop making real ones. Estimates become buffers. Planning becomes performance.</p><p>You thought you were helping. You were slowly teaching the team that planning does not mean anything.</p><p>The sprint backlog belongs to the development team. Not the product owner. Not the engineering manager. Not the head of product.</p><p>Protect it accordingly.</p><h3>A list of stories is not a goal. It is a to-do list.</h3><p>Look at most sprint planning sessions and you will find a list of stories, a capacity number, and a velocity target.</p><p>But No goal.</p><p>This feels fine because the stories are right there. Everyone knows what they are building. What else would a goal add?</p><p>It adds a compass.</p><p>Without a goal, every story in the sprint carries equal weight. When something unexpected happens, and it always does, the team has no way to decide what to protect and what to drop. Decisions are made in isolation. People optimize locally. Energy distributes toward whatever is loudest, not whatever matters most.</p><p>A sprint goal answers one question: if we could only get one thing right this sprint, what is it?</p><p>That question is uncomfortable. If the team cannot answer it, the stories they have chosen may not actually belong together. They may just be the next items in the backlog. That discomfort is not a sign of bad planning. It is planning doing its job, surfacing incoherence before the sprint starts rather than halfway through it.</p><p>A goal also needs to be specific enough that the team knows what success looks and feels like. Not “improve the onboarding experience.” Something they can stand in front of at the sprint review and verify. When the goal is vague, the evidence of success is vague. When completion is vague, so is the sense of progress. And when progress is invisible, motivation follows it down.</p><p>A team without a sprint goal is not moving toward something. It is just moving.</p><h3>You may think rolling over saves time</h3><p>A story did not complete. Most of the work is done. Sending it back to the backlog feels wasteful, even absurd. The team already understands it. The estimate is still valid. Just carry it over and finish it in the next sprint.</p><p>This feels like efficiency.</p><p>It is one of the quieter ways teams end up working on the wrong things.</p><p>The human mind gives disproportionate attention to unfinished work. Incomplete tasks occupy mental space in a way that finished ones do not. They feel urgent. They pull focus. That pull has nothing to do with actual priority. It is a cognitive response to incompletion, not a signal that the work is still the most valuable thing to do next.</p><p>Underneath that is something even stronger. Work that has already been invested in, estimated, discussed, and partially started, feels like an asset. Sending it back feels like a loss. So we protect it. We carry it forward without asking whether it has earned its place in the next sprint.</p><p>And beneath both of these is the quietest distortion of all. The hours already spent on a story are not an argument for continuing it. They are gone regardless of what happens next. The only question that matters is whether this work is still the highest priority given what is known today.</p><p>Priorities change. Frequently. What was most important two weeks ago may not be most important now. When you roll a story forward automatically, you remove it from that competition. It enters the next sprint without being evaluated against everything else, carrying inherited urgency it may no longer deserve.</p><p>You are not abandoning the work. You are refusing to protect it from scrutiny.</p><p>Every story that did not complete goes back to the product backlog. It competes with everything else for the next sprint. If it is still the most important thing, it surfaces on its own merits. If it does not surface, you have just learned something real about its actual priority.</p><h3>What changes when the beliefs change</h3><p>None of what is described above is a process failure.</p><p>Assigning work, rushing estimation, interrupting sprints, skipping goals, rolling over stories. These are not mistakes made by careless teams. They are the natural output of beliefs that have never been examined.</p><p>Beliefs about who knows best. About what efficiency looks like. About what it means to be helpful. About the relationship between control and performance.</p><p>Those beliefs are not visible on a Jira board. But they show up in every planning session, in who speaks, who decides, who commits, and who carries the same story forward for the fourth sprint in a row.</p><p>Process improvements applied on top of unchanged beliefs produce the same results with more steps.</p><p>The teams that plan well are not using a better framework. They are operating from a different set of assumptions about people, ownership, and what commitment actually means.</p><p>Change the beliefs in the room. The process follows.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8643f6d1ba54" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>