4 ms·
I’ve seen this crash and burn too often. If you have someone build something, and then explain it, you don’t find out until after if they are capable of explain
by hinkley 6y ago
I’ve seen this crash and burn too often. If you have someone build something, and then explain it, you don’t find out until after if they are capable of explaining it. Just like a product MVP, you have to explain it as you go along.
Without it, you start out with a multiplier but end with a divisor.
- sgtnoodle 6y agoI think that's why it's very important to get buy-in and solicit feedback from coworkers even if you're the domain expert. Also, regression test coverage from the beginning is very important if you ever expect anyone else or even your future self to have a shot at safely modifying mission critical pieces of code.
- hinkley 6y agoYou have to get people invested in the solution. Some people call that buy-in, others use that term a little more tepidly.
- NotPavlovsDog 6y agoIt could be described as about the bus factor, couldn't it? If an organization has a product, and that product is not retired, it should be sustainable by a team. Lone points of breakage such as a single visionary or the mythic 10x-er are not optimal for the product if the unit taking care of the product is a team or several teams.