|
|
|
|
|
|
by dkarl
1839 days ago
|
|
|
This went in the opposite direction to what I expected, but I think I agree with it. I expected it to be about getting feedback early and often from real users, but it was about trusting your own feelings about a project. Both are valid approaches and better than fretting about the imagined reactions of people you aren't getting direct feedback from. |
|
|
was also when I started disagreeing. Sure, your gut-feeling is a good guidence. Asking yourself "do i need this polished" or "would I stop using the software if X is removed" is great advice.
I disagree because I think better advice is to make it slightly more scientific: "Most people would jump ship to a competitor if I remove X" is easily proven (just remove it), but also researchable: remove it for a cohort. Ask 10 random customers. Check your event-log or database if X is actually used currently.