“Nope, that’s not a problem.”

One of the things that separates a more senior person from a more junior person is statement, “nope, that’s not a problem.” At the very least, the statement may be more like, “that is a problem, but we’re not going to solve it now. Ship it!” I’ve been through this several times, on both sides of the seniority curve and now respect people who can wisely decide when not to care about a problem and go on with the work.

For example, let’s say you’ve done a fair amount of work on the deck for The Big Meeting, and at the 11th hour you found that something is slightly wrong: you’ve mis-categorized one of the 30 sub-categories in your market sizing. The worker bees are all upset that there’s an error and are having a call to see how to redo “everything.” A good manager can come into a situation like this and say, “yeah, it’d bee too much chaos to change it now. We’ll do it later. Just put a little foot-note down there if you think it’s that bad. Ship it!” The worker bees are somewhat flummoxed, or maybe relieved: but that’s the power of management, to decide to go ahead with it instead of having to make it perfect.

There is some amount of risk to allowing such “bugs” to go through the process, but sometimes — oftentimes! — the risk is minimal and worth taking.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.