Iterate More, Plan Less
I'm always on the prowl for useful insights.
Alik sent me a link to Dustin Andrew's post,
Learn to Get Traction in Your Team. I like the collection of tips, and I found myself using the phrase, iterate more, plan less a few times. When I joined Microsoft, one of my rules was "avoid
analysis paralysis." I avoid analysis paralysis by taking action, producing results, and changing the approach as I learn. I've learned to improve by versioning perfection over time. I find it's easier to settle for "good enough' for now, if there's a chance to improve downstream (i.e. perfection as a journey vs. destination)
