3 ms·
The problem with your approach though is that there is no such thing as 'a user'. There are so many different cohorts of users. In your testing workflow it seem
by bosie 5y ago
The problem with your approach though is that there is no such thing as 'a user'. There are so many different cohorts of users. In your testing workflow it seems you are only using hardcore users for it. People obsessed with your software (internal or beta users) before pushing it out to the masses.
How do you avoid leaving the other cohorts behind?
- godelski 5y ago> How do you avoid leaving the other cohorts behind? Time, larger testing sizes, A/B testing in the main product, and not rushing things out.