Insights
Stories from inside the systems where work moves.
Field notes, patterns, and articles, organized by the part of the system each one reveals.
Search and filter stories
52 stories
The Next Reorg Will Be AI-Driven. Most Will Do It Wrong.
AI is forcing organizational redesign. The companies that benefit will redesign the work system underneath the chart before they restructure the chart itself.
Read the ArticleFrom 83 Observations to Five Things to Build
A global IT organization finished its diagnosis with eighty-three documented findings and a sponsor who said it was far too many to absorb. The way forward was not a longer plan. It was asking what condition produced each cluster of findings.
The Front Door Is Not Real Until Leaders Use It
A global technology organization rebuilt its intake process and still found people being asked to work outside it. The process held only after the leadership team admitted the habit, closed the urgent-work loophole, and committed to using the front door themselves.
Why Work Management Fails
A global IT organization kept attacking its most visible problem, releases, one fix at a time. Sequencing its redesign on a single grid showed why that never worked: release work could not even begin until intake and prioritization were redesigned with it.
Scope Is Where Hidden Rework Begins
A delivery executive's best number said her teams were productive. Two weeks inside the work showed they were guessing at scope, building, and rebuilding once stakeholders finally looked.
The Work Was Not Slow. The Request Was Not Ready.
A regulated product company's marketing team mapped every request from submission to publication. The delay was not in the work. It was at the front of the map, where incomplete requests sat waiting for information nobody had asked for.
The Quality Problem Began Before Testing
At a research and advisory firm, the internal acceptance tester was finding defects faster than she could log them. More testing wasn't the answer. Each team wrote down, and took ownership of, what done had to mean before work left its hands.
No Urgency, No Change
A good method does not create movement by itself. Transformation begins where standing still has become the most dangerous option.
The Meeting That Stopped Serving the Work
An audit of standing meetings in a large IT organization showed how much of the week they consumed. The more important finding was what those meetings had been trying to compensate for.
No Software, No Sprints, Still a Work System Problem
A small investment firm had no software teams and no sprints. It still needed what agility actually provides: a shared definition of value and a way to see where every piece of work stood.
When Goals Run Parallel to Work
A healthcare technology company set goals every quarter in a spreadsheet the work never touched. Replacing it with one shared backlog, a pull system, and a cap on active goals told leadership, for the first time, how much it could actually finish.
Two Teams Built the Same Thing Without Knowing
At a medical technology company, a sprint review revealed that another team had been building the same connection for months. Nobody had been careless. Work could reach a team through more than one door, and nothing connected those doors.
The Same Word Means Three Different Things
A PMO could not trust its portfolio reports because one work item name meant a few days on one team and more than a year on another. The fix started with evidence of work already done, not with a debate about definitions.
The Engine Nobody Builds
The launch is visible. Sustainment is a thousand quiet operating decisions, and most change efforts never build the engine that carries them.
We Stopped Making Documents and Started Building Machines
A slide deck is out of date the week it lands. A working system keeps producing results after the engagement ends.
Promising One Hundred. Finishing Fifty-Six.
A delivery organization was committing to roughly a hundred epics a quarter and finishing about fifty-six. Nobody knew, because nobody had ever measured what the team could actually carry.
Inside Agileon's AIC Experience
At the Agile International Conference 2025 in Miami, Agileon showed up as a keynote speaker, a small business, an active participant, and an executive attendee. The talks mattered less than the conversations that followed them, and some of those conversations became partnerships.
The Report Was Obsolete Before It Was Finished
One project's work was spread across seven separate databases. Producing its status took about four days by hand and was obsolete on arrival. The problem was not the report or the people. It was the data architecture underneath both.
The Bridge Lived in Leaders' Heads
At a global manufacturer, regional leaders spent a week turning the informal network they used to clear blockers into a visible escalation path any team member could use. On the last day they walked across the street and handed it to the delivery teams.
What Existing Findings Reveal
Before observing anything new, a diagnostic team read what a large IT organization already knew about itself. Two consulting reports written years apart named the same problems, and neither had been acted on.
Tool Sprawl Fragments the Truth
An inventory at a large IT organization found more than two hundred tools, parallel systems for the same work, and licenses almost nobody used. The cost that mattered most was that no one held a complete picture of the work.
The Consultants Left. The System Stayed.
Most transformations end when the pilot does, and the old patterns quietly return. This one turned its project team into a standing function that watched for drift, caught an intake bypass within weeks, and learned to run the method without its consultants.
All stories
The Next Reorg Will Be AI-Driven. Most Will Do It Wrong.
AI is forcing organizational redesign. The companies that benefit will redesign the work system underneath the chart before they restructure the chart itself.
No Urgency, No Change
A good method does not create movement by itself. Transformation begins where standing still has become the most dangerous option.
The Engine Nobody Builds
The launch is visible. Sustainment is a thousand quiet operating decisions, and most change efforts never build the engine that carries them.
We Stopped Making Documents and Started Building Machines
A slide deck is out of date the week it lands. A working system keeps producing results after the engagement ends.
The Seven Components of Work
Seven components describe how work enters, gets understood, gets ordered, breaks down, moves, crosses boundaries, and reports back. They came into focus when a notebook of symptoms was sorted by where in the flow of work each one happened.
From 83 Observations to Five Things to Build
A global IT organization finished its diagnosis with eighty-three documented findings and a sponsor who said it was far too many to absorb. The way forward was not a longer plan. It was asking what condition produced each cluster of findings.
When Goals Run Parallel to Work
A healthcare technology company set goals every quarter in a spreadsheet the work never touched. Replacing it with one shared backlog, a pull system, and a cap on active goals told leadership, for the first time, how much it could actually finish.
The Front Door Is Not Real Until Leaders Use It
A global technology organization rebuilt its intake process and still found people being asked to work outside it. The process held only after the leadership team admitted the habit, closed the urgent-work loophole, and committed to using the front door themselves.
Scope Is Where Hidden Rework Begins
A delivery executive's best number said her teams were productive. Two weeks inside the work showed they were guessing at scope, building, and rebuilding once stakeholders finally looked.
The Meeting That Stopped Serving the Work
An audit of standing meetings in a large IT organization showed how much of the week they consumed. The more important finding was what those meetings had been trying to compensate for.
What Existing Findings Reveal
Before observing anything new, a diagnostic team read what a large IT organization already knew about itself. Two consulting reports written years apart named the same problems, and neither had been acted on.
Tool Sprawl Fragments the Truth
An inventory at a large IT organization found more than two hundred tools, parallel systems for the same work, and licenses almost nobody used. The cost that mattered most was that no one held a complete picture of the work.
No Software, No Sprints, Still a Work System Problem
A small investment firm had no software teams and no sprints. It still needed what agility actually provides: a shared definition of value and a way to see where every piece of work stood.
Why Work Management Fails
A global IT organization kept attacking its most visible problem, releases, one fix at a time. Sequencing its redesign on a single grid showed why that never worked: release work could not even begin until intake and prioritization were redesigned with it.
Portfolio Governance Without Bureaucracy
A global IT organization's front-office delivery group was drowning in requests that all arrived marked urgent. The answer was not another approval meeting. It was a set of written prioritization policies that let the team say not yet, with a reason, and sent disagreements to a forum instead of a fight.
Inside Agileon's AIC Experience
At the Agile International Conference 2025 in Miami, Agileon showed up as a keynote speaker, a small business, an active participant, and an executive attendee. The talks mattered less than the conversations that followed them, and some of those conversations became partnerships.
The Work Was Not Slow. The Request Was Not Ready.
A regulated product company's marketing team mapped every request from submission to publication. The delay was not in the work. It was at the front of the map, where incomplete requests sat waiting for information nobody had asked for.
Seventy-Three Goals and No Way to Choose
A healthcare technology leadership team set out to cascade three annual goals and ended the next day with seventy-three. The fix was not a shorter list. It was a ranking method the leaders built themselves, one objection at a time.
Half the Portfolio Was Keeping the Lights On
A healthcare technology leadership team expected a tidy exercise in sorting its work into categories. A quiet question about new work versus keeping the lights on changed what its intake process recorded, and the first dashboard showed the portfolio split almost evenly.
Promising One Hundred. Finishing Fifty-Six.
A delivery organization was committing to roughly a hundred epics a quarter and finishing about fifty-six. Nobody knew, because nobody had ever measured what the team could actually carry.
When More Work Tripled the Wait
A delivery team more than doubled the work it carried at once and watched its cycle time nearly triple. It finished slightly more, and paid for it in burnout and a resignation.
The Report Was Obsolete Before It Was Finished
One project's work was spread across seven separate databases. Producing its status took about four days by hand and was obsolete on arrival. The problem was not the report or the people. It was the data architecture underneath both.
Two Teams Built the Same Thing Without Knowing
At a medical technology company, a sprint review revealed that another team had been building the same connection for months. Nobody had been careless. Work could reach a team through more than one door, and nothing connected those doors.
The Quality Problem Began Before Testing
At a research and advisory firm, the internal acceptance tester was finding defects faster than she could log them. More testing wasn't the answer. Each team wrote down, and took ownership of, what done had to mean before work left its hands.
One Backlog Ended the Duplication Nobody Chose
A global consumer goods enterprise put every region's and the global function's quarterly work on one board, and duplicate work surfaced within half an hour. Ranking the whole portfolio from the enterprise's point of view turned an old fight into one list everyone could plan against.
Approvals That Took Months Started Closing in Weeks
A global consumer goods enterprise with six regions cut approvals from months to weeks, and to days for some initiatives. The speed did not come from pushing approvers. It came from putting authority, evidence, and a steady rhythm into one forum.
The Consultants Left. The System Stayed.
Most transformations end when the pilot does, and the old patterns quietly return. This one turned its project team into a standing function that watched for drift, caught an intake bypass within weeks, and learned to run the method without its consultants.
AI Made the Request Better, Not the System
A healthcare technology company built a simple chat assistant that asked requesters the questions intake reviewers used to ask days later. Request quality improved immediately. The intake system itself did not change, and being precise about that difference is what made the result useful.
By the Time You Feel It, the Cost Is Already In
A healthcare technology leadership team estimated how much of its weekly work was actually planned. The room landed at about 43 percent, which meant most of the work was entering through an intake process never designed to receive it.
Six Front Doors Is the Same as None
A global technology organization was sure its intake process was clear. Hand-drawn maps from its own leaders showed six different ones, and the work arriving outside all of them was invisible to every report leadership relied on.
Your Intake Problem Is Not Volume
A global IT organization did not lack intake tools. It had four useful ones that could not see each other. Connecting them, and deciding that work only officially exists once it enters one, gave leaders a picture of demand they could trust, and that picture exposed a problem volume had been hiding.
Surface the Work Before It Surfaces as a Crisis
A stand-in scrum master at a global research and advisory firm kept staring at three items nobody would touch. A simple skills inventory showed why: the work waited on a specialist assigned to the team for a fifth of his time. With the evidence on screen, leadership moved him over before the stall became a missed delivery.
The Same Word Means Three Different Things
A PMO could not trust its portfolio reports because one work item name meant a few days on one team and more than a year on another. The fix started with evidence of work already done, not with a debate about definitions.
A Commitment Without Scope Is a Guess With a Deadline
A delivery group serving many business units kept inheriting commitments no one had scoped together. One shared weekly forum, with clear limits on what it would not do, moved scoping ahead of the promise.
Same Tool Is Not the Same System
In a global IT organization's front-office delivery function, every team used the same delivery tool and no two boards meant the same thing. The fix was not another tool or a better report. It was agreeing what each step of the work means, then building that meaning into the tool everyone already had.
Every Business Unit Had Priorities. Nobody Owned the Order.
A global IT organization assumed its problem was too many priorities. Mapping its own structure showed something else: priorities were being set everywhere, by every business unit, and the one step that should have reconciled them had no owner at all.
Paying Twice for the Same Requirements
A global IT organization found that its delivery teams were working out requirements the business had already thought through, and skipping test planning because the picture was still unclear. Making the business own acceptance criteria, with leadership holding the line, stopped the company paying for the same work twice.
Escalation Is the Most Expensive Way to Decide
At a medical technology company, a week of hard negotiation produced one forum to own priority. The group that had lost authority kept resequencing work around it until leadership made the shift visible and gave that group a legitimate seat.
Prioritization Is a System, Not a Meeting
In a healthcare technology company, every function ranked its own shared goals while almost every goal depended on the same few functions. A standing cross-functional council turned hallway surprises into explicit trade-offs.
Your Goals Never Reach the Work
A CIO demanded a roadmap for every business area within a month, and his business partners blamed their tools. The real gap was that the outcomes leaders agreed on never reached the teams in a form they could build. Once they did, the first forecast showed a commitment that could not be met.
Fix the Language Before You Fix the Work
After two organizations combined, the leadership team could not agree on what to call its work. Debating labels went nowhere. Decomposing one real multi-year goal together gave them a shared hierarchy in a single session.
Built to Present, or Built to Use
A global IT organization's change team put its whole redesign on a single page: where it stood, where it was going, and the sequence in between. The page exposed an overloaded quarter before it happened, priced the effort in hours, and gave the CIO a plan he could read whole.
The Better Practice Was Already in the Division
Inside one division of a global research and advisory firm, three closely linked teams had each built their own way of taking in and tracking work. The fix was not one team's process imposed on the others. It was finding the best practice that already existed among them and agreeing which few things had to be the same.
Stop Reassigning People Mid-Stream
A fast product development firm that had just joined a larger company was pulling engineers across client work, internal initiatives, and urgent requests mid-sprint. Smaller dedicated teams, planned batches of work, and a buffer for interruptions reduced the churn without giving up the firm's speed.
Your Process Is Accumulated, Not Chosen
An executive team put its own process maps on the wall and marked every step where work was being wasted. The steps nobody had chosen were easy to find. The one to fix first was the one nobody predicted.
Prove It on One Portfolio First
A global IT leadership team narrowed its pilot choice to four groups, then ruled out three for reasons that had nothing to do with willingness. The group that remained was the one that most resembled the organization the pilot was meant to convince.
The Events Were Running. The Work Was Not Flowing.
A global research and advisory firm had adopted Scrum in full, on paper. Its teams were busy with the framework and still short on results. Coaching inside the work, and leaders who learned that mid-sprint priorities were a tax on their teams, moved them from inconsistent results to consistent ones.
Order-Taking Is Not a Handoff
At a global research and advisory firm, requests crossed from internal customers to a delivery team through product owners who wrote the tickets alone. Refinement had turned into order-taking. Making it a two-way conversation, and asking the team what it needed to know, shrank the rework that had been eating every sprint.
The Bridge Lived in Leaders' Heads
At a global manufacturer, regional leaders spent a week turning the informal network they used to clear blockers into a visible escalation path any team member could use. On the last day they walked across the street and handed it to the delivery teams.
Reporting That Produces No Decision Is Overhead
A global IT organization had plenty of reports and little use for them. Instead of building better ones, it asked what decision each report was meant to support, then rebuilt its reporting around the forums where those decisions were actually made.
Too Many Metrics Is the Same as None
A healthcare technology leadership team brainstormed the measures it needed and covered a board. Five plain questions per metric showed how few it could actually produce. A second organization shows what the alternative looks like once it is running: a few measures, read in the room where decisions get made.
The Number That Looks Healthy Hides the Rot
A global IT organization scored above 80 percent on organizational effectiveness. Other readings of the same organization told a much harder story. Instead of trusting one number, it built a set of measures designed to catch what a healthy score can hide.
No stories match that combination.
Try a broader phrase or clear one of the filters.