The Observation
A single developer with an AI agent now completes in one day what once took a team two weeks. Backlogs empty. Sprint reviews drown in hundreds of stories no one can absorb. Two-week cycles become absurd when the work finishes in hours.
The universal reaction: abolish Scrum. Remove the process. Go faster.
This is the wrong response. Not because Scrum was right, but because removing it hides the real problem instead of solving it.
The real problem was never development speed. It was always the decisions.
Who decides what to build next? Who has the authority? Who has the context? Who is willing to be wrong? These questions existed before AI agents. They were always there, hidden beneath the comfortable fiction that if only the developers were faster, everything would work.
AI agents removed that fiction. The water level dropped. The rocks are visible now.
The Name
In 1978, Herbert Simon received the Nobel Prize for a deceptively simple insight: organizations are not systems of people — they are systems of decisions. Every structure, every hierarchy, every process exists to channel decisions. Remove everything else, and decisions are what remain.
In 1971, biophysicist Manfred Eigen described how simple chemical systems organize themselves into self-sustaining cycles — hypercycles — that enable the leap from chemistry to biology. From mechanical to alive. From simple repetition to emergent complexity.
We believe organizations face a similar transition. From process-driven to decision-driven. From coordinated to self-organizing.
We call this transition hycle — the hyper cycle.
German speakers hear heikel — delicate, precarious. That is deliberate. This transition is not comfortable. It challenges power structures, role definitions, and the identity of everyone involved. It is, indeed, heikel.
And yes — hype cycle is in there too. Deliberately. Every few years, a new technology triggers the same predictable curve of inflated expectations, disillusionment, and belated productivity. We named ourselves after that pattern as a reminder: hycle is not about riding the next wave. It is about what remains after the hype has passed.
What We See
These observations come from practice — from training teams, consulting organizations, and building software with AI agents ourselves.
1 AI agents shift the bottleneck.
Development speed is no longer the constraint. Decision-making is. One person builds an epic per day. The organization cannot decide what to build next at that pace.
2 Process models designed for development throughput collapse.
Scrum, SAFe, and similar frameworks optimized for a bottleneck that no longer exists. Sprint planning for 300 stories is not planning. Reviews of work already in production are not reviews.
3 The decision problem is not new — it is newly visible.
Like lowering the water level in a river reveals the rocks beneath, AI speed exposes organizational dysfunction that was always there. Slow decisions, unclear authority, missing domain knowledge, absent stakeholders.
4 Teams shrink. Responsibility grows.
One- to two-person teams with AI agents carry more domain scope than eight-person cross-functional teams did before. But the organizational structures around them have not adapted.
5 Role boundaries dissolve.
The separation of “developer” and “product manager” loses meaning when execution is instant and the bottleneck is domain understanding. Something new is emerging. We do not yet know what to call it.
6 Middle management faces an existential question.
The coordination layer that justified its existence through managing development complexity is losing its function. This is not an accusation — it is an observation that demands honest conversation.
What We Believe
We do not have answers. We have hypotheses. They come from practice, not theory. We hold them loosely and test them rigorously.
H1 Organizations must reorganize around decisions, not around development processes.
The fundamental unit of organizational value is a decision — not a feature, not a story, not a sprint goal.
H2 Organizational maturity is determined by where decisions are made — not by how fast code is shipped.
Speed without decision authority produces faster waste.
H3 Frustration is a signal, not a problem.
The discomfort teams feel when AI speed meets organizational inertia is the indicator of where to intervene next. Do not hide it. Follow it.
H4 The path is iterative and bottom-up.
There is no master plan for this transition. You navigate from bottleneck to bottleneck. Each one reveals the next.
H5 The default shifts from instruction to intent to autonomy.
Autonomy — for teams and for AI agents — must be earned through consistent delivery, not declared by management. You cannot skip levels. There are no shortcuts.
H6 Rationalization is not transformation.
Reducing headcount because AI makes execution cheaper is an option. It is not the same as building an organization that makes better decisions faster. One is cost optimization. The other is a competitive advantage that compounds.
The Model
The hycle model describes organizational maturity along two co-evolving dimensions:
These dimensions are not independent. You cannot advance on one without advancing on the other. An organization that grants AI agents full autonomy without team-level decision authority will build the wrong thing faster. A team with full decision authority but no trust in their AI tools will be too slow to use it.
The transition between levels is not linear. Organizations do not “implement Level 3.” They earn it — through practice, through pain, through honest confrontation with their own decision-making structures. You cannot skip levels. There are no shortcuts.
You are here if: Teams complain about having nothing to do.
You are here if: Frustration points at the organization, not at the tools.
You are here if: Teams ask “What should we build?” more often than “How should we build it?”
You are here if: Decisions emerge from customer need, not from hierarchy.
You are here if: We do not know yet. This is where we need your experience.
What does it take to move from one level to the next?
We have early hypotheses. We are testing them with real organizations. This is the question we most need help answering.
What hycle Is Not
hycle is not a new Scrum. It is not a process framework with ceremonies, roles, and artifacts to implement on Monday morning.
hycle is not against Agile. The values of the Agile Manifesto still hold. The process models built on top of them do not — not at this speed.
hycle is not a technology framework. It does not prescribe tools, architectures, or AI platforms.
hycle is not finished. It is a set of observations and hypotheses from practice, offered as an invitation to collective sense-making.
Walk the Talk
We apply these ideas in our own work and with our clients. This section will grow as we document what works, what fails, and what surprises us.
Coming soon.
The Authors
hycle emerged from a conversation between four practitioners who have spent decades building, consulting, and transforming software organizations.
The Invitation
hycle is not a declaration. It is an invitation to a conversation.
We believe the organizations that thrive in the age of AI agents will be the ones that learn to make better decisions faster — not the ones that write more code faster.
If you see what we see. If you have observations that confirm or contradict our hypotheses. If you are navigating this transition in your own organization — we want to hear from you.