The work
The moments we design
The measures we agree on before launch, so the team knows what to learn from.
- The main measure
- Early signals
- Activation moments
- Adoption and retention
- Targets that make sense
- What to track from day 1
- Feedback to collect
- What would change the plan
- Measures per release
- Business goals
- A shared definition of done
- Learning after launch
The problem
Sounds familiar?
If 2 or more of these ring true, define success before you launch.
{{ countLabel }}
Proof
“Her ability to manage time effectively and prioritize tasks has been instrumental in keeping our projects on track.”
- Upwork Job Success
- 100%
- Regular clients
- 10+
- Recognized by
- Dribbble Select
Ways to start
2 ways to start
Set measures for a launch, or reset the ones you have.
-
# Before launch
Define your measures
Agree on what success looks like before the first release.
- Main measure
- Early signals
- Targets and thresholds
- What to track from day 1
-
# After launch
Reset your measures
Replace vanity numbers with measures that guide decisions.
- Review of current measures
- New main measure
- Early signals
- Plan for learning
01Do you set up the analytics?
No. We define what to measure. Analytics setup and statistical validation are scoped separately.
02How long does a project take?
It depends on the scope. Once we’ve seen the full picture, we’ll share a rough timeline.
03How many measures should we have?
One main measure and a few early signals. More than that usually means nobody watches any of them.
04Can you help us read the results later?
Yes. We can review the data after launch and turn it into design changes.
05What do we get at the end?
A short document with the main measure, early signals, targets and what would change the plan.