We are only now starting to think about Enterprise Agility as a discrete domain. Over the last 20 years, as individual teams became agile, the constraining factor for agility to scale was the other teams within the division. Now, as entire divisions and departments scale to become agile, the constraining factor for agility is the rest of the organization.
Enterprise Agility emerges when there is an agile way of working across many teams and divisions. From a systems perspective, it can help to think of work in your organization as a flow. We have a pipeline of demand on one side and delivery to our users on the other. Somewhere along this flow is the next limiting constraint to business agility. 20 years ago, that was IT and the software teams. Which is why it was logical for Agile to emerge in that domain. But now there are new constraints that need a wider view. It differs across organizations, but it is generally found that the PMO, HR, sales, or finance departments are the next teams that need to be agile. In most organizations, we have an 18-month budgeting process limiting a development cycle that can deploy every day.
These are not easy problems to solve. You must help these divisions internalize an agile mindset and culture as well as providing appropriate practices aligned with their work context. This is key to achieving Enterprise Agility and ultimately true business agility.
Moving from Theory to Practice[edit | edit source]
Your goal is to bring agility across the organization; from IT, Finance, HR, Marketing, Sales, and Operations.
Create a Value Stream Network[edit | edit source]
Value stream maps are great for processes, however, in an organizational context with many inter-dependencies you have to build a Value Stream Network. A high-level network of different business processes and how they interact across the organization. For the purposes of transformation, keeping it high-level is usually sufficient. Then, by introducing measures to each of your processes across the network you can identify (and hopefully resolve) enterprise bottlenecks. One caveat though, mapping a process that shouldn’t exist may give it unwarranted validity. Remember that the purpose of mapping the organization is to eliminate bottlenecks and simplify complex processes.
Create an Adaptive Portfolio[edit | edit source]
Start by creating an adaptive portfolio; a managed list of major ideas, aligned by business outcome and ranked. Initiatives are then “pulled” by a team when they have the capacity, rather than forming temporary teams around work.
This doesn’t mean that we shouldn’t have strategic goals, nor does it negate the need for planning, but it does change the approach to planning. Strategic goals look out a year or more which then get translated into initiatives. Each initiative will have milestones and checkpoints to ensure the work being done aligns back to the organization’s goals and that our people and resources are being deployed in the wisest way possible.
Fund Outcomes or Teams[edit | edit source]
Traditional organization fund projects based on the estimated effort & duration of a fixed scope of work (which is often incorrect) and with benefits measured after the project is complete. Instead, start to fund initiatives based on a steady rate of financial spend against a regularly measured business outcome. There is still an assumption made around the return on investment, but the period of measure is exponentially shorter. By dynamically planning, prioritizing, and monitoring activities against outcomes, teams can manage their spending and deliver the highest value activities first.
Because we have greater predictability and can focus on value realization rather than measuring outputs, we’re in a much stronger position to demonstrate value to customers and shareholders.
Measuring your Business Agility Maturity[edit | edit source]
Funding Models[edit | edit source]
|All work (e.g. projects or products) has a predetermined & quantifiable value to the organization (in the context of a business outcome). We use this information to justify, prioritize, and fund the work.||Strategic goals have incremental checkpoints to ensure that all work aligns with our organization’s goals.||All our business outcomes have relative targets and regular measures (including non-financial measures). We are able to quickly and easily pivot or stop projects (or products) that are off-trend well ahead of time.||We use adaptive funding models to allocate funds against value streams (rather than projects). We align governance and KPI feedback loops to business (or customer) outcomes (rather than time, cost or scope measures).|
Supporting Functions[edit | edit source]
|At least 2 divisions have changed the way they work to be enablers and collaborators to others. This has had a positive impact on the business and feels more agile.||We have identified those business functions that limit (or constrain) the agility of our organization (through excessive process & governance, limited capacity or other reasons). We are actively working to remove the constraint.||Supporting functions enable business agility within our organization by actively supporting teams and creating simplified (and open) processes (e.g. Netflix’s expense policy – “Act in Netflix’s Best Interest”).||Each department understands they have an internal or external customer that they need to delight and are actively doing so.|
Case Studies[edit source]
- Shipping is NOT Success, Let it Sail
- A Story of Leadership Transformation
- Physical-Digital Transformation at a 125 year-old startup
- How Collaborative Play & Games can enable Human Resources to better support Business Agility
- Agile HR – a Game Changer
- Agile Contracting in the Federal Government
- Giving Hope - For Stakeholders, Employees and Clients by Rob Roe
- Agile Sales, or How to be Happy
- Expression Analysis - Agile Market Entry (AME)
- Agile in the healthcare sector
Further Reading[edit source]
- Evan's Theory of Agile Constraints
- Structuring Your Business for Agility
- Human Resources - The Secret to Business Agility
- Agile Contracts
- Build a network of viable teams for business agility
- Certain Uncertainty by Evan Leybourn
- Innovation culture is not a fancy hub by Jaroslav Procházka
- BOSSAnova - Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy by Jutta Eckstein
Books & Book Reviews[edit source]
- The Goal - A Process of Ongoing Improvement
- Reinventing Organisations
- Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy
Join the Business Agility Community[edit | edit source]
If you'd like to continue the conversation with like minded individuals around Business Agility Ways of Working, join the Business Agility slack community. Specifically the #future-of-work channel.
Library Steward[edit | edit source]
This section is currently un-stewarded. If you have a passion for this space and would like to take ownership for the guidance and insights within, please contact Evan Leybourn. The stewards of the Business Agility Library are leaders in their field and we quite literally couldn't create such amazing content without their support. These people & organisations are leaders in the community and, through their actions and insights, continue to expand the horizon of business agility for us all.