Goal Tree and Metric Deployment

Lesson 27.2
12 minOpsida Teknoloji · Last reviewed: October 30, 2026

In one sentence

A goal tree links a result to the process conditions believed to affect it; contribution calculations keep the common denominator and the dependencies.

By the end of this lesson

  • Calculate the delivery goal from 90% to 96% as percentage points and as an order count.
  • Separate the result metric from the factor metric and from the activity count.
  • Find the total affected orders by using the intersection of two delay causes.
  • Choose a verification and protection condition for the assumed causal relationship between metrics.

Why it matters

A goal tree is not a tool for mechanically splitting a number written at the top among lower units. It makes visible which process conditions affect the shared result and through which work those conditions will be changed. If only production quantity sits under the delivery goal, obstacles from planning, material and quality can be overlooked. Conversely, tying every metric to the tree does not explain the relationship either. For each link, state which behavior is expected, in which data it will be tested and which other conditions could affect the result. A drawn arrow does not mean a proven cause. The tree is a working record that organizes shared reasoning and assumptions that data can falsify.

The result metric shows reaching the customer or the shared operating purpose. The factor metric tracks the process condition expected to change that result. The activity count describes the work done. On-time delivery rate, material readiness rate and the number of completed inspections are therefore at different levels. Doing more inspections does not prove that material was ready on time. Even if material is ready, a defective product can delay delivery. If improvement in the factors does not show up in the expected result, the relationship is re-examined before people are pushed to do more activity. A wrong link can let the same delay continue despite a high volume of activity.

Percentages need particular care. Two rates with different denominators cannot be added; rates with the same denominator are also not added directly if they represent dependent events. An order can be affected by both a material shortage and rework. Seeing this order on the lists of two units does not mean there are two separate delivery losses. Without the intersection, total loss or total gain cannot be calculated. Some relationships are sequentially conditional; the rate of the later stage applies only to orders that passed the earlier stage. In that case multiplication with the proper conditions is needed. The type of operation is derived not from how the tree looks but from the definition of the events and denominators.

The purpose of metric deployment is not to give every unit a number that looks good, but to make clear the conditions that must change for the shared result. If a unit's local goal is met by overproducing, work-in-process inventory can grow while the delivery rate does not change. Alongside factor goals there are protection metrics that show such side effects. Quality acceptance, the inventory limit and safe working are parts of the same decision. Increasing the number of metrics does not create clarity by itself. For each metric the decision value, owner, unit, period and data source are determined. Working with a shared definition, instead of the same record being renamed by different units, makes the contribution discussion and the bias review easier.

Formula

Delivery gap (percentage points) = Goal delivery rate − Baseline delivery rate

Required net improvement (orders) = Round up(Number of orders × Goal delivery rate ÷ 100) − Baseline on-time count

Orders with at least one cause (orders) = Orders with a material problem + Orders with a quality problem − Orders with both problems

On-time delivery (%) = (Total orders − Late orders) ÷ Total orders × 100

Sequential success rate (%) = First-stage success rate × Second-stage success rate among those that passed the first stage ÷ 100

Unlock the rest of this lesson with an Academy account

Create a free Academy account with your work email address; it can be used once it is approved.

  • Step-by-step instructions
  • Worked example with real numbers
  • Where the method misleads
  • Common mistakes
Create a free Academy account