Progress over Perfection
How to be Useful Rather than Perfect
I remember when I first started working at USGS and feeling that I had so much to learn. And then my first experiences as a project manager, where I put together color-coded spreadsheets to document everything. It thought I had to know it all—all the administrative stuff and all the science.
Then there were the presentations at conferences and the nerves about the question-and-answer period at the end and thinking I had to know all the answers.
I studied. I practiced. I wrote prep questions.
But I soon learned that knowing everything there is to know was an impossible task. So, I stopped trying to look like I had all the answers and started being the person who could find them.
I still documented almost everything, but I started to treat unanswered questions as data points rather than failures. I started saying “I don’t know, but I will find out.”
It’s easy to think you have to chase perfection when you first start a job—but perfection doesn’t really exist in the messy reality of project management (or life, for that matter). But sometime around midcareer the rules change. Your responsibilities increase. You can’t keep up.
Perfection is internal—it’s about your ego and how the work reflects on you. Usefulness is external—it’s about the team and what they need to actually cross the finish line.
Perfection is a shield; usefulness is a tool.
Useful isn’t a quality compromise, and in fact, finding the useful path can be harder. It requires you to look at the messy, moving parts of your project and decide which single process is causing the most friction. It means providing a 70% solution today so you or your team can move, rather than a 100% solution next week that leads to a bottleneck.
Shifting from maintaining every little thing to identifying where the real leverage sits is the key. Gain enough clarity to see the whole map, so you can stop dodging the same potholes and start repaving the road for a smooth ride to your destination.
If you feel like you’re currently stuck in “A++ workerbee” mode, I asked industry veteran John Hambacher for his take. He has put together a practical guide on how to step back and re-assess your scope.
It isn’t an abstract framework; it’s a three-step process to help you find that “useful” priority, act on it, then build the habits that actually move the needle.
When you prioritize being useful, you build trust. And trust is a more valuable currency than a flawless color-coded spreadsheet.


"So, I stopped trying to look like I had all the answers and started being the person who could find them." Very nice! Great article
I love how you write "It means providing a 70% solution today so you or your team can move, rather than a 100% solution next week that leads to a bottleneck." Recognizing that a partial win is also valuable progress, too, is everything.