Verifying a repair to avoid false success claims

The situation

A message was received that required action to be taken, with the goal of verifying a repair. The message explicitly asked for live repair verification and forbade a speed success claim while a fatal issue remained. This message was a result of a previous issue that needed to be resolved. The tools used to work on this issue were available, and a summary of the thinking process behind the solution was provided. The task at hand was to build on the work that had already been done and avoid duplicating work.

What they weighed

• Act on the message and verify the result

  Chosen

• Keep it as context when no action is called for

What they decided

Act on the message and verify the result

Why

The message explicitly asked for live repair verification and forbade a speed success claim while the fatal issue remained. This indicated that verification was necessary before claiming success. The person directing the verification wanted to ensure that the repair was properly done before making any claims. The goal was to verify the deployed revision, check the desktop and phone screen paint, asset budget, and route timing, and then record the outcome.

The first step

Use the completed desktop and phone route reports and screenshots to report the repaired live result

How they would know it worked

All routes paint without the sidebar error at both viewports, and the asset is within budget

How it turned out

Not known yet. The result is added here when it comes in.