Aspiro — sheet 02 · process details
The loop a team actually runs.
None of these steps are new. The point is that they stay connected, week after week.
Capture
Signals from interviews, support threads, and meetings land in one repository and get processed, not hoarded. Triage keeps the inbox honest: every signal is either attached to the problem it belongs to or consciously let go.
Structure
Insights feed an opportunity tree that maps the problem space. Every opportunity has an address, a parent outcome, and the evidence that put it there.
Decide
An opportunity collects candidate solutions, and the next thing to build gets picked with the evidence attached. Disagreement gets settled by walking the chain, not by whoever spoke last.
Build
Every solution is a plain markdown document. A coding agent connects over a single link and reads the same document the team does: problem, evidence, success metric. It writes what it learned back when the work ships. Whoever builds, human or agent, starts from the why.
Measure
Metrics are wired to your own database, not typed into a slide. After the release, the question is not whether the work is done. It is whether the number moved. The loop closes where it started: at the outcome.
Run the rhythm
Meetings, check-ins, and a what's-up-today view keep the loop honest week after week. The cadence is light; the point is that the chain gets walked regularly, not admired occasionally.
Issue status: open to the public
Run the loop on your own product.
Free for you, paid for your team. Your evidence, your tree, your metrics. No sample-data theater.