When faced with a problem, people tend to collect into three mindsets. The first is not to do anything, lest we make the problem worse. These people tend to look around wildly for others to help rather than do anything. The second mindset is to take note of the problem characteristics and do some research before calling a vendor support line to verify their assumptions and planned approach. This is effective, but certainly not quick. The third mindset takes all the angles of the problem into account and gauges the potential impact of their first troubleshooting step, and then generally goes about fixing the problem. Well, most times -- sometimes they make things worse, but they also tend to leave themselves a path back to where they started when the situation goes even more pear-shaped.
The point is that they're not afraid to touch something that's broken without throwing the responsibility of that action on someone else. They're also generally consultants or have a background in consulting, where they were routinely called in to address problems that others couldn't -- or wouldn't -- solve. There's plenty of money to be made simply standing next to timid IT admins and soothing their fears while they stop and restart services on a Windows server.
All of these mindsets exist in just about every IT organization, and the intent isn't to disparage those with a more conservative outlook or to demonize the more flippant attitudes about critical IT systems. It's to find some sort of balance within the organization. There are times that being cautious is exactly the right move, and there are times that being somewhat reckless is what's needed.
The individuals who combine all those traits in the same brain are the black belts of IT. If you can understand enough about computers and computing infrastructure to be able to see several steps ahead while working on a difficult problem you've never faced before, and you know when to pull out the machete and start hacking -- and when to lock down the system and call a vendor (especially when there's downtime and time pressure involved) -- you're not just an admin.
You're even better than a technologist. You're an IT ninja.