Outcomes
Close the loop — record what you decided and whether it actually worked.
An outcome is the record of a decision and its result. When you accept a ranked problem, you note what you’ll do, which metric you expect to move, and the target. Later, you record what actually happened.
The lifecycle
Decide
Accept a problem, state the action.
Measure
Set the metric, baseline, target, date.
Result
Log the actual value — hit or miss.
The hit rate
Across all your measured outcomes, Synloom tracks a hit rate — how often your decisions moved the metric you intended. It’s an honest scorecard for your prioritization, shown in the status bar.
Why outcomes are the moat
This is the part that compounds. When an outcome hits, the evidence behind it is reinforced; when it misses, that evidence is penalized. Future synthesis runs weigh evidence by its track record — so the more you use Synloom, the better it gets at ranking the right problems for your product specifically.
How three months of outcomes sharpened the next roadmap
Marco, PM on a B2B SaaS product
The situation. Over a quarter, Marco accepts five problems and records an outcome for each — the metric he expected to move, and later the actual result. Two hit their targets, three missed.
What they do
- 1The two wins were both sourced from enterprise interviews — that evidence gets reinforced and now decays slower.
- 2Two of the misses came from a noisy public feedback board — that evidence gets penalized and decays faster.
- 3Next quarter, he imports fresh feedback and re-runs synthesis.
- 4Synthesis now weighs enterprise-interview evidence more heavily and the noisy board less — automatically, because of the recorded track record.
The result. His new top-ranked problems lean toward the evidence that has actually predicted wins for his product. He didn’t tune any weights by hand — the outcomes did it for him.
Lesson: the boring step is the competitive one
- What it is
- Recording an outcome takes a minute: what you did, the metric, and later the real result. It feels like admin.
- Why it matters
- It’s the only step that makes the system learn. Skip it and Synloom stays a smart-but-static tool. Do it consistently and it becomes calibrated to your product specifically — an advantage no competitor gets from your data.
Treat “record the result” as non-optional. It’s the difference between a tool you use and a tool that compounds.
No other step matters as much long-term. Recording outcomes is what makes the system learn.