Key insight
Problem management should be more than fixing incident root causes. Instead, use the process to identify and capture opportunities for business improvement.
The situation
O-I had too many open problems, many of which aged significantly without consistent review or resolution. This complicated its ability to track and prioritize solutions to key business issues.
The challenge
Teams didn’t always prioritize problem resolution, which led them to accept workarounds. Moreover, leadership had no visibility into existing problems, and there was no consistent process to identify, track, prioritize, and resolve known problems.
1. Change the problem definition to capture improvement opportunities
O-I changed how it defines problem management to capture continuous improvement opportunities. The new definition provides a yardstick—sustained negative impact—to guide prioritization.
2. Focus the problem manager’s role on building culture
O-I holds the full-time problem manager responsible for building a culture of effective problem management across the organization and not for problem resolution.
3a. Configure ServiceNow to build transparency
O-I used the ServiceNow email notification feature as a status report for problems and added all relevant stakeholders (including the CIO) in the watch list to ensure alignment and transparency.
3b. Configure ServiceNow to promote team coordination
O-I configured an additional fifth level, available out of the box, to track and manage all problems. Along with providing a prioritization scale, the levels influenced teams’ behavior and informed an approach to resolution.
The results
O-I has created an approach so problems are not seen as distractions to actual work but are prioritized to realize business outcomes faster.
Adam Jackson
IT Problem Manager, O-I