The AO Method

9 problems the Adaptive Organization helps you solve.

A field guide to the organizational tensions the AO Method diagnoses and redesigns — beyond framework compliance.

01

Problem 01

Framework theater: teams “do agile,” the org stays rigid

Scrum, SAFe, Kanban, and DevOps run perfectly at team level — while decision rights, interfaces, and structure never change. AO reads coherence of the whole system, not compliance of a single practice.

Framework vs. system Operating model design Structural coherence
02

Problem 02

Change that never becomes transformation

New roles, rituals, and reorganizations — without any shift in identity, decision rights, or culture. AO separates surface change from transformation of operating logic.

Decision rights Operating logic Identity shift
03

Problem 03

Strategy that never reaches the front line

Leadership intent stalls before it becomes local decisions and trade-offs. AO uses Hoshin Kanri, catchball, and a vision–strategy–tactics cascade to keep intent traceable to action.

Strategy deployment Hoshin Kanri Vision–strategy–tactics
04

Problem 04

Blurred ownership and executive decision bottlenecks

Escalation paths are unclear and authority pools at the top, creating latency everywhere below it. AO maps decision flow the way VSM thinking maps value flow.

Decision flow Authority mapping Escalation design
05

Problem 05

Local agility, global chaos

Individual teams are fast and adaptive — the enterprise around them stays incoherent. AO’s five-dimension lens (Deliver, Demand, Capacity, Capability, Organisation) names the systemic constraint before prescribing a fix.

Five-dimension diagnostic Systemic constraints Value-stream fragmentation
06

Problem 06

Politeness that hides the real conflict

Nice meetings mask misalignment, conflict avoidance, and undiscussables. AO diagnostics separate surface civility from substantive candor.

Candor vs. politeness Psychological safety Undiscussables
07

Problem 07

M&A integration that stalls after day one

Two systems merge on paper but never truly integrate decision flow or culture. AO applies a Diagnose–Design–Pilot–Scale loop with flocking primitives — alignment, cohesion, separation, avoidance — for day-one coordination.

M&A integration Diagnose–Design–Pilot–Scale Day-one coordination
08

Problem 08

A business that can’t survive without its founder

Growth, expertise, and authority stay trapped in one person. AO redesigns decision continuity over 24–36 months so the system outlives its owner.

Founder dependency Decision continuity Reversible delegation
09

Problem 09

Transformation fatigue and AI-driven change that dictates people

Another initiative, another tool rollout — trust and adaptive capacity erode with each cycle. AO treats ERP and AI as accelerants that must land on redesigned human decision flow, not replace it.

Transformation fatigue Human-agent governance Adaptive capacity

One method, read as a design problem — not a checklist.

The AO Method diagnoses decision flow, culture, structure, and adaptive capacity as one connected system — then redesigns it with you, not for you. Curious where your organization sits? Start with an AO Health Check across the Deliver, Demand, Capacity, Capability, and Organisation dimensions.

Start an AO Health Check

BPMN in Traditional Transformation vs. the AO Method

BPMN 2.0 is a notation, not a method. What differs between a traditional transformation programme and an AO-led one is not whether BPMN is used, but what BPMN is asked to represent, who owns the model, and what decision it feeds.

Section 1

1.Framing the question

In traditional transformation, BPMN is typically deployed as an artifact of control: a standardised description of how work should flow, used to align people to a predefined process, automate steps, or satisfy compliance.

In the AO Method, BPMN is used as a diagnostic and negotiation surface: a partial map of the value and decision flow that helps a system see itself, expose ambiguity, and redesign interaction rules — never as the definition of the organisation.

The comparison below is written from that stance: BPMN is welcome, but it sits inside a design method, not the other way around.

Section 2

2.Side-by-side comparison

Dimension Traditional transformation with BPMN AO Method use of BPMN
Primary purpose Standardise, automate, and control processes; align people to a target “to-be” flow. Reveal decision flow, coupling, and ambiguity; support redesign of interaction rules and authority.
Unit of analysis The process (activities, tasks, gateways, swimlanes). The system: decision rights, feedback loops, informal power, culture, capacity — with process as one signal among several.
Direction of fit People are fitted to the process. Deviations are treated as non-conformance. Processes are organised around people and around what the system needs to sense and decide. Deviation is treated as diagnostic evidence.
Model status Prescriptive. The “to-be” BPMN is the truth the organisation must converge to. Provisional. The BPMN is a hypothesis of current flow; the “to-be” is a bounded experiment, not a target state.
Ownership Process owners, BPM CoE, PMO, and automation/IT. Business is a “stakeholder”. Distributed. The people doing the work co-model with facilitation; sponsors own enabling conditions, not the diagram.
What gets modelled Happy-path activities, exceptions, hand-offs, systems, RACI. The same, plus decision rights, escalation and reversal paths, informal power, and the boundary between reversible and irreversible calls.
Metrics Cycle time, throughput, cost per case, automation rate, SLA conformance. Deliver, Demand, Capacity, Capability, Organisation — the AO five-dimension lens read through the process, not compliance to the drawn flow.
Relationship to autonomy Autonomy is a residual: whatever the process doesn’t specify. Autonomy is designed: reversible, contained decisions stay local; high-blast-radius decisions get explicit guardrails and escalation, and both are visible in the model.
Change logic First-order change: redraw the diagram, retrain, deploy, enforce. Second-order change: shift identity, decision rights, culture, and operating logic. The diagram follows the redesign, not the other way around.
Tooling posture ERP/BPMS/workflow engines as the destination — the model exists to be executable. Tools (BPMS, ERP, AI agents) treated as accelerants that must land on redesigned human decision flow rather than dictate it.
Handling of exceptions Modelled as edge cases; ideally removed or automated away. Treated as information about where the system’s real intelligence lives and where standardisation would destroy adaptive capacity.
Success signal Adherence to the “to-be” model; automation coverage. Healthier flow, shorter decision latency, higher candor, reduced dependency, growing team self-sufficiency — regardless of diagram conformance.
Typical failure mode Framework/process compliance without organisational change: the BPMN is clean, the system is unchanged. Over-modelling: producing rich diagnostics without converting them into bounded redesign experiments.

Section 3

3.Where the two approaches actually diverge

Three points matter more than the rest.

1. What the model is of

Traditional BPM models the work. AO uses BPMN to model the decisions the work requires — who can decide, under what constraints, with what reversibility, and against which feedback. A traditional swimlane says “Legal reviews the contract”; an AO reading of the same lane asks whether that review is a real decision, a rubber stamp, or a substitute for missing authority elsewhere.

2. Prescriptive or provisional

Traditional programmes treat the “to-be” as the answer; deviation is defect. AO treats every “to-be” as an intervention-as-hypothesis: a bounded, reversible experiment against a named constraint, expected to teach the system something and to be redrawn.

3. Who the model is for

Traditional BPMN serves owners of standardisation (PMO, BPM CoE, IT, audit). AO BPMN serves the people who have to make judgement calls inside the flow — it exists to give them a shared picture of coupling, ambiguity, and authority so they can negotiate better, not to remove their judgement.

Section 4

4.When each approach is appropriate

BPMN in its traditional form is genuinely useful when…

  • the work is high-volume, low-variance, and regulated (payments, claims, KYC, statutory reporting);
  • the decision content of each step is low and the value is in consistency, auditability, and automation;
  • the organisation needs a common language with vendors, auditors, or ERP integrators.

The AO reading of BPMN becomes necessary when…

  • decision rights are unclear, disputed, or invisibly held by informal power;
  • the process on paper and the process in practice have diverged, and standardisation would freeze the wrong version;
  • the transformation is coupled to ERP, AI agents, or an operating-model change, so the tool will otherwise dictate the organisation;
  • the organisation is stuck in local-agility / global-chaos, executive decision bottlenecks, or transformation fatigue — the AO problem families where redrawing flows without touching authority reliably fails.

In practice, most serious transformations need both: BPMN as a language for the standardisable layer, AO as the design method for the decision and interaction layer that BPMN cannot represent on its own.

Section 5

5.A practical integration pattern

The pattern I use with clients — including in ATAVA-style multi-partner design and in AO Master Diagnostic engagements — sequences the two deliberately.

  1. AO framing first. Name the system’s purpose, the five-dimension read (Deliver, Demand, Capacity, Capability, Organisation), and the decision-flow hypothesis. This defines what the BPMN should see.
  2. BPMN as diagnostic. Model current flow at macro-chain level (typically 5–7 processes), with swimlanes that include decision authority and escalation, not only functional roles. Treat the model as evidence, not truth.
  3. Read the gap. Compare the modelled flow against decision latency, exception patterns, informal power maps, and the five-dimension signals. Name where standardisation helps and where it would destroy adaptive capacity.
  4. Bounded redesign. Convert the highest-leverage gap into a small, reversible experiment with an explicit constraint hypothesis and exit criteria — not a full “to-be” rollout.
  5. Standardise only what has stabilised. Move a sub-flow into executable BPMN / BPMS / automation only after the human decision flow around it has been redesigned and has held under load. Tool follows design.

This keeps BPMN’s strengths — shared notation, executability, auditability — while refusing its usual failure mode: mistaking a clean diagram for a changed organisation.

In one line

6.Summary

Traditional transformation uses BPMN to fit people to processes. The AO Method uses BPMN to make the decision system visible so processes can be organised around people, and standardises only what the redesign has proven safe to standardise.

Executive Summary

Internal coaching supervision for agile leaders presents a set of challenges that are structurally different from external coaching supervision. When a coach operates inside an organization — whether as an embedded agile coach, a leader-as-coach, or an internal AO practitioner — the layered power relationships of hierarchy, role ambiguity, organizational loyalty, and confidentiality create tensions that can undermine both the quality of coaching and the psychological safety of all parties. This report identifies the unique challenges, maps the dominant power dynamics at play, and provides practical frameworks and strategies to navigate them effectively.


Why Internal Coaching Supervision Is Uniquely Complex

Internal coaches operate in dynamic, constantly changing organizations and face multiple unique challenges not common to external coaches. The core structural tension is the dual role: the internal coach is simultaneously an employee and a coach, which creates inherent conflict around confidentiality, neutral positioning, and organizational loyalty — especially when the organization’s priorities conflict with individual client needs.

For agile leaders specifically, this complexity is amplified. They are often “stuck in the middle,” holding simultaneous pressure from executives above who expect delivery and alignment, and from teams below who need psychological safety, empowerment, and autonomy. Adding a supervision relationship to this structure introduces yet another layer: who holds power over whom, and in whose interest does the supervision serve?

Without proper supervision support, these dynamics lead to predictable failure modes: loss of perspective, enmeshment in organizational conflicts, erosion of coaching quality, and ultimately burnout.


The Power Dynamics at Play

1. Hierarchical Power

Even when an agile coach or leader-coach has no formal authority over a supervisee, their organizational rank creates implicit power. Supervisees may withhold sensitive cases, avoid bringing “failure” stories, or self-censor when they fear that information will circulate in performance evaluations, team assignments, or leadership assessments.

The supervisor’s rank — whether they are a senior leader, an organizational development expert, or a designated internal coach supervisor — carries inherent authority that can “lead to anxiety on the part of the supervisee, and even fear”. The risk is that supervision becomes an evaluative relationship rather than a reflective one, shutting down the very vulnerability that makes supervision valuable.

2. Dual Relationships and Role Confusion

Coaching within the same organizational system heightens power dynamics even when formal authority does not exist. When an agile leader coaches their own team members and simultaneously receives or provides supervision, multiple relationship layers overlap. Supervisees may be unsure which “hat” is being worn — colleague, coach, supervisor, or peer — leading to confusion, mistrust, and compromised safety.

Dual relationships introduce specific risks:

  • Blurred boundaries: Harder to keep interactions within the contracted scope of the coaching or supervision relationship.
  • Conflicts of interest: The agile leader’s organizational role may unconsciously influence how they coach or what they bring to supervision.
  • Loss of objectivity: Pre-existing knowledge of colleagues or organizational politics makes neutral presence difficult.
  • Unconscious games: Leader-coaches are susceptible to parent-child dynamics with team members, which can replicate in the supervision relationship itself.

3. Confidentiality Under Organizational Pressure

Confidentiality is both a practical and ethical challenge in internal supervision. Clients (coachees or leaders in supervision) may reasonably question whether their reflections could influence promotion decisions, performance reviews, or team restructuring — even if the supervisor has no formal mandate to share information.

The question is not only “what is kept confidential” but “is absolute confidentiality even possible inside an organization?”. When supervision is embedded in an internal coaching program, there is often an implicit expectation from the organization (sponsor) that some accountability information will flow back. Without explicit contracting, this ambiguity corrodes trust and safety.

4. Systemic Enmeshment and Loss of “Balcony” Perspective

Internal agile coaches and leaders risk becoming so entangled in the organizational system that they lose the “balcony view” necessary for effective coaching and supervision. This manifests as:

  • Normalization of toxic dynamics (accepting dysfunction as “just how things work here”)
  • Unconscious collusion with leadership narratives that serve the organization at the expense of teams
  • “No-one speaking truth to power,” where coaches internalize a culture of silence around senior-level bullying or political behavior

The longer the coach is embedded in the system, the more their perception becomes shaped by the system’s own assumptions, making the external supervisor (or external supervision element) essential.


Key Challenges in Practice

ChallengeInternal ContextSupervision Risk
Dual loyaltyCoach serves both organization and individualSupervision colluded into organizational agenda
ConfidentialityInformation circulates within same systemCoachees self-censor; cases not fully explored
Power imbalanceSupervisor may be senior in hierarchySupervisee withholds vulnerability; fear of evaluation
EnmeshmentCoach absorbed into system dynamicsBlind spots normalized; balcony view lost
Role confusionMultiple hats worn simultaneouslyBoundaries erode; psychological safety compromised
Ethical ambiguityNo clear separation between coaching, management, consultingStandards drift; harm risk increases

Strategies for Navigating Power Dynamics

1. Name the Power Dynamic Explicitly

The first and most important step is to make power dynamics visible rather than leaving them latent. At the start of a supervision relationship, the supervisor should explicitly acknowledge:

  • The natural hierarchy within the relationship and what it does or does not imply
  • How the supervisor and supervisee feel about sharing vulnerable or uncertain topics in this organizational context
  • Moments when the supervisor recognizes they are “leading” rather than co-exploring

Naming the dynamic removes its invisibility and creates space for open, honest dialogue. This is a relational act, not a procedural one: it must be revisited regularly, not just stated once at contracting.

2. Invest Deeply in Tripartite Contracting

Arguably, the most common cause of problems in organizational coaching — and therefore in supervision — is a mismatch of expectations at the contracting stage. For internal coaching supervision involving agile leaders, a tripartite contract between supervisor, supervisee-coach, and organizational sponsor is essential.

The C.O.N.T.R.A.C.T. model offers a structured map:

  • C – Context & Purpose: Why is supervision happening? Who commissioned it and why?
  • O – Outcomes & Objectives: What does the supervisee-coach want to develop?
  • N – Norms & Ethics: Which ethical framework applies (ICF, EMCC, AC)? How will ethical dilemmas be handled?
  • T – Terms & Practicalities: Frequency, format, duration, virtual or in-person
  • R – Roles & Responsibilities: What does the supervisor do? What does the supervisee bring?
  • A – Agreements on Confidentiality: What is shared with the sponsor, and in what form?
  • C – Closure: What are the review points and exit conditions?

In the three-way contracting meeting with the organizational sponsor, key commitments to establish include: that the supervisor will not provide performance feedback to the sponsor unless explicitly agreed with the supervisee; that coaching insights will not be used in evaluations; and that the sponsor’s role is support, not oversight.

3. Use the 7-Eyed Model as a Systemic Navigation Tool

The Seven-Eyed Model (Hawkins & Shohet) is one of the most widely used frameworks in coaching supervision and is directly applicable to agile leadership contexts. It offers seven lenses through which to examine what is happening in the supervision space:

  1. The client and their story — What is the coachee (the agile team or leader) actually bringing?
  2. The coach’s interventions — How is the agile coach/leader working with the situation?
  3. The coach–client relationship — What dynamics exist between coach and coachee?
  4. The coach’s own process and feelings — What is being triggered in the supervisor?
  5. The supervisory relationship — What is happening between supervisor and supervisee right now?
  6. The supervisor’s own process — What is the supervisor bringing from their own system?
  7. The wider organizational context — How is the organizational system shaping everything above?

For agile leaders, Eye 7 (the organizational system) is particularly important and often under-examined. Using this lens helps supervision avoid being only a “case clinic” and instead examines how structural power, culture, and transformation pressures shape both the coaching work and the supervision conversation.

4. Separate Supervision from Performance Management

A clear structural distinction must be made between supervision (developmental, reflective, confidential) and performance management (evaluative, organizational, hierarchical). Without this separation:

  • Internal coaches will self-censor and bring only “safe” cases to supervision
  • The supervision space becomes contaminated by organizational politics
  • Ethical dilemmas will not surface until they become crises

In practice, this means the supervisor should hold no formal evaluative power over the supervisee in the organizational hierarchy. Where this is not structurally possible — as in many lean agile organizations — the supervisor must make the developmental intent of supervision explicit through contracting, re-contracting regularly, and modeling the humility and vulnerability they wish the supervisee to bring.

5. Introduce External Supervision as a Complement

For cases involving toxic dynamics, conflicts of interest, or deep enmeshment, external supervision is often the most responsible option. External supervisors bring:

  • A fresh, independent perspective untainted by organizational history
  • Ability to challenge assumptions that internal supervisors may share
  • A safe container for ethical dilemmas that are “forbidden to discuss with a colleague”
  • Accountability and quality assurance outside the organizational reporting structure

A blended model — internal group supervision for routine developmental reflection, plus periodic external individual supervision for high-complexity cases — offers both accessibility and independence.

6. Build Psychological Safety Through Preparation and Co-Creation

Group coaching supervision in agile contexts faces particular challenges: differences in coaching styles, personalities, cultural nuances, and power differences between participants can lead to conflict, misunderstanding, and rupture. Strategies to address this include:

  • Psychological contracting at setup: Establish clear ways of working, including confidentiality norms, respect, and active listening, before any case work begins.
  • Surfacing rank and privilege: Explicitly discuss whether power, rank, or organizational proximity may be affecting participation.
  • Preparation rituals: Ask supervisees to reflect on their practice, identify a challenge, and set a session intention before each meeting.
  • Regular feedback loops: Build in structured feedback — not only on cases, but on the group’s own dynamics and the supervisor’s facilitation.

7. Model Supervisory Reflexivity

Supervisors have a responsibility to model how power can be used constructively. Supervisors who demonstrate humility, curiosity, and openness — including naming their own uncertainties and blind spots — create permission for supervisees to do the same. This is especially important in agile cultures that espouse transparency and learning but often struggle to enact these values at the leadership level.

The supervisor of supervisors (meta-supervision) dimension is equally important: supervisors of internal agile leader coaches should themselves receive supervision, ensuring that the reflective practice loops outward rather than terminating at the internal layer.


Specific Risks in Agile Transformation Contexts

Agile transformations add layers of complexity not present in standard organizational coaching:

  • Framework pressure: Agile leaders are expected to adopt and role-model specific practices (Scrum, Kanban, OKRs). Supervision cases may be unconsciously filtered through “are we doing agile right?” rather than “what is this person actually needing?”
  • Sponsor–coach collusion: An agile coach acting as internal supervisor may reinforce an organization’s agile “story” rather than challenging it, especially when the transformation is tied to the coach’s own professional identity or the AO Method being implemented.
  • Restorative underinvestment: Agile transformations are high-pressure; the restorative function of supervision (processing stress, role conflicts, emotional load) is often neglected in favor of the formative function (skill building). This increases burnout risk.
  • Ethical ambiguity in hybrid roles: An agile leader simultaneously coaching team members, attending retrospectives, writing performance reviews, and influencing roadmap priorities cannot maintain clean coaching boundaries without explicit, ongoing contracting.

Recommendations for AO Method Practitioners and Internal Agile Leaders

  1. Contract explicitly for power: At every new supervision relationship, name the organizational power hierarchy and agree on what it does and does not mean for the supervision space.
  2. Adopt a systemic model: Use the 7-Eyed Model or equivalent to ensure supervision addresses the organizational context, not only the coach–coachee dyad.
  3. Separate evaluation from reflection: Ensure that the supervisor holds no evaluative function over the supervisee in the same period and context as the supervision relationship.
  4. Use tripartite contracting: Always involve the organizational sponsor in initial contracting to align expectations on confidentiality, outcomes, and accountability — and document agreements explicitly.
  5. Blend internal and external supervision: Reserve internal supervision for formative and peer-reflective work; use external supervision for restorative, ethical, and high-complexity cases.
  6. Revisit contracts regularly: Power dynamics, organizational contexts, and role configurations shift continuously in agile organizations; supervision contracts must be living documents, not one-time agreements.
  7. Model vulnerability from the top: Leaders who receive and are transparent about their own supervision involvement normalize reflective practice and signal genuine commitment to psychological safety across the system.

There are a few recurring “families of problems” where the AO method, as an organizational operating system, is especially useful in practice.

To keep it concrete, here is a first cut, phrased as problems leaders actually feel:

1. Chronic misalignment between strategy and operations

Many organizations have a nice strategy deck, but daily work is driven by local priorities, legacy structures, and firefighting.
AO helps by:

  • Making the value-creation pathways explicit (who serves whom, with what promises, via which capabilities).
  • Creating clear, minimal service contracts between units, so strategic intents are translated into concrete, testable expectations.

In other words, AO can address the “strategy theater vs. operational reality” gap.

2. Silo conflicts and unclear accountabilities

Classic functional or project structures often create blurred ownership: multiple teams touching the same domain, but no one truly accountable for outcomes.

AO helps by:

  • Defining stable, end-to-end service domains (or platforms) with explicit outcome ownership.
  • Clarifying what is “mandatory” vs “optional” in collaboration, reducing endless negotiation and escalation.

So, AO is good at reducing political friction and making collaboration more contractual and transparent.

3. Scaling agility without scaling chaos

Many organizations “go agile” in teams, but fail to design the surrounding system (governance, interfaces, escalation paths), leading to local agility and global chaos.

AO helps by:

  • Designing an integrated architecture of units where autonomy is bounded by clear service expectations and economic logic.
  • Providing patterns for how to scale (replicate, split, federate, or platformize) when demand or complexity grows.

It’s particularly strong when the question is: “We have agile teams; how do we make the whole organization behave coherently?”

4. Overloaded leadership and decision bottlenecks

Executives often become bottlenecks because every exception, escalation, or cross-silo issue ends up on their desks.

AO helps by:

  • Distributing decision rights along value flows and service domains, rather than hierarchy alone.
  • Creating explicit escalation and arbitration mechanisms embedded in the design, so fewer things require heroic leadership intervention.

This tends to reduce cognitive overload at the top and increase local problem-solving capability.

5. Transformations that never “stick”

Many change programs launch with enthusiasm and then regress to old patterns once the consultants leave.

AO helps by:

  • Focusing on structural and contractual changes (how work is organized, who serves whom, which promises are made) rather than only mindset or process coaching.
  • Giving a stable reference model that leaders can continuously refine, instead of a one-off framework that fades after the project.

So it is well-suited to organizations that have “transformation fatigue” but still need deep, systemic change.

Distinguishing between local autonomy and organizational risk is one of the trickiest balances in AO work. The goal is not to choose one over the other, but to make the boundary explicit so teams can move fast where it is safe and slow down where it genuinely matters.

The core distinction

  • Local autonomy is the freedom of a team to decide how they work, what they prioritize within their mandate, and which local trade-offs they make — without seeking permission upward.
  • Organizational risk is exposure that, if a decision goes wrong, spills beyond the team: legal, financial, safety, reputational, security, or systemic consequences that affect others who did not make the call.

The principle: autonomy should be wide where blast radius is small and reversible; constrained where blast radius is large and irreversible.

A simple test for any decision

Ask three questions:

  1. Reversibility — Can we undo this within days at low cost? (Reversible = lean toward autonomy.)
  2. Blast radius — Does the downside stay inside the team, or spill onto customers, other teams, regulators, or the brand? (Contained = autonomy; spreading = shared/escalated.)
  3. Correlation — If every team made this same call independently, would the aggregate create a systemic problem? (e.g., each team picking its own data-handling approach creates a compliance risk no single team can see.)

If all three point local, delegate fully. If any point to wide, irreversible, or correlated risk, that decision needs guardrails or escalation.

Decision categories

CategoryRisk profileWho decides
Reversible, containedLowTeam, full autonomy, no notification
Reversible, visible to othersLow–mediumTeam decides, informs affected parties
Hard to reverse, containedMediumTeam decides within explicit guardrails
High blast radius or correlatedHighEscalate or decide against a shared policy
Legal / safety / security / brandHighAlways governed by org-level boundaries

How to make the boundary work in practice

  • Set guardrails, not approvals. Instead of “ask before X,” define the boundaries inside which teams are free: budget limits, risk appetite, mandatory standards (security, data, accessibility), and the few things that always require escalation. Within those lines, autonomy is real.
  • Name the few non-negotiables explicitly. Most organizations have a small set of genuine org-level risks. Make them a short, visible list rather than a vague sense that “leadership might not like this.”
  • Distinguish risk type from risk size. A team can have full autonomy over a high-effort decision that carries low organizational risk. Effort and risk are different axes.
  • Push the decision to where the knowledge is — unless the risk is shared. The team usually understands the local context best. The exception is when the consequences land on people who weren’t in the room.
  • Make correlated risk a leadership job. No single team can see that “everyone is independently doing the same risky thing.” Surfacing and governing correlation is precisely what the center is for.

Common failure modes

  • False autonomy — teams are told they’re empowered, but every meaningful decision quietly gets second-guessed. Result: people stop deciding.
  • Risk laundering — large organizational risks are pushed down to teams that lack the authority or visibility to carry them, so the org “feels agile” while exposure accumulates.
  • Blanket caution — treating all decisions as high-risk, which kills speed for the 90% that are actually reversible and contained.
  • Invisible boundaries — the line between “your call” and “needs escalation” exists only in leaders’ heads, so teams hesitate or guess.

A practical move

For one team this week, take five recurring decisions and sort them on two axes: reversibility (easy ↔ hard to undo) and blast radius (contained ↔ spreads beyond the team). Decisions in the easy/contained corner get full autonomy, made explicit. Decisions in the hard/spreading corner get a named guardrail or escalation path. The middle gets autonomy within stated limits. Write the result down where the team can see it — that visible map is usually what converts vague empowerment into confident, fast local decisions.

The aim is a system where teams rarely have to ask “am I allowed?” because they already know exactly where their freedom ends and shared risk begins.

Acknowledgement: Many thanks to my friend and partner in business, Pierre Hervouet, who introduced me to Hum Hum.

Imagine you are paid to solve a dull task: you get a sheet of random letters and must circle specific pairs, then hand the sheet to an experimenter. The pay decreases with each sheet you complete, so each new sheet is a slightly worse deal.

Now change only one thing: how the experimenter treats your work.

  • In condition 1 – Hum! Hum! – the experimenter takes your sheet, looks at it briefly, mutters a neutral “hum hum,” and places it on a pile.
  • In condition 2 – Indifference – the experimenter takes the sheet without looking at it and silently places it face down on a pile.
  • In condition 3 – Shredder – the experimenter takes the sheet and feeds it directly into a shredder without looking at it at all.

Nothing else changes: same task, same pay schedule, same room.

What happens?

  • In the Hum! Hum! condition, participants on average complete more sheets than in the other two conditions and accept lower pay before they stop.
  • In the Indifference condition, people give up earlier: if nobody even glances at the work, its meaning collapses.
  • In the Shredder condition, motivation drops dramatically: watching your work destroyed in front of you is a powerful signal that it doesn’t matter.

The “Hum! Hum!” – no praise, no speech, just a brief acknowledgment – is enough to change behavior and perceived value of the work.

This logic is directly inspired by Dan Ariely’s studies on acknowledgment and meaning at work, in which he showed that the presence or absence of minimal recognition can strongly affect how much effort people invest, even when financial incentives are fixed.


The invisible employee: recognition as a human need

The lesson from these experiments is simple and uncomfortable: people do not work only for money or rational trade‑offs. They also work for something far more fragile: the feeling that their effort is seen and that it counts for someone.

This need for recognition is not a soft “nice to have”; it is a core human and social need:

  • Contemporary leadership and motivation research shows that recognition sits alongside inclusion, fairness, and caring as a fundamental psychological need in organizational life.
  • Large‑scale engagement studies repeatedly find that employees who feel appropriately recognized show higher productivity, profitability, and lower absenteeism and turnover.
  • Leaders rated highly on recognizing others are consistently evaluated as more effective overall, and their teams are more engaged and committed.

In my own slide deck on recognition, I summarize some of this evidence: engaged employees contribute to 20% higher productivity and 20% higher profitability, alongside significant reductions in absenteeism and turnover. Companies that systematically recognize people report up to a 3x higher return on equity compared to those that do not.

And yet: a survey snippet in the same deck shows that around 75% of managers do not systematically apply acknowledgment practices, despite this clear value.

That gap between “we know it matters” and “we don’t do it” is where the human paradox emerges.


Why being acknowledged feels both good and… threatening

When I run the “Hum! Hum!” exercise and follow‑up practices, I ask participants:

“What emotions do you associate with being acknowledged?”

The answers cluster around two poles:

  • Positive: happy, proud, inspired, moved, valued, touched.
  • Uncomfortable: embarrassed, awkward, self‑conscious, suspicious, shame, fear of appearing cocky, fear of jealousy.

In other words, people:

  • Deeply enjoy and need acknowledgment – they feel more valued and connected when they receive it.
  • Simultaneously feel exposed, vulnerable, and socially at risk in the moment they are seen.

Social psychology and leadership research help explain this tension:

  • Recognition satisfies esteem and belonging needs, but it also increases visibility and potential judgment, which can threaten perceived psychological safety.
  • Many professionals have internalized rules like “don’t brag,” “don’t stand out,” or “don’t make others jealous,” which create an internal “little voice” that polices their desire to be seen.
  • In cultures where recognition is scarce or politicized, people learn that visibility is dangerous: attracting envy, scrutiny, or extra expectations, so they prefer to keep their heads down, even while craving acknowledgment.

This is the paradox:

“I want to be recognized – but I also want to be safe.”

So people adopt subtle hiding strategies: they downplay their contribution, deflect praise, or prefer to be invisible rather than risk awkwardness, jealousy, or accusations of being “cocky.”


Recognition, hiding, and organizational systems

Look at the three experimental conditions not just as lab tricks but as metaphors for real organizational patterns:

  • Hum! Hum! organizations
    Work is seen, even briefly. Deliverables are acknowledged. People’s names are attached to contributions. Regular rituals (reviews, retrospectives, kudos boards) make contributions visible. In such systems, people are more willing to invest discretionary effort and even accept short‑term trade‑offs because their work carries meaning beyond the paycheck.
  • Indifference organizations
    Work is technically accepted but rarely acknowledged. Reports disappear into email black holes. Stakeholders barely look at deliverables. Performance reviews focus mainly on gaps. People feel like “invisible employees.” The system doesn’t shred their work, but it quietly erases the emotional value of their effort through silence and neglect.
  • Shredder organizations
    Work is openly invalidated, discarded, or undone without explanation. Decisions shift abruptly, projects are canceled without acknowledgment of the effort invested, and leadership re‑writes history without crediting those who tried. Here, the message is clear: “Nothing you do here matters for long,” and motivation collapses.

In my deck, I explicitly connect recognition to Agile practices and culture:

  • Agile is described as alignment, focus, value, feedback, collaboration, communication, frequent delivery, and visibility.
  • Rituals such as review meetings, retrospectives, kudos systems (e.g., KudoBox), and celebration practices are presented as structural supports for acknowledgment.

These are not “soft” add‑ons. They are the systemic equivalent of the “Hum! Hum!” condition: repeating patterns where the organization briefly but clearly says, “We see this. It matters.”


The traps of acknowledgment: flattery, formulas, and the T2P2S recipe

Because recognition is so powerful, it can also go wrong very quickly.

In the slides, I name several traps:

  • Flattery – empty, generalized praise (“You’re amazing!”) that feels manipulative rather than genuine.
  • The sandwich – “good–bad–good” feedback that people recognize as a technique, not a real acknowledgment.
  • Generic thanks – over‑used phrases (“Great job, team!”) with no connection to the person or the actual effort.

To counter these, I propose a simple recipe, borrowing the metaphor of a taco casserole:

T2P2S – Timely, Personal, Proportional, Sincere, Specific

Well‑crafted acknowledgment:

  • Is Timely – close to the event, when the effort is still fresh.
  • Is Personal – addresses the person, not an anonymous group.
  • Is Proportional – neither over‑nor under‑done compared to the effort and impact.
  • Is Sincere – aligned with what you truly think and feel, not just a technique.
  • Is Specific – naming the concrete behavior or contribution that mattered.

This recipe helps leaders avoid performative praise and instead deliver acknowledgment that truly feeds the human need for recognition without triggering as much suspicion or discomfort.


From experiment to practice: design choices for leaders

So what can leaders, coaches, and organizations do with all this?

  1. Recognize the need behind performance
    Stop treating recognition as a bonus after “real work” and start seeing it as a non‑negotiable nutrient for effort, learning, and resilience.
  2. Design Hum! Hum! moments into the system
    • Short, regular review rituals where work is explicitly seen.
    • Recognition “grooming” sessions where leaders and peers intentionally look for contributions to acknowledge (not just problems).
    • Simple tools like Kudo cards or digital kudos walls embedded into normal workflows.
  3. Respect the ambivalence
    When people feel uncomfortable receiving acknowledgment, don’t pathologize it. It reveals the double bind between craving recognition and wanting safety. Offer different channels: public, small group, one‑to‑one, written – so individuals can choose what feels safe enough.
  4. Model healthy vulnerability as a leader
    Leaders can normalize both sides of the paradox by:
    • Openly acknowledging others and explaining why it matters.
    • Allowing themselves to be acknowledged without deflecting or turning it into a joke – simply saying “Thank you, it means a lot” already changes the norm.
  5. Audit where you are: Hum! Hum!, Indifference, or Shredder?
    Use Ariely’s logic as a diagnostic lens:
    • Where in our organization do people feel acknowledged (Hum! Hum!)?
    • Where do we practice silent indifference?
    • Where do we shred people’s work – cancel projects, reverse decisions, ignore efforts – without any acknowledgment of what was invested?

The answers will often explain more about engagement, turnover, and “quiet quitting” than any formal strategy document.


Why this matters now

In a world of constant transformation, agile initiatives, and pressure for performance, the temptation is to optimize everything except the human experience of being seen. Yet the “Hum! Hum!” experiments remind us that people’s willingness to go the extra mile – to learn, to adapt, to stay – depends profoundly on whether someone, somewhere, genuinely recognizes their effort.

At the same time, the emotional data from acknowledgment exercises shows that recognition is not frictionless: it touches shame, jealousy, fear of exposure, and complex histories around value and worth.

If we want agile, adaptive, and humane organizations, we must learn to hold this paradox:

  • Designing systems that generously acknowledge contribution.
  • Creating cultures where it also feels safe to be seen.

Because in the end, what keeps people engaged is rarely the salary band alone. It is the quiet, repeated message:

“I see you. What you do matters here.”

That is the true power – and responsibility – of acknowledgment.


Selected references

  • Ariely, D. (2012). The (honest) truth about dishonesty: How we lie to everyone—especially ourselves. (Chapter on meaning and acknowledgment in work; experimental evidence on the impact of recognition on motivation).
  • Ariely, D., Kamenica, E., & Prelec, D. (2008). “Man’s search for meaning: The case of Legos.” Journal of Economic Behavior & Organization. (Foundational experimental work on acknowledgment and meaning at work).
  • Gostick, A., & Elton, C. (2007). The Carrot Principle: How the best managers use recognition to engage their people, retain talent, and accelerate performance. (Global studies on recognition, engagement, and performance; cited as “The Carrot Principle” in the slide deck).
  • Gostick, A., & Elton, C. (2010). The Orange Revolution: How one great team can transform an entire organization. (Team‑level impact of recognition and positive culture).
  • Littlefield, C. – AcknowledgementWorks. (Contributions to acknowledgment practices, exercises, and emotional mapping around being acknowledged; credited in the slide deck).
  • “Recognition (Acknowledgement) – The Neuroscience of Recognition.” The Happiness Index (2024). Overview of how acknowledgment affects wellbeing, engagement, and business outcomes.
  • “The Power of Personalized Leadership: Addressing Team Members’ Unique Psychological Needs.” BrainFirst Institute (2025). Links between recognition, psychological needs, and leadership behavior.
  • “Leadership as a determinant of need fulfillment.” Frontiers in Psychology (2024). Discusses how leadership behaviors satisfy core psychological needs such as relatedness, competence, and autonomy.
  • “Psychology of Employee Recognition.” Team Brandscape (2025). Summarizes research on how and why recognition practices influence engagement and retention.

(Experimental and practice‑oriented content, figures, and exercises referenced in this article are drawn from the slide deck “Recognition – The philosopher’s stone of every improvement in the Agile team and beyond.”)

A few months ago, I was invited into a family‑owned manufacturer in the German‑speaking part of Switzerland. They produce highly customized mechanical components, around 250 employees, with customers across Europe. They had experienced several strong years. During this time, they expanded into new markets. They also added a layer of “project managers” to coordinate larger orders. On paper, this looked like professionalization. In practice, lead times were slipping, quality incidents were creeping up, and nobody could quite explain why.

When we mapped the journey of one “typical” strategic order, the pattern became visible. Sales closed a deal with a tight delivery promise, then handed it to a project manager. The project manager, sitting between departments, chased engineering for drawings, then production for slots, then purchasing for critical parts. Each department optimized its own queue; nobody owned the end‑to‑end flow. Escalations landed on the COO’s desk, who spent evenings manually re‑prioritizing orders to keep key customers happy.

From an AO perspective, the problem was not “lazy people” or “weak project managers”. The system was missing a real swarm around strategic orders. We brought together a small cross‑functional group. It included one person from sales, one engineer, one production planner, and one quality lead. We gave them explicit authority over a handful of critical orders for six weeks. They met daily for 15 minutes. They made decisions on the spot. They adjusted priorities based on what they saw, not on departmental queues.

The numbers were interesting, but the real shift was felt. Lead times for those orders dropped. More importantly, the COO’s escalations fell sharply. The team started spotting structural issues in planning. They also noticed supplier choices that had never surfaced before. At the end of the experiment, one of the production supervisors shared their thoughts. They said: “For the first time, I see the same picture as sales. I see the same picture as engineering. We can actually act on it together.” That sentence contains the AO question I invite you to sit with. Where in your organization would a small, empowered swarm around real work make more difference than one more coordination layer?

Article content

Try this AO move this week

You don’t need a reorg to start working with AO. The simplest entry point is to look honestly at how one important piece of work really flows across your organization. It is important to understand how it truly flows, not just how the process diagram says it flows.

  1. Pick one meaningful case. Choose something that matters. Consider Onboarding a strategic client, delivering a key feature, resolving a major incident, or implementing a new regulation. The higher the stakes, the more clearly you’ll see your real system at work.
  2. Map the real journey. On one page, list who actually touches this work from first signal (“we should do this”) to “truly done”. Record the actual steps in order. Include side chats. Add ad‑hoc spreadsheets. Also, consider unofficial approvals that never appear on a formal process map.
  3. Mark the friction points. Circle 1–2 places where work waits, bounces, or gets escalated – handoffs between teams, unclear ownership, conflicting priorities, repeated rework. Add a word or two on what seems to be happening at each hotspot.
  4. Ask the AO swarm question. For each hotspots, ask: “If we formed a small swarm around this work, who should be in the initial conversation?” Who should be involved from the start?” In a software company, this might include product, design, engineering, and operations. In a hospital, it might involve clinician, nurse, admin, and IT. The principle is the same. Bring key perspectives to the work together. Do this instead of pushing the work through them in sequence.
  5. Run one small swarm experiment. For the next one or two instances, invite that swarm into a short joint planning session. Alternatively, hold a 15‑minute daily touchpoints. Allow them to make decisions for this narrow slice of work. Do this without creating a new permanent committee or governance layer.

If you do this, don’t just track throughput. Pay attention to what people start noticing and learning. They do this once they share a single, end‑to‑end picture of the work. That’s often where AO becomes a lived practice rather than a slide.

Workshop’s outcome

Executive Summary

This document consolidates a comprehensive workshop on building sustainable organizational culture. It focuses on long-term strategy and continuous improvement loops. The workshop also highlights leadership development. Additionally, it addresses embedding culture into talent management practices. The session emphasized practical frameworks, diagnostic tools, and real-world implementation challenges faced by leaders attempting cultural transformation.

Workshop Objectives and Structure

The session aimed to share practical long-term strategies for sustainable culture development through conversation, case studies, and theoretical frameworks. Key focus areas included:

  • Exploring continuous improvement and innovation loops
  • Aligning leadership development with cultural goals
  • Embedding culture into talent management practices
  • Understanding the role of leaders in cultural sustainability

The workshop format combined presentation, interactive discussion, and practical tool-sharing. Planned exercises (Kata) are scheduled every two weeks. These are for focused practice on specific cultural angles.

Understanding Sustainable Culture

Why Sustainable Culture Matters

Sustainable organizational culture drives long-term performance, retention, innovation, and reputation. Key benefits include:

  • Reducing costs associated with poor decisions and talent loss
  • Preventing culture drift as organizations grow or shift
  • Enabling scalable, repeatable behaviors that support strategy
  • Creating environments where people want to stay and contribute

Essential Elements of Sustainable Culture

Clear Values Translated into Observable Behaviors

Values must be explicit and understood uniformly across the organization. As emphasized in Kanban methodologies: “make everything implicit explicit and talk about it.” For example, if a company values “working together,” actual collaborative behaviors must be observable—not just stated commitments.

Continuous Feedback Loops and Learning Mechanisms

Organizations need structured post-mortems, post-incident reviews, and customer feedback loops. Regular retrospectives help teams discuss what happened and extract lessons learned. Proactive customer follow-up after delivery creates valuable connection points beyond “no news is good news” silence.

Leaders Who Model and Are Held Accountable for Cultural Behaviors

Leadership accountability is critical. Leaders must create self-organizing teams while being held responsible for cultural outcomes. Without accountability, leaders can operate without cultural constraints.

Reinforcing Processes, Rituals, and Systems

Rituals create belonging—a concept traced back to Confucius (Kong Zi). Regular ceremonies and symbols help establish cultural routines that bind teams together.

Long-Term Cultural Strategy Framework

Four-Part Framework for Sustainable Culture
ComponentDescription
Strategic AnchorsLink cultural transformation to business strategy; articulate how cultural behaviors support strategic objectives
GovernanceMeasure cultural metrics through audits; track turnover rates (sustainable companies maintain <15% turnover)
Learning Improvement LoopsRoot cause analysis and continuous learning; great leaders facilitate extensive learning time
Talent ArchitecturePeople management deeply integrated into leadership activities; hiring, development, and offboarding protect culture

Strategic Focus Areas

  1. Values Definition – Conduct workshops where teams collectively define shared values (sociocratic approach from agile methodologies)
  2. Decision-Making Frameworks – Transfer values into operational norms and decision principles
  3. Cultural Governance Model – Establish councils and cross-functional oversight
  4. Multi-Year Cultural Roadmap – Create flexible roadmaps that adapt as teams evolve (not rigid, written-in-stone documents)

Continuous Improvement: PDSA Cycle

The Plan-Do-Study-Act (PDSA) cycle, also known as the Deming Loop, provides the foundation for continuous improvement:

  • Plan – Define what needs to be tested
  • Do – Execute the plan
  • Study – Analyze outcomes and learn
  • Act – Implement changes and prevent regression

The “Act” phase is critical—it blocks the boulder from rolling back down the hill (Sisyphus metaphor). Without this step, teams revert to old patterns.

Practical Implementation

Weekly reflection sessions (e.g., Friday 11:00-12:00) allow teams to:

  • Reflect on the week’s work
  • Identify what can be done better
  • Decide what to stop, start, or continue
  • Plan automation opportunities
  • Unleash 10% of time for creative problem-solving

These sessions transform routine work by making it visible, revealing dependencies, and enabling cross-pollination of ideas between team members.

Tools for Continuous Improvement
  • Pulse Surveys – Regular check-ins on team sentiment and engagement
  • Weather Channel – Excel-based mood tracking (sun/cloud indicators) showing team trends over time
  • Engagement Surveys – Gallup Q12-style assessments measuring connection and belonging
  • Experiment Design Cards – Structured templates for testing cultural initiatives
  • Learning Journals – Documentation of lessons and insights
  • Innovation Sprints/Pilot Programs – Time-boxed experiments for new approaches

Leadership Development and Cultural Alignment

The Leader’s Dual Challenge

Leaders occupy an uncomfortable middle position, balancing two cultural demands:

  • Supporting team culture to flourish organically
  • Enforcing corporate culture mandates from above

This creates a “completely schizophrenic” situation where leaders must embrace and navigate two potentially conflicting cultures simultaneously.

Leadership Accountability

Effective leaders use structured approaches like balanced scorecards to:

  • Link vision to measurable objectives
  • Track customer satisfaction and process effectiveness
  • Monitor team motivation and preparedness
  • Set clear goals with regular touchpoints (not just annual reviews)
  • Provide constructive feedback tied to development opportunities
Cultural Leadership in Practice: Real-World Example

Working with ProCredit Group (Quipu), cultural variations emerged across locations:

  • Frankfurt headquarters – Diverse, internationally experienced staff working cohesively
  • Pristina (Kosovo) – Dynamic team functioning well independently
  • Skopje (Macedonia) – Junior-heavy team requiring more support

Recommendation: Rather than centralizing coaches at headquarters, distribute them regionally to understand local cultural nuances. One coach in Ukraine, one in Moldova, one in Romania—embedded to work with local teams who understand regional cultural impacts.

Embedding Culture into Talent Management

Hiring for Cultural Fit
Behavioral Interview Approaches

Move beyond CV evaluation to assess:

  • Curiosity and learning orientation
  • Ability to interact and communicate effectively
  • Cultural alignment beyond technical skills
  • Character and adaptability
The Voting Experiment

In Luxembourg, a candidate was hired through an open-space voting process. All 50 team members asked questions. They voted with thumbs up or down in front of the candidate. This transparent approach ensured team buy-in and cultural alignment from day one.

Onboarding for Cultural Integration
Five-Minute Onboarding Philosophy

“Jump in the water to get wet”—immerse new hires immediately rather than prolonged theoretical orientation. Learn by doing, with support available as needed.

Cultural Clarity from Day One

Make values, behaviors, and expectations explicit during Onboarding. Reinforce narrative, identity, and expectations through stories and rituals.

Performance Management and Development
Constructive Rating Approach

Start with the assumption everyone deserves top ratings, then provide clear feedback on what specific actions would earn that rating. Focus on “What can you do to get the five next time?” rather than justifying why someone didn’t achieve it.

Defending Your People

Leaders must advocate for their team members when their work merits recognition, even when facing organizational pushback or quota limitations.

Offboarding and Cultural Protection

Offboarding reviews are essential for:

  • Team grieving process (part of culture is leaving)
  • Learning why people depart
  • Protecting external reputation
  • Preventing toxic narratives (especially in small industries where “everybody knows each other”)

Companies with poor offboarding practices develop negative reputations quickly. These reputations spread through professional networks. Platforms like Glassdoor further amplify them, making future recruitment nearly impossible.

Cultural Diagnostic Checklist
Strategic Anchors Assessment
  • Are all values translated into explicit, observable behaviors?
  • Are decision principles clearly used in trade-offs?
  • Do leaders model anchors consistently?
  • Are anchors aligned with strategy and customer promises?
Governance and Measurement
  • Are cultural metrics included in business reviews?
  • Is there accountability and structure for cultural behaviors?
  • Are leaders held accountable through defined frameworks (e.g., RACI matrices adapted for self-organizing teams)?
Learning and Improvement Loops
  • Are continuous improvement routines established (daily stand-ups, weekly retrospectives)?
  • Are failures and breakdowns analyzed for learning (post-incident reviews)?
  • Is experimentation encouraged and celebrated?
Talent Architecture
  • Are hiring criteria tied to values and behaviors?
  • Does Onboarding reinforce narrative, identity, and expectations?
  • Do development pathways support cultural goals?
  • Does offboarding protect culture and reputation?

Real-World Challenges and Solutions

Challenge: Sustaining Momentum Over Time

Cultural initiatives often die after initial enthusiasm fades. Senior leadership shifts focus, and continuity is lost.

Solution: Embed culture as routine through rituals and ceremonies. Make it “the way we work” rather than a special initiative. Use Confucian wisdom—rituals and celebrations reinforce desired culture continuously.

Challenge: Measuring Culture

Unlike operational KPIs, cultural metrics are difficult to define and track consistently.

Solution: Focus on leading indicators like:

  • Turnover rates (<15% for sustainable organizations)
  • Engagement survey scores
  • Time-to-productivity for new hires
  • Customer satisfaction linked to team behaviors
  • Frequency and quality of retrospectives
Challenge: Cultural Friction Across Departments

When one department implements new cultural practices, friction occurs with departments operating differently.

Solution: Don’t try to change everyone. Focus on your sphere of influence. Work so well that your approach becomes attractive rather than imposed. Build bridges that allow interaction without forcing conformity. Use “judo”—leverage the force of the environment rather than fighting it.

Practical Example: Create a dedicated zone in the company where teams operate with new practices. Give them critical projects. After 6 months of visible success, require new hires to spend 3 months in this zone. They should do this before choosing their permanent team assignment.

Challenge: Hiring for Culture in Quantity-Driven Environments

HR and recruitment systems often prioritize filling positions quickly over cultural fit, leading to misalignment and rapid turnover.

Solution:

  • Managers must own hiring decisions, with HR supporting process compliance
  • Use behavioral scoring rubrics beyond CV evaluation
  • Involve teams in hiring processes (voting, peer interviews)
  • Be willing to reject candidates who don’t fit, even if technically qualified
  • Look for cultural potential, not just current cultural match
Challenge: Consulting and Third-Party Workers

Consultants and contractors often find themselves culturally isolated. They do not belong to their employer’s culture as they are rarely in the office. They are also not fully integrated into the client culture since they are marked as “external”.

Solution:

  • Consultancies should acknowledge this reality
  • Mission for consultants: be hired by your customer (transition from contractor to employee)
  • Clients should consider integrating valuable consultants into permanent teams
  • Leaders should recognize cultural isolation and provide support structures

Questions Asked by Audience and our Answers

Q: How do you understand “building a sustainable culture and long-term strategy?” What about “continuous improvement and innovation loops?” How do you view “leadership development and integrating culture into talent management?”

Pierre’s Answer (Summary):

Continuous improvement requires structured approaches beyond ad-hoc team efforts—Kata provides this structure. Innovation is challenging because teams are told to “be innovative” without clear definition of what that means. Embedding culture into talent management is rarely done effectively. These topics are often viewed skeptically because they lack concrete implementation frameworks.

Q: What’s the difference between adhering to corporate culture versus embracing diverse cultures in the room?

Pierre’s Answer:

These are “two different beasts.” Leaders are caught in the middle—required to help team culture flourish while also enforcing corporate mandates. This creates an uncomfortable, “schizophrenic” position where leaders must navigate both simultaneously without being able to fully commit to either.

Q: What about taking care of pronouns and DEI values?

Pierre’s Answer (Context):

DEI compliance can trigger strong reactions (example: board member fired for DEI violation, leading to company-wide 6-8 week mandatory training). The challenge is balancing inclusivity with freedom of expression. “If you’re inclusive, please include me as maybe an “asshole” when I’m okay with it.” This means diversity includes personality diversity, not just demographic diversity. Leaders should “let people be, people should be free to express themselves how they want.”

Q: What’s your take on the change from “Merry Christmas” to “Happy Winter Holidays” in France?

Chris’s Answer:

France’s multicultural mix has led to avoiding language that might upset anyone. The move from “Merry Christmas” with traditional decorations to generic “happy winter holidays” feels like denying Christianity. This shift challenges Christianity as part of French culture. It’s complicated—not wanting to adhere to religion but also uncomfortable rejecting this cultural heritage.

Pierre’s Commentary:

Christmas isn’t exclusively Christian—even in France, Jews and Muslims celebrate it. It’s become culturally universal like Chinese New Year. The key leadership principle: embrace diversity without forcing everyone to abandon their traditions. Give people choice rather than imposing uniformity.

Q: Is there a difference between Pulse Survey and Engagement Survey?

Pierre’s Answer:

They can be the same thing. Gallup Q12 is the standard employee engagement survey. Generic pulse surveys ask: How are you feeling? How is work? What do you want to focus on? Do you understand business goals? These lead to quarterly one-on-ones. In these sessions, you track progress. You ask about annual goals. You also document development needs in the performance system.

Q: Do you know the PDCA cycle (Plan Do Check Act)?

The PDSA (Plan Do Study Act) variation emphasizes “Study” over “Check” to reinforce learning orientation over mere verification.

Q: Your definition of Sisyphus is different from mine—can you clarify?

Dominic’s Original Understanding: “The ball keeps rolling back. You start from zero again.”

Pierre’s Clarification:

Sisyphus in continuous improvement context means climbing uphill step by step. The “Act” phase blocks the boulder with a stone so it doesn’t roll back. If you don’t make a stop and reflect, progress rolls back to you. In linear, reactive work like sales, accounting, and support, it is valuable to take one hour on Friday (11-12). Use this time to reflect on the week. This practice prevents the Sisyphus trap. This creates small improvements that accumulate rather than constant restarts.

Q: What tools do you use for pulse surveys and continuous improvement?

Pierre’s Answer:

  • Weather Channel – Excel sheet tracking team mood (sun/cloud indicators) to show trends over time
  • Niko Niko Calendar – Daily mood check-in application
  • Engagement Surveys – Including questions like “Do you have a friend in the team?” to measure social connection
  • Experiment Design Cards – Structured templates for testing cultural changes
  • Learning Journals – Documentation of insights and lessons
  • Innovation Sprints/Pilot Programs – Time-boxed cultural experiments
  • Dashboard Highlighting Culture Metrics – Making cultural data visible

Q: Can you give concrete behavioral interview questions you would ask?

Pierre’s Answer:

Rather than specific questions, focus on behavioral signals:

  • Ask: “How was your daily meeting?” (Look for real examples, not methodology recitation)
  • Ask: “How was the review meeting? Where was the customer? Do you know the customer?” (Good: frequent customer interaction. Bad: “We don’t need the customer, they’re a distraction”)
  • Watch for: Curiosity, desire to learn, ability to communicate, character
  • Red flags: Too slimy/agreeable, just repeating methodology, lack of customer awareness
  • Green flags: Smart but incomplete skillset (can be trained), strong interpersonal skills, genuine engagement

Provocative question for highly credentialed candidates: “Forget everything you know.” Watch their reaction to gauge adaptability and ego management.

Q: Do you use Balanced Scorecard at your level?

Dominic’s Answer:

“The real balanced scorecard is supposed to be for board level. We have a full automated BI solution for that. A lot of teams use it—sales, chief sales officer needs metrics, reporting weekly to the board.”

Pierre’s Context:

In IT, balanced scorecards are used weekly for portfolio management with green/amber/red/blue status indicators. If amber (risk), leaders must provide countermeasures. This tracks initiatives and ensures accountability.

Q: How do you navigate implementing cultural change when the rest of the organization isn’t on board? What if you’re a new senior director/VP wanting to implement this approach but other departments aren’t aligned?

Pierre’s Answer:

“I will give you a trick. The trick is simple.”

  1. Don’t try to convince everyone – “The best change is the way you’re working makes everything else obsolete”
  2. Focus on your sphere of influence – Change what you can control, not everything
  3. Work well and let others observe – Invite people to “come and meet the team, take a look, and then we can discuss”
  4. Let team members build bridges – Your team will naturally interact with other teams. They will explain: “This is how we’re working. Can we work together?” We won’t change our game, but there are bridges we can build
  5. Use judo, not force – “You’re using the force of your opponent” – work with the environment, not against it
  6. Avoid pride – Don’t announce “we are the best.” One day you’re best, next day you’re bad. “C’est la vie”
  7. Create a cultural zone – Recommend creating a dedicated area in the company where teams work the new way. Give them all critical projects (not simple ones). After 6 months of visible success, require new hires to work 3 months in that zone before joining other teams
Additional Strategy for Convincing Leadership:

For a private bank implementation, Pierre recommended: “Create a zone in your company. All teams working in this area, including meeting rooms, operate this way. Let them feel it. Test if it works for 6 months. If not, stop—it’s fine. But after 6 months, it will work.” Then integrate it into Onboarding.

Q: How do you handle the German “fail fast” culture issue?

Context: Germany struggles with failure acceptance despite agile rhetoric about “fail fast.”

Pierre’s Answer:

“It’s horrible. I asked Daimler at first contact: ‘What is your fail fast culture?’ Response: ‘We don’t fail at Daimler.'”

This reveals cultural misalignment. German culture fundamentally resists failure. The solution: “Usually they do it, but they call it differently.” Find language and framing that works within the existing culture rather than importing incompatible terminology.

Q: How do you handle cultural adaptation when working internationally?

Pierre’s Self-Reflection:

  • Switzerland – “Still trying to understand the Swiss guys. They don’t take you seriously if you’re a foreigner. They favor people from their own region—won’t even listen to a Swiss guy from Romandie (French-speaking part). You’re treated as a servant. If you push back, they brand you arrogant.”
  • Lebanon context – “We are transparent in conversation here. Now I understand women who told me they felt transparent” (invisible/dismissed)
  • Adaptation insight – “After 6 months, you’re no longer Indian, you’re German. After longer, you’re not German, you’re Bavarian—you go one layer deeper”
  • Professional approach – Use culturally appropriate team members for different contexts. For Middle East: Lebanese descent works in Beirut (seen as local), but North Africa sees “Monsieur Pierre” (distance/formality). Morocco requires Moroccan team members.

Dominic’s Asia-to-Europe Perspective:

“At the beginning was quite a big culture shock. Now if I go back to Asia, I’ll experience another culture shock. I’m not used to the culture in Asia anymore. I’m more used to the culture here.”

Silvio’s Distinction on Integration:

Two types of expatriates:

  1. Those on short-term assignments who don’t bother learning language or culture (“What do I care? I know English”)
  2. Those wanting to integrate and build a life (“You cannot live in a country for more than one year without being influenced. You’re gonna take something with you”)

Q: How does culture work for consultants who align more with client values than their own company?

Silvio’s Experience:

“I was more aligned with clients’ values than with Cognizant’s values. This happens a lot when you spend time on a project. When the contract ends, you find yourself out of values for everyone. You don’t align with your company anymore. You don’t align with the new client anymore.”

Pierre’s Analysis:

Consultants (McKinsey, Bain, BCG, Cognizant) are fundamentally alone:

  • Proud of prestigious business cards, but family asks “Are you happy?” (forced to say yes)
  • Never in office, so don’t know colleagues
  • At client site, not acknowledged as team member because you’re external
  • “You’re alone all the time”
  • Advice to daughter: “Go to consulting company, but don’t stay too long. Your mission: be hired by your customer”

This structural isolation makes cultural belonging nearly impossible for consultants.

Q: Why do cultural initiatives die out after a certain time?

Dominic’s Observation:

“A lot of these things die out after a certain time. Senior leadership stops looking at this, needs to focus on what board is looking at. Culture takes really a long time to implement, not just training.”

Pierre’s Answer:

This is the “January 1st intention” problem—like buying a gym membership and never going. Book recommendation: Change or Die addresses this phenomenon.

Solution:

  • Create routines, not intentions
  • Build context that prevents backsliding
  • Establish rituals and celebrations (Confucian wisdom—rituals reinforce culture)
  • Make it “how we work” not “special initiative”
  • Family example: Annual Christmas/Easter reunions create cultural continuity through ritual

Q: How do you measure culture? What KPIs work?

Chris’s Observation:

“I never saw any KPIs in the culture implementation of any of my companies. There is no follow up. You just guess, ‘Yeah, I have the feeling it’s okay.’ Everybody’s happy with the culture. But based on nothing.”

Dominic’s Agreement:

“It’s really tough to find metrics that really drive and move the needle, that are measurable over time.”

Pierre’s Answer:

Measurement must be continuous and evolve toward simplicity:

  • Turnover rate – Sustainable companies: <15%. Switzerland often >20% (red flag for leadership quality)
  • Don’t overcomplicate – Start with detailed metrics, but over time focus on core human values. Eventually reduces to: “Behave like a decent human being”
  • Link to strategy – If you can’t link cultural work to strategy, you’ll be considered noise/distraction
  • Track trends – Weather channel/mood tracking shows patterns over time
  • Use for reinforcement – Metrics aren’t just for follow-up, they’re “the blocker for the Sisyphus wheel”—preventing regression

Q: What about feedback going both ways—teams giving feedback to leaders?

Chris’s Insight:

“Something I found very powerful in only one company: feedback both ways. The team also feedback the performance of their own leader. You need to be very open-minded. Being a real leader requires accepting feedback. Sometimes, feedback hurts.”

Linked to psychological safety—people must feel safe to give honest feedback to leaders, even if initially anonymous surveys.

Pierre’s Implicit Agreement:

This aligns with his philosophy of transparency and constructive feedback. Leaders who can’t accept upward feedback can’t create psychologically safe environments.

Q: What about offboarding—how important is it?

Chris’s Experience:

Some companies have bad culture. They forget to learn during offboarding. It’s important to listen to why people left and improve. But outside, they talk and spread: ‘It was a piece of shit in this company, the manager did that.’ It’s known very fast. I know companies not able to hire at all because of this. If you go on Glassdoor, you see that company doesn’t have much feedback—nobody wants to go there. To kill it and come back to the good side is going to be a lot of effort.

Pierre’s Context:

Offboarding is part of talent architecture. When someone leaves, it’s a grieving process for the team—part of culture is going away, new culture forms. In small industries (“everybody knows each other” like aerospace design), bad offboarding creates a toxic reputation. This reputation spreads rapidly. It destroys future recruitment ability.

Q: How do you handle hiring when HR uses templates instead of manager specifications?

Pierre’s Frustration:

Multi-month delays common. Example process:

  1. Manager requests specific profile
  2. HR uses their own templates (ignoring manager’s request)
  3. ATS system connects to recruitment company
  4. Recruitment company never talks to manager or HR, just sees opening
  5. After 3-6 months, manager gets first contact
  6. Candidate doesn’t have required skills because HR “polished” the requirements

Historical Better Practice:

Managers could hire and fire people directly. HR’s role: ensure procedure compliance and protect people. Managers had budget to hire external service providers (coaches, consultants) without procurement gatekeeping.

Current Problem:

Procurement automation leads to “not the best people” because ATS systems filter out qualified candidates.

Pierre’s Personal Experience:

“100% rejection in Switzerland, even on jobs where I’m an expert. Agile Coach, nevermind.” Recruiters struggle to understand roles and show CVs for wrong positions. “This happens a lot more in Switzerland than anywhere else.”

Contrast: BCG Hiring Process:

“50 minutes total. BCG Director from Australia calls: ‘We have this mission. Interested? Yes/no? Available tomorrow? Okay, I send flight ticket. Meeting 10 o’clock London. Join.’ Ending process took 2 minutes. Everything straight to the point.

Sometimes started mission after first hour, then: ‘Pierre, you have to leave. Architect disagrees with you. He doesn’t want you here because he believes you studied NLP.’ Done.”

Q: How do you handle hiring people who challenge or annoy you?

Pierre’s Provocative Advice:

“You have to hire the person that annoys you or maybe pisses you off. The one who scratches, who stresses you. Because you see in that person something you don’t like in yourself. This person will push you to become a better person.”

Diversity Imperative:

If I have a team of mid-age white males from Switzerland, you need to hire different people. Hiring only similar people will change nothing. I need young people, old people, men, women, in between, all the colors of the rainbow. I’ll feel more comfortable that maybe one will see from a different angle, which is maybe part of the solution.

Q: How did performance reviews work at Cognizant, and how did you improve them?

Silvio’s Reflection on Standard Process:

“The process wasn’t wrong. In the past, you would have reportees, you’d forget about them. End of year comes, reviews, you’re asked about direct reportees—what did they do, do they deserve raise, bonuses? You have no idea because one year passed, you never saw them. If you worked together in same project, you’d have feedback. But like Pierre and me working in totally different areas, he’d have no idea what I did. Having set checkpoints is nice, but it was very little.”

Pierre’s Enhancement Approach:

  1. Asked at beginning of year: “Silvio, what’s your plan for this year? What do you want to work on?”
  2. If response: “I want your position” → “All right, fine. Let’s take a look, what do you need to get there?”
  3. Documented everything in system (tracking progress)
  4. Rating approach: “For me, you all have five points [maximum]. Based on what you’re doing, maybe you don’t deserve five. What can you do to get the five next time? Please do it.”
  5. Gave constructive feedback with clear path to top rating
  6. Defended team members’ ratings to directors when merited
  7. Example: Colleague rated down by others. “I was really angry because it was based on work delivered and interactions during six months. Somebody said ‘it’s impossible, too much, you should not deserve it because it’s limited.’ Not my problem. He deserved this. You have to defend your people if you believe.”

Silvio’s Conclusion:

Pierre’s approach improved the process. It gave us the opportunity to set really clear goals. We could have exact checkpoints and something to measure against. If you discuss once every six months, that’s not good, not going to be enough.

Cultural Requirement:

“Culture needs to come from above. They need to trust that you’re doing a good job with your reportees. If they question how you did it, we have a problem. If you gave me a five and they question the five, we have a problem.”

Key Takeaways and Action Items

For Individual Leaders

  1. Link all cultural work to business strategy—or risk being dismissed as “noise”
  2. Establish weekly reflection routines (e.g., Friday 11-12) for continuous improvement
  3. Use behavioral interviews focused on curiosity, character, and communication
  4. Defend your team members when their work merits recognition
  5. Create bridges with other departments rather than forcing conformity
  6. Focus on your sphere of influence; make your approach attractive through results

For Organizations

  1. Embed culture into all talent processes: hiring, Onboarding, development, offboarding
  2. Measure what matters: turnover rates, engagement, time-to-productivity
  3. Create cultural zones where new practices can demonstrate value
  4. Give critical projects to high-functioning teams to showcase effectiveness
  5. Require new hires to experience best-practice teams during Onboarding
  6. Establish rituals and ceremonies that reinforce desired culture

Cultural Sustainability Principles

  • Culture is an ongoing system, not a one-time initiative
  • Simplify over time to core human values
  • Use rituals to create belonging and continuity
  • Make implicit expectations explicit
  • Celebrate learning and wins (even small ones)
  • Protect culture through thoughtful offboarding
  • Adapt cultural approaches to local contexts

Conclusion

Building sustainable organizational culture requires patience, strategic alignment, leadership accountability, and systemic thinking. It cannot be imposed top-down or achieved through workshops alone. Culture emerges from daily practices, reinforced through rituals, measured through meaningful metrics, and protected through every talent management touchpoints.

The most effective approach is to focus on your sphere of influence. Work so well that your methods become attractive to others. Build bridges that allow collaboration without forcing conformity. As Pierre emphasized, “The best change is the way you’re working makes everything else obsolete.”

Culture work must connect to business strategy, or it will be dismissed as distraction. When done well, culture work requires clear values and continuous learning. It also involves accountable leadership and thoughtful talent practices. Sustainable culture becomes the foundation for long-term performance, innovation, and organizational resilience.

Next Steps

  • Review diagnostic checklist and assess current state
  • Implement weekly reflection routine (Kata every two weeks)
  • Access shared documents and templates on Circle platform
  • Plan 30-day commitment based on workshop insights
  • Schedule follow-up session for practical game-based planning exercise using Miro

Pr Dr Peter Nieschmidt Conference on “Rolle und Wertschätzung menschlicher Arbeit im gesellschaftlichen Wandel” is available on YouTube. It is (only in German). This conference was a source of inspiration to me. It helped me understand cultural challenges in my projects. Unfortunately, I didn’t find any English transcription. So, I created a short Executive Summary.

This learning script begins by outlining the core ideas of Peter Nieschmidt’s presentation. Then, it applies these ideas to the practical experience of managers and organizations. It is intended as a basis for reflection, discussion, and personal notes.


1. Work in a Changing Society

  • Today, work is much more than simply securing one’s livelihood. It fosters identity. It provides social integration. It gives meaning to life.
  • At the same time, many people experience a growing discrepancy between their commitment and the appreciation they get.

For leadership, this means not just “organizing jobs.” It involves shaping the conditions under which people experience their work as meaningful. It also ensures they feel valued.


2. Historical Development of Work Perceptions

  • In pre-modern societies, work was often linked to coercion, social hierarchy, and survival. Appreciation was more related to status than to specific tasks.
  • With industrialization and Taylorism, efficiency, standardization, and measurability took center stage; people often became mere “appendages of the machine.”

For today’s knowledge-based and service-oriented work, this mechanical thinking is no longer enough. The contribution of individual judgment is crucial. Creativity and interaction are also essential.


3. Present: Decoupling of Performance and Appreciation

  • Many employees invest additional emotional, cognitive, and temporal effort. However, they primarily experience recognition through formal key performance indicators. They also receive recognition via bonuses or target achievement.
  • Digitization, bureaucratization, and a fast pace mean that genuine personal feedback and dialogic recognition are often marginalized.

Typical practical phenomenon:

  • Annual performance review as the only “official” moment of appreciation, while daily life is dominated by emails, KPIs, and meetings.
  • Employees experience: “If I make a mistake, I notice it immediately – if I do good work, no one notices.”

4. Dimensions of Appreciation

Appreciation is not only expressed in words, but also in structures, rules, and routines. Four practical dimensions:

  • Person-related: Respect for the individual, recognition of their background, skills, and limitations.
  • Task-related: Interest in the specific work, understanding of the effort involved, complexity, and quality standards.
  • Context-related: Transparent integration of the work into the bigger picture, explanation of decisions and framework conditions.
  • Participative: Involvement in decisions, serious consideration of suggestions and objections.

Leadership that relies solely on bonuses, titles, and formal feedback often remains superficial in these dimensions.


5. Societal Trends with Consequences for Work

  • Demographic change and skills shortages increase the value of human labor, but structures often still treat people as easily replaceable.
  • Knowledge work, service work, and care work bring a new quality. In these fields, results are difficult to measure. Relationship building and emotional labor are central.

Practical areas of tension:

  • Economic logic demands continuous efficiency improvements. However, meaning, relationships, and learning time are more difficult to translate into short-term key performance indicators.
  • Employees expect more autonomy, development, and purpose, but encounter organizations with rigid rules and strong control.

6. Typical Misunderstandings of Appreciation

  • Confusing “feel-good sentimentality” with genuine recognition: Praise without substance comes across as paternalistic.
  • Reduction to material recognition: Salary and bonuses are necessary, but they don’t replace genuine, situation-based recognition of specific contributions.

Practical Example:

  • A team receives a bonus once a year but has little influence on goals and working methods.
  • Employees report that honest feedback in their daily work would mean more to them than a bonus. Feedback provides guidance. It promotes learning and encourages dialogue.

7. Consequences for Motivation and Health

  • Experiencing appreciation is a key protective factor against burnout, cynicism, and quiet quitting.
  • Conversely, a lack of recognition, combined with increasing demands and low autonomy, exacerbates exhaustion and psychological stress.

For managers, this means:

  • Not only managing workload but also actively integrating “recognition practices” into daily routines.
  • Systematically create spaces where employees can showcase their performance, reflect on it, and receive feedback.

8. Leadership Behavior in Everyday Life

Concrete levers for managers to make appreciation tangible:

  • Show presence: Regularly go to the places where value is created, listen, ask questions, without immediately “optimizing.”
  • Provide concrete feedback: Not “Good work,” but “The way you resolved the conflicts in today’s meeting made the decision possible.”
  • Recognize interests: Ask about learning interests and strengths and align task allocation accordingly, as far as the framework allows.
  • Respect boundaries: Respect occupational safety, breaks, availability, and private obligations; don’t tacitly expect constant availability.

9. Structural Framework Conditions


Appreciative leadership often fails not due to good intentions, but due to structures. Typical structural pitfalls:

  • KPI and reporting obligations that consume almost all of a manager’s time.
  • Positioning and budget logics that treat people as a cost item, not as a core resource.
  • Organizational design that fragments responsibility, so that no one sees “whole people” anymore, only functions.

Possible countermeasures:

  • Redesign meetings to create space for reflection, learning, and recognition, not just status reports.
  • Add key performance indicators (KPIs): In addition to output KPIs, use indicators for learning progress, collaboration, and customer/patient feedback.

10. Examples of leadership practices:

Concrete, easy-to-implement practices that capture the spirit of the presentation:

  • Appreciative weekly reviews: Briefly gather the team each week to ask: “What did we accomplish this week? Who benefited from what?”
  • Recognition retrospective: Dedicate 60 minutes each quarter. Highlight successful contributions and unexpected successes. Acknowledge quiet achievements that might otherwise go unnoticed.
  • Storytelling in Meetings: In each meeting, one person shares a short story from their workday. They recount an experience where they found meaning or value.

For you as a leader:

  • Each week, express appreciation to different employees at least three times with very specific words.
  • Observe how the quality of relationships and openness within the team changes.

11. Linking to Productivity and Quality (MTM Context)

  • In productivity-oriented approaches like MTM, the analysis and optimization of work systems are paramount.
  • Appreciation and efficiency are not mutually exclusive: Good system design that takes people seriously reduces waste, overload, and errors.

Important Mindset:

  • People are not disruptive elements in the system, but rather the central drivers of learning, adaptability, and quality awareness.
  • Appreciation therefore also means designing work in a way that is feasible, understandable, and manageable.

12. Reflection Questions for Your Own Learning


To conclude, here are some questions you can use for your learning script:

  • Where in your environment is performance visible but undervalued?
  • Which routines in your team foster appreciation, and which undermine it?
  • When did you last experience appreciation as powerful – what exactly happened?
  • Which specific practice from this script would you like to try out in the next four weeks?

These questions will help you understand the concepts of the role and appreciation of human work theoretically. They will also help anchor them in your own everyday leadership practice.