Showing Posts From

Leadership

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?"

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.

When integrity costs your seat, but saves your leadership

There’s a version of corporate leadership that looks structured on paper, but in practice runs on something far less formal: influence, alliances, internal politics, and the quiet redistribution of power. I didn’t just observe that system. I operated inside it. And at a certain point, I made a conscious decision about where I stand in it. I held a senior leadership responsibility across technology, engineering, architecture, portfolio and product domains within a large managed services organization in the Netherlands. On paper, authority is defined by role. In reality, authority is defined by whether people choose to respect it. And once that alignment breaks, you are no longer in a stable system. You are in a political one. At that point, there are only two options left: adjust your principles to fit the environment, or stay aligned with your own standards and accept the consequences of that choice. I chose the latter. The shift that starts before it is visible These kinds of transitions rarely start where people think they start. In my case, the shift began with a change in the leadership layer above me. The Managing Director was pushed out after internal disagreement about direction and leadership style. Two senior directors had already aligned in that process. From that moment on, the balance inside the executive team changed. Influence started to outweigh structure. One of those directors—let’s call him Harry, responsible for service delivery and customer engagement—began pushing for organizational redesigns that would significantly increase his span of control. Most of the leadership team did not fully align with that direction. But disagreement has limited impact when escalation mechanisms no longer function as safeguards, but become formalities. At the same time, behaviour that normally would be addressed through direct leadership accountability was handled differently in practice. Escalations. Emotional outbursts. Walking away from responsibility. Periods of absence. And instead of direct intervention, the response was containment: home visits, informal conversations, coffee at kitchen tables. Not necessarily ill-intended. But structurally inconsistent. And that inconsistency sends a very clear signal into any organization: accountability is not applied evenly. Once that signal is embedded, culture changes faster than policy ever can. When you become the inconvenient perspective At a certain point, I became the person who no longer fully aligned with how decisions were being made and how behaviour was being interpreted. Not because I was opposing change, but because I refused to normalize inconsistency in leadership accountability. There was a moment where trust in my position was explicitly questioned by Harry. I asked the rest of the leadership team a simple question: Do you stand behind me? The answer was yes. Privately, there was alignment. Publicly, nothing changed. No correction. No reset. No visible follow-through. That gap is not neutral. That is where organizations start to drift. Because it exposes a fundamental truth: internal agreement does not automatically translate into external action. From that point on, I stopped experiencing the environment as a purely functional system. It became political navigation. When leadership meets cost logic Later, financial pressure added another layer. A proposal emerged that effectively meant structurally assigning low performance ratings in order to reduce headcount through forced exits or settlements. Not based on performance reality, but as a mechanism. I did not participate in that approach. Not selectively. Not conditionally. Not partially. That created tension that unfolded over time. It was often framed as “just how things work in organizations”. I don’t accept that as a default argument. Because there are moments where that sentence is exactly the problem, not the explanation. I escalated the matter to holding level with a simple request: Address it. Don’t ignore it. Don’t leave it in silence. What followed was not resolution, but hesitation. Fear of internal relationships. Fear of political consequences. Fear of reputational friction. And as a result, nothing changed. But nothing is also a decision. Just an unspoken one. The meeting that clarified everything Weeks later, I had a conversation with Garry, a holding-level portfolio director (superior to the Managing Director, in this moment interim Managing Director himself), about the increasing tension between responsibilities, behaviour, and unresolved accountability. The conversation itself was calm. Not emotional. Not escalatory. But it became a defining moment. I stated clearly that I could not continue operating in a system where accountability was inconsistent and where responsibilities were continuously blurred in practice. That was not a complaint. It was a conclusion. Afterwards, a message followed suggesting that the initiative for separation was placed with me. That was not my intention, and I immediately corrected that position. But something had already shifted. Not formally. Structurally. From that point on, one thing became unavoidable: the system was not going to self-correct in a way that aligned with my standards of leadership integrity. And that meant the real question was no longer whether things would change. It was what staying would require from me. The disappearance of a role during absence In the period after the conversation with Garry, I deliberately took a few days of distance from the day-to-day environment. Not as a withdrawal, but to process a moment that was, for me, professionally significant and personally disappointing, and to reflect on next steps with clarity. Shortly after that brief period of distance, I was confronted with an unexpected medical situation and required surgery. That immediately shifted the context from reflection to recovery. While I was away from the organization for medical reasons, the system continued to move. Technology operations, engineering leadership, and all my other responsibilities were split into separate functions. Responsibilities were redistributed. People were promoted into those areas. Reporting lines were changed. None of this involved me. No consultation. No alignment. No conversation. It simply happened in my absence. Returning to something that no longer exists Six months later, I was ready to return. What I returned to was not a paused role. It was a structure that had already been fundamentally redesigned. There was no longer a coherent function to step back into. There was a new Managing Director, who didn't know me, or the role I had. The role still existed on paper once. But not in reality anymore. In that moment, I did not experience confusion. I experienced clarity. In the meantime, conversations had taken place about alternative directions. Senior leadership roles within other entities in the same holding structure. Advisory positions. Holding-level functions. I participated in those conversations. I explored them in good faith. I engaged with them professionally. But underneath it, one thing was already true: I was not looking for a way back in. I was observing whether there was still a meaningful way forward inside the same system. And I concluded there wasn’t. So the decision became simple. Not emotional. Not reactive. Clear. I chose not to return. Not because I had lost something. But because I no longer needed to stay in a system where alignment required compromise on principle. And I choose not to build success in environments where I do not believe in the foundation. I would rather lose on my own terms than win on someone else’s. What this revealed to me What stayed with me was not frustration. It was clarity. Organizations are often far more decisive when redistributing power than when addressing behavioural inconsistency. The same system that struggled to intervene when it mattered most became highly efficient when restructuring in my absence. That contrast is not incidental. It is diagnostic. It shows where real power sits. Not in org charts. But in influence, alignment, and internal stability. Integrity as a leadership position Over time, something became non-negotiable for me. I do not operate from fear. Not in leadership. Not in decisions. Not in how I treat people. My baseline is simple: Remove status, politics, and self-interest, and ask what the right decision is. That is not always comfortable. And it is rarely rewarded in the short term. But I remain convinced of this: integrity is not a moral statement. It is a leadership strategy. Because people may tolerate politics for a while. But they do not forget consistency. And they talk. I still speak to people from that period. Some are still inside the organization, quietly re-evaluating their path. Some have already left. Some were affected by structural changes that felt more political than performance-driven. And many express the same reflection in different words: this is not what leadership should feel like.Final reflection Leadership is not control. It is followership. And followership is never enforced. It is earned. In the end, I did not lose a role. I made a decision about where I would and would not continue to invest my energy. And that distinction matters. Because sometimes leaving is not loss. Sometimes it is alignment. And that is exactly what this was.

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.

The future of managed services is letting go of control

For decades, managed services have been built around a simple idea: The provider builds. The customer consumes. We standardized desktops. We standardized servers. We standardized networks. We defined what users were allowed to do, locked everything else down, and called it governance. It made perfect sense. Technology was complex. Expertise was scarce. Standardization created stability. But if I look at the direction our industry has taken over the past fifteen years, I don't see a story about better infrastructure. I see a story about increasing autonomy. And I don't think we've fully realized what that means for the future of managed services. This didn't start with AI AI is getting all the attention. But the shift started long before large language models. Think about what we've introduced over the last decade. Infrastructure as Code allowed engineers to describe infrastructure instead of manually configuring it. Cloud platforms removed the need to provision hardware. The modern workplace allowed users to work from anywhere, on almost any device. Power Platform enabled business users to automate processes without waiting for IT. Platform engineering is giving development teams self-service platforms instead of ticket queues. These aren't isolated innovations. They all move in exactly the same direction. Every generation of technology removes another dependency on central IT. Every generation gives more capability directly to the people creating value. AI simply accelerates that trend. Customers don't want fewer capabilities They want fewer dependencies. That's an important difference. Organizations don't want to submit tickets to deploy an application. They want to deploy it themselves. They don't want to wait three weeks for an environment. They want it in three minutes. They don't want IT departments approving every workflow. They want to automate their own. For years, many managed service providers viewed this as a threat. I think it's exactly the opposite. Because customers aren't trying to eliminate the MSP. They're trying to eliminate unnecessary friction. The MSP is no longer the builder Imagine a product team in three years. A product owner describes a new customer portal. An AI engineering team generates the application. Another agent provisions infrastructure. Security agents validate policies. Test agents perform functional and performance testing. Deployment agents roll everything into production. None of that feels unrealistic anymore. The interesting question isn't whether this will happen. It's what role the MSP still plays. I don't believe the answer is "building the platform." Because increasingly, customers will do that themselves. Or rather, their AI agents will. The foundation becomes the product If customers can build, deploy and operate faster than ever before, then the value of the MSP shifts underneath the visible work. The platform becomes the product. Not the portal. Not the virtual machine. Not the Kubernetes cluster. The invisible foundation beneath all of it. The landing zones. Identity. Networking. Compliance. Policies. Guardrails. Observability. Knowledge. Recovery. Customers won't ask an MSP to deploy an application. They'll expect an environment where deploying applications is safe by default. That's a fundamentally different business. Governance stops saying "no" Many organizations still think governance means restricting users. Removing permissions. Blocking installations. Limiting change. That approach worked when IT was responsible for every change. It breaks down completely when hundreds of developers, business users and AI agents are continuously creating new workloads. The answer cannot be to review every deployment. It cannot be to manually approve every prompt. And it certainly cannot be to lock everything down. Governance has to evolve from permission to policy. Instead of deciding who may build, we decide the conditions under which anything may be built. Instead of reviewing every change, we continuously validate every outcome. Instead of configuring environments manually, we enforce compliance automatically. Control doesn't disappear. It simply moves to a different layer. The MSP becomes an enabler of autonomy This may be the biggest mindset shift our industry has ever faced. For years, success was measured by how much work the provider performed. Tomorrow, success may be measured by how little intervention is required. The best managed service providers won't be the ones operating every workload. They'll be the ones enabling thousands of safe deployments that never required them in the first place. Their customers will move faster. Developers will have more freedom. Business teams will automate more processes. AI agents will continuously improve solutions. And underneath all of it, the MSP quietly ensures that security, compliance and operational resilience remain intact. Invisible when everything works. Essential when it doesn't. Expertise doesn't disappear Some people interpret AI as the end of expertise. History suggests otherwise. Every abstraction has increased demand for people who understand the layer beneath it. Cloud didn't eliminate infrastructure expertise. Infrastructure as Code didn't eliminate architects. Platform engineering didn't eliminate operations. It simply changed where expertise creates value. AI will do exactly the same. The future MSP won't spend its days deploying resources. It will design the ecosystems in which autonomous systems can safely deploy themselves. Closing thought I don't believe the future of managed services is about doing more work for customers. I think it's about making customers capable of doing more themselves. Not because the MSP becomes less relevant. But because relevance is moving. From operating technology... ...to enabling autonomy. The organizations that understand this will stop asking how AI fits into managed services. They'll realize managed services are being redefined by the same force that is reshaping every other part of IT: giving more control to the people closest to the problem, while ensuring the platform beneath them remains secure, compliant and resilient. That, to me, is what the next generation of managed services looks like.