Leadership, Autonomy, and a Low-Hierarchy Working Culture
A reflections on guidance, responsibility, and trust in high-performing teams
If you need a team lead to show you a path, that can be useful and even enjoyable. If you need a manager to make sure you do your work, however, something is wrong on both sides.
Leadership is direction, not surveillance
A strong team lead helps people see the landscape. They clarify the purpose, expose constraints, connect decisions to the wider system, and help the team discover a credible path forward.
This is leadership as navigation: the lead may know the terrain better, but the team still has to think, choose, and walk the path themselves.
That is very different from management as constant supervision. When an experienced professional needs someone to repeatedly check whether the work has started, whether promises will be kept, or whether quality matters, the problem is no longer a lack of guidance. It is a breakdown of ownership.
At the same time, when a manager assumes that capable people cannot be trusted without continuous oversight, the manager also contributes to that breakdown.
What I learned from working in the Netherlands
I am not a native Dutch person, so I cannot define a single "Dutch mindset." I can only describe the working habits I encountered and came to value while working in the Netherlands.
Many Dutch professional environments are associated with direct communication, relatively low hierarchy, and a willingness to challenge ideas regardless of job title. These qualities are not unique to the Netherlands, and not every Dutch workplace operates in the same way.
The healthiest version of this mindset is not bluntness for its own sake. It is the belief that adults at work should be able to speak plainly, explain their reasoning, question a decision, and accept responsibility for the outcome.
In such an environment, a title does not make an argument correct. A team lead earns influence by providing context, judgment, and consistency. Team members earn autonomy by being dependable, transparent, and willing to surface problems early.
Directness works only when it travels in both directions and remains respectful.
What trust can look like in a Dutch workplace
Trust at work is not merely a pleasant value. It changes how a team operates.
Here are some practical examples I associate with healthy, low-hierarchy teams in the Netherlands:
A junior engineer can question a senior architect's proposal during a design discussion. The response should address the argument rather than invoke seniority.
A team member can say, "I disagree because this creates an operational risk," without that disagreement being treated as disloyalty.
People are generally expected to manage their own working day. The emphasis is on commitments, decisions, and outcomes rather than on appearing continuously busy.
A colleague working four days a week is not automatically considered less committed. The team plans around the person's agreed availability.
When someone has a family commitment or needs flexibility, the default response can be coordination rather than suspicion.
A team lead explains the goal and constraints, then allows the people closest to the problem to decide how to implement the solution.
Bad news is expected early. Saying that a deadline is at risk is viewed as responsible when it gives the team time to respond.
This kind of trust is not blind. It depends on people doing what they promised, communicating when circumstances change, and accepting feedback directly.
Consensus does not have to mean hierarchy
The Netherlands also has a long tradition of consultation and negotiation, often described as the polder model. A Dutch government publication describes this as a tradition in which civil-society organizations, employers' associations, and trade unions were consulted before decisions were made.
That national model is not identical to how a software team works, but the principle is recognizable: involve the people affected by a decision, allow disagreement to become visible, and build enough shared understanding to move forward.
Consensus should not mean that every person has a veto or that decisions take forever. A strong lead listens broadly, makes the decision boundary clear, and closes the discussion when action is required.
Fewer hours do not automatically mean less prosperity
One reason this working culture interests me is that the Netherlands challenges the assumption that prosperity must come from spending the longest possible time at work.
According to Eurostat's 2025 figures, employed people in the Netherlands recorded the EU's shortest average actual working week in their main job: 31.9 hours, compared with an EU average of roughly 36 hours. The national average is strongly influenced by the Netherlands' high level of part-time employment, so it should not be interpreted as every Dutch full-time employee working only 31.9 hours.
At the same time, Eurostat's preliminary 2025 comparison placed Dutch GDP per capita, adjusted for price differences, more than 20% above the EU average. The OECD describes the Netherlands as having a high standard of living, even while warning that recent productivity growth has slowed.
These figures do not prove that shorter hours create prosperity. Trade, infrastructure, education, capital, technology, institutions, labour-force participation, and many other factors contribute to economic performance. But they do challenge a simplistic belief:
More hours at work do not automatically produce more value.
The more useful question is what happens during those hours. Clear priorities, professional autonomy, good tools, candid communication, and mutual trust can allow people to create substantial value without turning visible exhaustion into a measure of commitment.
There is also statistical evidence that autonomy is not merely an impression. Statistics Netherlands reported that 65.9% of employed people aged 15-74 were free to decide how to do their work in 2022.
For me, that is the more interesting connection between culture and performance: trust is expressed through autonomy, but autonomy is sustained through responsibility.
What a team lead should provide
Purpose: Explain why the work matters and what outcome the team is trying to achieve.
Context: Expose dependencies, constraints, risks, and organizational realities that are not visible from an individual task.
A path when needed: Offer experience, options, and a starting direction without removing the team's responsibility to think.
Decision clarity: Make or escalate decisions when the team cannot resolve ambiguity within the available time.
Safety for candour: Make it acceptable to disagree, report bad news, and admit mistakes without unnecessary punishment.
Coaching: Help people improve their judgment so that they need less direction over time, not more.
What every team member should provide
Ownership: Understand the expected outcome and drive the work without waiting for repeated reminders.
Visibility: Communicate progress, uncertainty, delays, and risks before they become surprises.
Independent judgment: Bring possible solutions, not only problems, while remaining open to correction.
Reliability: Honour commitments or renegotiate them early when the facts change.
Constructive dissent: Challenge decisions with evidence and then support the agreed direction.
Accountability: Own mistakes, repair their effects, and improve the system that allowed them.
Autonomy is reciprocal
Autonomy is not the absence of accountability. It is a relationship built on evidence.
A manager gives people room to operate; team members make their work and reasoning visible enough that trust is rational. Neither side should require constant reassurance.
A useful test is whether the team can operate when the lead is unavailable for a few days.
If work stops because every decision requires permission, leadership has created dependency. If commitments disappear because nobody is watching, the team has confused freedom with a lack of responsibility.
A mature team avoids both extremes.
Direct communication instead of unnecessary control
Candid communication should replace much of the need for monitoring.
A team member should be able to say:
I committed to Friday, but the integration risk is larger than I understood. I can deliver safely on Tuesday, or we can reduce scope and keep Friday.
That statement gives the team facts, choices, and ownership. It is far more useful than a green status that turns red at the last moment.
A lead should respond with the same clarity:
Tuesday affects another team, so let us reduce scope and preserve the safety work.
The lead does not need to hover over implementation. They need to make the trade-off explicit and ensure that the decision is understood.
When intervention is necessary
Low hierarchy does not mean the absence of management.
A lead must intervene when risk is hidden, commitments are repeatedly missed, quality is knowingly compromised, or behaviour harms the team. The difference lies in the purpose of intervention: restore clarity and accountability rather than normalize permanent supervision.
The first response should normally be a direct conversation about expectations, evidence, and consequences.
If the problem is missing skill, provide coaching.
If the problem is conflicting priorities, resolve them.
If expectations are unclear, make them explicit.
If ownership remains absent after expectations and support are clear, address it as a performance issue.
One person's performance problem is not a reason to micromanage the entire team.
A practical operating model
Agree on outcomes and boundaries, not a list of movements to monitor.
Make ownership explicit: one accountable person for each meaningful outcome.
Use short, factual progress updates focused on changes, risks, and decisions needed.
Escalate early when a commitment is threatened; do not wait for a status meeting.
Record important decisions and the reasoning behind them.
Review outcomes and learning, not hours of visible activity.
Increase autonomy when judgment and reliability grow; add support when either is missing.
The balanced principle
A good lead can show a path, remove obstacles, and strengthen judgment. A good professional does not need a manager to manufacture motivation or enforce every ordinary responsibility.
High-performing teams emerge when leadership offers context and courage, while individuals offer ownership and candour.
A team lead should help you find the path; they should not have to push you along it.