3 ms·
How do you handle input that does need to be dismissed? I've seen entire teams stall out and become stuck in perpetual design loops due to 1-2 members construc
by aeternum 6y ago
How do you handle input that does need to be dismissed?
I've seen entire teams stall out and become stuck in perpetual design loops due to 1-2 members constructing endless 'what-if' scenarios. Engineering involves tradeoffs, there is rarely a single perfect solution.
There are also times like when attempting to find product-market fit when pointing out all the possible problems is close to useless. There are so many unknowns that the most important thing is often to get your product out there and start validating your assumptions and collecting data.
- flukus 6y ago> How do you handle input that does need to be dismissed? Hierarchy. You need someone to make the calls and the team to follow them, even if it's going to be wrong. That should be enough to break any perpetual design loop and move forward. Ultimately this hierarchy will exist anyway, the person paying you gets to decide what you're going to do or delegate that decision to someone else. Soliciting feedback along they way is important, but ultimately you need some decision makers. > There are also times like when attempting to find product-market fit when pointing out all the possible problems is close to useless This is building solution and then finding the problem which can be entirely avoided.