Managing Operational Risk During Business Process Changes
A business replaces its scheduling system to make work easier. The new platform performs as expected during demonstrations, employees attend training, and the launch proceeds on time. On the first busy morning, however, the team discovers that urgent requests do not reach the person authorized to assign them. The software works, but an important part of the business process does not. This hypothetical example illustrates a useful question for any organization introducing change: how will the proposed arrangement work under actual operating conditions? Whether a business is changing software, reorganizing responsibilities, relocating a department, or outsourcing a service, a focused operational risk review can help management identify gaps before they affect customers and employees. Describe the Change in Business Terms Begin with a clear description of what will change and why. Explain which activities will move, which responsibilities will be reassigned, and which outcomes should improve. A statement such as ‘introduce a new system’ is less useful than explaining how customer requests will be received, approved, assigned, and completed. Define the boundaries of the project. Identify what is included in the launch and what will remain for a later phase. This helps teams recognize dependencies that could otherwise fall between separate projects. Record assumptions requiring confirmation, including vendor support, employee availability, and access to necessary information. Map the Current Process Before Replacing It Ask employees to explain how the activity currently works, including exceptions and informal steps. A written procedure may describe the intended workflow while overlooking the extra checks employees use to keep work moving. Understanding those checks helps management decide which should be preserved, redesigned, or discontinued. Follow a recent piece of work from beginning to end. Identify who supplied information, who checked it, who approved the next step, and how completion was recorded. Include any outside organization involved. Use the findings to compare the existing process with the proposed arrangement rather than assuming the project plan captures every important activity. Pay Attention to Handoffs Look closely at points where responsibility moves between people, departments, systems, or providers. Ask what the receiving party needs and how they know work is ready for them. Clarify who responds when information is incomplete or a request falls outside the normal workflow. For example, a hypothetical manufacturer might change how sales orders reach production. The assessment could examine who confirms product specifications, how revisions are communicated, and which version controls the work. A successful transfer requires more than sending a record; the receiving team needs enough reliable information to act. Bring the Right People Into the Review Include the people who perform the work, those who approve decisions, and those who support the process. Depending on the change, this may involve operations, finance, technology, human resources, facilities, and customer service. Ask each participant which part of the proposal needs further clarification. The International Organization for Standardization’s overview of ISO 31000 describes integrating risk management into organizational planning and decision-making. The discussion framework here applies that general idea to everyday process changes. It is a suggested management exercise rather than a claim of compliance with the standard. Identify What Could Go Wrong During Transition Examine the period between the old arrangement and the new one. Ask how unfinished work will be handled, how employees will identify the correct procedure, and whether customer commitments span the transition date. Specify which records remain authoritative during that period. Discuss realistic scenarios such as missing information, unavailable support, unexpected workload, or a delayed dependency. For each scenario, describe the business consequence and the time available to respond. Prioritize issues that could interrupt essential work or create commitments the organization cannot reliably fulfill. Test Complete Workflows and Unusual Cases Choose test cases that represent actual work. Include a normal transaction, an urgent request, a correction, and an incomplete submission where relevant. Follow each case through approval, execution, reporting, and closure. Confirm that the people responsible for later steps can use the output from earlier ones. Agree on what a successful result looks like before testing begins. Record the results and unresolved findings. A demonstration that one feature works should not be treated as evidence that an entire workflow is ready. Use qualified specialists to design and evaluate tests involving technical, safety, or other specialized matters. Check Workload and Training Together Determine whether employees have time to learn the new process while maintaining existing responsibilities. Training plans should reflect the tasks each person will perform, including how to recognize exceptions and obtain help. Identify supervisors or support contacts who will be available during the initial operating period. Where practical, ask employees to demonstrate a representative task using the approved instructions. Note unclear steps, missing permissions, and questions requiring follow-up. Update the instructions before wider use. Avoid assuming that attendance at a presentation establishes readiness to perform unfamiliar work independently. Prepare a Practical Response if Launch Problems Occur Before launch, discuss what management will do if the new arrangement cannot support essential activities. Depending on the situation, options might include a limited rollout, a temporary approved procedure, or postponement. Evaluate the feasibility and consequences of each option rather than listing an alternative that has never been checked. Returning to the previous process may also require preparation. Ask whether new transactions can be reconciled, whether records would remain consistent, and who has authority to make the decision. Do not assume reversal is simple. Have the relevant professionals assess technical and operational requirements before relying on that option. Make Launch Approval a Defined Decision Create a short readiness record identifying the conditions management expects to be met. These might include completed workflow tests, available support, confirmed staffing, approved instructions, and resolved critical findings. Name the people responsible for confirming each condition. Separate completed work from accepted limitations. If management decides to proceed with an unresolved issue, document the reason, interim arrangement, responsible person, and review date. That record helps the organization distinguish a deliberate decision from a gap that went unnoticed. Coordinate Changes Across Locations Organizations operating across regions or countries
Managing Operational Risk During Business Process Changes Read More »