Cost Ownership Map

Assign every cost element a named owner: not the controller — the designer, buyer or process engineer who can move it.

Time30 min
FormatSmall group
StageTrack

Cost Ownership Map: what it is and why it works

The Cost Ownership Map assigns every element of the cost breakdown structure to one named person who can actually move it: the designer who controls material and geometry, the buyer who controls sourcing and terms, the process engineer who controls cycle times and yield, the logistics planner who controls packaging and freight. Controllers and cost engineers support the owners with data and analysis, but they do not own the numbers. The map is published to the whole project team, reviewed in one-on-one conversations between owners and their managers, and updated when people change roles or when an element stays stuck.

The method works because shared responsibility dilutes action. When a cost line belongs to a committee, it gets discussed and rarely changes; when it belongs to someone with the authority and skills to change it, it becomes part of their job. Responsibility accounting has long held that costs should be reported to those who control them. Assigning a cost to a controller creates a reporter, not an owner. The map makes the Cost Dashboard actionable by showing a name beside each line, uses the structure from Top-Down Cost Driver analysis to decide what to assign, and gives the Cost Gate Review a clear person to present each recovery plan.

What you need

The cost breakdown structure with elements at a level where one person can act
Current cost and target per element
The project organization and each person's scope of authority
The cost dashboard that will display owners

What you get

A published map: element, owner, target, current cost
Clarified support roles for controllers and cost engineers
One-on-one review agenda per owner
Reassignment triggers and a log of changes

When to use it

When cost is everyone’s concern and therefore no one’s job.

How to do it, step by step

Take the cost breakdown structure and its cost elements.
Assign each element to the person who can move it: designer, buyer, process engineer.
Publish the ownership map to the project team.
Review the owned elements in one-on-ones, not in committees.
Reassign when people change or when an element stays stuck.

Worked example: Assigning owners on an agricultural sprayer program

Illustrative scenario — figures are realistic but not from a real company.

A manufacturer of self-propelled crop sprayers was 6% above target on a new model. The cost report listed 26 elements, and the program controller was named as responsible for all of them. Monthly cost meetings had 14 attendees and rarely produced actions.

The program manager and cost engineer went through the 26 elements and asked, for each, who could change it this quarter. Boom structure went to the boom design lead, hydraulic components to a commodity buyer, paint and pretreatment to the paint shop process engineer, and so on.
Four elements had two plausible owners; each was split or given to the person with the larger lever.
The map was posted in the program room and added as a column on the cost dashboard. The controller's role was redefined as data provider.
Managers added a 10-minute cost item to existing one-on-ones with the owners, and the monthly cost meeting was replaced by the dashboard review in the weekly program meeting.

Result. Within two months, 17 elements had active actions against 9 before. The paint engineer cut paint consumption by tightening film thickness control and reducing overspray, and the buyer consolidated hydraulic fittings to one supplier. The model closed to 2% above target by the pre-production gate.

Open it in the FieldKit Design to Cost app → Get the Design to Cost template pack — join the waitlist

Common pitfalls and how to avoid them

Assigning cost elements to finance or controlling.Give ownership to the person who can change the cost; keep finance in a support role.
Assigning one element to several people.Name a single owner per element; split the element if two people genuinely control different parts.
Reviewing owned elements in large committees.Review in one-on-ones where the owner can discuss obstacles openly, and use the group meeting for decisions.
Leaving stuck elements with the same owner indefinitely.Reassign or escalate when an element shows no progress over an agreed number of reviews.

Frequently asked questions

What is responsibility accounting?

It is a management accounting approach that assigns costs, revenues or results to the managers who control them, and evaluates those managers on what they can influence. In design-to-cost work, the same idea is applied at the level of cost elements, so each element has an owner with real authority to change it.

Who should own product cost in a development project?

The people who make the decisions that set the cost: designers for materials, geometry and tolerances; buyers for sourcing and terms; process engineers for methods, cycle times and yield. The project manager owns the total. Cost engineers and controllers provide data and analysis but are not the owners of individual elements.

How detailed should a cost ownership map be?

Detailed enough that each element has one person who can act on it, but not so detailed that owners manage hundreds of lines. For a typical product program, a few dozen elements at module or commodity level work well. Drill further only where one element is large enough to warrant several owners.