Showing Posts From

Culture

Accountability begins where blame ends

One of the biggest differences I've observed between average managers and exceptional leaders has nothing to do with intelligence. Or experience. Or technical expertise. It has everything to do with a simple question: "From which position do I choose to act?" Do I wait until circumstances improve? Or do I accept responsibility for influencing the outcome? That distinction sounds subtle. In practice, it changes everything. Waiting is often a decision disguised as patience Recently I witnessed an interesting situation. One of the companies within our group had entered into a strategic partnership with another IT company several years ago. Over time, that partner was acquired by a competing investment group. Suddenly, the partnership no longer made strategic sense. The conclusion was obvious. The partnership had to end. The company did exactly what you would expect. They evaluated alternatives. Created a longlist. Reduced it to a shortlist. Performed technical and commercial assessments. Produced a thorough recommendation. Everything was ready for the next phase. Except... Nothing happened. The recommendation was sent upwards. Everyone waited. The contract termination deadline approached. Time became increasingly valuable. And so did urgency. The conversations gradually shifted from: "How do we move this forward?" to "We're still waiting for a decision." Blame feels safe What struck me wasn't the delay itself. It was the mindset that emerged. "We already warned them." "We're still waiting." "There's nothing more we can do." None of those statements were factually incorrect. But every single one had something in common. They transferred control to someone else. And once you believe someone else owns the outcome... You also surrender your ability to influence it. Blame is strangely comfortable. Because it removes responsibility. Unfortunately, it also removes agency. Responsibility is not the same as fault One of the most valuable lessons I've ever taken is the distinction between being responsible and being guilty. Those are not the same thing. Leadership is not about accepting blame for everything. Leadership is about accepting responsibility for what happens next. That shift changes the entire conversation. Instead of asking: "Whose fault is this?" Leaders ask: "Given where we are today, what can I do?" That's an entirely different mindset. One keeps you waiting. The other gets you moving. Accountability isn't permission The company in this situation had already done almost all the hard work. They knew the preferred supplier. They understood the risks. They owned the operational relationship. They had the expertise. Yet they were waiting for permission to continue. I couldn't help wondering: What would happen if they simply behaved like owners? Not recklessly. Not ignoring governance. But proactively. Preparing implementation. Scheduling conversations. Building momentum. Reducing the time needed once formal approval arrived. Sometimes leadership means asking for permission. Sometimes it means asking for forgiveness. Knowing the difference is part of the job. Ownership is a state of mind Many people think ownership is something an organization gives you. A title. A role. A mandate. I don't believe that. Ownership is a choice. It's the decision to stop defining yourself by the constraints around you. Every leader experiences moments of frustration. Every leader encounters bureaucracy. Every leader occasionally has to wait. The question isn't whether those obstacles exist. The question is whether you allow them to determine your behavior. Owners ask: "What is still within my control?" Victims ask: "Why won't somebody else fix this?" The circumstances may be identical. The outcomes rarely are. Leaders create options One of the dangers of the victim mindset is that it gradually convinces you there are no choices left. You're waiting. You're blocked. Someone else has to decide. The world becomes smaller. Real leadership does the opposite. It expands possibilities. Not because every obstacle disappears. But because leaders instinctively search for the next move they can make. Even under pressure. Especially under pressure. Because time is both your greatest enemy... ...and often your greatest ally. Pressure creates movement. If you're willing to create it. Accountability is contagious Just like culture, accountability spreads. When leaders blame circumstances... Others blame circumstances. When leaders wait... Others wait. When leaders take ownership... Others start looking for what they can influence instead of what they can't. Organizations rarely become accountable because accountability appears in a set of company values. They become accountable because enough people consistently model that behavior. Leadership is always more visible than leaders think. Closing thought There will always be reasons why something cannot move forward. Budgets. Governance. Approvals. Dependencies. Those constraints are real. But they should never become an excuse for giving away ownership. The most effective leaders I've worked with don't spend much time asking who is responsible for the situation. They ask what they are responsible for next. Because blame looks backwards. Accountability looks forwards. And that's where leadership begins. Not when someone hands you authority. Not when circumstances become perfect. But the moment you decide: "I am responsible for what happens next."

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.

Your experience has no value if nobody wants to work with you

Every election produces winners. Yet the largest political party doesn't automatically end up governing. Why? Because winning votes and building a coalition are two very different skills. Influence has never been about numbers alone. Influence doesn't come from being right. It comes from others being willing to work with you. I think exactly the same principle applies inside organizations. Experience earns expertise. Relationships create impact. We've all met them. The engineer with twenty-five years of experience. The consultant who has seen every technology come and go. The architect who always seems to have the right answer. Brilliant people. Yet somehow... Nobody enjoys working with them. People avoid asking them questions. Meetings become uncomfortable. Conversations become debates. Eventually, people stop involving them altogether. Not because they lack knowledge. Because they lack influence. Experience creates expertise. Relationships create impact. Without the second, the first becomes remarkably ineffective. Being right is surprisingly overrated One of the biggest misconceptions in leadership is believing that being right is enough. It isn't. You can have the best idea in the room. The best architecture. The best strategy. The most accurate analysis. If people no longer want to collaborate with you, those ideas rarely leave the meeting room. Knowledge has little value if it never influences decisions. The ability to convince, inspire and collaborate is often far more valuable than simply having the correct answer. Being right is surprisingly overrated if people stop listening. It's the tone that makes the music In Dutch, we have a saying. "It's the tone that makes the music." I've always liked that expression because it captures something every experienced leader eventually learns. People can handle difficult feedback. They can handle disagreement. They can even handle hearing they're wrong. What they struggle with is unnecessary disrespect. The words are rarely the problem. The way they're are delivered usually is. The difference between: *"This design is wrong." and "Can I challenge one assumption? I think there's another approach worth considering." isn't technical. It's relational. One damages trust. The other builds it. Leadership is not about winning arguments Many leaders unknowingly turn every discussion into a competition. They need to have the final word. They need to prove they know more. They need everyone to recognize their experience. Ironically, the most respected leaders I've worked with did the opposite. They asked more questions than they gave answers. They listened before they challenged. They corrected without humiliating. And they made people feel smarter after the conversation than before it. That's influence. Not authority. Authority comes with a job title. Influence has to be earned every single day. The cost of being difficult I've seen incredibly capable people quietly become irrelevant. Not because their expertise became outdated. Because people stopped inviting them. Stopped asking for advice. Stopped involving them in important discussions. Not out of spite. Out of self-preservation. Every difficult interaction teaches people something. Either: "I'd like to work with this person again." Or: "Next time, I'll ask someone else." Few professionals realize how quickly that reputation spreads. Leadership by example This matters for everyone. But it matters even more for leaders. Because leaders don't just influence individual conversations. They influence culture. When leaders interrupt, others interrupt. When leaders dismiss opinions, others stop contributing. When leaders publicly criticize people instead of ideas, psychological safety disappears. And when leaders consistently treat people with respect, even during disagreement... The organization learns that respect isn't weakness. It's professionalism. Leadership by example isn't a slogan. It's how culture is transmitted. Expertise is only valuable when it creates more expertise The best leaders I've worked with all had one thing in common. They weren't interested in demonstrating how much they knew. They were interested in helping others become better. Their expertise didn't make them the smartest person in every room. It made everyone else smarter. That's a subtle but profound difference. Because leadership isn't about collecting followers. It's about multiplying capability. Closing thought I've met people with decades of experience who struggled to create lasting influence. And I've met relatively young professionals who inspired entire teams. The difference was rarely technical expertise. It was trust. People naturally follow those who make them feel respected. Those who challenge ideas without attacking people. Those who make collaboration easier instead of harder. Because in the end, your experience isn't measured by the number of years on your résumé. Nor by the certifications you've collected. Nor by how often you've been right. The value of your expertise isn't measured by what you know. It's measured by how much of that knowledge helps others succeed. And if nobody wants to work with you... Your experience has very little value at all.

Ownership is not a KPI. It's a culture.

One of the most common frustrations I hear from leaders is surprisingly consistent. "People don't take enough ownership." It's often followed by familiar observations:"Nobody takes responsibility." "Everyone waits for someone else." "Things keep falling between the cracks."I understand the frustration. I just think we're asking the wrong question. Ownership isn't something you can demand from people. It's something your organization either produces... ...or suppresses. And that starts with leadership. Every organization gets the culture it designs for Culture is often described as something intangible. Something that "just exists." I don't believe that. Culture is simply the collection of behaviors that leaders consistently reward, tolerate or ignore. If leaders reward collaboration, collaboration grows. If leaders reward accountability, accountability grows. If leaders reward hitting individual targets regardless of the outcome... That's exactly what people will optimize for. Culture isn't what is written on the wall. It's what happens when nobody is watching. The lease car wasn't the problem Recently I received a lease car through my employer. On paper, everything had gone according to plan. The administration was complete. The delivery had been scheduled. The paperwork was ready. Every process had apparently been followed. Yet the experience told a different story. The car smelled of smoke. Parts were missing. The key battery was almost empty. The interior clearly hadn't received the attention you would expect before handing it to a new driver. None of those issues were catastrophic. Individually, they were almost trivial. Together, they sent a very clear message: Nobody owned the outcome. I'm convinced everyone involved completed their own task. Someone scheduled the delivery. Someone processed the paperwork. Someone prepared the vehicle. Someone cleaned it. Someone inspected it. The problem wasn't that nobody did any work. The problem was that nobody seemed to ask one simple question before handing it over. "Would I be proud to deliver this myself?" That's the difference between completing a process and owning a result. Activity is not accountability I've seen the same pattern throughout my career. Hours spent in meetings. Good discussions. Interesting ideas. Everyone contributing. And then the meeting ends. No action list. No owners. No deadlines. No follow-up. A week later, the same discussion starts all over again. Not because people didn't care. Because nobody was explicitly responsible for making something happen. The meeting produced activity. Not accountability. Those are very different things. You can't manage what you haven't defined The same applies to performance. I've worked with organizations that wanted to improve quality, customer satisfaction and operational excellence. All admirable ambitions. Then I asked a simple question: "Which KPI tells us whether we're succeeding?" Silence. Not because people lacked intelligence. Because nobody had translated ambition into something measurable. If you don't know which outcomes matter... How do people know where to focus? How do they know which trade-offs are acceptable? How do they know when something deserves escalation? Leadership often asks for ownership while failing to define success. That's an impossible assignment. The danger of optimizing the wrong thing This is where KPIs often get a bad reputation. People say: "KPIs don't create ownership." That's true. But poor KPIs can absolutely destroy it. If you measure ticket closure, don't be surprised when people close tickets quickly. If you measure utilization, don't be surprised when calendars fill up. If you measure cost reduction, don't be surprised when quality quietly declines. People optimize for what the organization demonstrates is important. Not for what leadership says is important. Metrics don't create culture. They reveal it. Leadership by example is more than a slogan Leadership by example has become one of those phrases everyone agrees with. Yet few organizations truly live it. Ownership starts long before employees decide to take responsibility. It starts when leaders do. Leaders who admit mistakes instead of explaining them away. Leaders who finish what they start. Leaders who make responsibilities explicit instead of assuming someone will "pick it up." Leaders who ask not only what happened, but also who owns making it better. Culture copies behavior. Far more than it copies presentations. Ownership is designed into the organization Many leaders try to solve ownership by asking for more of it. I think that's backwards. Instead, ask different questions:Does every important outcome have a clearly identifiable owner? Does everyone understand what success looks like? Are responsibilities explicit? Are decisions made where the knowledge exists? Do our KPIs reinforce the behavior we actually want? Would our leaders behave the same way they expect others to?Those questions reveal far more about ownership than another workshop ever will. Closing thought I've become convinced that organizations rarely have an ownership problem. They have a leadership problem. Not because leaders don't care. But because ownership isn't created by asking people to "take responsibility." It's created by designing an environment where responsibility is obvious. Where success is clearly defined. Where outcomes have owners. Where leaders model the behavior they expect from everyone else. Because in the end, people don't simply work within the culture of an organization. They work within the culture its leaders create. And if ownership is missing throughout the organization... The first place I would look isn't at the people. It's at the example they're following.

Onboarding is not an HR process

Every organization talks about Customer Experience. Increasingly, they talk about Employee Experience too. There are conferences dedicated to it. Dashboards measuring it. Entire software platforms promising to improve it. And yet, I continue to see organizations where a new employee spends the first weeks chasing a laptop, waiting for system access, wondering who to ask about a lease car, or discovering that nobody seems entirely sure what should happen next. That isn't an HR problem. It is an organizational one. The first experience shapes everything We often assume culture is something employees discover over time. I don't think that's true. Culture starts on day one. Not during a presentation about company values. Not during an all-hands meeting. Not because someone tells you what the organization stands for. Culture emerges from dozens of seemingly insignificant moments. Was someone expecting me? Was my manager prepared? Did my accounts work? Did I know where to go for help? Did different departments seem connected, or did I become the person connecting them? None of those moments appear in an annual report. Yet together they answer a much bigger question: "Do these people have their organization under control?" Every small interaction builds operational trust Trust is often discussed as something leaders earn over months or years. But there is another kind of trust. Operational trust. It has nothing to do with charisma. It comes from consistency. Every smooth handover, every proactive update and every well-prepared first day tells a new employee the same thing: "Someone thought this through." The opposite is equally powerful. Every missing approval. Every unanswered question. Every process that requires the employee to coordinate departments that should already be working together. Those moments don't just create frustration. They quietly undermine confidence in the organization itself. Onboarding is not an HR process This is perhaps the biggest misconception. Organizations often divide onboarding into responsibilities.HR prepares the contract. IT provisions the laptop. Facilities arranges a desk. Procurement orders the phone. The hiring manager schedules introductions.Individually, each team may perform perfectly. Collectively, the experience can still fail. Because onboarding isn't a collection of departmental tasks. It is the first end-to-end process an employee experiences. The employee doesn't care where HR ends and IT begins. They experience one company. Which means onboarding is not an HR process. It is one of the clearest demonstrations of operational excellence a company will ever give. Or fail to give. Culture is experienced before it is explained Organizations spend enormous effort defining culture. Mission statements. Leadership principles. Core values. Internal campaigns. Most of them are well intended. But people don't believe culture because they read it. They believe culture because they experience it. If your organization says people matter, but nobody notices a new colleague waiting three days for access to essential systems, the employee remembers the experience. Not the PowerPoint. Culture is never communicated as effectively as it is demonstrated. Different people need different beginnings One of the mistakes organizations make is assuming everyone wants the same onboarding experience. Some people want structure. Others want autonomy. Some appreciate detailed guidance. Others would rather receive a laptop, a login and the freedom to explore. Neither approach is right. Neither is wrong. The real challenge is recognizing that equality does not always mean uniformity. Good organizations don't standardize people. They standardize quality while allowing room for individual needs. AI isn't replacing onboarding Every technology conference seems to ask the same question: "What's our AI strategy?" Perhaps a better question is: "Which problems are we still asking people to solve manually?" Ironically, many onboarding activities have already been automated for years.HR-driven provisioning creates accounts automatically. Identity platforms assign access. Workflow engines trigger approvals.The technology already exists. Yet the employee experience often remains fragmented. Not because automation is missing. But because the process itself was never designed as a single experience. That is where AI becomes genuinely interesting. Not as another chatbot. But as an orchestration layer. An assistant that notices a laptop hasn't been delivered before the employee does. That reminds managers of conversations they should have already scheduled. That recognizes dependencies across HR, IT, Facilities and Procurement before they become delays. That answers questions before someone has to ask them. The real opportunity isn't replacing people. It is removing unnecessary friction between the people who are already involved. Why CEOs should care Too often, onboarding is delegated. HR owns part of it. IT owns another. Facilities owns something else. Everyone has responsibilities. Nobody owns the experience. That should concern every CEO. Because onboarding is rarely remembered for a single event. It is remembered as a pattern. A pattern that answers one simple question: "Is this an organization that operates deliberately, or one that reacts continuously?" That first impression influences trust. Trust influences engagement. Engagement influences retention. And retention ultimately influences business performance. This is no longer an HR conversation. It is a leadership conversation. Final reflection Organizations often say that people are their greatest asset. I believe most leaders genuinely mean it. But beliefs become visible through design. The first weeks of employment are not simply about receiving a laptop, signing policies or collecting access rights. They are the first demonstration of how an organization thinks, collaborates and executes. Customers experience your products. Employees experience your organization. Both form opinions remarkably quickly. The difference is that customers can walk away. Employees first decide whether they believe your culture. Only afterwards do they decide whether they want to become part of it.

Strategy is for decision-making. Marketing is for storytelling.

Organizations spend an extraordinary amount of time defining their vision, mission, purpose and values. Workshops are organized. Consultants are hired. Leadership teams debate every word. Marketing departments create beautiful presentations. Posters appear on office walls. And then, on Monday morning, nothing changes. Not because the strategy was poorly communicated. But because it was never designed to help people make decisions in the first place. Too often, organizations treat strategy as a communication tool. I believe it should be treated as a governance tool. The day I realized we were solving the wrong problem Not long ago, I was part of a leadership team redefining the identity of a growing IT services company. The ambition was clear. We wanted to define who we were, what we stood for, and where we wanted to go. Something people could genuinely recognize themselves in. Something that would unite the organization as it continued to grow. At least, that was my expectation. Instead, the conversation quickly became familiar. Customer intimacy. Innovation. Competitive pricing. Quality. The kinds of phrases every organization seems to use because nobody can reasonably disagree with them. None of them were wrong. But I kept asking myself a simple question. What will we do differently on Monday because of this? Nobody seemed able to answer. And that was the moment I realized we weren't creating a strategy. We were creating marketing. A strategy should answer questions before they're asked As organizations grow, decisions become increasingly decentralized.Recruiters hire people they've never worked with. Sales teams negotiate deals without involving the board. Architects design solutions independently. Product managers decide what gets built next. Marketing teams position the company every single day.The larger the organization becomes, the less practical it is for leadership to approve every decision. That is precisely why strategy exists. Not to inspire people. Not to impress customers. Not to look good on a website. But to ensure that hundreds of people make decisions that move in the same direction. A good strategy reduces uncertainty. It doesn't create it. Every strategic principle should have consequences Words like innovation, quality and customer intimacy sound impressive. But they only become meaningful when they influence behavior. Imagine a customer asks for a highly customized solution. Do we build it? The answer shouldn't depend on who happens to be leading the meeting. It should already be implied by the strategic framework. A recruiter finds an exceptional engineer. Technically brilliant. But unlikely to thrive within the organization's culture. Do we hire them? Again, the answer shouldn't require executive intervention. Marketing wants to launch a new campaign. Should we position ourselves as the cheapest provider? The premium specialist? The safest choice? The most innovative? If your strategy doesn't make that decision easier, what exactly is it for? Every strategic principle should eliminate options. If it doesn't help people decide what not to do, it isn't providing direction. Growth demands autonomy When organizations have fifty or a hundred employees, many decisions still happen organically. People know each other. Leadership is accessible. Context spreads through conversation. But as organizations scale, that changes. Information becomes fragmented. Teams specialize. Decision-making becomes distributed. You cannot build a thousand-person organization where every important decision depends on a handful of executives. Nor should you want to. Growth requires autonomy. But autonomy without direction creates inconsistency. That's where strategy becomes essential. Not because larger organizations need more slogans. But because they need better decision-making frameworks. Strategy should reduce debate, not create it One of the simplest ways to test whether a strategic framework works is to observe what happens during disagreement. Imagine a discussion about building custom software for an important customer. If the room immediately splits into opposing opinions, and the only way to resolve the discussion is by asking senior leadership... ...your strategy has already failed. A strong strategic framework should settle many of those discussions before they even begin. Not because it provides answers to every situation. But because it establishes principles that people trust when making difficult trade-offs. The best strategies don't eliminate judgment. They improve it. Storytelling still matters None of this means communication is unimportant. Quite the opposite. Organizations absolutely need stories. Stories create identity. They build culture. They attract customers. They help people feel connected to something larger than themselves. But stories should explain strategy. They should never replace it. Marketing tells people what the organization believes. Strategy determines what the organization actually does. Confusing those two is where many organizations lose their way. The real test The effectiveness of a strategy isn't measured during an annual kick-off. It isn't measured by how many employees can recite the mission statement. And it certainly isn't measured by how attractive it looks on a slide. It's measured in ordinary moments.A salesperson deciding whether to accept a customer. An architect deciding whether to build custom functionality. A recruiter choosing between two candidates. A product team deciding what not to build.Those are the moments where strategy either exists... ...or it doesn't. Closing thought I've seen organizations spend months debating the difference between a vision, a mission, a purpose and a set of values. Ironically, none of those discussions improved a single decision. Because the names don't matter. Whether you call it a strategy, a vision, a purpose or a strategic framework is largely irrelevant. The only question that matters is this: Does it help people make better decisions without asking for permission? If the answer is yes, you've built something that can genuinely guide an organization. If the answer is no... ...you've probably written excellent marketing copy.

Employees don't want another survey. They want to be heard.

Every year, thousands of organizations ask their employees exactly the same question. "How are we doing?" The survey has many names. The name hardly matters. The process is almost always the same. Employees are encouraged to be honest. Leadership promises to listen. The results arrive a few weeks later. A dashboard appears. Scores turn green, orange or red. Trends are compared to previous years and benchmarked against other organizations. And then something interesting happens. The organization starts explaining the results before it has really listened to them. The first reaction is almost never curiosity I've seen the same pattern more than once. Leadership gathers around a table to review the results. Some comments are dismissed as unrealistic. Others are explained away. "It's only a snapshot." "People don't see the full picture." "The reorganization clearly influenced the scores." "One department pulled the average down." Sometimes those explanations are entirely reasonable. But they all have one thing in common. They explain the outcome before they explore it. That subtle difference matters. Because the purpose of listening isn't to defend your decisions. It's to understand why people experienced them differently than you expected. Measuring trust doesn't create trust Organizations often invest significant time and money in measuring employee satisfaction. Ironically, they spend far less time creating the conversations that actually improve it. A survey can tell you that trust is low. It cannot explain why. It certainly cannot rebuild it. Trust isn't restored by presenting another PowerPoint with action points. It is restored when people believe someone genuinely wants to understand their experience. Not to agree with everything they say. But to understand it. We keep scaling the wrong thing One of the biggest mistakes organizations make is assuming that more data automatically leads to better leadership. It doesn't. If anything, leadership becomes more difficult when hundreds of comments are compressed into percentages, averages and trend lines. The individual disappears. The story disappears. The nuance disappears. By the time the executive team receives the report, employees have become statistics. That may be useful for reporting. It is rarely useful for understanding people. Leadership happens at dinner tables Imagine something different. Not another annual survey. Not another company-wide town hall where only the confident voices ask questions. Imagine inviting eight employees to dinner every month. No presentation. No agenda. No managers. No HR representative taking notes. Just a conversation. People from different teams. Different ages. Different backgrounds. Different perspectives. Some who have been with the company for fifteen years. Some who joined three months ago. No expectation that everyone will agree. No expectation that every suggestion will be implemented. Just a conversation where people are free to say what they genuinely think. Not because leadership needs more data. Because leadership needs more understanding. People don't expect perfection One of the biggest misconceptions in leadership is that employees expect every problem to be solved. Most don't. People understand that organizations have budgets. Priorities. Customers. Shareholders. Trade-offs. What they struggle with isn't disagreement. It's silence. If an idea isn't feasible, explain why. If priorities changed, explain why. If you disagree, explain why. Adults can handle disagreement remarkably well. What slowly destroys trust is the feeling that feedback disappears into a system that quietly moves on. The purpose of leadership isn't agreement A good leader doesn't exist to validate every opinion. Nor should they. Leadership requires making decisions that not everyone will support. That's part of the responsibility. But responsibility comes with another obligation. People deserve to understand why decisions were made. Not because it guarantees agreement. Because it demonstrates respect. Being heard and getting your way are two very different things. Confusing the two helps nobody. The survey isn't the problem Employee surveys have value. They reveal patterns. They identify trends. They help leaders recognize blind spots. The problem begins when the survey becomes the conversation. Or worse, when it replaces it. Culture isn't built through anonymous questionnaires. It is built through thousands of interactions in which people discover whether their voice genuinely matters. The best organizations don't treat feedback as an annual event. They make listening part of how they lead. Closing Words Organizations often ask employees one important question every year: "How are we doing?" Perhaps leaders should ask themselves another: "When was the last time I had a conversation where someone felt completely free to disagree with me?" Because culture is not measured by a survey. Trust is not created by a dashboard. And leadership is not demonstrated by publishing an action plan. It is demonstrated by listening before explaining. By responding before defending. And by creating an environment where people continue speaking—not because they expect to win every discussion, but because they know someone is genuinely willing to hear it.