Chapter 12

Measuring Current Process Performance

A practical SME guide to process measurement, baseline evidence, operational definitions and avoiding misleading metrics.

On this page

Use the headings in the article to move through the guide.

Current process performance is the baseline that shows how a process works before improvement. Without a baseline, the business may mistake opinion, frustration or one unusual case for the normal pattern. Good measurement does not need to be complicated, but it must be clear enough to support decisions.

The direct answer is this: measure the current process using a small set of indicators that show time, quality, cost, output, workload and customer impact. Define each measure carefully so people collect the same thing in the same way.

Core Process Performance Measures

Measure categoryWhat it showsExample
TimeHow long work takes or waits.Lead time from enquiry to quote.
QualityWhether output meets requirements.Percentage of orders delivered without correction.
CostResources consumed by the process.Labour hours per job or rework cost.
OutputVolume completed in a period.Invoices issued per week.
Backlog / WIPWork waiting or in progress.Open support tickets or orders awaiting approval.
Customer impactHow the process affects customer experience.Complaints, repeat calls, satisfaction comments.

Measurement Plan Template

FieldExampleYour notes
PurposeUnderstand quote delays.
MeasureEnquiry-to-quote lead time.
Start pointComplete enquiry received.
End pointQuote sent to customer.
UnitHours or working days.
Data sourceCRM timestamp and sent email.
Review rhythmWeekly for four weeks.
Decision useIdentify delay causes and improvement priority.

Lead Time, Cycle Time and Processing Time

TermPlain meaningSME example
Lead timeTotal time from start to finish from the customer or process-user perspective.Customer waits three days from enquiry to quote.
Cycle timeTime needed to complete one cycle of an operation when it is being worked.Estimator spends 35 minutes preparing a quote.
Processing timeTime work is actively being processed rather than waiting.Actual data entry time is 10 minutes, though the form waits two days.

Decision Tree: What Should You Measure First?

Problem patternMeasure firstWhy
Customers complain about waiting.Lead time and queue time.The pain is delay.
Work comes back for correction.Error rate, rework count and first-time-right quality.The pain is quality.
Staff feel overloaded.Demand volume, WIP and capacity.The pain may be workload balance.
Margins are falling.Labour time, rework cost and waste.The pain may be process cost.
Managers lack visibility.Output, backlog and status ageing.The pain is control and prioritisation.

Mini Chart Template: Weekly Baseline

WeekVolume receivedVolume completedAverage lead timeErrors / reworkBacklog at week end
Week 1
Week 2
Week 3
Week 4

Panith Illustrative Case Study

Panith Illustrative Case Study: A small marketing agency feels its design approval process is slow. The owner assumes designers need to work faster. Measurement shows that design work takes two hours on average, but client feedback waits six days and internal review waits two days. The bottleneck is not design effort; it is waiting and unclear approval rules.

Common Mistakes

  • Measuring too many things before knowing the decision you need to make.
  • Using vague definitions such as “fast” or “good quality”.
  • Measuring people in a way that creates fear instead of learning.
  • Ignoring waiting time because nobody is actively working during it.
  • Comparing before and after results without using the same measurement definition.

References and Further Reading

Next Lesson

Continue with Lesson 13: Process Time, Cost, Quality and Output.

SEO improvement pass: expanded depth and practical application

Expanded Practical Guidance

Measurement should begin with the decision the business needs to make. If the problem is customer waiting, start with lead time. If the problem is errors, start with first-time-right quality. If the problem is overload, start with demand, work in progress and capacity.

A good measure has an operational definition. That means everyone knows exactly when the clock starts, when it stops, what is counted and where the data comes from. Without this, two people can measure the same process and produce different numbers.

Good Measure Test

TestQuestion
RelevantWill this measure help us make a better process decision?
ClearCan two people collect it the same way?
PracticalCan we collect it without excessive admin?
BalancedDoes it avoid encouraging harmful behaviour?
ReviewedWill someone actually look at it and act?

Practical Next Step

Choose no more than three baseline measures for the first month. More measures can be added later once the team has learned what is useful.


Visual Learning Aids

The following visual structures translate this lesson into practical management tools. They are designed for SME use and can be copied into a workshop, team meeting or improvement plan.

1. Process Diagram

InputWork systemOutputOwnerMain risk
Customer need or business triggerMeasuring Current Process Performance applied to the business processReliable customer or internal outcomeProcess ownerRework, delay or quality failure

2. Flowchart

[Start] Trigger received
   |
   v
[Understand] Work is mapped
   |
   v
[Decide] Bottleneck or waste is identified
   |
   v
[Act] Improvement option is selected
   |
   v
[Review] New way of working is tested
   |
   v
[Improve] KPI review confirms next action

3. Decision Tree

Is the issue clear and evidence-based?
- No: clarify the problem, collect examples and involve the people closest to the work.
- Yes: does it affect customers, cost, quality, risk or growth?
  - No: document the learning and monitor lightly.
  - Yes: assign an owner, choose a practical method, define success measures and review progress.

4. Priority Matrix

Low effortHigh effort
High impactDo first: quick operational improvementPlan carefully: strategic improvement project
Low impactDo only if it removes frictionAvoid or defer unless required for risk, compliance or learning

5. Implementation Timeline

StageTypical SME timingOutput
DiagnoseWeek 1Problem statement and evidence
DesignWeek 2Chosen method, owner and measures
TestWeeks 3-4Small pilot or controlled trial
StandardiseWeeks 5-6Checklist, SOP, dashboard or decision rule
ImproveMonthlyReview notes and next improvement action

6. Illustrative Performance Chart

Illustrative example: replace these sample scores with real business data before using the chart for decisions.

MeasureCurrent scoreTarget scoreVisual gap
Clarity2/54/52 blocks to 4 blocks
Ownership2/55/52 blocks to 5 blocks
Measurement1/54/51 block to 4 blocks
Consistency3/54/53 blocks to 4 blocks

7. Maturity Model

LevelMaturity stageWhat it looks likeNext improvement
1Informal workInformal work is visible in the way the business manages this topic.Documented process
2Documented processDocumented process is visible in the way the business manages this topic.Measured process
3Measured processMeasured process is visible in the way the business manages this topic.Controlled process
4Controlled processControlled process is visible in the way the business manages this topic.Continuously improved process
5Continuously improved processContinuously improved process is visible in the way the business manages this topic.Sustain and refine through periodic review

8. Comparison Table

DimensionCurrent-state processFuture-state process
Decision basisExperience, urgency or individual memoryEvidence, agreed criteria and visible trade-offs
AccountabilityUnclear or dependent on the founderNamed owner with clear responsibility and review rhythm
MeasurementDiscussed only when something goes wrongTracked using cycle time, first-time-right rate, cost and customer impact
ScalabilityWorks only while the team is smallCan be taught, repeated and improved as the business grows