Leadership Models

The 5 Basics of a Team

anja

Find here valuable insights about the essential and basics for a team to thrive. It is intentionally written from a leadership perspective, not as a team facilitation guide—because this is where the real leverage is, and this article addresses leaders!

Why leaders must get these right—before asking for performance

Most leaders know the model of the five dysfunctions of a team, introduced by Patrick Lencioni in his book The Five Dysfunctions of a Team. What is less often discussed is this: If dysfunctions describe what breaks teams, then basics describe what leaders must actively build and protect.

Teams do not fail because people are unwilling. They fail because leaders underestimate what teams need to function.

Below are the five basics of a team—and why each of them is a leadership responsibility.

1. Trust – The Foundation of Everything

Trust is not about being nice or getting along. It is about psychological safety: the confidence that I can speak openly, admit mistakes, ask for help, and disagree without fear of humiliation or retaliation.

Without trust:

  • feedback becomes political,
  • mistakes get hidden,
  • learning slows to a crawl.

Why this matters to leaders:
Trust does not emerge from team-building exercises. It emerges from leader behavior. Leaders who admit uncertainty, own mistakes, and invite challenge make trust possible. Leaders who perform certainty and perfection quietly kill it.

No trust. No team. Just coordinated individuals.

2. Conflict – Productive Tension Instead of Artificial Harmony

Healthy teams argue. They challenge assumptions, test ideas, and surface differences early—before they turn into passive resistance.

What teams need is not less conflict, but better conflict:

  • focused on ideas, not people,
  • direct rather than whispered,
  • resolved rather than avoided.

Why this matters to leaders:
Leaders set the tone for conflict. If you shut down dissent—intentionally or not—you train people to disengage intellectually while appearing compliant. That is not alignment. That is silence.

If there is no conflict in your leadership team, you are not hearing the truth.

3. Commitment – Clarity Beats Consensus

Commitment does not require unanimous agreement. It requires clarity and closure.

Teams commit when they understand:

  • what has been decided,
  • why it was decided,
  • and what is expected now.

Ambiguity is the real enemy here—not disagreement.

Why this matters to leaders:
Leaders often mistake endless discussion for inclusiveness. In reality, teams need leaders who can listen deeply and then decide clearly. Commitment comes from knowing where we stand, not from endless alignment loops.

Unclear decisions create hesitation. Clear decisions create movement.

4. Accountability – Holding Each Other to the Standard

In strong teams, accountability is not top-down enforcement. It is peer-to-peer ownership. Team members care enough about the shared goal—and about each other—to address missed commitments directly.

Without accountability:

  • standards erode,
  • resentment grows,
  • leaders become bottlenecks.

Why this matters to leaders:
Leaders must model accountability before expecting it. If you avoid hard conversations, your team will too. If you tolerate low standards at the top, they will spread faster than any value statement.

Accountability is not control. It is respect for the team’s purpose.

5. Results – The Discipline to Prioritize the Collective Outcome

Teams exist to achieve results—not individual success stories. When personal goals, departmental metrics, or ego take precedence, team performance suffers.

A focus on results means:

  • putting team outcomes above personal wins,
  • making trade-offs visible,
  • measuring what actually matters.

Why this matters to leaders:
Leaders decide what gets rewarded—explicitly or implicitly. If you praise individual heroics over collective success, do not be surprised when collaboration evaporates.

Teams follow what leaders consistently value, not what they occasionally say.

The Leadership Reality Check

The five basics of a team are not a checklist. They are a system. Each element reinforces the others—and each one depends heavily on leadership behavior.

Here is the uncomfortable truth:
When teams struggle, it is rarely a team problem. It is almost always a leadership signal.

The question is not:

“Why isn’t my team functioning?”

The better question is:

“Which of these basics am I actively strengthening—and which one am I quietly undermining?”

Because teams do not rise to the level of the model.
They rise—or fall—to the level of leadership.

If you want, I can:

  • adapt this for a LinkedIn article with sharper hooks,
  • connect it to agile leadership or the Leadership Spiral,
  • or challenge it further with what happens when leaders skip one of the five.

Responsibility

anja

This is a clear, self-contained description of the Responsibility Process, structured for people who want to understand and take responsibility, written so it stands on its own—no prior knowledge required.

The Responsibility Process – Overview

The Responsibility Process describes how individuals relate to challenges, outcomes, and their own agency. It explains how people respond internally when things do not go as expected—and why some responses generate learning and progress, while others drain energy and stall movement.

At its core, the model distinguishes between below-the-line states, where responsibility is avoided or deflected, and above-the-line states, where responsibility is consciously taken. The shift upward is not about blame or self-criticism; it is about reclaiming choice, ownership, and the ability to act.

For leaders, this process is foundational. The state of responsibility a leader operates from directly shapes trust, culture, and performance across the organization.

The States of Responsibility (from bottom to top)

1. Denial

“This isn’t happening.”

At the lowest state, reality itself is resisted. Problems are minimized, ignored, or dismissed. Data is questioned, signals are overlooked, and uncomfortable facts are avoided.

  • Energy is spent on not seeing.
  • Learning is impossible.
  • Change is blocked before it even starts.

Denial creates organizational blindness—and leaders in denial unintentionally invite repetition of the same issues.

2. Lay Blame

“This is someone else’s fault.”

Here, the issue is acknowledged, but responsibility is externalized. Other people, circumstances, leadership, the market, or “the system” are blamed.

  • Attention moves away from influence.
  • Relationships erode.
  • Justification replaces curiosity.

Blame feels temporarily relieving, but it quietly strips away agency.

3. Justify

“Yes, but here’s why it couldn’t be different.”

In justification, individuals explain why the outcome was inevitable. Reasons, constraints, and exceptions dominate the narrative.

  • The past is defended instead of examined.
  • Energy goes into proving correctness.
  • Improvement remains theoretical.

This state often sounds reasonable—and that makes it particularly dangerous in leadership contexts.

4. Shame

“It’s my fault—and I’m the problem.”

Responsibility turns inward, but in a destructive way. Instead of ownership, there is self-attack. Capability and worth are questioned.

  • Confidence drops.
  • Risk-taking disappears.
  • Responsibility collapses into self-protection.

Shame is not accountability. It is responsibility without power.

5. Quit

“Whatever. I’m out.”

In Quit, responsibility is abandoned entirely. The person may still be physically present, but psychologically they have disengaged: effort drops to the minimum, initiative disappears, and ownership is actively withdrawn.

Quit can show up in two common forms:

  • Visible quitting: resignation, withdrawal, open refusal.
  • Invisible quitting: staying, but emotionally checking out—often called “quiet quitting,” although the real issue is not silence, it is disconnection.

This results into:

  • Energy is conserved through detachment.
  • Problems are avoided rather than faced.
  • Contribution shrinks to compliance—or to nothing at all.

For leaders, Quit is a red flag with a megaphone. It signals that restoring responsibility will require more than motivation—it requires rebuilding trust, agency, and meaning.

5. Obligation

“I have to.”

This is the transition zone. Action happens, but without ownership. Compliance replaces commitment.

  • Work gets done, but energy is low.
  • Creativity is limited.
  • People do what is required—and nothing more.

Organizations stuck here often look functional while slowly losing engagement.

7. Responsibility

“I choose.”

At the highest state, individuals fully own their role in the situation—without blame, excuse, or self-attack. Responsibility is taken as a conscious choice.

  • Focus shifts to learning and impact.
  • Options and influence become visible.
  • Action is intentional and aligned.

This is the state where leadership becomes powerful—not because control increases, but because agency does.

Why This Matters for Leadership

The Responsibility Process makes one thing explicit: responsibility is a state, not a trait. People move through these states moment by moment—especially under pressure.

Leaders who recognize the process can:

  • * intervene without blaming,
  • * model responsibility instead of demanding it,
  • * and create environments where ownership becomes the norm rather than the exception.

The real leadership question is not “Who is responsible?”
It is: “From which state of responsibility am I leading right now?”

Because organizations rise—or stall—at exactly that level.

Organizational Rocket

anja

The Organizational Rocket is a leadership model that explains how organizations move forward with clarity, force, and direction. It makes visible what many leaders sense intuitively: progress is not the result of isolated initiatives, but of alignment between direction, execution, and human energy.

The Front: Direction and Guidance

At the front of the rocket are the guiding elements. They determine where the organization is heading and how it navigates complexity.

  • Vision defines the future the organization is committed to creating. It is a longterm dream and gives orientation and direction.
  • Mission clarifies the organization’s purpose—why it exists and what it contributes.
  • Values set the non-negotiables for behavior and decision-making, especially when trade-offs are hard.
  • Strategy turns intent into direction, making deliberate choices about focus, priorities, and what not to do.

If these elements are unclear or misaligned, the rocket may generate a lot of activity—without meaningful progress.

The Body: Turning Direction into Action

The body of the rocket contains the tactical and operational elements that translate direction into movement.

  • Objectives and Goals create focus and measurability. They connect strategy to everyday decisions and work.
  • Structure and Culture form the internal mechanics of the organization.
    • Structure defines roles, responsibilities, decision paths, and coordination mechanisms.
    • Culture shapes how people actually think, interact, and act—especially when no one is watching.

Structure and culture constantly influence each other. When they are aligned, they reduce friction and enable flow. When they are not, even the best strategy struggles to gain traction.

The Engines: People and Motivation

At the back of the rocket are the engines—the motivation of the people in the organization.

This is where real power comes from. Movement does not originate from frameworks, targets, or processes. It originates from people who are willing to invest energy, take responsibility, and contribute their best thinking.

Motivation fuels commitment, adaptability, and resilience. Without it, the rocket remains technically sound—and stationary.

What This Means for Leadership

The Organizational Rocket makes one thing unmistakably clear: leaders do not create movement by pushing harder. They create movement by aligning direction, enabling execution, and cultivating the conditions in which people choose to engage.

If the organization is not moving, the question is not “Why aren’t people performing?”
The better question is: “What in our direction, alignment, or leadership is draining their energy?”

Because rockets do not move on plans alone.
They move on fuel—and in organizations, that fuel is human motivation.