Core Workflows
Close the loop in Impact Tracker
Impact Tracker is where predictions meet real outcomes so the system can learn what actually worked.
What this helps with: Help teams log, review, and learn from product outcomes properly.
What it is for
Impact Tracker is not just a note-taking surface. It is where the system compares predicted outcomes against real outcomes.
Pending records represent things that still need a real-world review.
Completed records should include actual outcomes and learnings.
System accuracy reflects how closely predictions matched reality.
Where records come from
Impact records can be created from grounded workflow steps, not just manual guesses.
They may start from strategic or feedback-driven hypotheses.
Manual records should still be contextual to the active project.
Metric values should be read carefully from real analysis blocks when available.
What to avoid
Accuracy only means something if the record is anchored to real outcomes.
Do not mark records complete without real outcome evidence.
Do not rely on placeholder predictions that are unrelated to the project.
Do not let invalid metric values silently become fake real results.