Ignoring a message with no clear call to action

The situation

They were dealing with a message that discussed bugs and a deep design principle, but did not clearly ask for anything to be done. The message talked about problems with guided tours and a desire to make all system features tunable. They were unsure how to proceed with the message. The message was part of a larger conversation about bugs and design principles. They had to decide what to do with the message.

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

They chose to keep the message as context because it discussed bugs and a design principle that was already being considered. They did not want to start duplicate work, so they decided to add the message to the existing decision. This way, they could consider the message as part of the larger conversation without taking unnecessary action. The message was added as evidence to the existing decision, which covered the same topics.

The first step

Add the message as evidence to the existing decision

How they would know it worked

The existing decision has the message appended to its evidence

How it turned out

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