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:
Reversibility — Can we undo this within days at low cost? (Reversible = lean toward autonomy.)
Blast radius — Does the downside stay inside the team, or spill onto customers, other teams, regulators, or the brand? (Contained = autonomy; spreading = shared/escalated.)
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
Category
Risk profile
Who decides
Reversible, contained
Low
Team, full autonomy, no notification
Reversible, visible to others
Low–medium
Team decides, informs affected parties
Hard to reverse, contained
Medium
Team decides within explicit guardrails
High blast radius or correlated
High
Escalate or decide against a shared policy
Legal / safety / security / brand
High
Always 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?”
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?
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.
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.
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.
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.
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.”)
Traditional Organizational Change Management (OCM) typically drives toward a predefined target state. In contrast, Agile Organization (AO) treats the “target” as an evolving, adaptive organizational capability. This difference is clear when viewed through a BPM lens. Traditional OCM adjusts people around processes, while AO organizes processes around the people doing the work.
Short reminder: what BPM is
Business Process Management (BPM) is a management discipline. It involves analyzing, designing, implementing, monitoring, and continually improving end‑to‑end business processes. The goal is to enhance performance and customer outcomes. It treats processes as repeatable flows of activities that can be modeled, measured, and optimized across the organization. A classic BPM initiative focuses on mapping processes. It defines owners and standardizes work. Governance and tools are used to control and improve those flows over time.
Target solution: fixed state vs evolving capability
In traditional OCM, the target solution is usually a relatively fixed “to‑be” state defined upfront. This includes new processes, structures, roles, and systems. The change effort is about moving people from the current state to the target state. This creates a linear narrative. First, diagnose the gap. Next, define the future state. Then build the change plan. Finally, drive adoption until the new state is “embedded.” AO, by contrast, assumes the environment changes faster than any fixed blueprint. Therefore, it treats the “target” as an adaptive organization. This organization can continuously sense, decide, and reconfigure itself.
This leads to different questions. Traditional OCM asks, “How do we get everyone to the new operating model and keep them there?” AO asks, “How do we build structures, practices, and agreements that make continual reconfiguration safe, fast, and purposeful?” In OCM, you measure success by the degree of compliance with the designed target. In AO, you measure success by the organization’s adaptive capacity. This includes the speed of learning, the quality of decisions, and the ability to re‑shape work as conditions change.
Change logic: gap closing vs pattern evolving
Traditional OCM is gap‑closing. It involves defining the desired end‑state. Then, assess readiness and treat resistance. Afterward, roll out communications and training. Finally, stabilize into BAU. This often assumes relatively stable strategy, technology, and process architectures, even if they are complex. Governance, templates, and standardized toolkit become very important. The organization is encouraged to align with the one approved solution.
AO works with evolving patterns instead of final states. It creates conditions where multiple hypotheses can be tried in parallel. Teams experiment with structures, roles, cadences, and interfaces. The most effective patterns are then scaled. The focus changes from managing resistance to engaging people. They become designers of their own context. Explicit mechanisms help retire obsolete structures and practices. These prevent defending them as the “new normal.”
BPM lens: process‑centric vs people‑centric organization
Seen through BPM, traditional OCM tends to be process‑centric. You begin with the process map. You then define the optimal flow. Next, ask: “How do we align people, roles, and org structures around this process so it can run efficiently?” People play roles in predefined sequences. Change management ensures they execute the new process correctly. It also ensures they do it consistently. The process is the primary object; people are variables to be aligned to it.
AO almost inverts this perspective. It treats people as the core organizing principle. This includes teams, networks, and communities of practice. Processes are used as flexible instruments. These instruments can be shaped, combined, or dropped by the people. Instead of “adjusting people around business processes,” AO focuses on the people in the BPM. This includes who actually carries the work, who holds the knowledge, and how they collaborate to create value. Processes become boundary objects and agreements. They are not cages. Teams can adapt workflow, sequencing, and interfaces as they learn. They must respect purpose, constraints, and minimal interoperability standards.
Concretely:
In traditional OCM+BPM, a process redesign project defines the new flow, roles, and KPIs. Then, OCM ensures training, communication, and adoption. This continues until variance is minimized.
In AO+BPM, the teams that own the work continuously define and refine their processes. The BPM artifacts are deliberately kept light and revisable. This makes it possible to change them when the work or context changes.
Organizational design implications
You tend to get functional or process‑tower structures if you start from a fixed target and process‑centric BPM. This approach leads to strong central governance. There is also a heavy emphasis on standardization and control. This works well for high‑volume, low‑variety work and for environments where predictability matters more than innovation. However, it struggles when customer needs, technology, or regulations shift frequently. Every change implies a new “big” OCM program to move from one fixed state to another.
AO’s adaptive target and people‑centric BPM logic lead to modular, networked structures. These consist of small, semi‑autonomous units. They are linked by minimal essential constraints, such as common principles, standards, and interfaces. AO embeds change into the operating model, instead of running a sequence of large OCM initiatives. Local changes are expected and supported. BPM provides just enough shared scaffolding for coherence and coordination. This reduces the dependency on central change programs and increases the organization’s ability to reconfigure itself from the edges.
Examples of companies using Traditional OCM successfully
Several well‑known companies have used traditional, plan‑driven OCM successfully, especially for large technology and process roll‑outs.
Illustrative company examples
A leading retail pharmacy chain introduced a new point‑of‑sale system. It used a classic OCM playbook. This included early stakeholder involvement, structured communications, and role‑based training. Within six months, it achieved 70% faster transactions. Customer satisfaction increased by 25%. This success shows how traditional OCM can work well for clearly bounded system changes.
A global pharmaceutical company implemented a new data management platform and faced strong initial resistance. By applying a standard methodology (sponsor coalition, communication plan, training, and incentives for early adopters), significant progress was made. It reached 80% user adoption in the first year. Data quality and decision speed improved.
A Fortune 500 chemical company followed a structured, multi‑phase ERP change management approach with defined phases, deliverables, and KPIs. The program delivered around a 25% gain in operational efficiency. Another firm in the same material reduced month‑end closing time from 15 to 5 days. This was achieved after optimizing ERP usage under a traditional OCM framework.
A public‑sector agency (the U.S. General Services Administration) migrated to Google Workspace using extensive up‑front training, communication campaigns, and a phased cut‑over. Within weeks, help‑desk call volume dropped below the prior baseline. Most users who attended training adapted quickly. This illustrates how standard OCM tools can smooth a large collaboration‑suite rollout.
These cases all share the typical traditional OCM characteristics. They include a predefined target solution such as POS, ERP, data platform, or collaboration suite. The methodology is structured for change. They have strong executive sponsorship. Success is measured as stable adoption of the designed end state.
Implementation steps for Adaptive OCM emphasize less on delivering a single change project. They focus more on building a system capable of continuous change. Here is a concise step set you can reuse and adapt.
1. Diagnose adaptiveness, not just readiness
Assess current culture, leadership behaviors, and structural constraints for adaptability (decision speed, psychological safety, learning habits, autonomy).
Map change fatigue, existing OCM practices, and where people already self‑organize successfully; treat these as seeds to amplify.
2. Define adaptive intent and guardrails
Clarify why you need an adaptive organization now (market volatility, digital pace, etc.) and what “more adaptive” means in concrete behavioral terms.
Set a small number of non‑negotiable constraints. These include principles, ethics, compliance, and customer promises. Within these, local units are free to experiment and redesign.
3. Create distributed change roles and capabilities
Shift from a central “OCM team that implements change” model. Develop a distributed network of change agents embedded in teams. Provide these teams with coaching from OCM specialists.
Design targeted training on adaptability skills (experimentation, feedback, conflict, facilitation) rather than only “how to use the new process/system.”
4. Implement iterative change planning and delivery
Replace big upfront change plans with rolling, lightweight plans that are revisited every few weeks based on feedback and impact.
Use small experiments like pilots or A/B testing in ways of working. Implement micro‑structural tweaks and scale what works. Do this instead of committing early to a single solution.
5. Build continuous feedback mechanisms
Install regular pulse checks, retrospectives, and qualitative sensing (focus groups, open forums) as a permanent feature, not just during “projects.”
Close the loop visibly. Show what was heard. Indicate what is being changed. Explain what will not change and why. This approach will maintain trust in the adaptive process.
6. Align operating model elements with adaptiveness
Adjust governance to allow faster local decisions, clear accountabilities, and simple escalation paths; avoid over‑complex approval chains.
Rework structures, roles, and BPM artifacts. This allows teams owning the work to modify processes within agreed boundaries. They can do this without launching a major program each time.
7. Reinforce and normalize adaptive BEHAVIORS
Recognize and reward experimentation, constructive challenge, and cross‑boundary collaboration, not only short‑term efficiency.
Integrate adaptive OCM practices into BAU. Use quarterly sense-and-respond cycles and establish standing change communities of practice. This ensures that “doing change” becomes “how we work.”
If you’re leading in a living organization, you are probably sitting in the middle of tensions every day. Deliver now vs. build for later. Standardize vs. let teams shape their own ways of working. Protect people vs. push for performance. After a while, these tensions start to feel like signs that something is wrong. They may seem to indicate issues with you, your team, or your design.
Seen through an AO and systems‑leadership lens, tensions are not a bug. They are how a living system tells you where it is stretching beyond its current design. Your role is less “fixer‑in‑chief” and more “sense‑maker‑in‑chief.” You help the system see itself. You hold competing perspectives without collapsing them too quickly. You translate that into small experiments the organization can learn from. In this issue, I share a story of a leadership team that faced AO‑related tensions. The team was drowning in these tensions. I also provide a simple 30‑minute SENSEMAKING loop you can try if you recognize similar patterns.
From the field: when AO tensions land on the leadership table
A leadership team of a mid‑size service organization reached out after running several AO‑style experiments. They had created swarms around key customer journeys, simplified some hierarchies, and given more autonomy to cross‑functional teams. On paper, things looked promising. In practice, the leadership meetings had become heavier. Every agenda item seemed to end in a tug‑of‑war: central standards vs. local freedom, efficiency vs. responsiveness, accountability vs. psychological safety.
In one session, we mapped what their past few meetings had actually been about. Instead of listing topics (“budget”, “Roadmap”, “reorg”), we noted the underlying tensions. The conversations kept circling around these issues: “We say teams own the customer, but we still sign off every exception.” “We want fewer escalations, but we keep inviting more issues into this table.” “We want to empower, but we also fear losing control.” Once the list was on the wall, there was a long silence. Someone said: “It feels like we are both pushing AO and pulling against it at the same time.”
From an AO perspective, this was not a sign that they had “failed”. It was a sign that the system was doing exactly what living systems do when they change. They explore, push, pull back, and test boundaries. The problem was not the tensions. Nobody was helping the leadership group turn those tensions into a shared picture. They were not facilitating deliberate experiments. Each leader was carrying their own private story about what was happening – and acting from it.
We proposed a very small intervention. It is a regular, 30‑minute “SENSEMAKING loop” inside their existing leadership meeting. This loop focuses on one tension at a time. No new committee, no big offsite. Just a consistent practice of stepping back from the latest incident and looking at the pattern together.
The first time we tried it, they identified a tension that everyone felt. “We say teams own their slice of work. However, big decisions keep bouncing back up here.” In 30 minutes, they:
collected short snapshots from each person of where they saw this tension show up;
drew a simple picture of the system dynamics that kept pulling decisions up;
Agreed on two small experiments to shift one concrete boundary of decision‑making. They also discussed how they would notice whether the system was responding.
What changed was not just those decisions. Over the next few weeks, the tone of leadership meetings shifted. Less “who is right?” and more “what is the pattern we are in, and what experiment could we run next?” One of the executives summed it up later: “I still feel the tensions. They no longer feel like a personal failure. They feel like the work.”
Try this AO move this week – a 30‑minute sensemaking loop
You don’t need a retreat to start leading as a sense‑maker. You can begin by carving out a single, disciplined 30‑minute loop with your team around one live tension.
Name one real tension, clearly. Pick something you and your team already feel – for example:
Do a quick me → we → us round (10–15 minutes).
Agree on 1–2 small experiments (10–15 minutes). Based on that picture, choose 1–2 experiments you can run over the next 2–4 weeks. Ensure these changes slightly alter how the system handles this tension. Aim for minor adjustments, not a giant transformation. Examples:
Close the loop in your next meeting. In your next leadership or team meeting, spend 10–15 minutes revisiting the tension: Did the experiments change anything? What did you notice about the system? What next adjustment does that suggest? Treat this as ongoing AO practice, not a one‑off.
If you do this regularly, you’ll likely notice two things. First, your conversations move from “who is to blame?” towards “what is the system doing?” Second, your AO experiments stop being isolated projects and start to feel like part of a continuous learning loop.
Conversation with Li Fang and Francisco Cortez
Executive Summary
This document consolidates a conversation between Pierre Neis and two key stakeholders from Quipu. They discussed a comprehensive agile transformation program delivered across the organization. The program spanned 10 months (May through March). It included 37 training sessions. It engaged 90% of active staff, representing over 12,000 training hours. The program covered employees across multiple international locations. This included Frankfurt, Skopje, Pristina, and remote participants.
The transformation employed the Agile Organization (AO) Method. It was adapted specifically for company-wide implementation. This includes back-office functions beyond traditional software development teams. The program emphasized practical experience over theoretical certification. It fostered cultural shifts around empowerment. It encouraged saying “no” based on facts. The approach also promoted team-based collaboration.
Company Context: Quipu
Organizational Profile
Quipu operates as the IT service division of the ProCredit Group, primarily serving the banking sector globally. The organization represents remarkable diversity:
45-47 different nationalities represented across the workforce
Primary geographic focus: South Eastern Europe, Eastern Europe, with historical presence in Latin America
Cultural composition: Colleagues from Ukraine, Moldova, Romania, Spain, Ghana, El Salvador, Nicaragua, Venezuela, Guatemala, Colombia, UK, Germany, Switzerland, and other nations
Main offices: Frankfurt (Germany), Skopje (North Macedonia), Pristina (Kosovo), with historical operations in Kiev (Ukraine)
Service focus: Banking sector technology solutions and support
Organizational Complexity
The company’s complexity stemmed from several factors:
Multicultural workforce with varied communication styles and cultural norms
Different functional areas: software development, testing, support operations, back office (HR, finance, procurement), credit card services, ATM maintenance
Varied maturity levels regarding agile understanding (from new graduates to long-tenured employees with change resistance)
Multiple stakeholder relationships including holding company oversight and diverse banking clients with contractual SLAs
Geographic distribution requiring both in-person and online training delivery
Program Overview
Timeline and Scope
Metric
Value
Program Duration
10 months (May – March)
Total Sessions
37 training sessions
Staff Coverage
90% of active staff
Total Training Hours
12,000+ hours (staff time investment)
Session Format
3-day workshops
Locations
Skopje, Pristina, Frankfurt, Online
Table 1: Agile Transformation Program Metrics
Program Launch
The transformation began strategically with a kickoff session targeting middle management:
Format: Three parallel sessions led by Pierre and two external colleagues (Virginia and another Pierre)
Objective: Set tone, secure buy-in, prepare leaders for cultural shifts
This leadership-first approach proved crucial for program success. It prepared managers for downstream behavioral changes. These changes include employees learning to say “no” based on facts and data.
Training Delivery Team
Lead trainer: Pierre Neis (primary facilitator for 37 sessions)
Support trainers: Virginia Anderson and Pierre Hervouet (Menschgeist Partners)
Internal coordination: Frank Cortez (Learning & Development) and Li Fang (Head of Agile)
Expertise requirement: Coaching skills prioritized over pure training skills due to intensive facilitation needs
Methodology and Approach
The Agile Organization (AO) Method
Pierre’s proprietary AO Method formed the foundation of the transformation. Key characteristics:
Target audience adaptation: Originally designed for leaders and agile coaches, successfully adapted for company-wide deployment
AO Matrix: 12-point assessment framework enabling teams to self-evaluate current agile maturity
Application: Used at beginning and end of training sessions to demonstrate progress and create awareness
Self-assessment approach: Teams identified their current position on the agile maturity spectrum. They visualized their target state. This process fostered ownership of the transformation journey.
Training Philosophy
The program rejected traditional certification-focused training in favor of experiential learning:
Priority: Practical application over theoretical knowledge
Goal: “Aha moments” connecting agile principles to daily work
Coaching over instruction: Facilitators guided discovery rather than lecturing
Content focus: Not about the trainer or material, but about the participants
Memorability: Exercises and games designed for lasting impact beyond slide content
Pierre’s facilitation principle: “The content is easy peasy. You have a scenario and you have to roll out. But every session, it was mostly the same thing, the same games… But in fact, because the nature of every team was different, [everyone had] a different experience.”
Core Frameworks: The “We-Us-Me” Triangle
The training centered on three interconnected perspectives:
WE (The Team): Primary focus and safety container
Your immediate team “watches your back”
Reduces individual tension through collective support
Team becomes the core unit of care and accountability
US (The Company): Organizational context and alignment
Understanding how your team serves Quipu’s mission
Focus on company purpose without making it the primary concern
Example: Work for IBM’s data analytics team, not “for IBM”
ME (The Individual): Personal gain and development
“What’s in it for me?”
How individual growth aligns with team and company success
Personal agency and empowerment through agile practices
Key Tools and Exercises
Value Stream Mapping
A critical exercise that created breakthrough understanding of workflows:
Process in Pristina example:
First team created initial value stream design
Design was improved through facilitated discussion
Subsequent teams from same entity reviewed the improved design
Teams added corrections: “This is belief, in reality it’s working differently”
Final output: Complete systemic picture of actual workflows
Pierre’s reflection: “The improvement of the us by the we… Only when you have the full picture, you can start improving the picture. Because if you want to change, you have to notice there is a change to do. If it’s theoretical, people will never buy it.”
Daily Retrospectives
An innovative addition to the 3-day workshop format:
Frequency: End of each training day
Purpose: Demonstrate trainer receptiveness to feedback, embody agile principles
Impact: Participants saw real-time adaptation based on their input
Cultural modeling: Trainers practiced what they preached about continuous improvement
Starting with Retrospectives: Pierre adopted the practice of beginning new engagements with retrospectives. He did this rather than starting with planning. This approach helps in understanding the team’s current state before prescribing changes.
Content Adaptation Strategy
Challenge: Company-Wide Scope
Traditional agile training focuses on software development teams (developers, testers, Scrum teams). Quipu required adaptation for:
Support teams: First-line customer support, operations
Back office: HR, finance, procurement, office managers
Pierre’s reflection: “Artificial software development is easy peasy. But then you have the challenge of what are you doing with the support team?… the guys doing the credit cards, or even… people in Pristina, they’re just doing the ATM maintenance. These are the guys driving through the sales offices to maintain the ATMs. And you have to… explain what is Agile for them. You can’t talk about Scrum and only Kanban, there’s something else.”
Content Customization Process
Initial material design: Frank and Li posed challenges related to different roles and functions
Continuous review: Pierre constantly revised materials to fit each context
Weekly feedback loops: Frank and Li provided formal and informal feedback
Anonymous participant surveys: Collected concerns and suggestions
Real-time adaptation: Content evolved dramatically from start to finish
Transparency: Feedback shared with staff to demonstrate listening
Final Training Structure
The program evolved to a refined format:
Days 1-2: Practical exercises, games, and discovery learning
Retrospective opening to understand current state
Tools and techniques applied to participants’ actual work contexts
Focus on enabling fact-based decision making (“saying no” effectively)
Day 3 (Half-day): Theoretical framework
Introduction to formal terminology: Scrum, Kanban, scaled agile frameworks
“Checking boxes training” – naming what participants already experienced
Connecting practice to theory rather than theory to practice
Key Learning Outcomes
Definition of Done
Li, Frank, and Pierre established clear success criteria at program outset:
People know each other: Cross-functional connection and collaboration
People start to say “no”: Evidence-based boundary setting
Engaged workforce: Passion beyond just “doing the job”
Awareness of agile principles: Understanding why agility matters for the organization
Cultural Shifts Achieved
Empowerment to Say “No”
The Challenge: Many participants, particularly those from certain cultural backgrounds (e.g., Indian colleagues), found it culturally difficult to refuse management requests.
The Solution: Training provided tools for fact-based refusal:
Checklists for decision-making
Clear alignment to strategy and vision
Data-driven justification frameworks
Permission and encouragement from trained leadership
Management preparation: Pierre warned managers during kickoff: “Starting next week, I will begin the transformative learning with your people. They will start to say no to you. Are you ready for that?”
Ongoing work: Li identified continued focus on empowerment as key post-training work for agile coaches.
Understanding the Big Picture
Li’s perspective on transformation value: “What motivated me to invest in Agile… is really… how to empower people, how to unleash their potentials. I believe each of us are smart people. It’s just you need to give them some overall picture and to give them some directions… with this vision and everybody will have this in mind and connect to their day-to-day work.”
Connection to purpose:
Core problem: How to react to market rapidly while serving end users
Meaning-making: Understanding how individual work benefits real people
Motivation: Finding purpose through connection to organizational North Star
Problem-Solving Focus Over Process Compliance
Fundamental shift: Purpose is not to “deliver our job” but to “use our job to solve a problem.”
This reframing proved transformative across functional areas. It helped participants understand agile as a means to an end rather than an end in itself.
Autonomy Recognition
Teams with direct customer interaction (support, operations) demonstrated higher initial autonomy scores on the AO Matrix:
Direct feedback loops with customers enabled faster learning
Customer-facing teams naturally developed agile behaviors
Recognition of existing agility built confidence rather than imposing foreign concepts
Challenges and Solutions
Challenge 1: Maturity Level Diversity
Problem: Participants included recent graduates who were enthusiastic about change. It also included long-tenured employees who were resistant to transformation. They had varying degrees of understanding of agile concepts.
Solution:
Start-where-you-are approach (Kanban principle)
Self-assessment via AO Matrix to meet teams at their level
Coaching facilitation adapting to each group’s needs
Focus on sense-making: “What makes sense to everyone?”
Challenge 2: Logistical Complexity
Problem: Reaching 90% of geographically distributed, culturally diverse workforce.
Accommodating last-minute cancellations and transfers between sessions
Deliberate overbooking some courses to maximize attendance
Frank’s reflection: “It’s very challenging to get them… different offices. You also have the flexibility to deliver online. Additionally, you support us with these other last minute cancellations.”
Challenge 3: Initial Participant Confusion
Problem: Early feedback indicated confusion about training purpose and relevance.
Solution:
Clearer framing: Not traditional training but awareness creation and challenge sessions
Retrospectives demonstrating responsiveness to concerns
Immediate content adjustments based on feedback (e.g., reducing overwhelming content volume)
Transparent communication about program goals and participant feedback incorporation
Challenge 4: Multicultural Communication
Observations on diversity:
Pierre’s experience: “I really get your point. I would say the challenge will be if you only work with mid-age white male from Switzerland. This will be a challenge. All thinking the same way. You don’t have this kind of diversity of voices.”
Specific cultural moments:
Colleagues from Kiev and Moscow working together despite geopolitical tensions
Participants from El Salvador traveling to Pristina, Kosovo for training
Language barriers (e.g., Ukrainian participants with very fluent UK English speakers)
Different communication styles requiring calibration
Solution approach:
Humor and willingness to communicate bridged gaps
Creating psychological safety for misunderstandings
Trainer vulnerability and dark humor built trust
Encouraged participants to joke back as proof of trust
Li’s perspective: “For me, multicultural shouldn’t be a big problem. Rather, it’s… the different understanding, different level, maturity of the understanding of what is agile.”
Challenge 5: Systemic Complexity
Problem: Multiple layers of stakeholder relationships (holding company, diverse banking clients, contractual SLAs) created alignment challenges.
Solution approach:
Focus on communication improvement across boundaries
Questioning outdated contracts and SLAs blocking progress
Shift from output-based to outcome-based partnerships
Recognition that agility requires social skills, not just engineering practices
“Putting butter in the system so it’s more fluid”
Questions from Audience and Pierre’s Responses
Q1: Do you find multiculturalism a challenge to work with?
Asked by: Li Fang
Pierre’s Response:
“I really get your point. I would say the challenge will be if you only work with mid-age white male from Switzerland. This will be a challenge. All thinking the same way. You don’t have this kind of diversity of voices. And this is making the thing awesome.”
Pierre acknowledged specific cultural challenges:
Communication factors (e.g., fluency differences creating perceived coach preference)
Cultural norms around humor and communication style
Importance of considering cultural context in facilitation
He emphasized that diversity strengthened outcomes. It did not hinder them. He noted the team’s “sense of collaboration, which is awesome.”
Q2: What was the challenge from your perspective as head of learning and development?
Asked by: Pierre to Frank
Frank’s Response (with Pierre’s follow-up):
Frank identified reaching everyone across the distributed organization as the primary challenge. The solution involved:
Strategic timing: Launching with quarterly middle management meeting
Multiple delivery modalities (online and in-person)
Flexibility for cancellations and schedule changes
Focus on interactive feedback loops (weekly discussions, anonymous surveys)
Pierre’s validation: The middle management kickoff was crucial for securing buy-in. It prepared leaders for the cultural shifts their teams would experience. This was particularly true around empowerment and saying “no.”
Q3: What adjustments did you make based on feedback?
Context: Implied question from discussion of continuous adaptation
Pierre’s Response:
Pierre described implementing daily retrospectives at the end of each training day based on early feedback. This served multiple purposes:
Demonstrated trainer listening and responsiveness
Modeled agile principles in real-time
Reduced overwhelming content when participants felt overloaded
Created trust that feedback mattered
He also shifted the training structure to start with retrospectives even when engaging new teams. He said, “I adopt that into my work. When I work with a new team, I will start with a retrospective. This is very important to understand how they work currently. It also allows me to coach them instead of teaching them.”
Q4: How did you handle the “saying no” cultural shift with management?
Context: Discussion about empowerment outcomes
Pierre’s Approach:
During the management kickoff session, Pierre explicitly warned leaders:
“Hey, attention, this sounds for you maybe fancy. I believe you [will] not discover new things. It was just how you [are] using your tools, what you know. And what’s coming up is… Attention, next week I will start the transformative learning with your people. They will begin to say no to you. Are you ready for that?”
Li’s follow-up work:
Li identified this as ongoing work for agile coaches: providing clear metrics, rules, and checklists. They also offer guidance for strategic alignment. This helps employees have frameworks for fact-based decision making. “They have this awareness to say no, but how?… We must provide tools to empower them. Providing guidance is also essential to empower them to say no.”
Q5: How did you adapt agile training for back-office functions?
Context: Implied question about customization strategy
Pierre’s Response:
Pierre acknowledged the challenge. He said, “Artificial software development is easy.” However, it’s more difficult to explain agile to ATM maintenance technicians, credit card services staff, or HR personnel.
His approach:
Constant material review and revision with Frank and Li
Context-specific examples relevant to each function’s work
Less focus on Scrum/Kanban frameworks initially
More emphasis on universal principles: collaboration, problem-solving, continuous improvement
Value stream mapping to help all functions visualize their workflows
Connecting agile practices to actual problems each function faces
Final day included framework overview (“this is called Scrum, this is called Kanban”) after participants experienced the principles in practice.
Q6: What made the value stream mapping exercise so impactful?
Context: Discussion of specific tools and their effects
Pierre’s Explanation:
The value stream mapping game demonstrated breakthrough understanding through iterative improvement:
Initial team creates value stream design
Design gets improved through discussion
Subsequent teams review and correct the “improved” design
Teams add real-world complexity: “This is belief, in reality it’s working differently”
Result: Complete systemic picture emerges
Key insight: “The improvement of the us by the we. Is the entities, how the system of all the entities are really working together… And only when you have the full picture, you can start improving the picture. Because if you want to change, you have to notice there is a change to do. If it’s theoretical, people will never buy it.”
This simple tool created lasting impact by making invisible workflows visible and connecting individual work to organizational systems.
Q7: Why did you decide to use the AO Method for company-wide training?
Context: Discussion about methodology selection
Pierre’s Response:
Pierre expressed initial hesitation: “I created this methodology… this is mostly for leaders and agile coaches.”
Li and Frank insisted on using it: “No, no, no, you tell me. No, no, Pierre… we know why we have to go agile. But we didn’t have a proper plan at the beginning, which is in progress.”
Application: The AO Matrix (12-point assessment framework) worked effectively because:
Allowed self-assessment: “Where are you now? Where do you think you are?”
Created baseline and target visualization
Used at beginning and end of training to demonstrate progress
Gave teams ownership of their transformation journey
Discovery: Teams with direct customer contact, such as support and operations, scored higher on autonomy initially. They received direct feedback. This feedback helped them naturally develop agile behaviors. This validated “start where you are” rather than imposing foreign concepts.
Q8: How did you maintain consistency across 37 sessions while keeping each one fresh?
Context: Implied question about facilitation approach
Pierre’s Response:
Pierre used repeatable structure with adaptive facilitation:
Consistency elements:
Same core games and exercises across all sessions
Same scenario and rollout structure
Even same jokes to enable peer sharing (“Did you attend also this crazy training with Pierre?”)
Adaptive elements:
Full focus on participants, not content
Reading the room and listening constantly
Responding to each team’s unique nature and needs
Coaching skills over training skills
7-8 hours of intense facilitation per session
Result: “Every session, it was mostly the same thing, the same games… But in fact, because the nature of every team was different, [everyone had] a different experience.”
Li’s observation: Pierre finished every day “with a sweating shirt” from the intensive facilitation effort. Participants often said “I survived from today” due to the immersive, challenging nature.
Q9: What should participants remember most from the training?
Context: Discussion about lasting impact
Pierre’s Philosophy:
“Maybe after a week I will forget what you teach and what you showed in the slides. But when I start to think about implementing something, I will recall something from your training. I will remember something from the session… from the method you used and then I can copy or reuse. So this is the thing we really need. This is the valuable. It’s not about the theory, but really the experience you shared with us.”
Tools that can be recalled when needed rather than memorized content
Frank added: “People have different ways to react to this… In conversations with you, with Lee, and with me, they will hopefully keep something from it. They may reference it and then be able to apply it.”
Q10: What role did contracts and SLAs play in the transformation discussion?
Context: Systemic challenges mentioned briefly
Pierre’s Perspective:
Pierre challenged the status quo around contractual relationships:
“We talked about the SLAs… have you never thought about to improve and review the SLAs? [Response:] Why should we review the contract? [Pierre:] Yeah, because if the contract is not helping you moving forward, it’s just a blocker.”
Key insight: Contracts valid 10 years ago or even 5 years ago may no longer serve current needs. Agile transformation requires:
Questioning outdated agreements
Shifting from output-based to outcome-based partnerships
Making contracts coherent with current reality
Recognizing that social skills, not just engineering, drive agility
Improving communication to make systems more fluid
This challenged the notion that agile is purely technical: “People talk, agile is mostly of engineering. No, it’s social skills.”
Critical Success Factors
Based on the conversation, several factors enabled the program’s success:
1. Leadership Buy-In
Early engagement with middle management created top-down support for cultural shifts, particularly around empowerment and boundary-setting.
2. Continuous Feedback Loops
Weekly coordination meetings between Pierre, Li, and Frank
Daily retrospectives during training sessions
Anonymous participant surveys
Informal corridor conversations
Transparent communication back to staff about changes made
3. Experiential Learning Design
Games, simulations, and practical exercises created lasting memories and recall triggers rather than forgettable slide presentations.
4. Adaptation and Flexibility
Willingness to completely revise content between sessions based on feedback, customize for different functions, and pivot delivery methods as needed.
5. Coaching Expertise
Facilitators with coaching skills who could read the room, adapt in real-time, and focus on participants rather than content delivery.
6. Partnership Model
Pierre, Li, and Frank operated as partners rather than vendor-client relationship, with shared ownership of outcomes and continuous collaboration.
7. Cultural Sensitivity with Universal Principles
Acknowledging cultural differences while focusing on universal human needs: purpose, autonomy, mastery, connection.
Lessons Learned and Reflections
For Trainers/Consultants
Pierre’s insights:
Closeness matters more than formality – avoid suits and ties, be human
Dark humor and stupid jokes build trust when rules of engagement are clear
Allow participants to joke back as proof of trust
Focus 100% on people, not content
Repeat structure but adapt to each unique group
Expect emotional reactions and emails – perfection is impossible
Travel, logistics, and organizational details consume significant time
Coaching skills trump training skills for transformative work
For Learning & Development Leaders
Frank’s insights:
Record time achievement possible with right partnerships (10 months, 90% coverage)
Strategic timing of kickoff sessions amplifies impact
Multiple feedback mechanisms catch different concerns
Geographical and scheduling flexibility essential for distributed organizations
Frank mentioned efforts to support continuous learning:
Training materials adapted for independent study
Resources shared with staff for reference
Materials available for newcomers to understand organizational approach
Creating institutional memory: “Who was this Pierre guy who was with us?”
Conclusion
The Quipu agile transformation is a comprehensive, company-wide initiative. It successfully engaged 90% of a diverse workforce. This workforce was geographically distributed and the engagement occurred over 10 months. The program created lasting awareness and cultural shifts. It focused on empowerment, collaboration, and problem-solving. This was achieved by prioritizing experiential learning over certification. The program also adapted content for all organizational functions and maintained continuous feedback loops.
Key differentiators included:
Early leadership engagement preparing managers for cultural change
Partnership model between external consultant and internal champions
Consistent structure with adaptive facilitation responding to each group’s needs
We-Us-Me framework connecting individual, team, and organizational perspectives
Tools like value stream mapping creating systemic visibility
Daily retrospectives modeling agile principles in training delivery itself
The success stemmed not from perfect execution. Instead, it was due to genuine partnership, continuous adaptation, and cultural sensitivity. There was also an unwavering focus on participants rather than content. As Pierre emphasized, “It’s not about the trainer, it’s not about the matter, it’s all about the people.”
The journey required significant investment. It involved over 12,000 training hours, extensive travel, logistical complexity, and emotional energy. However, it achieved remarkable reach and impact through collaboration. This was possible due to Pierre’s facilitation expertise, Li’s agile leadership, and Frank’s learning and development orchestration.
As the program concluded, attention shifted to sustaining momentum. This was to be achieved through continued empowerment frameworks and strategic clarity. Additionally, the application of learned principles would guide the organization’s ongoing evolution.
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.
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
Component
Description
Strategic Anchors
Link cultural transformation to business strategy; articulate how cultural behaviors support strategic objectives
Governance
Measure cultural metrics through audits; track turnover rates (sustainable companies maintain <15% turnover)
Learning Improvement Loops
Root cause analysis and continuous learning; great leaders facilitate extensive learning time
Talent Architecture
People management deeply integrated into leadership activities; hiring, development, and offboarding protect culture
Strategic Focus Areas
Values Definition – Conduct workshops where teams collectively define shared values (sociocratic approach from agile methodologies)
Decision-Making Frameworks – Transfer values into operational norms and decision principles
Cultural Governance Model – Establish councils and cross-functional oversight
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.”
Don’t try to convince everyone – “The best change is the way you’re working makes everything else obsolete”
Focus on your sphere of influence – Change what you can control, not everything
Work well and let others observe – Invite people to “come and meet the team, take a look, and then we can discuss”
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
Use judo, not force – “You’re using the force of your opponent” – work with the environment, not against it
Avoid pride – Don’t announce “we are the best.” One day you’re best, next day you’re bad. “C’est la vie”
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:
Those on short-term assignments who don’t bother learning language or culture (“What do I care? I know English”)
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:
Manager requests specific profile
HR uses their own templates (ignoring manager’s request)
ATS system connects to recruitment company
Recruitment company never talks to manager or HR, just sees opening
After 3-6 months, manager gets first contact
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:
Asked at beginning of year: “Silvio, what’s your plan for this year? What do you want to work on?”
If response: “I want your position” → “All right, fine. Let’s take a look, what do you need to get there?”
Documented everything in system (tracking progress)
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.”
Gave constructive feedback with clear path to top rating
Defended team members’ ratings to directors when merited
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
Link all cultural work to business strategy—or risk being dismissed as “noise”
Establish weekly reflection routines (e.g., Friday 11-12) for continuous improvement
Use behavioral interviews focused on curiosity, character, and communication
Defend your team members when their work merits recognition
Create bridges with other departments rather than forcing conformity
Focus on your sphere of influence; make your approach attractive through results
For Organizations
Embed culture into all talent processes: hiring, Onboarding, development, offboarding
Measure what matters: turnover rates, engagement, time-to-productivity
Create cultural zones where new practices can demonstrate value
Give critical projects to high-functioning teams to showcase effectiveness
Require new hires to experience best-practice teams during Onboarding
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
The AO Method (Agile Organization/Agile Organizations Method) is Pierre Neis’s own framework. It is distilled from more than a decade of agile coaching. This includes organizational transformation work across many companies, cultures, and contexts.
Core origins
Practice-based patterns: Neis describes AO as emerging from recurring patterns. He observed these while coaching and redesigning organizations of different sizes over many years. He then consolidated these into a coherent model. Later, he wrote a book called “AO.”
Response to “Agile as system dynamic”: AO starts from the hypothesis that “Agile” is not a method. It is a dynamic within a social system (the organization). An “Agile Organization” enables highly efficient human interactions for better response to threats and opportunities.
Organic/anthropomorphic view of organizations: AO was formulated as an answer to the mechanistic, purely structural view of organizations. It favors an organic, anthropomorphic model. In this model, all actors are engaged around a shared purpose. Agility emerges from conditions rather than imposed methods.
Theoretical influences
Complexity and complex adaptive systems: AO integrates complexity science and views organizations as living, adaptive systems. It focuses on emergence, feedback loops, and enabling conditions. It does so rather than using rigid frameworks.
Agile values beyond teams: It extends agile principles. These include individuals and interactions, responsiveness to change, and iterative learning. The extension moves from the team/process level to organization-wide design, leadership, and culture.
Organizational design & systemic thinking: AO is explicitly positioned alongside frameworks like Requisite Organization and the Viable System Model. It draws on systemic organizational theory while emphasizing adaptive structure and human-centric design.
First FORMALIZATION
Initial consolidation (around 2018): Neis publicly consolidated recurring agile patterns into the AO Model around 2018. He presents it as “key agile patterns from a decade of experience.”
Program for coaches, managers, HR: He created a program for agile coaches. It was also designed for managers and HR practitioners. This happened about five years before the 2022 Agile Alliance book listing. It was deliberately decoupled from any single agile methodology. This approach later fed into the AO concepts and patterns.
Books and “New Normal” framing: The Agile Alliance description of “The New Normal – AO Concepts and Patterns of 21st Century Agile Organizations” shows AO being framed as a comprehensive model with five areas (e.g., “Structure is not Organization,” transition phases, five experiences, five work areas) used to guide large-scale transformation.
Distinctive design choices
People-centric, organic growth: AO explicitly promotes “people-centric organic growth.” It is based on pillars such as coherence, cohesion, and simple rules. It also emphasizes avoidance and separation. These pillars reflect its origin in lived transformation work rather than abstract org charts.
Systemic, human-centric method: It positions itself as a systemic, human-centric method for agile transformation. This approach contrasts with more structural or team-bounded agile approaches.
Integration with existing agile practices: AO is often presented as something that extends or complements Scrum. It also enhances other frameworks. AO enables internal startups, swarms, and plexus-like networks inside organizations.
Five experiences or metrics in AO-method
The AO‑method defines five experiences (or experience‑based metrics) as its core measurement dimensions:
Enterprise experience – How the whole enterprise experiences agility. This includes strategy coherence and economic performance. It also covers the ability to respond to threats and opportunities. Lastly, it involves the perceived “agility of the business” at the top level.
Organization experience – This refers to how the internal organization experiences its own design. This includes the clarity of structures and roles, the flow of work, and decision latency. It also assesses how well the organizational setup supports agile dynamics.
People experience – How individuals and teams experience work. It includes engagement, autonomy, mastery, and psychological safety. It also encompasses the everyday feel of collaboration and leadership.
Customer experience – It encompasses how customers perceive the organization’s delivery. This includes value relevance, speed, reliability, and the ease of interacting with the company.
System experience – This refers to the behavior of the overall socio-technical system. It includes aspects such as stability, adaptability, and quality of feedback loops. Additionally, it considers how well the technical and social systems support continuous learning.
AO uses these five experiences as feedback loops. They are not merely output numbers like velocity. The “Experience Metrics Workbook” then breaks each dimension down into concrete indicators and templates.
Five work areas in AO-method
In AO, the “five work areas” are:
The platform – The stable, shared backbone of the organization. It includes core services, enabling functions, governance, and standards. These provide a safe container for experiments and day‑to‑day work. It is where you ensure coherence, basic rules, and support structures.
The Plexus – The dynamic network of relationships, communities, and cross‑cutting coordination mechanisms that connect units beyond the formal hierarchy. This is where knowledge flows, sense‑making, and alignment across silos happen.
Programs – Longer‑lived, mission‑driven streams that coordinate multiple initiatives around strategic themes or products. They give continuity, funding, and direction to clusters of work aligned with strategic outcomes.
Projects – Time‑bounded efforts with a clear goal, scope, and delivery horizon. They organize work that needs focus and structure but does not require a permanent or semi‑permanent stream.
Swarms – Highly adaptive, short‑lived, cross‑functional groups that self‑organize around urgent opportunities or problems. They embody the most fluid, emergent form of collaboration in AO, forming and dissolving quickly as needs arise.
Three frameworks dominate practical behavior change work: Fogg Behavior Model (FBM), COM-B, and nudge theory. Each operates at a different level—from moment-of-action design to systems diagnosis to policy choice architecture—and each has strengths and limitations. This guide consolidates the frameworks, compares them, and provides practical steps for designing nudges in health behavior change.
Part 1: Fogg Behavior Model (FBM)
Overview
The Fogg Behavior Model, developed by BJ Fogg at Stanford, explains behavior through a simple formula: B=MAP
Where:
B = Behavior (the specific action that occurs)
M = Motivation (the desire to perform the behavior)
A = Ability (how easy or simple the behavior is)
P = Prompt (the trigger or cue that says “do this now”)
Key Principle
Behavior occurs only when all three elements—motivation, ability, and prompt—converge at the same moment. If the target behavior is not happening, at least one of these three is missing or insufficiently strong.[1]
Core Components
Motivation
Motivation is the desire or inclination to perform a behavior. In Fogg’s view:
Motivation is variable and unreliable over time
It fluctuates based on circumstances, emotions, and context
Rather than relying on sustained motivation, effective behavior design focuses on making the action feel successful and reducing friction
Ability (Simplicity)
Ability refers to how easy or simple a behavior is to execute. Fogg defines this as “simplicity” and identifies six factors that increase or decrease ability:
Social deviance: How much the behavior violates social norms
Non-routine: How far removed the behavior is from established habits
Behavior design strategy: Shrink behaviors to “tiny” versions (e.g., 2 push-ups instead of a full workout, 30 seconds of journaling) and systematically reduce friction across these six dimensions.
Prompt (Trigger)
A prompt is the cue or signal that initiates the behavior at a specific moment. Without a prompt, even highly motivated and capable people often do nothing. Fogg identifies three types of prompts, matched to the person’s current motivation/ability profile:
Spark: Used when ability is high but motivation is low; adds motivational energy (e.g., urgency messages, benefit highlights, emotional appeals)
Facilitator: Used when motivation is high but ability is low; helps make the behavior easier (e.g., step-by-step guides, one-click options, walk-through)
Signal: Used when both motivation and ability are already high; simply a reminder (e.g., notification, calendar alert, familiar cue)
Prompts can also initiate behavior chains. A prompt for a small action naturally leads to larger actions. This progression happens without requiring additional external triggers.
Practical Application: Tiny Habits Method
The Fogg framework underlies the “Tiny Habits” approach, which involves:
Choosing a very small version of the desired behavior
Anchoring it to an existing routine (using that routine as the prompt)
Immediately celebrating success (to build automaticity and emotional reinforcement)
Example: To increase exercise, anchor “2 push-ups” to the moment after you pour your morning coffee, then celebrate immediately (“Yes!”). Over time, the behavior grows naturally without willpower.
Strengths of FBM
Clarity and simplicity: The three-part formula is easy to understand and apply
Immediate action focus: Excellent for designing specific moments and micro-actions
Practical for product and UX: Well-suited to app flows, habit-building, and digital design
Evidence-based: Rooted in behavioral science and widely tested in tech, marketing, and coaching contexts
Quick diagnosis: Helps identify which of the three elements is missing in any behavior
Limitations of FBM
Oversimplification: Ignores unconscious processes, social and structural influences, and feedback loops that sustain or extinguish behavior over time[2]
Limited for long-term complex change: Strong for triggering simple, discrete actions, but weak for multi-step, evolving, or culture-level behavior change[2]
Single-moment focus: Doesn’t model how behavior develops, generalizes, or is maintained across repeated episodes and contexts
Ethical gaps: Offers limited built-in guidance on whose interests are served or how to protect autonomy; the same tools can power both beneficial and manipulative design[2]
Attributed novelty: Some argue it repackages earlier behavioral science concepts without sufficient acknowledgment of prior work[2]
Part 2: COM-B Model
Overview
COM-B (Capability, Opportunity, Motivation → Behavior) is a systems-level framework for diagnosing and planning behavior change interventions. Michie, van Stralen, and West developed it. This framework is at the heart of the Behavior Change Wheel. The Wheel is a comprehensive taxonomy used in public health, clinical practice, and organizational change.[3]
Core Formula
Behavior = Capability+Opportunity+Motivation
Unlike Fogg’s moment-of-action model, COM-B views these three factors as a broader system. This system must be assessed and addressed for sustained behavior change.
Core Components
Capability
Capability encompasses the physical and psychological capacity to perform a behavior:
Physical capability: Strength, stamina, dexterity, sensory function
Intervention approach: Use feedback, incentives, goal-setting, identity appeals, and emotional messaging to shift both reflective and automatic motivation.
COM-B in Practice
To diagnose why a target behavior isn’t occurring or to design interventions:
Map the current behavior and identify barriers/facilitators across all three factors
Test assumptions with qualitative research (interviews, observations) and quantitative data
Design multi-level interventions: Change capability (training), opportunity (environment/policy), and motivation (incentives/messaging) in concert
Use the Behavior Change Wheel to translate diagnoses into specific intervention types (education, persuasion, incentivization, coercion, training, restriction, environmental restructuring, modeling, enablement)
Part 3: Comparing Fogg, COM-B, and Nudge Theory
FBM vs COM-B
Both models explain behavior through multiple factors, but at different scales and for different purposes.
Aspect
Fogg Behavior Model
COM-B Model
Primary Use
Designing specific, discrete actions and micro-habits[1]
Diagnosing and planning comprehensive behavior change interventions[3]
Key Components
Motivation, Ability (simplicity), Prompt[1]
Capability, Opportunity, Motivation[3]
Time Horizon
Short-term, moment-of-action[1]
Short- and long-term; includes skill and context development[3]
Environment Role
Via Ability and prompt placement; environment as friction or support
Central via Opportunity (physical and social environment)[3]
Typical Domains
Apps, UX, marketing, habit coaching[1]
Public health, clinical practice, organizational change, policy[3]
Depth
Surface level; what must align right now
Systemic; what must change for sustained behavior
Component Mapping
Motivation ↔ Motivation; Ability ↔ Capability + parts of Opportunity; Prompt ≈ specific behavior-change technique[4]
Broader, multi-level system
When to use Fogg: Designing app flows, habit-stacking, habit formation in controlled environments, moment-of-decision nudges.
When to use COM-B: Organizational transformation, health policy, long-term lifestyle change, diagnosing multi-level barriers, designing systemic interventions.
FBM vs Nudge Theory
Fogg and nudge theory both influence behavior through small design changes. They work from different angles. Fogg is a psychological causal model. Nudge theory is a design philosophy and toolkit.
Aspect
Fogg Behavior Model
Nudge Theory
What It Is
A behavioral model explaining why behavior occurs[1]
A policy and design philosophy about steering choices through choice architecture[5]
Role of Prompts
Explicit cues/triggers that initiate behavior[1]
One class of nudge among many (reminders, notifications)[5]
Defaults, framing, salience, simplification, social proof, loss aversion, anchoring[5]
Ethical Framework
Content-neutral; can be used for any behavior[1]
Rooted in “libertarian paternalism”: helping people choose better per their own interests, without coercion[5]
Freedom of Choice
Not a central concern; can be persuasive or neutral
Explicitly preserves all options and makes opting out easy[5]
Typical Use
App flows, micro-habits, trigger design
Public policy, pensions, health, savings, workplace programs[5]
Key insight: Fogg’s prompts are a specific nudge tactic. Nudges encompass a broader set of choice-architecture moves that often operate through motivation and opportunity shifts.
COM-B vs Nudge Theory
COM-B is a diagnostic framework, while nudge theory is one possible intervention style within it.
COM-B identifies levers (capability, opportunity, motivation) to intervene on
Nudges typically operate on motivation (framing, social norms, salience) and opportunity (simplification, defaults) without large incentive changes or bans
In a COM-B intervention plan, nudges are specific tactics under “opportunity” and “motivation” categories[3][5]
Integration: Use COM-B to diagnose; use nudge theory and Fogg’s model to operationalize specific intervention moves.
Part 4: Practical Steps to Design a Nudge for Health Behavior Change
Designing a nudge means systematically shaping the choice environment so the healthier option becomes easy, likely, and voluntary.[6]
Step 1: Define the Target Behavior Precisely
Specify exactly who does what, when, and where in concrete, measurable terms.
Example: “Employees aged 40+ book a preventive health check via the intranet portal. They should do this within the next 30 days. It can be done during their lunch break.”
Make behavior small and specific enough that it can be prompted, measured, and tracked
Ensure it is a reasonable, acceptable choice for the audience
Suitability check: Is this behavior low to moderate stakes? Are there multiple acceptable options? Is there a clear “better” choice as judged by the person’s own interests? If yes to all three, nudging is appropriate.
Step 2: Diagnose Barriers Using COM-B and Fogg
Conduct quick research (interviews, surveys, journey mapping, observational data) to understand why people are not doing the behavior now. Use both frameworks:
COM-B lens (broader system):
Capability: Do people know about the health check? Do they understand its benefits? Do they have the skills to book it (e.g., navigating a portal)?
Opportunity: Is the booking portal accessible? Is there sufficient time in their day? Do workplace norms support taking time for health checks? Are there scheduling or transportation barriers?
Motivation: Do people believe in the value? Is there anxiety or avoidance? Are competing priorities more salient?
Fogg lens (moment of action):
Motivation at the moment: Would an email or reminder raise desire?
Ability at the moment: Is the booking flow simple enough, or does it require too many clicks/decisions?
Prompt: Is there a clear cue/trigger for when to act?
Output: A prioritized list of barriers. Typically 1–3 factors block the behavior. Your nudge should address the primary one.
Select concrete mechanisms from established nudge toolkits. For health behavior, common and evidence-supported nudges include:
Defaults
Pre-select the healthier option but allow easy opt-out.
Example: Automatically schedule a follow-up health check appointment after each visit; patient can reschedule or cancel
Why it works: Overcomes inertia and status-quo bias; signals that the behavior is the norm
Salience and Simplification
Make the healthy action highly visible and cognitively easy.
Example: Clear, contrasting button (“Book Check-up in 2 Taps”); color-coded risk indicators; single-click booking via pre-filled forms
Why it works: Reduces cognitive load; reduces friction from Fogg’s “ability” dimension
Reminders and Timing
Send prompts when action is most feasible.
Example: SMS reminder the day before a scheduled appointment; in-app alert after lab results are ready; email 30 days before eligibility expires
Why it works: Provides the prompt (Fogg); aligns with moment when motivation and ability are likely highest
Social Norms
Highlight what peers are doing or what is considered normal.
Example: “8 out of 10 employees with your health profile attend their annual check-up”; “95% of team members are up to date with preventive screening”
Why it works: Leverages normative influence; reduces social anxiety; signals acceptability
Commitment and Progress Tracking
Ask for small, public or logged commitments and visibly show progress.
Example: “I commit to booking my health check by [date]”; dashboard showing team participation rates; streaks and badges for attendance
Why it works: Builds consistency motivation; leverages identity and public commitment; provides feedback
Incentives (Small, Non-coercive)
Offer modest rewards for behavior completion, without large financial penalties for non-compliance.
Example: Entry into a prize draw; small wellness points redeemable for minor perks; recognition in team communications
Why it works: Addresses motivation; must remain small and non-coercive to preserve libertarian paternalism
Design principle: Combine 1–3 mechanisms that directly address the barriers you identified, rather than stacking many unrelated nudges.
Step 4: Design the Concrete Intervention
Translate strategy into a specific flow, message, or environmental change.
Micro-copy and Messaging
Draft messages and interaction flows that are:
Easy: Use simple language, short sentences, active voice
Specific: Mention concrete benefits, time commitment, next steps (“Book in 2 minutes”)
Framed in gains: Emphasize what people gain, not what they risk losing (though some loss framing can work in specific health contexts)
Example:
❌ “You should schedule a preventive health check because health is important”
✅ “Free health check: 10 minutes, zero cost. Catch issues early. Book now in 2 taps”
Preserving Choice
Ensure all options remain available and transparent
Make opting out at least as easy as opting in (no dark patterns)
Do not use large penalties or restrictions to force compliance
Clearly explain what the nudge is doing (“We pre-selected Option A as the recommended choice, but you can choose anything you prefer”)
Ethics and Equity Check
Use frameworks such as APPEASE (Acceptability, Practicability, Effectiveness, Affordability, Side-effects, Equity)[6]:
Acceptability: Is the nudge acceptable to the target group and stakeholders?
Practicability: Can it be implemented in the real setting with available resources?
Effectiveness: Does evidence suggest it will work?
Affordability: What is the cost relative to benefit?
Side-effects: Are there unintended negative consequences?
Equity: Does the nudge work equally for all subgroups, or does it widen health disparities?
If possible, co-design with patients, employees, or end-users (design workshops, nudgeathons) to ensure buy-in and surface unintended consequences early.
Step 5: Test, Measure, and Iterate
Pilot Testing
Run a small, controlled test (A/B comparison or phased rollout) comparing nudge vs. baseline on a clear outcome: sign-up rate, appointment attendance, health-check completion rate, etc.
Document the design, message, timing, and audience precisely so results can be replicated or adjusted
Measurement
Track primary outcome (e.g., % of eligible employees who book within 30 days)
Monitor secondary outcomes: drop-off rates in booking flow, appointment no-show rates, equity gaps between demographic groups
Gather qualitative feedback: surveys, interviews, focus groups on usability, trust, and acceptability
Evidence on Effectiveness
Meta-analyses show that nudges are effective on average. Typical effect sizes range from 5 to 15% improvement in targeted behavior. Outcomes vary significantly by domain, quality of design, and population.[7]
Iterate and Refine
If effects are strong and equitable: Roll out more broadly, monitor ongoing, and optimize details
If effects are weak or unequal: Diagnose why (Was the barrier misidentified? Did the nudge fail to activate? Did it work only for some groups?)
Revisit COM-B/Fogg diagnosis: Perhaps the primary barrier was capability (need training) rather than motivation, or vice versa
Test alternate nudge mechanisms or combinations
Part 5: Criticisms and Ethical Considerations
Criticisms of Fogg Behavior Model
While FBM is widely used and has strong practical appeal, it faces several substantive criticisms:
Oversimplification
Reduces behavior to three factors while ignoring unconscious processes, social structures, feedback loops, and reinforcement that sustain behavior over time[2]
Does not model how behavior develops, generalizes across contexts, or is maintained across multiple episodes
Missing richer accounts of emotion, identity, social identity, and power dynamics
Limited Scope for Complex, Long-Term Change
Excels at triggering simple, discrete actions (clicking a button, 2 push-ups) but struggles with multi-step behavior change and lifestyle shifts[2]
Does not address how individuals develop skills, adapt to new environments, overcome setbacks, or internalize new values
Organizational and cultural behavior change requires more than prompts and ability tweaks
Ethical Concerns about Persuasive Technology
Fogg’s background in “captology” (computers as persuasive technology) has raised concerns that behavior design tools can power addictive, manipulative, or exploitative digital products[8]
The model itself is ethically neutral; it can be used to help people build good habits or to exploit cognitive biases for corporate profit
The model offers limited built-in guidance on whose interests are served, how autonomy is protected, or how “good” end behaviors are evaluated
Critics worry that widespread use of behavior design in tech, marketing, and social media has tilted toward manipulation rather than genuine user benefit[8]
Questions of Originality
Some argue that FBM repackages earlier behavioral science (operant conditioning, behavioral economics, habit formation) into a branded formula without sufficient acknowledgment[2]
This has led to concerns that promotion of FBM in tech may crowd out richer, evidence-based frameworks such as COM-B or the Behavior Change Wheel in policy and health contexts
Defenses and Internal Nuance
Even sympathetic accounts note that FBM is intentionally simple and must be combined with other models for fuller understanding, especially in health or organizational change[1]
Fogg’s Behavior Design Lab has published guidelines on ethical use of persuasive technology, emphasizing user autonomy, transparency, and well-being, though practice in industry often lags behind these ideals[9]
Ethical Use of Behavior Design
Whether using Fogg, COM-B, nudges, or other frameworks, ethical behavior design requires:
Transparency: Make clear to users that you are attempting to influence their behavior and how
User autonomy: Preserve freedom of choice and make it easy to opt out
Genuine benefit: Ensure the target behavior aligns with the person’s long-term interests and values, not just what is profitable for an organization
Equity: Test that interventions work fairly across all demographic groups and do not widen health or opportunity gaps
Accountability: Design with oversight, co-design with end-users, and be willing to stop or revise interventions that backfire or cause harm
Part 6: Integration and When to Use Each Model
Quick Decision Guide
Use Fogg Behavior Model when:
Designing a specific action or micro-habit (e.g., app on-boarding, sign-up flow, daily routine trigger)
The primary constraint is friction or prompting (not deep capability gaps or system-level barriers)
You have control over the user’s immediate environment (product, message, timing)
You want a fast, practical diagnosis of what’s blocking a discrete behavior
Use COM-B when:
Diagnosing why a behavior is not occurring at scale (organization, community, population)
You need to address multiple levels: individual, organizational, systemic
Create small initial action (register for clinic, not full check-up)
Nudge Designs:
Default: Pre-select clinic nearest employee’s home
Salience: Dashboard showing team participation rate (“87% of team is up to date”)
Simplification: Single-button booking from HR portal
Framing: Emphasize “free” and “10 minutes,” not disease risk
Capability Intervention:
Send brief video explainer: what the check includes, why it matters
Opportunity Intervention:
Partner with clinics for evening/weekend slots
Allow booking during work time without manager approval
Motivation Intervention:
Milestone recognition: badge at 50% and 100% team participation
Small incentive: wellness points toward gym or app subscriptions
Test & Iterate:
Measure sign-up rate, appointment attendance, and equity across age/tenure groups
Refine nudge copy, timing, and defaults based on feedback and data
References
[1] Fogg, B. J. (2009). A behavior model for persuasive design. In Proceedings of the 4th International Conference on Persuasive Technology. ACM.
[2] Halonen, E. (2024). Battle of the behavioral models: Fogg vs. COM-B vs. Behavior Change Wheel. LinkedIn.
[3] Michie, S., van Stralen, M. M., & West, R. (2011). The behavior change wheel: A new method for characterizing and designing behavior change interventions. Implementation Science, 6(1), 42.
[5] Thaler, R. H., & Sunstein, C. R. (2008). Nudge: Improving decisions about health, wealth, and happiness. Yale University Press.
[6] Michie, S., Atkins, L., & West, R. (2014). The behavior change wheel: A guide to designing interventions. Silverback Publishing.
[7] Pinder, C., Vermeulen, J., Cowan, L., & Beale, R. (2018). Digital behavior change interventions to break and form habits. ACM Transactions on Computer-Human Interaction, 25(3), 1–24.
[8] Susser, D., Roessler, B., & Nissenbaum, H. (2019). Technology, autonomy, and manipulation. Internet Policy Review, 8(2), 1–22.
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.
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.
Using the three supervision functions (normative, formative, restorative), the dual‑relationship situation surfaces different types of challenges. Each function highlights specific risks you would want to explore in supervision.
Normative function: ethics and standards
From a normative (ethical/standards) lens, challenges include:
Ambiguity about conflicts of interest and whether the dual relationship breaches your code of ethics or internal coaching policy (e.g. coaching someone you also appraise or influence organizationally).
Pressure from the organization or sponsor that pulls you away from agreed boundaries (e.g. requests for confidential information, subtle alignment with management’s agenda).
Formative function: learning and practice
From a formative (learning/development) lens, challenges include:
Limited skill or repertoire to work cleanly in a dual role: contracting. This includes resetting boundaries mid‑engagement. It also involves naming power dynamics in the room.
Your other role, whether HR, leader, or Agile coach, shapes your questions. It affects your challenge level and the topics you unconsciously avoid with this client.
Restorative function: well-being and impact on you
From a restorative (support/well-being) lens, challenges include:
Emotional strain arises from “split loyalties” between the client and the organization. There is also anxiety about “getting it wrong” ethically in a political system you belong to.
Over‑involvement or depletion: ruminating about the case. It includes difficulty switching off. You feel isolated because you can’t freely discuss it with internal peers due to confidentiality.
Systemic themes to surface in supervision
Across all three functions, supervision would explore:
How organizational culture (politics, expectations of HR/OD, leadership style) amplifies dual‑relationship risks for internal coaches.
What structures are missing or weak? These include policy, allocation rules, or access to external supervision. This issue is making you personally carry too much of the ethical and emotional load.
Internal coaches face several recurring ethical challenges, mostly around confidentiality, role conflict, and organizational power dynamics. Even when aligned with a formal code of ethics (e.g. ICF), the internal context makes these dilemmas more frequent and ambiguous.
Key ethical tensions
Confidentiality vs. sponsor expectations
Leaders or HR often expect detailed “updates” on the coachee’s progress or mindset. This expectation clashes with strict confidentiality obligations in most coaching codes.
Internal coaches can be formally or informally pressured to reveal sensitive information. This includes whether someone is a “flight risk”, under-performing, or critical of leadership. Such pressures directly test the code of ethics.
Conflict of interest and multiple roles
Internal coaches commonly hold another role, like manager, HR, OD, or Agile coach. This creates overlapping obligations and loyalties to the organization, the boss, and the client.
Expectations to “follow the boss’s directive” are a major source of pressure. This pressure often leads HR and internal practitioners to compromise ethical standards.
Perceived independence and psychological safety
Coachees not fully trust an internal coach’s independence. They fear that what they share harm their careers. This fear persists even if the coach adheres strictly to the code.
Organizational politics and informal networks can influence how people perceive the coach’s neutrality. They can also subtly shape which topics Coachees feel safe to explore.
Code of ethics specifics that get strained
Confidentiality and privacy
Professional frameworks (like ICF) emphasize that what is shared in sessions stays private unless explicitly agreed otherwise in the contract.
In internal coaching, standard HR practices (e.g. documenting risk, performance, misconduct) can clash with these commitments when the coach is also part of HR or management.
Autonomy and non-maleficence (no harm)
Ethical guidance highlights protecting client well‑being and autonomy, avoiding harm, and not exploiting the relationship.
Internal coaches are aware of organizational plans. These can include restructuring, layoffs, or performance procedures. These plans affect the client. But, coaches can’t always share them. This inability creates moral tension around “harm” and transparency.
Objectivity and avoiding misuse of power
Codes emphasize fairness, avoiding favoritism, and keeping clear boundaries with other roles.
Internal coaches are drawn into political games. They are used to influence employees towards certain decisions. Coaches also be subtly expected to “align” employees with management agendas rather than the client’s goals.
Typical dilemma patterns for internal coaches
Triangular relationship: sponsor–coach–Coachees
Ambiguity around what is shared at “three‑way” meetings (e.g. between HR, manager and Coachees) risks sliding from high‑level themes into personal details, breaching the code.
Misaligned expectations at the contracting stage can often lead to ethical conflict later in the engagement. The manager expects behavioral reports, but the coach promises confidentiality.
Boundary management and scope creep
Internal coaches can be asked to “just give some advice” on HR or performance issues. This can cross into consulting, assessment, or even disciplinary influence. These areas differ from coaching.
Coachees also seek special treatment or information since the coach is “on the inside”. This tests the boundary between coaching and confidential organizational knowledge.
Supervision and escalation challenges
Internal coaches sometimes lack a truly independent supervisor or ethics body inside the organization to discuss dilemmas safely.
Without clear internal policies and an external reference (e.g. ICF’s ethical complaint and review structures), coaches can feel isolated when they need to push back against senior leaders.
Practices that help uphold the code
Robust contracting and transparency
Clear three‑way contracting that spells out goals, reporting limits, and confidentiality boundaries from the start reduces later pressure and misunderstanding.
Documented coaching policies are aligned with a recognized code of ethics. They give internal coaches a formal reference when they need to say “no” to inappropriate requests.
Structural protections for independence
Some norms help preserve perceived and actual independence. One such norm is coaching outside one’s line of control. Another is having an independent ethics or review board.
Regular supervision, often with an external supervisor, aids reflection on ethical tensions. It also helps find blind spots and assess the impact of organizational politics on the coaching stance.
If helpful, the next step can be to map your specific internal role (e.g. HR, Agile coach, OD) against these patterns and design a tailored “ethical operating model” for your internal coaching practice.
Dual relationships are best handled by minimizing them where possible. When they can’t be avoided, it is important to make them highly explicit, contracted, and supervised. As an internal coach, that usually means separating roles structurally, naming conflicts early, and sometimes declining or ending coaching relationships.
Clarify what “dual relationship” means
A dual relationship exists when you and the Coachees have more than one role or relationship (e.g. coach and line manager, coach and HRBP, coach and close colleague/friend).
These situations create conflicts of interest and power imbalances. The ICF and EMCC codes need you to recognize, reveal, and manage or avoid these conflicts.
Design structural safeguards
Avoid coaching people where you have evaluative or formal power (direct reports, people you appraise, HR cases you manage). Swap coaches across units or levels instead.
Define in your internal coaching policy who internal coaches can and not coach (e.g. “never within own reporting line, never in active HR processes”).
Use transparent contracting
In the intake, name the dual role explicitly. You say, “I am both your Agile coach and your internal coach; here is how that will affect us.” Then explore risks together.
Build the dual role and its limits into the written coaching agreement: what you will not do (e.g. no performance advice, no participation in promotion decisions) and what happens if a conflict appears.
Monitor boundaries in practice
Regularly check: “Are my other roles influencing this conversation?” and “The client feel pressured because of my position?”
If topics drift into areas where your other role is dominant (e.g. HR investigation, performance rating), pause and either re‑route that topic to the appropriate process or end the coaching relationship for that issue.
Escalate, supervise, or step out
Use supervision (ideally external) to unpack any dual‑relationship tensions, blind spots, or emotional hooks before they harm the client.
If the conflict of interest can’t be mitigated, ethics guidance supports ending or transferring the coaching. For example, you must soon evaluate the Coachees. In such cases, it’s important to explain clearly why this step is necessary.
If you share your specific dual roles (e.g. “HR + internal coach for managers”), a concrete script and decision rules can be drafted for your context.
In a dual‑relationship case, HR gets involved when organizational risk or formal processes are triggered. An external supervisor is involved as soon as you feel ethically “stuck”. You should also involve them if you feel emotionally entangled or unsure how to continue. In practice, internal coaches are encouraged to consult supervision early. They should escalate to HR when the dilemma touches employment decisions. This includes policy breaches or potential harm to the client or others.
When to involve HR
Involve HR (or your equivalent role) when:
There is possible misconduct, discrimination, harassment, or safety risk disclosed in coaching. The organization is legally or ethically obliged to tackle these issues.
The dual relationship intersects with formal HR processes. These include performance management, restructuring, investigation, grievance, and whistle-blowing. You are expected to play a role in those processes.
You need to renegotiate the three‑way contract (sponsor–coach–Coachees). For example, do this if expectations on confidentiality have become misaligned. You should also do it if reporting has become impossible to honor.
When to seek external supervision
Seek an external (or at least independent) supervisor when:
You notice conflicting loyalties, strong emotions, or attraction. Over‑identification with the client can cloud your judgment in the dual relationship.
You are unsure whether to continue, refer, or terminate the coaching because of boundary issues or conflict of interest.
You need help to clarify options that protect client welfare. These options should respect the coaching code of ethics. They must also remain realistic in your internal political context.
How to decide whom to involve first
If the issue is primarily about organizational rules or employment risk, start with HR. Consult a trusted senior HR or ethics contact. Ideally, obtain the client’s knowledge where possible.
If the issue is primarily about your own boundaries, bias, or confusion, begin with external supervision. Consider a confidential ethics consultation. Then decide whether HR involvement is needed.
Good practice in a case study response
For a written case study or exam scenario, you can show ethical maturity by:
Stating that you would seek supervision early when a dual relationship emerges or shifts, to explore impact and options.
Explain clear criteria for HR escalation. These include risk, policy breach, and formal processes. State your intention to be transparent with the client about any need to involve HR.