Before the artifact
A step before the obvious decision
This is a continuation of the earlier Spiral opportunity piece. That method looked outward: it combined existing writing, maps, case studies, and other artifacts to see whether a useful direction was already forming.
Sifting moves earlier. It asks: What small signals appear before a decision has a shape?
Most of us notice more than we use. A phrase repeats in meetings. A workaround becomes normal. A handoff gets heavier. A metric moves without an agreed explanation. These fragments often disappear because they are not ready to become roadmap items, proposals, or product decisions.
Give rough material enough structure to become useful without forcing it to become polished too early.
Sifting supports the moment before judgment gets asked to perform. It does not replace judgment, prove that a market exists, or make every observation important.
Weak signals
They rarely arrive with a label
A weak signal might be a repeated stakeholder question, a UX concern that keeps returning, a tolerated process step nobody trusts, customer behavior that diverges from the expected journey, or a tool being used in a way it was never designed to be used.
On its own, each can be too small to act on. Several pointing in the same direction may expose an unframed decision, a broken handoff, a trust gap, or the need for a clearer path.
Business analysis asks
What is happening in the process?
Experience design asks
What is this doing to the person moving through it?
Product asks
What decision should this help us make next?
The questions work best together. The people noticing the signal, those doing the work, the decision owner, and those living with the change each hold part of the picture.
Triangulation
The value may be in the combination
One support ticket may be noise. One stakeholder concern may be preference. One metric shift may be timing. One confusing screen may need better copy. Combinations deserve a closer look.
You are not trying to make every observation important. You are testing which observations become meaningful beside each other, what alternative explanations remain, and whether the cluster recurs.
- SignalNotice the repeated fragment.
- PatternPlace it beside related evidence.
- DecisionName what needs to become clearer.
- ArtifactBuild the smallest useful support.
Visual before verbal
A diagram makes the gaps harder to hide
A paragraph can move quickly past uncertainty. A diagram tends to expose it. An unclear handoff appears as a break; a missing decision owner leaves an empty place; a looping workflow makes drag visible; a signal with no connection to value refuses to pretend that it has one.
The useful result may be a signal map, decision tree, friction map, stakeholder alignment view, or one-page canvas. Once the shape is visible, the words often become easier and shorter.
This is decision support before polished opinion: quieter questions about who decides, what information is scattered, which uncertainty matters, and what would help the next person understand faster.
Useful friction
Constraint gives the work an edge
An environment with no constraint can make thinking strangely soft. If anything is possible, almost nothing is prioritized. The question is not whether friction exists but whether it is useful.
Useful friction reveals
Where people hesitate, where the process becomes heavy, where trust is missing, or where an artifact could make the next decision easier.
Unhelpful friction consumes
Time and attention without changing the choice, protecting a goal, or reducing decision-relevant uncertainty.
When a signal returns around the same friction point, slow down long enough to test whether the resistance matters not to analyze forever. Set a learning budget and stop when new observations become redundant rather than materially changing the options.
What comes after the signal?
Choose the artifact to fit the decision
The first question is not “How do we write about this?” It is “What would make this easier for someone else to decide?”
- Checklist
- When the same judgment repeats.
- Map
- When the path, handoff, or ownership is unclear.
- Decision brief
- When assumptions, evidence, and trade-offs need one shared view.
- Calculator
- When cost, effort, timing, or the price of waiting needs sizing.
- Workshop
- When shared understanding is the bottleneck.
- Sharper question
- When the group is not ready for a larger artifact.
A format is not the starting point. The decision is. Record what the selected option protects, what it gives up, what remains uncertain, who can commit, and what evidence or event should reopen the choice.
Start with the signal that keeps bothering you. Follow it until it points to a decision. Then choose the smallest artifact that makes the options easier to compare.
Choose how far to go
Give the signal somewhere useful to go
Try the same ideas one signal at a time, carry the structure into a Decision Brief, or read the related decision questions. Each route stands on its own and none requires signup.
Email starts a fit conversation only if direct help would be useful; scope and fee are agreed before work begins.