Showing Posts From

Management

Why leaders shouldn't give weight to every battle

As a leader, you are constantly surrounded by information, conflicts, opinions, and unexpected events. It feels natural to address everything that lands on your plate. However, there is a fundamental rule in leadership that many overlook: your reaction creates reality. When you choose to respond to a situation, you publicly give it weight. You acknowledge that it is real, important, and worthy of attention. But what happens when you react to the wrong things? Understanding when to step into the ring and when to pretend you didn't see a thing is one of the most critical skills a leader can master. The hidden danger of acknowledging everything It is tempting to believe that a good leader handles every problem directly. But acknowledging every minor conflict, provocation, or mistake can backfire quickly. When you validate every issue by responding to it, two things happen:You give up your power: If you constantly react to what others do or say, you let them set your agenda. You become reactive instead of strategic. You risk looking weak or submissive: Formally acknowledging minor politics or small attacks can make you look defensive. It shows that those small things can easily disturb you.If you react to every small distraction, you erode your own authority and mandate. You waste precious energy on noise instead of focusing on long-term impact. When to "play dumb" Sometimes, the most powerful response is no response at all. In management, choosing not to see or hear something—turning a blind eye—can be a strong tactical move.It starves negative energy: Small drama and minor provocations rely on oxygen. If you don't give them attention, they usually fade away on their own. It preserves focus: Your team watches what you pay attention to. If you focus on small details, they will too. If you ignore the noise, they stay focused on the real work. It maintains your position: By ignoring trivial issues, you signal that certain low-level behavior is simply beneath your level of engagement.Act or ignore? Before you jump into action, ask yourself these three filtering questions: 1. Does this threaten our core values or strategic goals? If a situation directly harms team safety, ethics, or main targets, you must act firmly and immediately. Leaving these issues unaddressed damages your credibility. 2. Am I reacting out of ego or true necessity? If someone makes a light remark or questions your stance, ask yourself if your ego is just feeling hurt. If there is no real impact on the business, let it go. 3. Will my reaction solve the problem or just amplify it? Sometimes, bringing an issue into the spotlight creates a bigger crisis than the original problem. If acknowledging an event makes your position weaker or subordinate, step back. Protecting your mandate and authority Leadership is not about fighting every battle; it is about choosing which battles are worth winning. When you are selective with your energy, your team learns that when you do speak or act, it truly matters. By refusing to acknowledge small, distracting realities, you protect your authority and stay in control of the narrative. Closing Thoughts Mastering the balance between action and silence takes practice. Acknowledge what builds your team and advances your mission. Ignore the noise that drags you into petty politics. Your authority does not come from controlling every detail, but from directing your focus toward what truly lasts. True authority is not shown by responding to everything, but by choosing what truly deserves your energy.

Why saying 'no' is the only sustainable choice

Many operational leaders recognize this scenario: you return from vacation and discover that important decisions were made informally over coffee. Official rules were ignored, and there is no proper handover. Suddenly, an urgent executive presentation lands on your desk with a 48-hour deadline. Your first instinct is likely to work overtime and clean up the mess. It feels helpful, useful, and necessary. However, stepping in to fix everything is the worst thing you can do. Leadership expert Bas Kodden explains in his book The Devil Inside that you end up sabotaging yourself and your organization. When you solve problems caused by poor leadership, you hide the real damage of broken agreements and keep the chaos alive. To build a healthy organization, you must face the truth: you have to stop helping. The trap of self-sabotage Why is it so hard to say "no"? Why is our default reaction always a stressed "yes"? It comes down to internal "saboteurs" or emotional triggers:Fear: Fear of conflict, fear of appearing unhelpful, or fear that everything will fall apart if you do not step in. Empathy: Excessive sympathy for desperate colleagues, which causes you to take on their pressure and stress. Ego: The desire to be the hero who saves the day, or the fear of feeling guilty.Because of these triggers, we constantly compensate for broken processes. True leadership starts with self-leadership: leading yourself first. You need to reflect on these emotional traps and stop making excuses for poor planning. Why "no" is the most sustainable choice Saying "no" to artificial urgency is not selfish or unhelpful. It is the most sustainable choice for your team and organization. When you decline an unplanned request, three positive things happen:The problem stays with the owner: The person who ignored rules or failed to plan feels the direct consequences, which encourages better behavior next time. You protect your team: You save your team's energy and capacity for planned operational goals. Governance is restored: Declining informal requests forces managers to use official decision-making channels.7 Rules for operational boundaries Saying "no" requires self-control. Use these seven practical rules to evaluate last-minute requests:No goal means "no": If the request does not directly support agreed goals, it is not a priority. Urgent is not always important: Someone else's panic usually means poor planning. Do not make it your problem. Look at hidden costs: Every extra task takes time. Ask yourself: Which important goal must I sacrifice for this? Saying "yes" to chaos means saying "no" to strategy: Time is limited. Last-minute work always hurts the quality of your core duties. Take time to pause: Stop reacting automatically. Take a moment to think before giving a clear answer. Let your calendar decide: If the task does not fit into your schedule, the calendar makes the decision for you. Demand context first: Ask for the business objective and proper approval. Often, you will find the request was not necessary after all.Closing thoughts An organization cannot grow on heroic acts, overtime, and personal favors. Sustainable success comes from clear agreements, structured roles, and respect for operational boundaries. Once you learn to manage fear, ego, and excessive empathy, you realize that saying "no" is not a rejection—it is professional respect. It forces the organization to mature and protect its own systems. Stop helping. Start protecting the system. Saying "no" to artificial chaos is the most sustainable choice you can make.

Why great leadership is about agreements, not expectations

Every morning, millions of professionals wake up and unconsciously ask themselves the exact same question: “What is expected of me today?” They spend the rest of their day trying to satisfy an endless list of imagined demands. What does my boss expect? What does my partner expect? What do my children expect? Trying to guess and fulfill everyone’s hidden expectations is an impossible task. It creates a painful cycle of stress and frustration. Instead of growing into who they could truly be, people get trapped in a passive routine. Unspoken expectations never bring clarity; they only grow bigger, heavier, and more exhausting over time. Why expectations create immature relationships To understand why expectations fail in business, we can look at psychologist Eric Berne’s famous theory of Transactional Analysis. Berne explained that human interactions usually fall into specific roles: Parent, Child, or Adult. Expectation Culture: [Parent Leader] ⟷ [Child Employee] (Control & Frustration) Agreement Culture: [Adult Leader] ⟷ [Adult Employee] (Equality & Ownership)When management relies on vague expectations, it creates an unhealthy Parent-Child dynamic:The Manager acts as the Parent: Trying to micro-manage behaviors, soften every conflict, or act like a caretaker to be liked by everyone. The Employee acts as the Child: Waiting to be told what to do, feeling patronized, and complaining about unclear workload.Many managers make the mistake of practicing "amateur psychotherapy." They focus on controlling the personalities and emotions of their team members rather than building direct working relationships. This caretaking behavior is often just a way to avoid uncomfortable conversations. Real leadership is not about managing feelings; it is about treating people as equals who can take responsibility for their promises. Victims wait, owners agree In his book Conscious Business, leadership expert Fred Kofman highlights the fundamental difference between a Victim mindset and an Owner mindset. Expectations are, by definition, completely passive. When you expect something, you sit back in a false sense of safety, silently hoping someone else will act.The Victim Mindset: Victims prefer expectations because expectations require no courage. A stressed employee sits at their desk silently worrying: "Does my manager really expect this report by Friday? That's impossible, I'm already so overworked!" Instead of speaking up, the victim stays silent, misses the deadline, and blames the system. The Owner Mindset: Owners hate vague expectations. They know that promises require action, clarity, and bold communication. An owner steps forward, opens a direct dialogue, and creates a firm agreement: "I can deliver section A by Friday at 3 PM, but to do that, we need to push project B to next Tuesday. Do we agree?"Making an agreement requires real bravery. You must make clear promises, set measurable goals, and accept total responsibility for the outcome. How to build an agreement-driven workplace Replacing expectations with clear commitments instantly cleans up team communication. When two adults make a voluntary agreement, traditional micro-management becomes obsolete. The leader's role shifts simply to monitoring what was agreed upon. Key Elements of Effective Agreements:Explicit Deadlines and Numbers: Vague statements like "finish this soon" must be replaced with "delivered by Thursday at 12:00 PM." Mutual Input: Agreements are made together. Both parties must freely say "yes" or negotiate better terms before committing. Direct Problem-Solving: When an agreement is broken, you do not judge the person's character; you discuss the facts of the broken promise directly and respectfully.Closing thoughts Leadership is not about carrying the weight of everyone's emotions or expecting people to read your mind. It takes courage to stop guessing, abandon false safety, and start making clear, equal commitments with your team. When you replace passive expectations with active agreements, you build a culture of high performance, deep trust, and mutual respect. True leadership is not about managing personalities or setting vague expectations; it is about making clear agreements as equals and holding each other accountable.

The decision spectrum: Why unclear decision-making is slowing your team down

Most frustration in teams doesn't come from bad decisions. It comes from leaders using the wrong decision style for the problem at hand. In struggling leadership teams, you often see the same two mistakes. On one end, leaders make big choices completely on their own without asking anyone, creating anger and resistance. On the other end, they pull every small daily choice into endless meetings, turning simple tasks into slow bureaucratic debates. Good leadership is not a choice between acting like a dictator or running a democracy. It is about choosing the right approach for the right moment. To lead effectively, managers need to understand five clear ways of making decisions—and know exactly when to use each one. The 5 Modes of Making Decisions Decision theories and modern organizational models show that your authority must adapt to the situation. A strong leader clearly switches between five different modes: [ Mode 1 ] ------------> [ Mode 2 ] ------------> [ Mode 3 ] ------------> [ Mode 4 ] ------------> [ Mode 5 ] Silent Action Decide & Inform Ask for Advice Check Objections Group Decision1. Silent Action: Decide, act, and do NOT informWhen to use it: Small operational fixes or confidential personal matters. Why it matters: Flooding your team with useless updates creates unnecessary noise. If a decision has zero impact on a colleague's daily work, just make the call and keep moving.2. Unilateral Command: Decide and inform immediatelyWhen to use it: Urgent emergencies, clear expert choices, or small decisions that are easy to reverse. Why it matters: Speed is critical. When a crisis hits or you are the expert, asking for everyone's opinion is a waste of time. You make the choice, take responsibility, and inform your team right away.3. Ask for Advice: Consult experts, but keep ownershipWhen to use it: Important strategic choices where you need extra input, but you are still responsible for the outcome. Why it matters: This is where many managers get stuck. They confuse asking for advice with asking for a vote. In this mode, you tell your team: "I am making this decision, but I need your input first." You gather perspectives, but the final choice remains yours.4. Check for Objections: The Consent ModelWhen to use it: Major changes to policy or structure where hidden resistance could break execution later. Why it matters: Instead of trying to make everyone happy (which leads to weak compromises), you present a clear plan and ask: "Does anyone see a critical reason why this will not work?" You are not asking if everyone loves the plan; you are checking if anyone sees a real danger.5. Group Decision: Delegate to collective agreementWhen to use it: High-impact team goals where success depends 100% on everyone owning the plan. Why it matters: True consensus should be rare. Use it only when the entire team must own the result together. The manager steps back and becomes a facilitator, agreeing to follow whatever the group decides.Be clear about the rules upfront The secret to fast decision-making is transparency. Before you start a conversation, tell your team which mode you are using. If you call a meeting to ask for advice, but your team thinks they are gathered to vote, they will feel cheated when you make a different choice.Fake democracy causes far more damage than clear authority.When leaders hide behind fake group decisions to avoid personal responsibility, progress stops. But when leaders force decisions without checking for real objections, execution fails anyway. Closing thought Leadership is not about making every choice yourself, nor is it about dumping every problem on a committee. It is about picking the right decision style for the problem in front of you. Be crystal clear about how a decision will be made before you start the conversation. Clarity on how you decide is just as important as the decision itself.

We are teaching managers how to be machines. Just as machines are taking over.

For decades, business schools and executive programs have relied on a familiar curriculum. If you want to become a successful manager, you learn data analysis, financial modeling, operational planning, and strategic execution. You are trained to optimize processes, map out roadmaps, and treat an organization like a mechanical system that can be tuned with the right metrics. This is the exact, analytical side of business administration. It is logical, structured, and comfortably measurable. There is just one fundamental problem with this approach: We are spending billions teaching human leaders how to perform tasks that computers can now do significantly better, faster, and cheaper. The crisis of relevance in management science The traditional management discipline is facing a quiet crisis of relevance. Analytical capacity, resource scheduling, operational planning, and data-driven scenario analysis used to be the exclusive domain of senior executives and high-priced consultants. Today, algorithmic models, automated platforms, and AI systems can synthesize complex organizational data in seconds. The hard, analytical side of management is rapidly becoming software. Yet, our educational institutions and corporate training programs continue to produce managers trained for a world that no longer exists. Instead of evolving, we pass down the exact same playbook from generation to generation. A playbook that produces managers who default to the classic 3 C's: Coordinating, Commanding, and Controlling. They try to act like human processors, optimizing spreadsheets while remaining distant from the human reality of their teams. Real leadership cannot be automated If machines are taking over the mechanics of management, what is left for human leaders to do? Everything that actually matters. True leadership has never been about process management. It is, first and foremost, an emotional, personal, and interpersonal discipline. It requires traits that no software model possesses:Authenticity: The courage to be transparent, vulnerable, and consistent in your values. Social and Emotional Intelligence: The ability to navigate conflict, read unsaid dynamics, and build genuine trust. Sense-Making: Helping teams find purpose, context, and direction in an increasingly complex world.You cannot learn these qualities by studying a framework or passing a written exam. Emotional maturity and authentic leadership require rigorous personal reflection, deep self-awareness, and—above all—the willingness to experiment, fail, and gain messy, real-world experience. From command to connection We have reached a fork in the road. We can either double down on outdated management models and watch our organizations become rigid and disengaged, or we can fundamentally shift our course. We must stop training leaders to be analytical overseers and start developing them as social-emotional anchors. When you strip away the administrative and analytical tasks that technology now handles, a leader's true responsibility becomes clear: Don't manage the process; empower the people. That means stepping away from the urge to command and control. It means creating an environment of psychological safety where employees feel trusted to take ownership, innovate, and make decisions within a clear direction. The generational loop we need to break The reason bad management persists is not a lack of books or webinars. It persists because it is copied. Young professionals enter the workplace, watch their managers lead through control and coordination, and assume that is what authority looks like. When they eventually get promoted, they repeat the cycle. They pass down the 3 C's because nobody taught them how to navigate the uncomfortable, human side of leadership. Breaking this cycle is the most urgent challenge facing modern organizations. We don't need more managers who act like algorithms. We need leaders who have done the hard internal work of becoming emotionally developed human beings. Closing thought Technology is stripping away the illusion that management is merely an analytical science. It is forcing us to confront a truth we should have embraced long ago. If your value as a leader relies solely on planning, tracking, and operational control, you are already redundant. The future belongs to leaders who understand that technology handles the logic, but humans supply the soul. Stop training managers to compete with machines. Start raising leaders who know how to connect with people.

Why helping your team is secretly destroying their ownership

When pressure builds inside an organization, a predictable instinct kicks in for many leaders. They lean into what they know. They start managing closer, checking status updates more frequently, and making decisions on behalf of their teams. Without realizing it, they default to a classic, comfortable playbook built on three traditional pillars: Coordinating, Commanding, and Controlling. It feels responsible. It feels like taking charge. But in reality, it is an outdated operating system that paralyzes organizations, smothers initiative, and creates an environment where nobody takes true responsibility for the outcome. If we want to build resilient, adaptive teams, we have to abandon the old 3 C's—and rethink what leadership actually means. The trap of the 3 C’s The traditional manager spends their day coordinating schedules, commanding who does what, and controlling every output before it reaches the outside world. That model might have worked in assembly-line factories a century ago, where tasks were predictable and repetition was the goal. But in modern knowledge work—and especially in an era shaped by complex tech and fast-moving environments—it falls completely flat. When a leader coordinates everything, employees stop aligning with each other. When a leader commands, employees stop thinking critically. And when a leader controls, employees stop caring about quality because "the boss will check it anyway." You don't get speed, quality, or innovation. You just get a bottleneck with a title. A different triad: Direction, Space, and Accountability Leading effectively requires a fundamental shift in posture. Instead of managing tasks, leaders must design the environment in which work happens. That comes down to three entirely different principles:Provide Direction: Be crystal clear about where the team is going and why. What is the strategic goal? What does success look like? What are the boundaries? Offer Space: Step back and grant the team complete autonomy over how they achieve that goal. Give them the trust, tools, and psychological safety to figure out the path themselves. Ask for Results: Hold people accountable for the outcomes, not the hours spent or the exact steps taken. Expect ownership and high standards.Direction without space is micromanagement. Space without direction is chaos. Space without accountability is just apathy. But when you balance all three, ownership naturally flourishes. The dangerous illusion of "helping" This brings us to one of the most subtle ways leaders accidentally ruin their teams: the urge to help. It usually sounds benevolent: "Let me quickly take care of that for you," or "I'll jump into this meeting and fix it." It comes from a good place. Leaders want to be supportive, alleviate stress, or just get things done faster. But let’s be honest about what "helping" actually means in practice. In most cases, helping means partially or fully stepping in to take over ownership of a problem. The moment a leader takes the pen out of an employee's hand to rewrite the slide, or steps in to solve an operational issue, a invisible contract is signed: This is no longer your problem. It is now mine. What happens when ownership is stolen When you "help" by taking over tasks, two things break down instantly: First, you rob your team of the discomfort required for growth. Problem-solving is muscle memory. If you never let your team struggle through a complex challenge, they will never build the capability or confidence to handle it next time. Second, you create a culture of learned helplessness. Employees quickly realize that if a problem gets tough enough, the leader will step in and solve it for them. Ownership evaporates, and the leader is left wondering why "nobody takes initiative around here." Real support isn't stepping in to do the work. Real support is coaching from the sidelines while keeping the ball firmly in the team's field. Bringing leadership back to intent True leadership is not measured by how much work passes through your hands, or how indispensable you make yourself to the daily execution. It is measured by how well your team performs when you are not in the room. That requires letting go of the need to control the micro-details. It means being willing to sit with the temporary discomfort of watching someone else solve a problem differently than you would have solved it yourself. Closing thought The role of a leader is not to carry the weight of every problem. It is to build a team capable of carrying it themselves. If you spend your days coordinating every move, commanding every step, and stepping in to "help" whenever things get difficult, you aren't leading. You are just holding your organization hostage to your own capacity. Stop managing the execution. Give direction, create genuine space, demand results—and leave the ownership exactly where it belongs.

The invisible tax of organizational immaturity

When organizations talk about costs, the conversation usually revolves around salaries. Or around software licenses, cloud consumption. Office space even, or procurement. Those costs are easy to measure. They appear neatly on financial statements. But after working with organizations of different sizes and maturity levels, I've become convinced there's another cost almost nobody measures. An invisible tax. One that quietly drains productivity, frustrates employees and slows decision-making. Not because people aren't working hard. But because the organization itself creates friction. Everyone is busy. Few people are moving forward. One of the first things I pay attention to when joining an organization isn't the technology. It isn't the financial performance. It isn't even the organizational chart. I watch how people work. How decisions are made. How priorities change. How meetings end. How often people say things like:"We're waiting." "Nobody knows who's responsible." "We'll discuss it again next week." "I assumed someone else was taking care of it."Those sentences rarely point to individual performance. They point to organizational design. Because mature organizations don't become productive by hiring smarter people. They become productive by reducing unnecessary friction. The tax nobody budgets for Organizational immaturity doesn't usually appear as one dramatic failure. It appears as thousands of tiny inefficiencies. Like a meeting without decisions. An action without an owner. A priority that changes three times in one week. An approval that waits in someone's inbox. A project delayed because two departments assumed the other was responsible. Individually, none of those events seem particularly significant. Collectively, they become incredibly expensive. Not because they cost money directly. Because they consume something even more valuable: Leadership capacity. Attention. Momentum. Friction compounds Recently I observed an organization working through several operational challenges at the same time. None of them were catastrophic. A leadership transition. A supplier decision waiting for approval. Priorities shifting as new information became available. Teams adjusting schedules to respond to unexpected developments. Every individual situation was understandable. What interested me wasn't the incidents themselves. It was how much organizational energy disappeared into coordinating them. People weren't solving customer problems. They were reorganizing calendars. Clarifying responsibilities. Following up on decisions. Waiting for answers. Every interruption looked small. Together, they formed a pattern. The organization wasn't paying for the incidents. It was paying for the friction between them. Activity is not progress Immature organizations often look incredibly busy. Calendars are full. Teams work hard. Everyone feels under pressure. From the outside, it almost looks impressive. Until you ask a few simple questions: What are our three most important priorities this quarter? Which KPI tells us whether we're improving? Who owns this decision? What happens if nothing changes?Surprisingly often, the answers become vague. Because activity is easy to observe. Progress requires clarity. And clarity requires leadership. The hidden cost of ambiguity Ambiguity is one of the most underestimated operational costs I know. If priorities are unclear... People create their own. If ownership is unclear... People wait. If success is undefined... Everyone believes they're doing the right thing. The irony is that highly capable people become less effective, not because they lack competence, but because they're forced to spend their energy navigating uncertainty instead of creating value. Organizations don't lose momentum because employees suddenly become less talented. They lose momentum because ambiguity quietly taxes every decision. Every interruption has a cost One unexpected meeting. One rescheduled customer visit. One delayed approval. One forgotten follow-up. One unclear decision. Individually, they're almost invisible. But organizations rarely suffer from one interruption. They suffer from hundreds. Every context switch costs attention. Every unclear responsibility creates another conversation. Every missing KPI creates another opinion. Every delayed decision creates another dependency. Eventually, the organization becomes extremely busy managing itself. Instead of serving customers. Maturity isn't about perfection No organization operates without surprises. Nor should it. Markets change. Customers change. People leave. Plans evolve. Operational maturity isn't the absence of unexpected events. It's the ability to absorb them without disrupting everything else. The most mature organizations I've worked with weren't necessarily the most structured. They were the most predictable. People knew who decided. People knew what mattered. People knew what success looked like. That predictability creates an enormous competitive advantage. Because it allows talented people to focus on solving meaningful problems instead of organizational ones. The role of leadership This is why I believe organizational maturity is fundamentally a leadership responsibility. Not because leaders should solve every problem. But because leaders design the environment in which problems are solved. Good leaders don't simply remove obstacles. They remove recurring obstacles. They don't fix today's confusion. They redesign tomorrow's process. They don't celebrate people who constantly save the day. They build organizations that need fewer heroes. Because every recurring operational problem is usually trying to tell you something. Not about the people. About the system. Closing thought The most expensive organizations aren't always the ones with the highest payroll. Sometimes they're the ones quietly paying an invisible tax every single day. A tax on attention. A tax on momentum. A tax on decision-making. A tax on leadership. Most organizations never notice it because they experience it gradually. It simply becomes "the way we work." But it doesn't have to be. Because organizational maturity isn't measured by how hard people work. It's measured by how little unnecessary friction they have to overcome before they can do their best work.

Great organizations don't react faster. They lead sooner.

Every organization faces unexpected events. A key employee resigns. A customer leaves. A supplier disappoints. A critical project slips behind schedule. None of those situations are remarkable. The interesting question isn't whether they happen. It's what happens next. Because while every organization reacts... Not every organization leads. Two conversations always emerge I've noticed that almost every unexpected event creates two conversations. The first is about what happened. Who made the decision? Could it have been prevented? What were the circumstances? Who approved it? Those questions are natural. Sometimes they're even necessary. But then there's a second conversation. One that often receives far less attention. What are we going to do now? That's where leadership begins. Reality doesn't care whose fault it is One of the most common patterns I observe inside organizations is how quickly conversations drift toward explanation. Why this happened. Why another department was involved. Why someone else needed to decide first. Why a dependency caused the delay. Why governance prevented action. Interestingly, most of those explanations are factually correct. They're also largely irrelevant. Reality doesn't change because we understand it better. Leadership starts the moment we stop negotiating with reality and start working with it. The circumstances are what they are. The only remaining question is what we intend to do next. Waiting is often a decision Every leader encounters situations where formal approval is required. That's normal. Governance exists for a reason. But I've also seen organizations confuse governance with inertia. A recommendation has been written. The preferred solution has been identified. The risks are understood. The business case is complete. Everything is ready. And then... Everyone waits. Not because there's nothing left to do. But because everyone assumes someone else now owns the next step. Waiting feels safe. After all, nobody can criticize you for acting too early. The problem is that waiting is rarely neutral. It is often a decision disguised as patience. Great leaders create momentum The most effective leaders I've worked with share one characteristic. They don't spend much time asking whether circumstances are ideal. They ask a different question. "Given today's reality, what can we move forward?" Maybe implementation can't start yet. But preparation can. Maybe contracts can't be signed. But planning can begin. Maybe a final decision hasn't been made. But dependencies can already be removed. Momentum rarely appears on its own. Someone creates it. Governance should enable action One of the biggest misconceptions about governance is that it's primarily about control. I don't think it is. Good governance exists to improve decision-making. Not to delay it. Not to spread accountability so thinly that nobody feels responsible. And certainly not to create an environment where people stop thinking for themselves. The healthiest organizations I've seen combine strong governance with strong initiative. People understand the boundaries. But they also understand that leadership begins long before formal approval arrives. Governance should answer the question: "How do we make better decisions?" Not: "How do we avoid making them?" Leadership is accepting reality quickly One lesson I've learned over the years is that exceptional leaders don't waste much energy wishing reality were different. They don't spend days arguing with circumstances. Or blaming timing. Or waiting for perfect conditions. They accept reality remarkably quickly. Not because they like it. Because they understand that accepting reality isn't surrender. It's the starting point for changing it. You can't influence the situation you're refusing to acknowledge. The difference between reacting and leading Reactive organizations ask: "Who owns this?" Leading organizations ask: "What can we influence right now?" Reactive organizations focus on why progress is difficult. Leading organizations focus on removing the next obstacle. Reactive organizations wait until certainty appears. Leading organizations create clarity through action. The circumstances may be identical. The outcomes rarely are. Leadership is a mindset before it's a position Titles don't create leadership. Authority doesn't create leadership. Experience doesn't create leadership. Leadership begins with a decision. The decision to stop defining yourself by what others haven't done. And start defining yourself by what you can do next. That doesn't mean ignoring governance. Or bypassing colleagues. Or acting recklessly. It means refusing to surrender your ability to influence the outcome simply because someone else hasn't moved yet. There is almost always another conversation to have. Another dependency to remove. Another scenario to prepare. Another problem you can solve before someone asks you to. That's what leaders do. Closing thought Every organization will experience disruption. Every organization will encounter uncertainty. Every organization will have days where carefully made plans suddenly become obsolete. Those moments don't reveal whether an organization is successful. They reveal how it thinks. Some organizations become trapped in explanations. Others immediately start creating options. Because leadership isn't demonstrated when everything goes according to plan. It's demonstrated in the moment reality refuses to cooperate. You can spend your energy explaining why circumstances prevented progress. Or you can ask the only question that has ever moved an organization forward. "Given reality as it is... what's our next move?"