The tension
Simbex was already fast, and the real danger after the acquisition was that the structure it now needed would slowly turn into drag.
Simbex made its reputation by getting from idea to working prototype quickly, across medical devices, health technology, and sports technology. Then it joined a larger corporate organization, and that speed suddenly had to live alongside longer planning horizons, broader priorities, and resource commitments everyone could see.
Simbex did not need a new framework. It needed just enough structure to connect each sprint to what the larger company was trying to achieve, without flattening the independence and technical judgment that made its teams good at what they do.
What was happening underneath
Where the system was getting in the way.
Strategy stopped at the team's door
Teams were delivering meaningful work, but leaders could not consistently see how it connected to the larger company's longer-term priorities. There was no regular moment where the sprint plan and the strategy above it were put side by side.
One big team carried all the coordination
A single delivery group approaching 20 people meant every planning conversation ran long and every decision took longer than it should. The same scarce specialists were pulled into request after request.
Business priorities arrived secondhand
Delivery teams heard about business priorities through layers of people rather than from the business itself. They needed quicker access to what mattered, clearer definitions of success, and a more direct feedback loop with the acquiring company.
Focus was treated as spare capacity
Engineers were reassigned in the middle of a sprint across client work, internal initiatives, and urgent requests. Each move created churn and made the team's forecasts a little harder to believe.
What Agileon designed
A connected set of operating moves.
The value came from how the parts worked together, not from any one meeting, tool, or template.
Look further ahead
Quarterly planning was added above the existing sprint rhythm so teams could spot dependencies earlier and connect near-term work to the larger company's goals. Capacity tradeoffs started happening with the bigger picture in view instead of one sprint at a time.
Break the big team into focused ones
The large delivery group was split into smaller teams organized around specific domains, each with its own Product Owner and Project Engineer. Instead of the whole group meeting to stay in sync, team leads now coordinate lightly with one another.
Put the business beside the builders
Product Owners from the parent company worked directly with the teams to sort out priorities and define what success looked like. Sprint reviews turned from status updates into working sessions where the business gave feedback on the work itself.
Stop pulling engineers off their work
Teams stayed dedicated, planned further ahead, rotated people less, and mapped out where scarce skills would be needed before the crunch. A buffer set aside for urgent requests meant new demand did not have to pull an engineer off their sprint every time.
Observed outcomes
Movement the organization could see.
These are early results, and they were uneven across the teams involved. Not every product group changed at the same pace.
Clearer line of sight
Dependencies showed up earlier, and leaders could see how sprint work connected to longer-term initiatives.
Steadier sprints
Teams changed tasks mid-sprint less often, thanks to better planning and a managed buffer for interruptions.
Room to concentrate
Engineers described more room to focus and less strain from switching between projects.
Confidence in delivery
Several pilot teams delivered more high-value work earlier and heard from the business during the sprint instead of after it.
What this work teaches
The principles that traveled beyond the engagement.
Speed needs structure, not bureaucracy
The right planning context let teams move faster with confidence, without adding layers of approval.
Focus is scarce
Protecting people's attention produced real value without another tool or more headcount.
Ownership has to cross the line between business and delivery
Alignment improved once strategic context and delivery decisions lived in the same working relationship.
Change sticks when people can see progress
Early wins, faster feedback, and practical adjustments gave teams evidence that the new way of working was worth keeping.


