How to Discover How Work Really Happens in a Small Business

Before improving a process, you need to understand how work really happens. Not how the procedure says it happens. Not how the owner thinks it happens. Not how it works on a perfect day. The current state is the real pattern of work, including informal shortcuts, missing information, waiting, rework, exceptions and workarounds.

The direct answer is this: discover real work by observing it, speaking with the people who do it, reviewing actual examples and following the flow from start to finish. Lean practice calls this going to the gemba, the actual place where value is created. The purpose is learning, not catching people out.

Why Official Processes Are Often Incomplete

Many SMEs have a gap between the official process and the lived process. The official version may say that every customer request is recorded in the CRM, but staff may also use WhatsApp, notebooks and email flags. The official version may say that approvals take one day, but people know that urgent jobs are approved by phone. These realities matter because improvement based only on the official process will miss the true causes of delay and risk.

Discovery Methods Comparison Table

Method	Best for	Watch out for
Direct observation	Seeing steps, delays, handoffs and workarounds.	People may behave differently while being observed.
Employee conversations	Understanding judgement, exceptions and pain points.	Avoid turning it into blame or performance review.
Document review	Finding official standards, forms, records and evidence.	Documents may be outdated or ignored.
System data review	Checking timestamps, backlog, errors and volumes.	Data may not explain why problems happen.
Customer examples	Understanding the outcome and experience.	One dramatic complaint may not represent the whole pattern.

Simple Current-State Discovery Flow

Step	Action	Output
1	Define the process boundary.	Start and end point.
2	Collect real examples of recent work.	Evidence set.
3	Observe the work from trigger to output.	Current-state notes.
4	Ask people what usually happens and what happens on difficult days.	Exception patterns.
5	Compare observation, interviews and records.	Reality check.
6	Summarise what is known, uncertain and assumed.	Discovery findings.

Observation Checklist

What starts the work?
What information is needed before work can continue?
Who touches the work?
Where does it wait?
Where is judgement required?
Where do people leave the official path?
What gets checked, corrected or repeated?
What evidence shows the output was accepted?

Decision Tree: When to Observe, Interview or Measure

Situation	Best first method	Why
Nobody agrees what the steps are.	Observe the work and build a rough map.	The team needs shared reality.
People agree on steps but not causes.	Interview and review examples.	The issue may be hidden in exceptions.
The process looks clear but performance varies.	Measure timestamps, errors or backlog.	Variation needs evidence.
The process involves customer frustration.	Review customer examples and follow the case backwards.	The outcome reveals where value was lost.

Panith Illustrative Case Study

Panith Illustrative Case Study: A local plumbing company believes its booking process is simple: customer calls, office books job, plumber attends. Observation shows a different reality. Some jobs start through WhatsApp, urgent calls bypass the diary, plumbers reschedule directly, and job notes are sometimes sent as voice messages. The process is not one process; it is several informal paths.

The owner originally wanted booking software. Discovery shows that software may help later, but the first need is a single intake standard and a clear rule for schedule changes.

Worksheet: Current-State Discovery Notes

Prompt	Notes
Process being studied
Observed start point
Observed end point
People involved
Systems or records used
Visible delays
Workarounds
Questions to verify

Common Mistakes

Assuming the written procedure is accurate.
Starting with solutions before observing real work.
Blaming people for workarounds created by weak systems.
Observing only the easiest case, not exceptions.
Failing to validate findings with the people who do the work.

References and Further Reading

Next Lesson

Continue with Lesson 8: Stakeholder and Employee Process Interviews.

SEO improvement pass: expanded depth and practical application

Expanded Practical Guidance

A good discovery exercise should produce a small set of reliable facts, not a large document that nobody trusts. For an SME, the most useful output is usually a current-state summary: the real start point, real end point, main steps, people involved, systems used, visible delays, common exceptions and questions that still need evidence.

The discovery phase should also separate normal work from exception work. A process may look simple on an ordinary day but become fragile when a customer asks for a change, a supplier misses a delivery or the owner is away. Those difficult cases often reveal the true weakness of the process.

Current-State Evidence Matrix

Evidence type	What it proves	Example
Observation	What people actually do.	A quote waits in an inbox before review.
Interview	Why people do it that way.	Staff use WhatsApp because the CRM is slow.
Record	How often it happens.	Timestamps show approval takes two days.
Customer example	How the outcome feels outside the business.	A customer chased three times for an update.

Practical Next Step

Choose one process and collect five recent examples before mapping it. Those examples keep the discussion grounded in reality and reduce the risk of designing around assumptions.

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

Input	Work system	Output	Owner	Main risk
Customer need or business trigger	How to Discover How Work Really Happens applied to the business process	Reliable customer or internal outcome	Process owner	Rework, 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 effort	High effort
High impact	Do first: quick operational improvement	Plan carefully: strategic improvement project
Low impact	Do only if it removes friction	Avoid or defer unless required for risk, compliance or learning

5. Implementation Timeline

Stage	Typical SME timing	Output
Diagnose	Week 1	Problem statement and evidence
Design	Week 2	Chosen method, owner and measures
Test	Weeks 3-4	Small pilot or controlled trial
Standardise	Weeks 5-6	Checklist, SOP, dashboard or decision rule
Improve	Monthly	Review 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.

Measure	Current score	Target score	Visual gap
Clarity	2/5	4/5	2 blocks to 4 blocks
Ownership	2/5	5/5	2 blocks to 5 blocks
Measurement	1/5	4/5	1 block to 4 blocks
Consistency	3/5	4/5	3 blocks to 4 blocks

7. Maturity Model

Level	Maturity stage	What it looks like	Next improvement
1	Informal work	Informal work is visible in the way the business manages this topic.	Documented process
2	Documented process	Documented process is visible in the way the business manages this topic.	Measured process
3	Measured process	Measured process is visible in the way the business manages this topic.	Controlled process
4	Controlled process	Controlled process is visible in the way the business manages this topic.	Continuously improved process
5	Continuously improved process	Continuously improved process is visible in the way the business manages this topic.	Sustain and refine through periodic review

8. Comparison Table

Dimension	Current-state process	Future-state process
Decision basis	Experience, urgency or individual memory	Evidence, agreed criteria and visible trade-offs
Accountability	Unclear or dependent on the founder	Named owner with clear responsibility and review rhythm
Measurement	Discussed only when something goes wrong	Tracked using cycle time, first-time-right rate, cost and customer impact
Scalability	Works only while the team is small	Can be taught, repeated and improved as the business grows