Process Types and Process Hierarchies

A process hierarchy is a structured way to organise the work of a business, from broad end-to-end processes down to detailed activities and tasks. For an SME, this is useful because it stops every task from looking equally important. It helps owners see which processes create customer value, which processes govern the business, and which processes support the people doing the work.

The direct answer is simple: most business processes can be grouped into management processes, core business processes and support processes. A process hierarchy then breaks those processes into smaller levels so the business can understand, document, measure and improve them without drowning in detail.

Why SMEs Need Process Categories

Small businesses often manage work through departments or people: sales, admin, workshop, finance, the owner, the operations manager. That is understandable, but it can hide how work actually flows. A customer order may involve sales, production, purchasing, dispatch and finance. If each team only improves its own tasks, the whole customer experience may still remain slow or unreliable.

Process categories give the business a clearer operating map. They show which work sets direction, which work creates value for customers, and which work enables the rest of the company to function. ASQ describes broad enterprise process types as management, business and support processes; APQC also uses process frameworks to create common language and hierarchy for process management.

The Three Main Process Types

Process type	Purpose	SME examples	Main question
Management processes	Set direction, make decisions, allocate resources and review performance.	Strategy review, budgeting, performance management, compliance review, management meetings.	How do we steer and control the business?
Core business processes	Create direct value for external customers and usually define what the business exists to do.	Enquiry-to-order, order fulfilment, service delivery, product development, customer support.	How do we create and deliver value customers care about?
Support processes	Enable core processes and management processes to work effectively.	Recruitment, payroll, IT support, purchasing, facilities, bookkeeping, training.	What must run well internally so value can be delivered externally?

Process Hierarchy Levels

A hierarchy lets you zoom in and out. At the top, you see the major value streams and process groups. At the bottom, you see detailed tasks. Both views matter, but they are used for different decisions. Senior leaders need the high-level process landscape. Team members need clear steps, standards and responsibilities.

Hierarchy level	What it describes	Example
Level 1: Process category	A broad family of work across the business.	Core business processes
Level 2: Process group	A major group of related processes.	Sell products and services
Level 3: Process	A repeatable end-to-end flow with a defined output.	Convert enquiry to confirmed order
Level 4: Activity	A meaningful part of the process.	Prepare customer quote
Level 5: Task	A specific action or instruction.	Check price list, confirm delivery date, send quote email

Conceptual Framework: SME Process Landscape

Layer	What belongs here	How often to review
Direction layer	Strategy, governance, performance review, risk decisions.	Monthly or quarterly.
Customer value layer	Sales, delivery, fulfilment, support, product or service creation.	Weekly to monthly, depending on volume.
Enablement layer	People, finance, technology, suppliers, facilities and knowledge.	Monthly or when pain appears.
Task layer	Detailed instructions, forms, checklists and role-level work.	Whenever errors, training gaps or changes appear.

Decision Tree: How Much Detail Do You Need?

Question	If yes	If no
Is the process causing customer, cost, quality or growth pain?	Map it at process and activity level.	Keep a light overview only.
Do staff perform the work inconsistently?	Document key tasks and standards.	Avoid unnecessary task-level detail.
Does the process cross departments or roles?	Show handoffs, ownership and inputs clearly.	A simple checklist may be enough.
Is the work regulated or high risk?	Define controls, approvals and evidence requirements.	Use lighter controls and review later.

Panith Illustrative Case Study

Panith Illustrative Case Study: A small ecommerce business thinks it has a “shipping problem” because customers complain about late deliveries. When the owner maps the process hierarchy, the issue becomes clearer. The core process is order fulfilment. Within it, the picking activity is reliable, but the stock availability activity and courier booking activity are weak. The support process for inventory records is also unreliable.

The hierarchy prevents the owner from blaming the dispatch person alone. It shows how a support process, inventory accuracy, is damaging a core process, order fulfilment. The improvement can now target the right level of work.

Worksheet: Build a First Process Hierarchy

Prompt	Your notes
List three core processes customers directly experience.
List three support processes those core processes depend on.
List two management processes that steer priorities and standards.
Choose one painful process and identify its main activities.
Identify one task that needs clearer instruction or training.

Common Mistakes

Documenting detailed tasks before understanding the end-to-end process.
Confusing departments with processes.
Treating support processes as unimportant because customers do not directly see them.
Creating too many hierarchy levels for a small team.
Ignoring management processes such as decision-making, review and accountability.

Self-Assessment Questions

Which process in your business creates the most direct customer value?
Which support process most often damages that customer-value process?
Where are you currently managing a cross-functional process as if it belonged to one department?
What process needs a high-level map, and what task needs a detailed instruction?

References and Further Reading

Next Lesson

Continue with Lesson 5: End-to-End Process Thinking. That lesson explains why many process problems sit between functions, handoffs and customer outcomes rather than inside a single task.

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	Process Types and Process Hierarchies 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