At some point, if you’re paying attention and doing the work, this will happen. Senior leadership will come to you and ask: “Give me your honest opinion.” Sounds simple. It’s not. Because what they’re really asking is: “Tell me what’s wrong—without blowing up the system.” This is where most people make a mistake. They either: Hold back and say nothing meaningful Or unload everything with no structure or discipline Neither helps. 1. Don’t Make It Personal The fastest way to lose credibility is to turn it into a list of people problems. Most leadership issues aren’t about individuals. They’re about unclear expectations, weak standards, and inconsistent enforcement. Focus on: Where decisions break down Where roles are unclear Where standards are not defined or not enforced If you make it about people, it becomes defensive. If you make it about systems, it becomes fixable. 2. Be Honest—but Controlled They asked for your opinion. Give it. But don’t rant. Don’t vent. Don’t speculate. Be clear and specific: “This is where communication breaks down.” “This is where ownership is unclear.” “This is where standards are not being held.” Say it plainly. Then stop talking. Confidence doesn’t come from saying more. It comes from saying what matters. 3. Tie Everything to Impact If you want to be taken seriously, connect leadership gaps to outcomes. Turnover Rework Missed deadlines Frustration between teams Leadership problems are rarely just leadership problems. They are operational problems—and operational problems eventually become financial problems. Make that connection clear. 4. Offer Direction, Not Just Diagnosis Don’t just point out what’s broken. Give them a starting point: Clarify roles and ownership Establish clear standards Improve information flow Hold consistent follow-through You don’t need a full plan. You need a clear first step. 5. Understand What You Just Stepped Into The moment you speak honestly, things change. You’re no longer just “one of the team.”

After reading Tim's post and reflecting on it I feel like this is a good time to write this post. Everyone talks about resilience like it’s something you either have or you don’t. That’s not how it works. Resilience is built through pressure—repeatedly. Not by avoiding it, but by learning how to operate inside it without losing judgment, standards, or control. Most people want less stress. Leaders learn how to handle more of it—without breaking down or passing it on to others. That matters because your ability to stay steady doesn’t just affect you. It affects everyone around you. When you stay grounded: - Your team thinks clearer - Problems get addressed earlier - Decisions improve - Panic doesn’t spread When you don’t, the opposite happens. Resilience isn’t about being emotionless. It’s about not letting emotion drive your decisions. Yes, it is easier said than done, but this is where the real work needs to happen. You build it by: - Slowing down when things speed up - Focusing on what you can control - Taking the next step, not solving everything at once - Staying consistent when it would be easier to drift Pressure is not the problem. How you handle it is. And every time you do it right, you’re not just improving yourself—you’re setting the standard for everyone around you. Question: When pressure hits, do you stabilize the situation—or absorb the chaos?

This post is heavily influenced by my training as a Maxwell Leadership speaker, coach and trainer, but also lived out through real world experiences... When I say “crisis thinking is a distraction,” I don’t mean that recognizing a crisis is wrong. In my world—emergency management, public safety, peer support—crisis awareness is part of the job. We’re trained to see it quickly and respond. But here’s the shift: Crisis thinking is helpful for awareness… but harmful if we stay there too long. If we stay in that space, everything becomes urgent, emotional, and reactive. Our thinking narrows. We start asking “what if?” instead of “what is.” That’s where mistakes happen—not because we didn’t care, but because we never transitioned out of reaction mode. What I’ve learned over time—through 18 federal disasters, critical incidents, and even personal seasons—is that leadership requires a deliberate shift: From reaction → to intention From emotion → to evaluation From chaos → to clarity For me, that shift usually comes back to a few simple questions: - What do I actually know right now? - What is within my control? - What is the next right step? That’s it. Not the whole plan—just the next step. In high stress environments, especially for responders, if we aren't careful, our default could be to absorb the intensity of the moment. But leadership—whether formal or informal—means we don’t just feel the moment… we help steady it....after all, that's the job, right? That doesn’t mean we ignore stress or pressure. It means we don’t let it drive. I’ve also seen this play out in peer support. When someone is overwhelmed, they’re often stuck in that same “crisis thinking” loop. Our role isn’t to match that intensity—it’s to help them slow down, ground, and begin to see clearly again. We’re not removing the problem—we’re helping them regain the ability to face it. At the end of the day, crisis will always show up. In fact, it shows up almost daily on various scales. That part isn’t optional and it's actually good news because it allows us to practice the concepts mentioned above.

Early in my Marine Corps career, I worked for a NCO who should never have been put in charge of people. He was unpredictable. Some days he wanted everything done by the book, other days the rules didn’t matter at all. Standards changed depending on his mood. Problems were ignored until they blew up. And when something went wrong, someone else was always to blame. It drove everyone crazy. Young Marines would gather in the smoke pit complaining about him. Some stopped caring, others just counted the days until they got out. One day a Gunnery Sergeant overheard the complaining. He didn’t raise his voice. He just said something simple: “He may be a bad leader, but that doesn’t give you permission to be one.” That stuck with me. Because the truth is, almost everyone will work for a bad leader at some point in their career. Sometimes it’s incompetence. Sometimes it’s ego. Sometimes it’s fear. But the real test of leadership isn’t when everything is running smoothly. The real test is what you do when leadership above you falls short. Here are four things professionals do when they find themselves in that situation. 1. Control What You Can Control You cannot control your boss. You cannot control the politics inside an organization. But you can control your own standards. Maintain professionalism. Maintain discipline. Maintain the quality of your work. If your boss lacks structure, create structure for your team. If communication is poor, communicate clearly with your people. Leadership is not a title. It’s behavior, and your team should never suffer because someone above you is failing. 2. Solve Problems — Don’t Feed the Drama Bad leadership environments always create rumor mills. People gather in corners complaining about management. You’ll hear the same conversations every day. “This place is a mess.” “Leadership doesn’t care.” “Nothing will ever change.” Complaining might feel good for five minutes, but it fixes absolutely nothing. Professionals bring solutions.

One of the simplest leadership tests I use is this: Ask a leader what they actually do. Not their title. Not their department. Not their job description. What problem do you solve every day? Most people struggle with this question. You’ll hear things like: - “I manage the team.” - “I supervise operations.” - “I make sure things run smoothly.” Those answers sound fine on the surface, but they don’t actually explain anything. Leadership isn’t defined by a title. Leadership is defined by the problems you solve. If a leader cannot clearly explain what they do, three things usually happen inside the organization: 1. Expectations become unclear 2. Accountability disappears 3. Performance becomes inconsistent When nobody clearly understands what a leader is responsible for, problems start bouncing around the organization with no real ownership. That’s when you hear things like: - “That’s not my job.” - “Nobody told me.” - “I thought someone else was handling it.” A simple framework that helps solve this is a three-part explanation: 1. The problem you solve 2. The skill or role you bring 3. The result people get For example, a leader in manufacturing might explain their role like this: “You know how production slows down when teams aren’t aligned or problems aren’t caught early? I lead the line and coordinate the work so the team stays focused, the process runs smoothly, and output stays consistent.” Notice what that does. It clearly explains: - The problem — misalignment and missed problems - The role — leading the line and coordinating work - The result — smooth processes and consistent output Now everyone understands the purpose of the role. This is not just about communication. It’s about clarity of leadership responsibility. Because here’s the truth most organizations ignore: Leadership problems are rarely just leadership problems. They are operational problems — and operational problems eventually become financial problems.