Deciding not to act on a complaint about a broken guide

The situation

Someone complained about a guided tour being broken due to a technical issue. The problem had turned off the guided overlay instead of fixing it, causing problems with the navigation flow. The person wondered if the guide was working. However, the issue was already being tracked and fixed by the team responsible. The guided tours were also thought to look great by everyone, which was a positive note. The complaint was received in a conversation thread, but it seemed that no new action was needed as the issue was already being addressed. The team was already on top of the problem, and the guide was proven to work in most cases. The complaint was more of a statement than a call for action, and the person's concerns were already being addressed.

What they weighed

• Act on the message and verify the result

• Keep it as context when no action is called for

  Chosen

What they decided

Keep it as context when no action is called for

Why

The team responsible was already fixing the issue, and the guide was proven to work in most cases. The complaint was more of a statement than a call for action, and the person's concerns were already being addressed. The positive feedback about the guided tours also suggested that the overall system was functioning well. As a result, no further action was needed, and the message could simply be kept as context. This approach avoided duplicating effort and allowed the team to focus on other tasks.

The first step

No further action needed for this message, and the team can move on to other tasks.

How they would know it worked

No action is taken, and the issue is resolved by the team responsible.

How it turned out

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