Dealing with the Click-Next-Admin

I had a good deal of yard work to do this weekend; I see yard work in a similar way that a click-next-admin sees Windows PowerShell. I want no part in it. So I wrote a quick bit on how we can deal with the click-next-admin.

Jeffrey Snover recently gave a TechDays Online session where he candidly asked us to "make today the last day you hire a click next admin."

Reward the right people

This is a fantastic goal, but how do we get there? There's no set answer, but I listed out some of the major challenges I see.

Would love to hear your feedback and ideas - flip through the post and stop back here to discuss!

If you'd like to have some fun, share your click-next-admin stories on twitter with the #ClickNextAdmin tag.

Too Busy

Aside: Thank you for the invite to contribute here, it's an honor.

Cheers!

About the Author

Warren Frame

Systems Engineer with a penchant for PowerShell, science, cooking, information security, family, cookies, and the Oxford comma.

2 Comments

  1. The simple answer is that changes in the environment will cause click-next-admins to go extinct. If the management of those admins does not support the transition to automation engineers, then that company will also go extinct.

    All businesses today are dependent on their IT Operations. The ability to adapt quickly is now the standard for business survival. The Wizard will probably continue to exist, but it will always be a bottleneck to implementing change safely and rapidly.

  2. I'd like to add a perhaps softer topic to the discussion and that's the resporisity style of the individual. There is a great book called Give and Take by Adam Grant, which describes three types of people. Givers, Matchers and takers. I'll spare the details and explain why you should also scan candidates for being a Giver. Many of the advocates for PowerShell are givers, they write posts as you've done explaining how to help onboard others and teach them the ways of PowerShell. They go to extreme lengths to teach others and to share knowledge, often expecting nothing in return. The key part here is knowledge sharing, we all know we can't learn everything and now with PowerShell there is more than one way to accomplish any one tasks. PowerShell is also a programming language not a system. You will need people experienced at some level with the system and PowerShell to automate a task, who better to have on the team than someone willing to share that knowledge with the whole team. This also falls into a DevOps term CAMS (Culture Automation Measurement and Sharing). Hiring Givers will certainly be a catalyst for sharing.