Feedback is great, but should never be relied upon without context in place. The context is what was going on surrounding that particular item. It’s the work that was going on at that point in time. It’s the goals that were trying to be achieved but might not have worked. Feedback is incredibly useful, but only if everything surrounding the feedback is understood.
Getting it right requires measuring twice and cutting once. It’s about making mistakes and going back to try again to be better. It’s about the bugs coming in and the updates going out. Not everyone wants to get it right because it means realizing you have work to do and that work never end. But many people do, and those are the people you want on your team.
After one release that goes well, you’re perfect. If your second and third ones go just as well, you’ll maintain that perfection. But eventually, the more you do, the greater you open yourself up to the chance that something will go wrong, that you won’t have the perfect release. That your code might blow up. That a bug might get missed. What factors outside of your control will cause you to slip? Because presumably, you…
Maybe make a plan (I do this from time to time). Writing it down helps (I heard and have tried). Committing to a schedule (yes this is definitely great). Get a support group (this never helped me too much). Break it into smaller tasks and when you’ve mastered one task, move on to the next (this helps greatly). Always keep challenging yourself with variations on what you are doing (prevents falling into a mold). But…
Good Leaders show up every day, keep things humming, and tell everyone they are doing a great job. Great leaders show up every day, they ensure the team is working on the right things at the right time and aren’t afraid to make a call to change the direction of the ship if it means the team can get better and stronger, they are always looking towards what is coming down the pipe, prepping it…