I know people preach Lean methodology (Build, Measure, Learn) but how many people actually implement it?
I’m finding out, not many.
Specifically startups don’t have great A/B testing or feature validation processes even though most agree that they should. It’s seen as a “nice to have” given the piles of priorities that seem to be never ending.
Do you agree?
————————————————————
p.s I’m also validating a related project I’m working on. If you’re interested, read on. If not, STOP HERE!
I’m building a tool that lets PMs deploy new features the same way FB, Twitter, and AirBnB do.
It will be extremely easy to toggle or split test new features from a dashboard. I’m talking about:
1. A/B Testing
2. Controlled Rollouts
3. Testing in production (forget expensive and inconsistent staging environments)
4. Beta releases
5. Location targeting
6. Feature kill switch (in the case of bugs)
and more...
I’d love to hear your thoughts. If you’re willing to have a chat I’d love to talk to you too!
I’ve built this solution for several companies already and know firsthand how valuable it can be in your feature release process. Not only can you push new feature with less risk, but you can test their effectiveness as well. All without adding complexity to the actual implementation.
I believe it’s something all devs teams should implement whether they use my tool or not. The problem is that most startups simply don’t have time to add this to their workflow. I want to solve this.
I’m finding out, not many.
Specifically startups don’t have great A/B testing or feature validation processes even though most agree that they should. It’s seen as a “nice to have” given the piles of priorities that seem to be never ending.
Do you agree?
————————————————————
p.s I’m also validating a related project I’m working on. If you’re interested, read on. If not, STOP HERE!
I’m building a tool that lets PMs deploy new features the same way FB, Twitter, and AirBnB do.
It will be extremely easy to toggle or split test new features from a dashboard. I’m talking about:
1. A/B Testing 2. Controlled Rollouts 3. Testing in production (forget expensive and inconsistent staging environments) 4. Beta releases 5. Location targeting 6. Feature kill switch (in the case of bugs) and more...
I’d love to hear your thoughts. If you’re willing to have a chat I’d love to talk to you too!
I’ve built this solution for several companies already and know firsthand how valuable it can be in your feature release process. Not only can you push new feature with less risk, but you can test their effectiveness as well. All without adding complexity to the actual implementation.
I believe it’s something all devs teams should implement whether they use my tool or not. The problem is that most startups simply don’t have time to add this to their workflow. I want to solve this.