How we measure whether a solution worked
We measure against the problem, not the delivery. Baseline, outcome metrics and periodic reviews to know whether a project met its goal.
- Published
- November 13, 2026
- Reading time
- 2 minutes
- Written by
- The Roshal Lab team

Measure against the problem, not the delivery
Delivering on time is necessary, but it isn't enough. A project worked if the problem that started it actually got smaller. That's why the metric is defined in the first step, while we're still working to understand the problem.
No baseline, no measurement
Before changing anything, we record how things stand today. If we don't know how long a process takes or how many errors it has now, there's no way to prove the improvement later.
Outcome metrics, not activity metrics
The number of screens designed or automations built is an activity metric: it tells you how much was done, not whether it helped. We prefer metrics that show the effect on the business. Depending on the problem, they might be:
- How long a process takes from start to finish.
- Hours of manual work per week.
- Errors or complaints per hundred transactions.
- Conversion at a key step in the customer journey.
- Repeat questions reaching your support team.
Follow-up and maintenance
- A simple dashboard with the main metric, visible to your team.
- Periodic reviews to compare against the baseline and catch drift.
- Adjustments when reality doesn't match what we expected.
- A maintenance plan so the solution keeps working as the business changes.

