Decision Matrix

Make the trade-off visible before the project gets expensive.

Answer seven practical questions, including whether the current process reliably meets the need. The transparent rule explains when to retain, stop, wait, or change the path. Your answers and result stay in this browser; the site records tool-use events, not your answers.

How often does this occur?How much does it affect the business?How stable is the workflow?How much human judgment does it need?How much ongoing maintenance can you absorb?How important is control of the capability or data?How well does the current process meet the need?

Use observed performance, not just how familiar the process feels.

This is a transparent starting rule, not management advice. Legal, security, financial, and team constraints remain yours to investigate.

Decision state

—

Choose the constraints.

The matrix will identify a starting path and show the assumptions driving it.

Decision memo

Waiting for a result.

After the result

Turn the output into one reversible next move.

A good result does not make the choice permanent. It tells you what to test: the cost, a vendor boundary, an operator handoff, the control requirement, or whether the task should exist at all.

Read the playbooks as they are published