Business Processes and Systems Thinking
Undergraduate textbook notes · Process analysis · Modelling · Performance · Improvement
Introduction
Organisations achieve outcomes through connected processes. Information systems support these processes by coordinating people, data, decisions and technology. This chapter develops the process and systems perspective required to analyse work before selecting or implementing digital solutions.
1. Understanding business processes
A business process is a coordinated set of activities that transforms inputs into outputs to achieve a defined organisational outcome. It may deliver a product, provide a service, meet a regulatory obligation or support another process. Examples include customer enquiry to resolution, order to cash, procure to pay, recruit to retire, product development, student admission and patient discharge. A process is not simply a list of tasks: it has a purpose, a trigger, participants, information, decision rules, resources, outputs and measures of performance. A process perspective directs attention to how work flows across roles and departments rather than treating each organisational unit as an isolated function.
Processes may be classified as core, support or management processes. Core processes directly create value for customers or service users, such as selling, manufacturing, teaching or clinical care. Support processes provide capabilities needed by core activities, including finance, human resources, procurement and IT support. Management processes establish direction, allocate resources, monitor performance and manage risk. The categories are useful for analysis but not absolute: a process that is supportive in one organisation may be central to the service offered by another.
A process boundary defines where analysis begins and ends. Analysts must identify the event that triggers the process and the condition that represents successful completion. If a customer order process begins only when an order is accepted, it may exclude important failures in product discovery and quotation. If it ends at dispatch rather than confirmed delivery, it may miss the customer experience after the goods leave the warehouse. Clear boundaries prevent incomplete analysis while avoiding an unmanageable scope.
PEOPLE · INFORMATION · TECHNOLOGY · RULES
FEEDBACK: MEASURES, CUSTOMER RESPONSE AND CONTROL
2. Process thinking and systems thinking
Process thinking examines the sequence and coordination of work needed to produce an outcome. Systems thinking examines the wider set of interacting elements, relationships, feedback loops and environmental influences that shape behaviour. Together, they help analysts avoid local optimisation. A department may reduce its own processing time by passing incomplete work to another team, increasing total cycle time. A purchasing unit may obtain a lower unit price by ordering large quantities, while raising storage costs and obsolescence risk elsewhere. The organisation should evaluate end-to-end performance, not only isolated departmental targets.
A system boundary identifies which elements are included in an analysis and which are treated as part of the environment. Boundaries are analytical choices rather than natural walls. A hospital appointment process may include patients, clinicians, reception staff, referral systems, transport, laboratories and external providers. A narrow boundary around the booking application may conceal the causes of missed appointments, such as transport barriers or unclear referral information. Analysts should state assumptions and examine dependencies beyond the immediate software solution.
Systems exhibit interdependence, emergence, feedback, delays and adaptation. Interdependence means a change in one component can affect others. Emergence refers to outcomes that arise from interactions and cannot be understood by examining each component alone. Feedback occurs when outputs influence future behaviour. Delays can make consequences appear long after a decision. Adaptation occurs when people change their behaviour in response to new rules or technology. These properties explain why process change can produce unexpected outcomes and why post-implementation monitoring is essential.
3. Process hierarchy and classification
Processes can be represented at different levels of detail. A process architecture shows major end-to-end processes and their relationships. A value chain groups activities that contribute to creating and delivering value. A process group can be decomposed into processes, subprocesses, activities and tasks. For example, order fulfilment may contain order validation, inventory allocation, picking, packing, dispatch and delivery confirmation. A task is a specific unit of work performed by a person or system. Decomposition allows analysts to move from a high-level overview to detailed operational analysis without losing sight of the overall outcome.
Process classification frameworks provide common categories and reference models. They can help organisations compare their process coverage and identify missing capabilities. However, a framework should be adapted to the organisation's strategy, industry, size and regulatory context. Copying a generic process map without checking actual work can produce documentation that looks comprehensive but does not describe reality. Reference models are starting points for investigation, not substitutes for observation and stakeholder engagement.
Processes may also be classified by frequency, variability, criticality, customer contact, degree of structure and level of automation. High-volume routine processes may benefit from standardisation and transaction automation. Complex, exception-rich processes may require professional judgement and flexible case management. Critical processes deserve stronger controls, continuity arrangements and monitoring. Classification supports prioritisation: not every process should receive the same investment or level of standardisation.
4. Customers, stakeholders and value propositions
Process design begins with identifying the people who receive or influence its outputs. Customers may be external purchasers, citizens, learners, patients or internal users. Stakeholders also include employees, managers, suppliers, regulators, owners, communities and technology partners. Their interests can differ. A process that is convenient for administrators may create unnecessary effort for customers. A process that maximises speed may reduce accessibility or procedural fairness. Stakeholder analysis makes these tensions visible and supports balanced design decisions.
A value proposition explains the benefit an organisation intends to provide to a particular group. Process performance should be evaluated in relation to that benefit. A low-cost service may prioritise affordability and predictable delivery; a specialist service may prioritise accuracy, expertise and continuity. The same process measure can have different meaning in different contexts. Reducing average handling time may improve a simple enquiry service but harm a complex advisory service if staff are pressured to end conversations before issues are resolved.
Voice-of-customer methods include interviews, surveys, complaints analysis, observation, service analytics and co-design workshops. Data should be interpreted carefully because response rates may be uneven and some groups may be less able to provide feedback. Analysts should look for patterns across customer segments and investigate the reasons behind dissatisfaction. Customer experience is shaped by the complete journey, including communications, waiting, hand-offs, accessibility, error correction and after-service support.
5. Process mapping and notation
Process maps make work visible by representing activities, decisions, events, roles and information flows. A simple flowchart uses rectangles for activities, diamonds for decisions, arrows for sequence and start/end symbols for boundaries. Swimlane diagrams place activities in lanes representing roles, departments or systems. They reveal hand-offs and help distinguish work performed by people from work performed by applications. Maps should be readable, consistently labelled and proportionate to the question being investigated.
Business Process Model and Notation (BPMN) provides a standard graphical language for process modelling. Common BPMN elements include events, activities, gateways, sequence flows, message flows, pools and lanes. A start event indicates a process trigger; an activity represents work; an exclusive gateway selects one path based on a condition; a parallel gateway enables concurrent paths; and an end event marks completion. Message flows represent communication between separate participants, while sequence flows show the order of activities within a process participant.
Notation should clarify rather than decorate. A model should state its level of detail, scope, assumptions and version. Analysts should avoid mixing incompatible meanings or using symbols without a legend. A process map is a model of reality, not reality itself. Validation with people who perform the work is essential because formal procedures may differ from actual practice. Shadowing and observation can reveal informal approvals, spreadsheets, workarounds and exceptions omitted from official documents.
IF COMPLETE → ASSESS → DECIDE → NOTIFY
IF INCOMPLETE → REQUEST INFORMATION → RECHECK
6. The as-is process: discovering actual work
As-is analysis documents how a process currently operates. It should capture the normal route, common variations, exceptions, rework, waiting, approvals, information sources and control activities. Evidence can be collected through interviews, workshops, direct observation, document review, system logs, forms, reports and customer feedback. Each method has limitations. Interviews may reflect what participants believe should happen rather than what happens; system logs may omit manual work; observation may alter behaviour; and written procedures may be outdated.
Analysts should compare multiple sources and record discrepancies rather than forcing premature agreement. A frontline employee may describe a workaround that a manager does not know about. A policy may require two approvals while the application permits only one. A process may appear efficient in the system but involve repeated calls to customers to correct missing information. These differences are valuable findings because they identify gaps between formal design and operational reality.
Process discovery should be respectful and non-punitive. Staff may hide workarounds if they fear blame. The purpose is to understand the system and improve it, not to assume that every deviation is misconduct. Analysts should protect confidential information, obtain appropriate permission for observation and explain how findings will be used. Where the process affects vulnerable service users, include their perspectives through safe and accessible engagement.
7. The to-be process and design principles
The to-be process describes a proposed future way of working. It should respond to evidence from the as-is analysis and connect directly to measurable organisational objectives. Design principles may include customer focus, simplicity, accessibility, prevention of errors, clear accountability, data reuse, security by design and resilience. A future-state map should identify what changes, why the change is expected to help and what assumptions must hold for the benefits to occur.
Good process design removes activities that do not contribute to value, control or legal obligations. It reduces unnecessary hand-offs, avoids repeated data entry, clarifies decision rights and places information where it is needed. Standardisation can improve consistency, but excessive standardisation can ignore legitimate differences in customer circumstances or professional judgement. The aim is not to eliminate all variation; it is to distinguish harmful inconsistency from necessary flexibility.
Design alternatives should be compared against criteria such as customer outcomes, cycle time, cost, error risk, compliance, accessibility, staff workload, technical feasibility and change complexity. A proposed process may be faster but require expensive integration or introduce a single point of failure. A pilot or prototype can test uncertain assumptions before full deployment. Design decisions should be documented so that future teams understand why a particular approach was selected.
8. Process performance and measurement
Process performance measures describe how effectively and efficiently a process achieves its purpose. Common dimensions include quality, time, cost, flexibility, reliability, safety, compliance, accessibility and customer experience. Measures should be linked to a clear process objective. A measure without a defined purpose may encourage activity that does not improve outcomes. For example, counting the number of cases closed says little about whether cases were resolved correctly or whether customers had to reopen them.
Efficiency concerns the relationship between outputs and resources used. Effectiveness concerns whether intended outcomes are achieved. A process may be efficient but ineffective if it rapidly produces the wrong result. Productivity may be measured as output per unit of input, but the output definition must include quality. Cycle time measures elapsed time from defined start to finish; processing time measures time actively spent working; waiting time is time spent in queues or pauses. These distinctions help locate opportunities for improvement.
Key performance indicators should have an operational definition, data source, owner, frequency, target and interpretation guidance. Analysts should examine distributions, not only averages, because a satisfactory mean may hide long delays for a minority of cases. Measures should be segmented carefully to identify unequal outcomes without exposing individuals. Targets must be balanced to avoid gaming, such as closing cases prematurely to meet a speed target. A small set of meaningful measures is usually more useful than a large dashboard of poorly understood indicators.
9. Process time, capacity and bottleneck analysis
Capacity is the maximum sustainable rate at which a process or resource can perform work under stated conditions. Demand is the rate at which work arrives. When demand approaches or exceeds capacity, queues and waiting times tend to increase. A bottleneck is a resource or activity that constrains the throughput of the wider process. Improving a non-bottleneck activity may have little effect on total output if the constrained stage remains unchanged.
Little's Law states that, under stable conditions, the average number of items in a system (L) equals the average throughput rate (λ) multiplied by the average time in the system (W): L = λW. If a service handles an average of 12 cases per hour and each case spends an average of 2 hours in the system, the average work in progress is 24 cases. The relationship helps analysts understand how waiting, throughput and work in progress are connected. It should not be applied blindly to systems that are not operating in a reasonably stable state.
Cycle-time analysis separates value-adding work from waiting, transport, inspection, correction and other activities. A process with 40 minutes of actual work but a 3-day elapsed time may have a queue or approval delay rather than a labour-capacity problem. Queueing behaviour becomes particularly important when arrival rates are variable and utilisation is high. Adding a small amount of spare capacity can sometimes reduce waiting substantially, especially in services where arrivals are unpredictable.
TO-BE: SET OBJECTIVES → REDESIGN → TEST → IMPLEMENT
MONITOR OUTCOMES AND REFINE
10. Process costs and activity-based thinking
Process cost analysis identifies the resources consumed in delivering an outcome. Costs may include labour, materials, facilities, technology, energy, supplier charges, rework, error correction and customer support. Direct costs can be traced to a particular process or output; indirect costs require allocation. Allocations should be transparent because arbitrary overhead assumptions can distort comparisons between process alternatives.
Activity-based costing assigns costs to activities using cost drivers that reflect resource consumption. For example, the cost of processing supplier invoices may be related to the number of invoices, complexity, exception rate or manual interventions rather than simply the number of suppliers. Activity-based thinking helps identify expensive activities and the reasons for cost variation. It can reveal that a seemingly low-cost product creates disproportionate support or administration work.
Total cost of ownership considers costs over the life of a solution, not just the purchase price. A new process may require software licences, integration, training, data migration, support, security controls, upgrades and eventual exit. Cost-benefit analysis should include measurable benefits and plausible non-financial effects, while making assumptions explicit. Sensitivity analysis tests how the business case changes when demand, cost, adoption or benefit estimates differ from the central forecast.
11. Process controls, risk and compliance
Process controls are activities designed to prevent, detect or correct errors, fraud, misuse, safety failures or non-compliance. Preventive controls include authorisation, validation, segregation of duties and access restrictions. Detective controls include reconciliations, exception reports, monitoring and audit trails. Corrective controls include reversal, recovery, remediation and incident response. Controls should be proportionate to risk and embedded into the workflow where possible.
Segregation of duties reduces the risk that one person can initiate, approve and conceal an inappropriate transaction. In a small organisation, complete separation may be impractical; compensating controls such as independent review, transaction limits and periodic reconciliation may be needed. A control should have a clear owner, frequency, evidence requirement and escalation route. A control that exists only in a policy but is not performed is not effective.
Compliance requirements may arise from legislation, regulation, contracts, professional standards and internal policy. Analysts should identify applicable obligations with qualified legal or compliance support rather than guessing. Privacy, record retention, consumer rights, financial controls, health and safety, accessibility and sector-specific requirements may influence process design. Compliance should be considered at the beginning of redesign because retrofitting controls can be expensive and disruptive.
12. Decision points, rules and exception handling
Business rules define or constrain decisions and actions. Examples include eligibility criteria, credit limits, approval thresholds, discount rules, stock reorder points and service priorities. Rules should be documented in clear language, assigned to an owner and reviewed when policies or conditions change. Where rules are embedded in software, organisations need a controlled method to update, test and communicate them.
Decision tables can represent combinations of conditions and their corresponding actions. They are useful when several factors determine an outcome. Decision trees show sequential branches and may help explain a decision path. Analysts should check for missing combinations, contradictory rules, duplicated conditions and rules that are impossible to satisfy. Ambiguous rules often create inconsistent treatment across employees or customer groups.
Exceptions are cases that cannot follow the standard path. They may arise from incomplete information, unusual customer needs, system failure, suspected fraud, legal restrictions or legitimate professional judgement. Good exception design defines detection, routing, ownership, time limits, escalation and resolution. If exceptions are frequent, the standard process may be poorly designed. Exception data should therefore feed continuous improvement rather than being treated only as operational noise.
13. Information flow and data requirements in processes
Every process uses and creates information. Analysts should identify what data are required at each step, where they originate, who is responsible for them, how they are validated and where they are stored. Data-flow diagrams can show external entities, processes, data stores and flows. A data dictionary defines fields, meanings, formats, permitted values, ownership and quality rules. Shared definitions reduce the risk that different departments interpret the same term differently.
Duplicate capture increases effort and creates inconsistent records. Reusing trusted data can improve efficiency, but only when the source is authoritative, current and appropriate for the new purpose. Data minimisation means collecting only what is necessary. Access should follow role and purpose, and sensitive information should not be exposed merely because it is technically available. Retention and deletion rules should reflect business need and applicable law.
Information hand-offs are common sources of failure. A receiving team may not know whether a field is mandatory, whether a record has been verified or whether a customer has consented to a particular use. Process design should specify hand-off conditions, acknowledgement, error handling and traceability. Integration can automate transfer, but interfaces must address failed messages, duplicate events, incompatible formats and changes to source systems.
14. Workflow, automation and orchestration
Workflow management coordinates tasks, information and approvals according to defined rules. A workflow may be human-centred, system-centred or a combination. Workflow software can route work to a person, assign deadlines, send notifications, record decisions and provide status visibility. It is particularly useful where work passes between roles or requires traceable approvals. However, automating an unclear process can make poor practices faster and harder to see.
Automation options range from simple validation and scheduled jobs to robotic process automation, application integration, business rules engines and AI-assisted processing. Robotic process automation can mimic repetitive interactions with existing applications, but it may be fragile when screens or data formats change. Direct integration through supported interfaces is often more robust for stable, high-volume exchanges. AI may help classify unstructured content or support decisions, but outputs require appropriate validation and oversight.
Automation suitability depends on volume, stability, rule clarity, exception frequency, data quality, risk and the need for human judgement. A repetitive, rules-based task with reliable input data may be a strong candidate. A complex decision involving empathy, ambiguous evidence or significant rights may require human responsibility. Process owners should measure error rates, exception volumes, time saved, user impact and total operating cost after automation.
15. Lean thinking and waste reduction
Lean thinking focuses on creating value while reducing activities that consume resources without contributing to that value. Common categories of waste include unnecessary transport, inventory, motion, waiting, overproduction, over-processing, defects and underused human capability. In service environments, waste may appear as repeated data entry, unnecessary approvals, unclear forms, avoidable customer contact and duplicated checks. The purpose is not simply to cut staff or time; it is to improve the flow and quality of work.
Value-stream mapping displays the flow of materials and information required to deliver a product or service. It distinguishes value-adding activities from necessary but non-value-adding activities and avoidable waste. The map can show process time, waiting time, inventory or work in progress, information triggers and constraints. A future-state map proposes a more continuous and reliable flow. The analysis should include the customer's perspective because an activity may appear efficient internally while creating effort for the customer.
Continuous improvement involves small, repeated changes informed by evidence. The Plan-Do-Check-Act cycle provides a simple structure: plan a change, test it, examine results and decide whether to adopt, adapt or abandon it. Improvement should involve the people who perform the work and should protect quality, safety and fairness. A reduction in time is not a genuine improvement if it increases defects, excludes users or shifts hidden work to another team.
DO: TEST ON A CONTROLLED SCALE
CHECK: COMPARE EVIDENCE WITH BASELINE
ACT: ADOPT, ADAPT OR ABANDON
16. Six Sigma and variation management
Six Sigma is an improvement approach that focuses on reducing process variation and defects through disciplined measurement and analysis. The DMAIC cycle consists of Define, Measure, Analyse, Improve and Control. Define clarifies the problem, customer needs and scope. Measure establishes baseline performance and checks whether the measurement system is reliable. Analyse investigates causes. Improve develops and tests solutions. Control sustains gains through ownership, monitoring and standard procedures.
Variation is the difference between process outcomes. Some variation is inherent in the current system, while other variation may arise from identifiable causes such as equipment failure, inconsistent training, supplier defects or data-entry errors. Analysts should avoid assuming that every unusual observation is a special cause or that every difference requires intervention. Statistical tools such as run charts, control charts, histograms and Pareto analysis help distinguish patterns and prioritise investigation.
Defect definitions must be meaningful to customers and process owners. A missing field may be a defect in one context but irrelevant in another. A service-level target should not be confused with a statistical control limit: a target describes desired performance, while control limits estimate the range of common-cause variation under a stable process. Improvement requires reliable data, suitable methods and an understanding of the operational context.
17. Business process reengineering and radical redesign
Business process reengineering (BPR) involves fundamental reconsideration and radical redesign of processes to achieve substantial improvements in performance. It differs from incremental improvement because it may question organisational structures, roles, technology and assumptions that shape the process. BPR may be considered when a process is fundamentally unsuitable, when customer expectations change sharply or when digital capabilities make a different operating model possible.
Radical redesign carries significant risk. It may disrupt operations, remove valuable informal knowledge, create resistance, require major investment or introduce new dependencies. A dramatic technology deployment does not guarantee transformation. BPR should begin with a clear strategic rationale and evidence of the problem, examine end-to-end outcomes and involve the people affected. Pilot testing and staged migration may reduce risk where the process cannot safely be replaced all at once.
Organisations should distinguish genuine redesign from cost-cutting presented as innovation. A sustainable redesign considers service quality, workload, accessibility, employee capability, control and resilience. It should define transition arrangements and preserve essential knowledge. Benefits should be measured after implementation, including unintended consequences and the distribution of effects across customer and employee groups.
18. Organisational structure, culture and process ownership
Organisational structure determines how responsibilities, authority and resources are arranged. Functional structures group people by specialist discipline; divisional structures group work around products, regions or customer segments; matrix structures combine functional and project or product responsibilities; process-oriented structures emphasise end-to-end outcomes. Each structure creates different coordination strengths and tensions. Processes frequently cross formal reporting lines, so process performance requires collaboration beyond departmental boundaries.
Process ownership assigns accountability for the performance, design, controls and improvement of an end-to-end process. A process owner should have authority to coordinate relevant teams, access performance information and escalate unresolved issues. Ownership does not mean that one person performs every task. Operational managers remain responsible for their teams, while process governance aligns local execution with overall outcomes.
Culture influences whether staff share information, raise concerns, follow controls, learn from errors and adopt new ways of working. A blame-oriented culture may conceal defects; a learning culture encourages investigation and improvement while maintaining accountability for deliberate misconduct. Leadership behaviour, incentives, workload, communication and psychological safety shape process culture. Technology cannot compensate for unresolved organisational conflict or unclear authority.
19. Enterprise systems and end-to-end process integration
Enterprise systems integrate data and workflows across organisational functions. An ERP platform may connect finance, procurement, inventory, manufacturing, projects and human resources. CRM systems coordinate customer-facing activity, while supply chain platforms connect suppliers, logistics and demand planning. Integration can improve visibility and reduce repeated entry, but it also creates shared dependencies: a configuration error or master-data defect may affect multiple departments.
End-to-end process integration requires common identifiers, agreed data definitions, consistent rules and clear ownership. Master data describe core entities such as customers, suppliers, products and locations. Poor master-data governance can produce duplicate records, incorrect deliveries, inaccurate reporting and failed integrations. Organisations should establish creation, validation, amendment, merge and retirement rules for important master data.
Enterprise platforms often embed standard process assumptions. Organisations must evaluate whether to adapt their practices to the platform, configure it or customise software. Standardisation may reduce complexity and improve upgrades, while excessive customisation can create long-term cost. However, forcing a generic process onto a regulated or strategically distinctive activity may be inappropriate. Fit-gap analysis documents where standard capabilities meet requirements and where justified changes are needed.
20. Process integration across suppliers and customers
Modern processes extend beyond organisational boundaries. Supply networks connect suppliers, manufacturers, distributors, retailers and customers. Service ecosystems connect public agencies, contractors, community organisations and service users. Integration may involve shared forecasts, electronic orders, shipment events, service referrals, payment messages and customer notifications. The purpose is to coordinate activity and reduce uncertainty across the wider value chain.
Inter-organisational integration requires agreements about data meaning, timing, security, service levels, responsibilities and dispute resolution. Technical connectivity alone does not create collaboration. Partners may have different incentives, capabilities, systems and legal obligations. A supplier may be unable to provide real-time inventory data, or a customer may not consent to a particular data use. Integration plans should consider unequal bargaining power and the risks of over-dependence on a dominant platform.
Supply-chain visibility can improve planning and response, but shared information may be incomplete or delayed. Organisations should identify critical dependencies, alternative suppliers and continuity options. They should also consider the security of third-party connections and the possibility that an incident at one partner may affect the wider network. Contracts, technical controls and relationship management work together to support resilience.
21. Customer journeys and service blueprinting
A customer journey describes a person's experience across stages and channels while attempting to achieve a goal. It may include awareness, enquiry, application, purchase, delivery, support and renewal. Journey mapping identifies customer actions, questions, emotions, touchpoints, pain points and opportunities. It helps reveal that a service is experienced as one connected journey even when different departments own individual stages.
Service blueprinting extends journey mapping by showing frontstage interactions visible to the customer, backstage activities, support processes, systems and physical or digital evidence. A learner applying to a training programme, for example, may interact with a web form while admissions staff verify documents, finance confirms payment and an academic department checks eligibility. The blueprint reveals dependencies that a simple user-interface design may overlook.
Journey maps should be based on evidence from real users and should represent different needs and circumstances. A single fictional persona can conceal diversity in language, disability, connectivity, income or digital confidence. Analysts should examine failure journeys as well as successful ones: abandoned applications, delayed refunds, inaccessible communications and unresolved complaints. Journey measures may include completion rate, effort, time, repeat contact and outcome quality.
22. Process governance and portfolio prioritisation
Process governance establishes how processes are owned, approved, measured, changed and assured. It defines roles for process owners, operational managers, data owners, risk specialists, IT teams and senior leadership. Governance should be sufficiently strong to protect consistency and accountability but not so bureaucratic that routine improvements become impossible. Decision rights should be clear for changes affecting multiple departments or critical controls.
Organisations often have more improvement opportunities than resources. Prioritisation can consider strategic alignment, customer impact, risk, legal urgency, cost, feasibility, expected benefits, process volume and readiness for change. A portfolio view helps balance quick wins with foundational improvements. High-risk processes may deserve priority even when their direct financial return is difficult to quantify.
Process documentation should be maintained as an operational asset. Models, procedures, rules, controls, data definitions and measures should have owners, version histories and review dates. Changes to applications or regulations may make process documents inaccurate. Governance should specify how changes are assessed, communicated and approved. Auditability is especially important where decisions affect money, safety, rights or sensitive information.
23. Process change and stakeholder adoption
Process change affects routines, authority, skills, workload and professional identity. Resistance may arise from uncertainty, previous failed projects, lack of trust, inadequate consultation, fear of job loss or concerns that the proposed process is unsafe. These reactions should be investigated rather than dismissed as unwillingness to change. Staff often understand operational constraints that are invisible to project teams.
Change planning includes stakeholder analysis, communication, leadership alignment, training, local support, transition arrangements and feedback. Communication should explain why change is needed, what will change, what will remain and how concerns can be raised. Training should be role-specific and practice-based. Users need opportunities to test new workflows with realistic cases before high-stakes implementation.
Adoption should be measured through actual behaviour and outcomes rather than attendance at training alone. Measures may include use of the new workflow, task completion, error rates, workarounds, support requests, confidence and customer experience. Leaders should review whether the process is workable and adjust it when evidence reveals unintended problems. Sustainable change is reinforced through role descriptions, procedures, performance measures and ongoing coaching.
24. Digital process innovation and intelligent automation
Digital process innovation uses technologies to change the design, reach or value of organisational work. Application programming interfaces can connect systems; event-driven architecture can trigger actions when events occur; workflow platforms can coordinate tasks; analytics can identify patterns; and AI can assist with classification, prediction or language-based interaction. These capabilities may support new services, not merely faster versions of old tasks.
Intelligent automation combines rules-based automation with data-driven techniques. A document workflow might extract fields, validate them against records, route exceptions to staff and retain an audit trail. The system should distinguish confidence levels and define when human review is required. Poor-quality input, unusual documents or model drift can cause errors. Organisations should monitor performance across user groups and provide a route to challenge or correct automated outcomes.
Automation can shift rather than eliminate work. Staff may spend less time entering data but more time resolving complex exceptions, monitoring systems and supporting customers. Workforce planning should consider reskilling and job redesign. Ethical assessment should examine surveillance, deskilling, accessibility, fairness, privacy and the distribution of productivity gains. The purpose of digital innovation should be better organisational and human outcomes.
25. Resilience, continuity and process risk
Operational resilience is the ability to continue or restore important services when disruptions occur. Process risk may arise from staff absence, equipment failure, cyber incidents, supplier disruption, inaccurate data, extreme weather, power loss, regulatory change or sudden demand. Risk assessment identifies critical activities, dependencies, vulnerabilities, likelihood and impact. It should consider how failures propagate across connected processes.
Business impact analysis estimates the consequences of disruption and identifies priorities for recovery. Recovery strategies may include alternative work locations, backup staff, manual procedures, redundant systems, alternative suppliers and data restoration. A workaround should be tested because an untested manual procedure may be unusable under pressure or may bypass important controls. Recovery plans should identify authority, communication channels and escalation thresholds.
Resilience is strengthened through monitoring, incident learning, exercises and continual improvement. Scenario exercises test whether people understand their roles and whether dependencies have been overlooked. After a disruption, a structured review should identify what happened, what worked, what failed and which corrective actions are necessary. Resilience does not mean preventing every failure; it means limiting harm and recovering in a controlled manner.
26. Process research and analytical methods
Process analysis uses qualitative and quantitative methods. Interviews and observation explain how work is performed and why exceptions occur. Document analysis identifies formal rules and responsibilities. Surveys gather perceptions across larger groups. Transaction logs and event data show actual sequences, timestamps and outcomes. Combining methods can improve understanding because system records may show what happened without explaining why it happened.
Process mining uses event logs to discover, compare and analyse process flows. A typical event record includes a case identifier, activity name and timestamp, with optional resource or context fields. Process discovery reconstructs observed pathways; conformance checking compares actual behaviour with a reference model; enhancement adds performance information to a model. Data quality is critical: missing events, inconsistent case identifiers and inaccurate timestamps can produce misleading results.
Analytical conclusions should distinguish correlation from causation. A process change followed by improved performance may have coincided with staffing changes, seasonal demand or a new policy. Evaluation designs can use comparison groups, interrupted time series or staged implementation where feasible. Analysts should document assumptions, limitations and data exclusions. Personal or sensitive data should be minimised and handled under appropriate ethical and legal requirements.
↓
DISCOVER FLOW → CHECK CONFORMANCE → ANALYSE PERFORMANCE
↓
IMPROVEMENT OPPORTUNITIES
27. Integrated applied case study: redesigning an online application process
A public training provider receives applications through paper forms, email and an online portal. Applicants often submit incomplete documents, staff manually re-enter details, payment confirmation is delayed and applicants repeatedly contact the office for updates. The first task is to define the end-to-end boundary: from initial application enquiry to a confirmed admission decision and communication. Stakeholders include applicants, admissions staff, finance, academic departments, IT support, managers and regulators.
As-is discovery combines interviews, observation, document review and system-log analysis. The process map identifies repeated data capture, unclear eligibility rules, multiple untracked hand-offs and a queue for manual payment reconciliation. Performance measures establish a baseline for completion time, incomplete applications, repeat contacts, error rates and applicant satisfaction. The team also investigates whether applicants with limited connectivity or disabilities experience different barriers.
The to-be design introduces a clear application journey, accessible forms, save-and-return capability, transparent document requirements, secure payment confirmation and a case-tracking workflow. Rules are documented and exceptional cases are routed to trained staff. Data are captured once and reused only for appropriate purposes. Controls verify identity and eligibility without collecting unnecessary information. The provider pilots the design with representative users, tests failure and recovery scenarios, trains staff and monitors results after launch. The case demonstrates how process thinking connects customer value, data, technology, control and organisational change.
28. Integrating business process management into organisational strategy
Business process management (BPM) is a continuing management discipline for identifying, modelling, analysing, designing, executing, monitoring and improving processes. It is not limited to a software platform or a one-off mapping exercise. BPM connects strategic objectives with operational work and creates a repeatable method for learning about performance. Its value depends on leadership, process ownership, data, employee participation and a culture of improvement.
A BPM lifecycle commonly begins with process identification and prioritisation, followed by discovery, analysis, redesign, implementation, monitoring and refinement. The stages are iterative. Monitoring may reveal a new constraint; a regulatory change may require redesign; customer feedback may expose an inaccessible step. Organisations should retain traceability between objectives, process models, requirements, implementation decisions and performance results.
An effective BPM capability balances standardisation with local learning. Shared methods and definitions allow comparison, while local teams contribute context and identify practical improvements. Process maturity grows when the organisation moves from undocumented and reactive work towards defined ownership, reliable measurement, controlled change and evidence-based improvement. The ultimate test is not the number of maps produced but whether the organisation consistently delivers better outcomes.
Structured university examination questions and model answers
For high-quality answers, define the concept, explain its practical significance, use a process example and evaluate limitations or implementation risks.
1. Define a business process.
Model answer: A coordinated set of activities that transforms inputs into outputs to achieve a defined organisational outcome, with triggers, participants, rules, information and measures.
2. Distinguish core, support and management processes.
Model answer: Core processes deliver customer value; support processes provide enabling capabilities; management processes set direction, allocate resources and monitor performance.
3. What is systems thinking?
Model answer: An approach that examines interacting elements, relationships, feedback, delays and environmental influences rather than treating components in isolation.
4. Explain local optimisation.
Model answer: Improving one unit's performance in a way that worsens the end-to-end system, such as shifting work or delay to another department.
5. What is a process boundary?
Model answer: The defined start and end of the process being analysed, including its trigger and completion condition.
6. Distinguish an activity from a task.
Model answer: An activity is a meaningful unit of process work; a task is a more specific action that contributes to an activity.
7. What is a swimlane diagram used for?
Model answer: It maps process steps across roles, departments or systems to show responsibility, hand-offs and coordination.
8. Name four common BPMN elements.
Model answer: Events, activities, gateways, sequence flows, message flows, pools and lanes are common BPMN elements.
9. Why is as-is analysis necessary?
Model answer: It documents actual work, including exceptions and workarounds, so redesign is based on evidence rather than assumptions.
10. What is a to-be process?
Model answer: A proposed future-state process designed to meet objectives and address problems identified in current operations.
11. Differentiate efficiency and effectiveness.
Model answer: Efficiency relates outputs to resources used; effectiveness concerns whether intended outcomes are achieved.
12. Define cycle time and processing time.
Model answer: Cycle time is elapsed time from defined start to finish; processing time is time actively spent performing work.
13. State Little's Law.
Model answer: Under stable conditions, average work in progress L equals average throughput rate λ multiplied by average time in the system W: L = λW.
14. What is a bottleneck?
Model answer: A constrained activity or resource that limits the throughput of the wider process.
15. Explain activity-based costing.
Model answer: It assigns costs to activities using cost drivers that reflect the resources consumed by those activities.
16. Differentiate preventive and detective controls.
Model answer: Preventive controls seek to stop errors or misuse; detective controls identify events or failures after they occur.
17. What is segregation of duties?
Model answer: Separating incompatible responsibilities so that one person cannot complete and conceal an inappropriate transaction alone.
18. What is a business rule?
Model answer: A documented condition or constraint that governs a decision or action within an organisational process.
19. Why is exception handling important?
Model answer: It provides safe, accountable routes for cases that cannot follow the standard process and reveals recurring design problems.
20. What is a data dictionary?
Model answer: A reference defining data fields, meanings, formats, permitted values, ownership and quality rules.
21. Explain workflow management.
Model answer: The coordination and routing of tasks, information, deadlines and approvals according to defined rules.
22. Outline the DMAIC cycle.
Model answer: Define the problem, Measure baseline performance, Analyse causes, Improve the process and Control the gains.
23. How does process reengineering differ from continuous improvement?
Model answer: Reengineering fundamentally redesigns a process; continuous improvement makes incremental, evidence-based changes over time.
24. What is process ownership?
Model answer: Accountability for the end-to-end performance, design, controls and improvement of a process.
25. What is customer journey mapping?
Model answer: A representation of customer actions, touchpoints, needs and pain points across the stages of achieving a goal.
26. What is process mining?
Model answer: The analysis of event-log data to discover process flows, compare actual behaviour with models and examine performance.
27. Why should automation suitability be assessed before implementation?
Model answer: Automation may amplify poor processes, fail on exceptions, create new risks or shift work; suitability depends on stability, rules, data and human judgement.
28. Define business process management.
Model answer: A continuing discipline for identifying, modelling, analysing, designing, executing, monitoring and improving organisational processes.
29. Identify four dimensions for prioritising process improvement.
Model answer: Strategic alignment, customer impact, risk, cost, feasibility, expected benefits, volume and readiness for change.
30. Why is post-implementation monitoring essential?
Model answer: It verifies adoption and benefits, detects workarounds and unintended consequences, and provides evidence for further improvement.
Chapter synthesis and revision guide
Business processes connect activities, people, data, rules and technology to produce outcomes. Systems thinking highlights interdependence, feedback, delays and unintended consequences. Analysts define process boundaries, identify customers and stakeholders, discover actual work and model both current and proposed states. Process maps and BPMN make sequences, decisions, responsibilities and hand-offs visible.
Performance analysis should balance effectiveness, efficiency, quality, time, cost, risk and customer experience. Capacity, queues and bottlenecks explain delays; cost analysis identifies resource consumption; controls manage error and compliance risks. Workflow and automation can improve coordination when processes and data are sufficiently stable, while Lean, Six Sigma and process reengineering provide different approaches to improvement.
Revision sequence: process foundations → systems thinking → process hierarchy → stakeholders and value → modelling → as-is discovery → to-be design → measures and bottlenecks → costs and controls → rules and data → workflow and automation → Lean and Six Sigma → reengineering → ownership and culture → integration → customer journeys → governance and change → resilience → research and process mining → BPM strategy.
Official Education References
Use these official organisations for curriculum guidance, examinations and further learning information.