INFO6007 Chap.13 Service Functions, Processes and Improvement
Service Functions, Processes and Improvement
This chapter distinguishes service records and practices by purpose. Incident management restores service, problem management investigates causes, change enablement controls modifications, and monitoring provides evidence about conditions. Continual improvement begins with an outcome and baseline, acts on a measurable gap and verifies the result rather than equating higher activity counts with better service value.
A workaround can restore an incident while leaving the underlying problem open. A known error records an analysed cause and workaround, while a change introduces the controlled correction. Events and requests also need correct classification so ownership and measures remain meaningful. Priority combines impact and urgency rather than technical severity alone.
Post incident review should improve systems and decisions without retrospective blame. Improvement items need value, risk, feasibility, owner and review evidence, and unsuccessful actions still create learning when assumptions and context are preserved.
What this chapter covers
- 01
Service desk coordination
- 02
Incident restoration
- 03
Problem cause analysis
- 04
Change enablement
- 05
Monitoring and events
- 06
Known errors and workarounds
- 07
Continual improvement measures
- 08
Map demand, value-chain activities, practices, information and feedback as an end-to-end value stream for the scenario
- 09
Separate incident restoration, problem-cause management and predefined service requests while preserving useful relationships among records
- 10
Distinguish change enablement, deployment and release by their different risk-control, movement and availability purposes
- 11
Pair speed or volume metrics with outcome, recurrence, user impact and experience measures to reduce gaming
- 12
Run continual improvement from current evidence to a measurable target, owned action, evaluation and revised learning
- 13
Use a blameless review to improve the system while retaining clear ownership for agreed follow-up actions
Worked example · free
Control recurring authentication failure
- +1Record and restore the incident.
- +1Communicate service status.
- +1Open a problem for the recurring cause.
- +1Authorise automated validation as a change.
- +1Measure recurrence and pre expiry success.
Key terms
- Incident
- An unplanned interruption or reduction in service quality requiring restoration.
- Problem
- A cause or potential cause of incidents requiring investigation and control.
- Workaround
- A temporary method that reduces impact without necessarily removing the underlying cause.
Service Functions, Processes and Improvement FAQ
What is the difference between incident and problem?
Incident management restores service for a current interruption. Problem management investigates and controls underlying causes so similar incidents become less likely to recur or less damaging.
When does a workaround close the work?
A workaround may resolve the immediate incident, but the problem remains open where recurrence or material exposure justifies cause analysis and a durable corrective system change.
How should continual improvement be measured?
Start with an outcome and baseline, identify a gap, implement action and verify the result. Ticket counts alone may reflect reporting changes rather than better service performance.
Exam move
Classify examples before recommending action. An incident is an interruption or reduction in service quality requiring restoration. A problem is a cause or potential cause that needs analysis and control. A change is a controlled addition, modification or removal. Continual improvement begins with a measured gap and verifies whether action improves the outcome.
Build paired scenarios where a workaround resolves an incident but leaves the problem open. Add a known error only after the cause and workaround are understood. Include service requests and monitoring events so not every record is mislabelled as an incident.
Practise the operational sequence: restore service, communicate status, preserve diagnostic evidence, investigate recurrence, authorise corrective change and measure whether exposure falls. Keep purposes and ownership distinct even when one team performs several practices. For continual improvement, define the desired outcome, current baseline, target, action, owner and review point.
Prioritise by value, risk, feasibility and strategic need. Do not assume a higher ticket closure count proves improvement; test restoration time, recurrence, user outcome and reporting behaviour. Use monitoring to connect technical conditions with user experience and business effect. On the notes sheet, keep concise classification triggers and the reminder that workaround is not root-cause removal.
In case answers, say what is restored now, what remains to investigate, which modification requires change authority and what measure verifies improvement. This structure prevents the common error of solving the immediate interruption while leaving the recurring service weakness unmanaged.
Working through Service Functions, Processes and Improvement in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 Service Functions, Processes and Improvement question and get a clear, step-by-step explanation grounded in how INFO6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.