3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis

Why a Black Belt needs the finance function

The Body of Knowledge names finance explicitly as a partner: understand the importance of finance and its role in supporting a project and confirming its outcome. In practice this means the financial analyst, not the Black Belt, owns the benefit number. Projects that book savings the controller will not recognize damage the whole deployment's credibility.

Top-line measures

Revenue growth is the percentage change in sales over a period:

$\text{Revenue growth} = \frac{R_t - R_{t-1}}{R_{t-1}} \times 100$

Market share is your revenue (or unit volume) as a percentage of total served-market revenue. Growing revenue while losing share means the market grew faster than you did -- an important distinction when justifying capacity or quality projects.

Margin comes in three flavours the exam expects you to distinguish:

Most Six Sigma projects move variable cost -- scrap, rework labour, overtime, expedited freight, warranty -- so contribution margin is usually the right lens for a project business case. Claiming a change in operating margin from a scrap-reduction project overstates the case, because fixed costs did not move.

Time value of money

Net present value discounts every future cash flow to today's money at a discount rate $r$:

$NPV = \sum_{t=0}^{n} \frac{CF_t}{(1 + r)^t}$

Decision rule: accept if $NPV > 0$ at the organization's hurdle rate. NPV is the theoretically correct criterion because it accounts for both the size and the timing of cash flows, and it is expressed in currency, so competing projects can be added.

Internal rate of return is the discount rate at which $NPV = 0$. Accept if IRR exceeds the hurdle rate. IRR is popular because it is a single comparable percentage, but it can be misleading when cash flows change sign more than once or when comparing projects of very different scale.

Payback period is the time until cumulative cash inflows repay the initial investment. It is a liquidity and risk screen, not a profitability measure: it ignores the time value of money and everything that happens after payback. A project that pays back in 8 months and then stops is not better than one that pays back in 14 months and runs for a decade.

Return on investment

$ROI = \frac{\text{Net benefit}}{\text{Investment}} \times 100 = \frac{\text{Gain} - \text{Cost}}{\text{Cost}} \times 100$

ROI is simple and widely understood, and it is the measure most often quoted in Six Sigma project closure reports. Its weaknesses are that it ignores timing entirely and that it is highly sensitive to what is counted as "investment" -- fully loaded belt time, capital, and training either included or excluded can double the reported figure. State the basis explicitly.

Worked example

A project requires $180,000 of capital in year 0 and is expected to save $70,000 per year for five years. The hurdle rate is 10%.

• NPV is $85,349, comfortably positive, so the project clears the hurdle.
• Simple payback is $180{,}000 / 70{,}000 = 2.57$ years.
• Five-year ROI on undiscounted cash: $(350{,}000 - 180{,}000)/180{,}000 = 94.4%$.

Note how differently the three measures read. Payback says "under three years", ROI says "94%", and only NPV states the value created in today's money. When they conflict, NPV governs.

Cost-benefit analysis

CBA compares the full economic cost of an action against its full benefit, expressed either as a net figure or as a benefit-cost ratio:

$BCR = \frac{\text{Present value of benefits}}{\text{Present value of costs}}$

A ratio above 1.0 indicates benefits exceed costs. The discipline of CBA lies in completeness. Costs that project teams routinely omit:

• Fully loaded belt and team member time, including SME hours.
• Training and requalification of operators on new standard work.
• Validation and revalidation in regulated environments.
• Ongoing cost of the control plan: added inspection, calibration, software licences.
• Opportunity cost -- the return of the next-best project not resourced.

Benefits routinely overstated: savings claimed from freed labour hours that were never removed from the payroll, and cost avoidance counted as if it were cash.

Getting benefits validated

Three rules keep a Black Belt out of trouble at closure:

1. Agree the calculation method with finance during Define, not during Control.
2. Baseline before you change anything, using the same accounting basis you will use afterwards.
3. Let finance sign the closure number. A benefit claimed without a controller's signature will not appear in any operating statement, and the deployment loses credibility one project at a time.