Keeping track of hypotheses, experiments and goals in startups
What do you use to keep track and share information about your hypotheses, experiments, associated features etc. in your projects / startups?
I feel like it becomes very complicated over time to keep track of all the information your startup receive through those tests and customer interviews and to share this with co-founders and employees. How do you deal with this?
(
4 comments
| 8 points
| on HN
)
Though it doesn't cover everything, I find it helpful to review with team on Mondays to make sure everyone is on same page about week's priorities and any recent findings.
The trick I find is in sticking to it, whatever the system is.
I ended turning this problem into a side project (leanlab.io) which you could checkout ;). I also know that Javelin are doing something similar with experiments (experiments.javelin.com).