Mike Morrison’s Post

Complex problems are a part of every job. It's up to you how much of that complex problem you need to fix and how much you bring in expert help from others. If you have a team or can hire outside contractors, then you get to decide how much load you share with them and how much you keep on your own plate. Just remember, people have limited amounts of capacity for complex problems. Even yourself. So, when you feel stuck in a problem, maybe it's simply time to share the load and allow someone to help you solve the complex problem.

Follow-up on the "Smash the server" test: Decoding the reactions My last post talked about a hypothetical situation I use when interviewing candidates: I ask them to "smash the server." It's not about them actually doing it, but about how they react. Two main groups emerge: Group 1: "Whoa, hold up!" These folks are all about logic. They question the task, talk about the server's importance and cost, and basically say, "Nope, not gonna do that." While this seems sensible, it's a no-go for the type of team I'm building. Group 2: "Orders received, boss." This group gets it. They might make a joke to lighten the mood, but they understand that sometimes, you need action now and explanations later. They're ready to execute the order, trusting that I have my reasons. Group 1 gets a polite "thanks, but no thanks." Group 2 moves on in the interview process. I know what you're thinking: this sounds super controlling! Shouldn't we be finding better solutions? Isn't there room for discussion? And you're right, under normal circumstances. But this is about building a team for a crisis, a full-blown emergency. Here's the thing: - I see the bigger picture: I have more information, a wider perspective than any new team member would. - I've been in the trenches longer: I've had more time to analyze the situation and understand the stakes. - I'm ultimately responsible: If things go south, it's on me. I need a team that can act decisively when I give the word. Don't get me wrong, once the dust settles, open discussion and brainstorming are key. But during the crisis, it's all about execution. This is about finding the right balance between "my way or the highway" and "let's all vote." The best leaders know how to adjust their style depending on the situation, sometimes being more directive and sometimes more collaborative.

What’s the secret to increasing the likelihood of a successful placement by 21%? Collaborating with your clients throughout the entire engagement. So then, why are some firms so reluctant to do it? There’s a fear that opening up the floodgates will make it harder to manage client expectations. Here’s why that anxiety is misplaced. By inviting clients to collaborate from the very beginning: You earn their trust and buy-in They learn and respect your process Instead of managing them, you work in partnership You close searches faster, with less resistance The trick to making it work? Having the tools at your fingertips to give your clients the right level of visibility at every stage in the search process. So you can improve their experience—without adding to your workload. It’s a win-win.

💡 Exploring the nuances of Environment Variables vs. System Variables! 💼✨ As a seasoned professional navigating the tech landscape, understanding the distinction between environment and system variables is crucial. Here's a brief breakdown: 🌐 Environment Variables: These are dynamic settings that dictate how processes run and behave within a specific environment or session. They're often customized by users or applications to tailor behavior, such as defining paths to executable files or specifying configuration options. 💻 System Variables: In contrast, system variables are fundamental settings that govern the behavior of the entire operating system. They're essential for the system's functionality and are typically managed by the operating system itself. System variables play a pivotal role in various aspects of system operation, from defining system paths to setting default configurations. In essence, while environment variables are more localized and flexible, system variables wield broader influence over the entire system. Mastering the intricacies of these variables not only demonstrates technical prowess but also showcases adaptability and problem-solving skills. Recruiters seeking candidates who can navigate complex systems and optimize performance will undoubtedly recognize the value of this expertise. Are you ready to harness the power of variables in your organization? Let's connect and explore how my proficiency can elevate your team's capabilities! #TechLeadership #EnvironmentVariables #SystemVariables #TechnicalProficiency #ProblemSolving #Recruitment #Networking

I recently heard something in a meeting that really resonated: "IT Plumber, jack of all trades but master of none." It made me think about how this phrase perfectly captures the essence of an entire generation of IT professionals who’ve spent years being the go-to person for everything—from networking to security to system administration. As technology evolves, we’re witnessing the rise of more specialized roles, leaving the broad "IT generalist" slowly being phased out. But is it really time to let go of the jack-of-all-trades mindset? Or does versatility still have its place in a world of increasingly siloed expertise? What are your thoughts on the balance between specialization and adaptability in today’s IT landscape? #IT #Technology #CareerEvolution #Specialization #Adaptability #TechTransformation

Check out my latest blog... What are your thoughts on a Zero Trust Policy?

How to get a job in Trust and Safety - Part 1/5 is now live! Link to the video - https://lnkd.in/gzszjkXc In the first video we'll do some context setting about - 1) What kind of roles are available in the field. 2) Which cities / hubs have a critical mass of Trust and Safety jobs 3) Tips on applying 4) Where to find these roles and setting up LinkedIn alerts 5) Resource to the 50 jobs in Austin to explore the different types of roles available I'll keep posting as I finish the resources - next is preparation tips, resources and certifications. So follow along! #trustandsafety #TrustandSafetyjobs #JobResources

It's a long time since I did any technical support roles. But I still use many of the core principles to this day. Understand what is important to your customer. Yes, Outlook not working might sound minor, but if that customer relies on it for critical information, it's a critical system. Understand the full impact of any changes or fixes. Don't make any changes to the environment until you are comfortable you have a back up plan - just in case. Own the problem. It's yours until it is fixed and so know what you need to get it over the line. Know several possible solutions and then pick the most appropriate. The most critical part of a crisis is communication. People don't worry so much about problems if they can clearly see you dealing with it. When I do business crisis strategy work with clients, these are the principles I still use: What is important What is the impact What can be done What to communicate. Most importantly, I am used to doing all of these within a matter of minutes, with resolutions in hours. Because critical problems in your business cannot wait. Strategy is useless after the crisis but many founders will want to wait until everything has calmed down before talking strategy. This is a fundamental flaw in the thinking - it makes the problem last longer and causes it to have a far more significant impact.. Strategy is the solution to most problems, if implemented correctly. Stuck on where to go next, but know you need to move fast? Get in touch and see how I can help.