Schutten.Cloud | Where Technology Meets Leadership

The invisible tax of organizational immaturity

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

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

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

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.