The plan agreed in January is out of date by March. Priorities change every week, and the office learns about it last. Every decision still waits for the owner. An agile operating model is a way of running a business that plans work in short cycles, reviews it often and lets the people closest to the work decide within agreed limits.
This guide explains what an agile operating model is, how it differs from a traditional or target operating model, what agile can and cannot mean for site-based, safety-critical installation work, and how a heating, ventilation and air conditioning (HVAC), electrical contracting or renewables business can adopt the parts that fit.
What is an agile operating model?
An agile operating model is the set of arrangements, covering structure, decision rights, planning rhythm, measures and tools, that is intended to let a business change course quickly while keeping control. Work is broken into short cycles, progress is made visible, and plans are reviewed regularly and adjusted on evidence.
An operating model describes how a business is organised to deliver what it sells: who does what, how decisions are made, how work moves between teams and which measures matter. The guide What Is an Operating Model? covers the components in full. A target operating model is the future version a business plans to move to: how it will operate to deliver services to its customers.
An agile operating model is not a structure chart. It changes how often the business plans, who is allowed to decide, and how quickly information reaches the people doing the work. The same people, offices and vans can run on a traditional rhythm or an agile one.
How is an agile operating model different from a traditional or target operating model?
An agile operating model differs from a traditional or target operating model mainly in how it handles change. A traditional model tends to fix the design and plan in advance and treat change as an exception; an agile operating model expects change, plans in short cycles and adjusts the design as evidence comes in. The main models for leading a change, from Kotter’s 8 steps to the PDCA cycle, are compared in the guide to change management frameworks.
Five differences can show up in day-to-day running: planning horizon, decision-making, information flow, team structure and how improvement happens. The table summarises them as general patterns, not fixed rules.
| Area | Traditional or target operating model | Agile operating model |
|---|---|---|
| Planning | Annual or project plan fixed at the start | Longer-term roadmap, with detailed plans for the next few weeks only |
| Decisions | Most decisions referred upwards | Decisions made close to the work, inside written limits |
| Information | Monthly reports | Work visible on a shared board and reviewed weekly or more often |
| Teams | Organised by department, with hand-offs between them | People from different functions working on one outcome |
| Improvement | Larger, less frequent change programmes | Small changes tested and kept or dropped each cycle |
The two are not opposites. A target operating model can stall when the design is fixed on paper and never tested against how the business actually runs; common causes are covered in why a target operating model fails and how to fix it.
Where does agile come from, and what does it ask for?
Agile comes from software development. The Manifesto for Agile Software Development, written in 2001, sets out what its authors had come to value: responding to change, collaboration and working results, while still recognising the value of plans, processes and documentation.
The Manifesto for Agile Software Development values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan, while recognising value in the items on the right. Its twelve principles are explained for a business audience in the 12 agile principles for business. The Scrum Guide (November 2020) describes Scrum as a lightweight framework in which work runs in fixed-length Sprints of one month or less. The Kanban Guide (May 2025) describes Kanban as a strategy for optimising the flow of value through a process, in which the number of work items in progress must be explicitly controlled. The UK Government Service Manual page on planning in agile states that planning is vital to the success of agile working. How a sprint or iteration runs step by step is covered in the guide to agile methodology.
What can agile mean for site-based, safety-critical installation work?
For a business that carries out site-based, safety-critical installation work, agile can shape how the office plans, decides and shares information. It cannot change legal duties or agreed designs: those sit outside the planning cycle, and short cycles operate around them.
The Association for Project Management (APM) describes agile project management as an iterative approach to delivering a project throughout its life cycle, and says it focuses on delivering maximum value against business priorities in the time and budget allowed, especially when the drive to deliver is greater than the risk. APM’s description of its guide Directing Agile Change says agile is not limited to software development. Its page on project life cycles, drawn from the APM Body of Knowledge 8th edition, describes linear life cycles as aiming to be highly structured, predictable and stable, notes that iterative cycles can only proceed when user feedback is available, and states there is no universal best approach. APM gives the example of a hybrid that uses iterative or agile methods for early requirements gathering, where the uncertainty is greatest, followed by incremental or sequential processes to formalise deployment.
A 2006 conference paper on construction reached a similar view. Owen, Koskela, Henrich and Codinhoto, Is Agile Project Management Applicable to Construction? (International Group for Lean Construction, 2006), assessed that agile project management offers considerable potential in pre-design and design, but identified significant hurdles to its adoption in the actual construction phase.
Two sets of regulations that apply in Great Britain show where the fixed boundaries sit for an installation business, the Construction (Design and Management) Regulations 2015 and the Electricity at Work Regulations 1989:
- Construction (Design and Management) Regulations 2015. Under regulation 12, the principal contractor (whom the client must appoint, under regulation 5, where more than one contractor is, or is reasonably foreseeably going to be, working on the project) must draw up a construction phase plan, or arrange for one to be drawn up, during the pre-construction phase and before setting up a construction site, and must ensure it is appropriately reviewed, updated and revised from time to time throughout the project. Where there is only one contractor, regulation 15 requires that contractor to draw up the plan, or arrange for one to be drawn up, as soon as is practicable before setting up a construction site. The Health and Safety Executive guidance on principal contractors says a principal contractor is appointed by the client to control the construction phase of any project involving more than one contractor, and must plan, manage, monitor and coordinate it.
- Electricity at Work Regulations 1989. Regulation 14 says no person shall be engaged in any work activity on or so near any live conductor (other than one suitably covered with insulating material so as to prevent danger) that danger may arise, unless all three conditions are met: it is unreasonable in all the circumstances for it to be dead; it is reasonable in all the circumstances for the person to be at work on or near it while it is live; and suitable precautions, including where necessary the provision of suitable protective equipment, are taken to prevent injury.
Regulation 12 already requires the principal contractor to ensure the plan is reviewed, updated and revised from time to time so that it stays sufficient for health and safety. A regular planning rhythm in the business can sit alongside those reviews; it does not replace them, and it does not move the legal duty from the person who holds it.
Which parts of a contracting business suit agile working?
The parts of a contracting business that suit agile working are those where requirements are uncertain and work can be split into small, reviewable pieces: estimating and design development, scheduling, procurement, recruitment, system changes and improvement projects. Legal duties, contract terms and agreed design stay outside the cycle.
Rostone Operating Partners separates the work that is fixed by regulation, contract and design from the work around it that can be planned in short cycles. Five areas can sit in the second group: estimating and pre-construction, scheduling and resourcing, procurement, office systems and processes, and improvement projects.
- Estimating and pre-construction. Design options, value engineering and tender queries change as the client responds, which is similar to the APM example of using iterative methods for early requirements gathering; the Owen et al. paper likewise saw the most potential in pre-design and design.
- Scheduling and resourcing. A weekly planning session that looks two to three weeks ahead, rather than a fixed monthly plan, lets the office respond to slipped jobs and absences.
- Procurement. Long-lead items such as heat pumps, switchgear or air handling units can be tracked on a shared board so delays surface while there is still time to act.
- Office systems and processes. Changing a job management system, a quoting template or an invoicing routine can be done in small releases, tested with the people who use them.
- Improvement projects. Fixing a recurring problem, such as late job paperwork, suits short test-and-learn cycles.
What are the building blocks of an agile operating model?
An agile operating model can be built from a short planning cycle, visible work, clear decision limits, cross-functional teams, regular reviews and a few leading measures. None of them requires software or new job titles; they change how often the business plans and who decides. How owners and managers can turn habits like these into a weekly routine is set out in leadership strategies to improve productivity in a contracting business.
Six building blocks draw on Scrum, Kanban and the GOV.UK Service Manual, though no one source contains all six: a planning rhythm, a visible board, decision limits, cross-functional teams, retrospectives and measures.
- Planning rhythm. A longer-term roadmap (the GOV.UK Service Manual suggests typically 6 to 12 months ahead) with a detailed plan for the next cycle of a few weeks (the Scrum Guide caps a Sprint at one month).
- Visible board. Work in progress shown on a physical or digital board, with columns for each stage and a limit on how many items sit in each. The Kanban method explains the board, its columns and work-in-progress limits.
- Decision limits. Written limits on what each manager or team can decide without referral, such as price changes, variations or supplier choices up to a set value.
- Cross-functional teams. Estimating, operations and accounts reviewing a problem together rather than passing it between departments.
- Retrospectives. A short, regular review of what worked, what did not and one change to try next, in line with the twelfth agile principle on reflecting at regular intervals.
- Leading measures. A few measures that move before profit does, such as quote turnaround, jobs waiting for materials or days from completion to invoice.
Where work waits between stages, a value stream map shows where the delays sit before a board or planning rhythm is designed around them.
How can a contracting business adopt agile elements?
A contracting business can adopt agile elements by starting with one team or process, introducing a short planning and review rhythm, making the work visible, and agreeing decision limits, then reviewing after a few cycles what to keep. A whole-business transformation is not required to gain from agile habits.
One way to start is in five steps: pick one area, set the rhythm, make the work visible, write the decision limits, and review and adapt.
- Pick one area. Choose a team or process where priorities change often and delay is costly, such as pre-construction or scheduling.
- Set the rhythm. Agree a planning session at the start of each cycle, a short daily or twice-weekly check-in, and a review at the end.
- Make the work visible. Put every live item on one board, with an owner and a next step.
- Write the decision limits. State what the team can decide alone and what still goes to a director.
- Review and adapt. After a few cycles, keep what helped, drop what did not and decide whether to extend the approach to another team.
Rostone’s check before adopting any agile practice is to name the decision each review will make and who will make it. A weekly meeting with no decision attached can become a status report, and the owner remains the bottleneck.
Agile habits overlap with Lean: both rely on small changes, short feedback loops and measuring results. How the improvement habit works week to week is covered in the guide to continuous improvement and Lean.
What does an agile operating model ask of leaders?
An agile operating model asks leaders to set the goal and priorities, then let teams choose how to reach them inside clear boundaries. Leaders remove obstacles, share information openly and hold the review rhythm, rather than making every operational decision themselves.
For an owner-managed business, letting go of decisions can be the hardest part. Behaviours that support it, such as holding themselves and others accountable, being approachable and leading by example, are covered in effective leadership behaviours.
Rostone looks at an agile operating model through GRAX (Grow, Raise, Acquire, Exit). At the Grow stage, short planning cycles and decision limits let the business take on more work without every choice reaching the owner. When raising finance, a regular review rhythm produces the up-to-date figures a funder may ask to see. After an acquisition, a shared planning cycle helps two teams work to one set of priorities. At Exit, a business that runs on a written rhythm of plans, reviews and measures is easier for a buyer to examine than one that runs on the owner’s memory.
The business improvement service for contractors works with owners to hand decisions to managers with clear limits and set up a weekly rhythm of meetings and numbers that runs without the owner.
Frequently asked questions
A target operating model describes the future way a business intends to run, usually designed in advance. An agile operating model describes a way of running that plans in short cycles, reviews often and adjusts as evidence comes in. A business can define a target operating model and move towards it in agile steps.
An example is a pre-construction team that plans its work every two weeks, shows every live tender on one board, and can agree value-engineering options on tenders up to a set value without referral. The construction phase plan and any design already agreed with the client sit outside that team’s limits.
Agile fits alongside health and safety rules, not in place of them. Duties such as the construction phase plan under the Construction (Design and Management) Regulations 2015 and the restrictions on live working in the Electricity at Work Regulations 1989 still apply in full where they apply. A planning cycle in the business cannot relax them.
Practices that work in a smaller business include a short weekly planning session, a visible board of work in progress, written decision limits and a regular review of what to change. None of them requires specialist software, certification or new job titles.
The time it takes to adopt agile working depends on how many teams are involved and how far decisions currently sit with the owner. A single team can try a planning and review rhythm within a few weeks, and a few cycles can give enough experience to decide what to keep.
Sources
Agile Manifesto: Manifesto for Agile Software Development; Principles behind the Agile Manifesto
Scrum Guides: The Scrum Guide (November 2020)
Kanban Guides: The Kanban Guide (May 2025)
GOV.UK Service Manual: Planning in agile
Association for Project Management: What is agile project management?; What is a project management life cycle?
legislation.gov.uk: Construction (Design and Management) Regulations 2015, regulation 5; Construction (Design and Management) Regulations 2015, regulation 12; Construction (Design and Management) Regulations 2015, regulation 15; Electricity at Work Regulations 1989, regulation 14
Health and Safety Executive: Principal contractors: roles and responsibilities
International Group for Lean Construction: Is Agile Project Management Applicable to Construction? (2006)
Last updated: 13 November 2026




