2 ms·
One limitation of this is when you do “no impact” work in year 1 and 2 that’s high value impact work in year 3. Sure, if everything is low hanging fruit go for
by vlovich123 4y ago
One limitation of this is when you do “no impact” work in year 1 and 2 that’s high value impact work in year 3. Sure, if everything is low hanging fruit go for it. But sometimes it can take longer to build something that has 10x impact. eg teams A, B, and C hit a wall because all their time is spent fighting fires because they didn’t invest in getting ahead of tech debt / product growth. Of course, it’s hard to make the case that that’s the case and you can be very wrong in which case you waste a lot of time. But making sure that you are managing smoldering fires and preventing them from becoming infernos is high impact “invisible” work - did you prevent the inferno or was it unlikely to ever catch in the first place”. The usual approach is to let things start tipping and hope you have enough lead time between “this is starting to become a problem” and “product growth has to cease and we have to start shedding customers”