Sometimes the fastest way forward is to say No to doing something. The trick is knowing when to say no.
Test driven development, Extreme Programming, and many other approaches encourage us to start typing in code, either as a test or as functionality. That’s good advice, but you should never start coding blindly.
People want estimates. Or they say they do. What they really want is predictability and value. How can you provide both when you just don’t know enough?
There’s a lot to learn from aviation. Particularly around incident management
Knowing when you’re done is just as important as knowning what to do.
Why does focusing on finishing rather than starting get more done?
What’s an elevator pitch, and why is it important?
Why is planning so hard?