Turn the answer into one next action

A thoughtful answer can still leave a project exactly where it was. You close the chat, return to the rest of the day, and later remember the conversation as useful without being able to name what changed.

The Act stage asks for less: turn the answer into one next action.

Find the smallest visible move

A next action should be something you can do, not a result you hope to achieve. “Improve our pricing” is a direction. “Use the new rate in the next proposal” is an action. You will be able to see whether it happened.

Use three checks:

• Is it under your control?
• Is the finish line visible?
• Does it preserve room for your judgment?

For the fictional design studio, the context supports keeping current rates for existing clients and testing the new rate with new clients. The immediate action is not to transform the whole pricing model. It is to use the new rate in the next proposal and review what happens.

Record the reason beside the action

An action without its reason becomes confusing later. Add one sentence: “We are changing new-client pricing while keeping two long-standing clients stable.” That sentence becomes useful context when the team reviews the decision or asks a new question.

This is how Act returns to Capture. The result, the exception, and any new constraint become the beginning of the next loop.

Convert advice with an action card

Copy this card beneath the answer before closing the chat:

# Action card

Decision I am making:
Chosen next action:
Owner:
Trigger or due condition:
Visible finish line:

Why this action:
Constraint it respects:
What I am not doing:

Evidence to capture afterward:
Review when:
Source note to update:

The card forces a separation between the assistant’s suggestion and your commitment. If you cannot name the owner or finish line, you probably still have an option rather than an action.

See three advice-to-action conversions

Advice	Still too vague	One visible next action
“Validate the new pricing.”	Improve pricing	Use the new rate in the next new-client proposal and record the response.
“Protect existing relationships.”	Be careful with clients	Keep the two long-standing clients on their current rates during the test.
“Avoid repeating the earlier mistake.”	Remember what happened	Add “Do not use a blanket increase” and its reason to the decision note.

Each action is small enough to observe. None pretends to guarantee the larger result.

Record what happened, not just completion

After the action, add one of three outcomes:

• Worked: keep the decision and capture the evidence.
• Did not work: record what happened and reopen the decision.
• Could not start: identify the missing constraint, owner, or prerequisite.

For the pricing test, “proposal sent” is completion, but the prospect’s response is new context. The next consultation should begin with that evidence rather than the original question.

Keep the assistant in the right role

An assistant can suggest options, expose tradeoffs, and help make an action concrete. It cannot own the consequence. Check the recommendation against the facts you know, choose the action yourself, and decide when more information is needed.

If you are still at the advice stage, start with a focused context handoff. If you want the wider rhythm, the four-stage loop shows how one action improves the next consultation.

Join the Starter Kit waitlist if you want one notification when the kit is ready.