When Everything is Important But Nothing is Getting Done

Here is a simple process for shipping software projects that works. First, decompose the project into a stream1 of headlines. Then pick an aggressive date to ship the first headline and work like hell to meet that date. Have everyone work only on one headline at a time– the upcoming one. Ignore everything else. Don’t work on anything that doesn’t h... See more

Not sure if anything changed my approach to work and engineering in the past five years more than this passage from @Lethain, written in the context of staff engineering but much more broadly applicable.

Organizations are often spread too thinly across too many priorities, and too many of them are ill defined. Things tend to get added to the pile over time, and before we know it, we have huge backlogs. We're spread a mile wide and an inch deep. The problems with pace and tempo are, of course, related to having too much going on at the same time. It... See more