Levers of Value

Demonstration
Scenario
Operational debt
–
a year, against a well-run position (4) on every value lever in scope
Identified
–
a year, from the improvement
Committed
–
the share a management team typically commits to
Banked
–
after reabsorption
Growth capability
–
more work absorbed with the same people
Payback
–
on committed value, net of cost

The example organisation

Made up for this demonstration from published benchmarks where they exist.
What the team does: its tasksRegister to edit

Each task the team handles, how many arrive a week and how long each takes, split into value-added, business-value-added (necessary, such as controls and compliance checks) and non-value-added work; each row must total 100%. Everything below is worked out from this table, including the value figures.

The team's demand and capacity

Capacity from gross hours to what the team can really use; demand from its task list. This is the team's current performance, before any improvement.

Choose your scenario

Levers of Value shows what poorly run work costs you, which management practices would release it, and what that is worth. Pick how far to look; each scenario includes everything in the ones before it, and the scenario strip in the bar at the top always shows which one you are looking at. Then read the current dashboard, pull the levers to see the improved dashboard, and see the business case.

Organisation level this scenario can reach

Level todayLevel after improvementLevels and key competences from Expertivity's Journey to Operational Excellence (PAI, 2013)

The organisation's figures

Team size, working time, costs and the scope of the scenario. Every figure above and in the dashboards follows them.
Other teams in the function

Shares are of each team's recorded work, so value-added, business-value-added and non-value-added always make 100%. Value-added is worked out as what's left. Each team starts with the starting team's profile and the scope's attrition rate; change any team that differs, and a blank cell uses the default shown.

The end-to-end processRegister to edit

An end-to-end process crosses functions. It is a chain of tasks, and each task belongs to a team: the starting team, another team in its function, or a team elsewhere in the business, which gives the process only the hours on those tasks. Teams in other functions join with just their slice. Team levers act on whole teams; process levers act on these tasks and their failure demand. Tick the tasks that are failure demand: work caused by something upstream going wrong.

Illustrative example, not client data.

Teams in other functions

Current dashboard

The dashboard for the scenario you chose, as the organisation runs now. For each practice, click the position that best describes how it works today. The dials, levels and operational debt show what today costs you. Practices new at this scenario are marked.

Example positions: a team that has the basics in place (position 2 on most practices) aiming for well run (4). Change them to match your own organisation.

Improved dashboard

The same dashboard after improvement. Pull each lever to the position you want to reach. A lever can't go below where you are today. Watch the dials and the value change, and read why in the panel beside the practice.

Example targets: well run (4) on the main value practices. Pull them wherever you want; the figures follow.

Value and cost of the improvement

Cost

Control framework

Instrument panelPractice readiness, 0–100 · grey tick = today · needle = after improvement · select a dial to see what drives it
Green labels: team effectiveness Blue labels: process management Yellow plate: joins in a wider scenario Anything that moves turns green if better, coral if worse, or yellow when you change scenario, for a moment

Click a position on any lever to pull it, or select a lever and use the arrow keys (Shift with an arrow sets today). Levers with a yellow plate join in a wider scenario.

Why did that change?