It’s fashionable in the tech world to say that you’re cool with failing. But failure leaves a bad taste in your mouth. The only way to get it out is to prove you’ve learned from your mistake. In that spirit, I recently kicked off a discussion amongst the engineering teams at Atlassian about setting deadlines for the sake of deadlines and, worse, prioritizing that deadline above customer value or the overall health of your product (and team, for that matter).
This is it! This is the project you’ve been waiting for. The one that’s going to define your career and challenge you and totally transform “the way things are done around here.” The project your team will point to five years from now as the inflection point that ushered in a new era of awesome. If, that is, you can get the project approved, prioritized, and properly resourced.
