Turning a message into a repeatable workflow process

The situation

A message was received asking for specific changes to be made to a product, including turning a task into a repeatable workflow process. The task involved finding a person's goal from various sources such as email, video transcripts, and voice or face recordings. The message was important as it had been discussed before in other meetings and was supposed to allow for the creation of a repeatable process for anything, not just a one-off instance. The goal was to make this process valuable for any domain, including examples like tennis.

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 asked for concrete product changes and each ask was matched to a commit or lane that would deliver it. The task of finding a person's goal was important and needed to be turned into a repeatable workflow process. This would involve checking each ask against a commit or a live readback, or the running lane brief that named it.

The first step

Open a lane to turn the task into a repeatable workflow process

How they would know it worked

Each ask being live on the app with its commit or delivered by the named lane with a live picture

How it turned out

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