How Team Coaching During Organizational Change Connects Reflection, Performance, and Enterprise Objectives

Team coaching during organizational change connects team reflection and the five GLCM layers with customer, departmental, operational, and enterprise perspectives.

A leadership team can contain capable people who perform well individually and still struggle collectively. Members arrive with different priorities, protect different measures of success, and leave meetings with different interpretations of what was decided.

An operational team can experience a similar problem. Employees cooperate well within the team, but their work depends on decisions, information, and resources controlled elsewhere. They compensate for unclear interfaces and competing initiatives until additional effort is no longer enough.

These difficulties rarely remain inside the team. They affect neighboring departments, project delivery, customer experience, and organizational performance.

Team coaching during organizational change can help a team examine how it interprets its environment, makes decisions, works across boundaries, and learns from experience. For that coaching to produce business value, it must connect internal team dynamics with operational responsibilities, customer outcomes, departmental objectives, and corporate strategy.

The team is not an isolated group. It is part of a wider organizational system.

What Is Team Coaching During Organizational Change?

The International Coaching Federation describes team coaching as working with a team as a collective to support sustainable results and continuing development. Its Team Coaching Competencies include team learning, systemic awareness, trust, safety, reflection, and collective action.

During organizational change, team coaching helps a team develop its capacity to:

Understand its collective purpose
Examine how members work together
Clarify roles and decision rights
Address disagreement constructively
Recognize assumptions and behavioral patterns
Learn from implementation experience
Understand customer and stakeholder expectations
Coordinate across functions
Connect its work with strategic objectives
Recognize issues that require wider organizational action

Team coaching is different from coaching several individuals separately. The subject of the coaching is the team: its purpose, relationships, decisions, performance, interfaces, and contribution to the organization.

It should be connected to real work. A team may need to make a difficult decision, implement a new operating model, coordinate several initiatives, improve a customer process, or establish responsibilities following a restructuring. These challenges provide practical material for reflection and development.

Begin With the Team’s Actual Responsibility

Before beginning a team-coaching engagement, clarify why the team exists and what it is collectively responsible for delivering.

This can be more difficult than it sounds.

Some groups called teams are primarily collections of individual managers. Members exchange information, but they have few shared deliverables or decisions. Other teams carry genuine collective responsibility but continue to operate as representatives of separate functions.

Useful questions include:

What must this team achieve together?
What decisions require the whole team?
Which outcomes can no individual member deliver alone?
Who are the team’s customers and stakeholders?
What authority does the team hold?
Which responsibilities remain with individual members?
Which objectives belong to the team, department, and enterprise?
What would be different if the team worked more effectively?

These questions establish whether coaching addresses a real collective need.

A team that lacks authority to resolve a priority conflict may need an executive decision. A team with unclear responsibilities may need organizational design work. A group missing essential expertise may need specialist support. Coaching can help identify these conditions, but it cannot substitute for the required management action.

Examine the Team From Four Perspectives

Team coaching can become too inward-looking if it concentrates only on relationships, meeting behavior, and communication. Those topics matter, but a team must also understand the consequences of its work beyond its own boundaries.

Four perspectives provide a more complete picture.

Perspective 1: What Are We Experiencing Inside the Team?

The first perspective examines the team’s internal experience.

Members may have different interpretations of the team’s purpose, priorities, and decision-making process. Some may believe that disagreement is welcome, while others have learned to remain silent. Responsibilities may appear clear on an organizational chart but become ambiguous when urgent work crosses functional boundaries.

Team coaching can explore:

Do we have a shared understanding of our purpose?
Are our priorities sufficiently clear?
Do roles and decision rights match the work?
How do we make and communicate decisions?
What happens when someone disagrees?
Can members acknowledge uncertainty and mistakes?
Which subjects are repeatedly avoided?
How is workload distributed?
Are we solving problems or passing them between members?
What have we learned from recent successes and difficulties?
Which behaviors strengthen or weaken trust?
How does the team respond under pressure?

This perspective includes culture, psychological safety, accountability, relationships, and working habits. It should also examine the team’s current capacity. A team cannot compensate indefinitely for excessive demands through better collaboration.

Perspective 2: What Are Customers and Stakeholders Experiencing?

A team may feel effective internally while producing poor results for the people who depend on its work.

Customer experience provides an important outside perspective. Depending on the organization, the customer may be a buyer, citizen, patient, member, supplier, partner, or internal recipient of the team’s services.

Relevant questions include:

What do customers need from this team?
What are they currently experiencing?
Are service quality, reliability, speed, or accessibility improving?
Which complaints or exceptions are recurring?
Where do customers experience gaps between departments?
Does an internal improvement create an external disadvantage?
Which assumptions about customer needs require testing?
How does current change affect customer relationships?
What do customer feedback and operational data show together?

A team may optimize one activity and still weaken the complete customer journey. For example, reducing handling time in one function may increase repeat contacts or create additional work elsewhere.

Team coaching can help members move beyond defending their own measures and examine the outcome from the customer’s perspective.

Perspective 3: What Do Our Department and Neighboring Teams Experience?

Teams work through interfaces. They receive information, decisions, resources, and services from others, and their own outputs become inputs elsewhere.

Difficulties often appear between teams rather than within them:

Responsibilities overlap or leave gaps
Handoffs are unclear
Information arrives too late
Several initiatives require the same specialists
Functions measure success differently
One team’s solution creates work for another
Local priorities conflict with departmental commitments
Problems are informally absorbed instead of escalated

Team coaching should therefore ask:

What does our department need from us?
What do neighboring teams need from us?
What do we require from them?
Where are our most important dependencies?
Which interfaces work well?
Where do delays, duplication, or misunderstandings occur?
Are local improvements shifting costs or risks elsewhere?
Which issues can the teams resolve together?
Which problems require a departmental decision?
How are other change initiatives affecting these relationships?

This is particularly important for cross-functional team coaching. Members must learn to hold both their functional responsibilities and their shared organizational responsibility.

Perspective 4: What Does the Enterprise Need From the Team?

The fourth perspective connects the team with corporate strategy and enterprise performance.

A team may deliver its local targets while contributing little to the broader objective. It may also be performing valuable work that is not visible through the measures currently used.

Questions should include:

How does our work contribute to corporate strategy?
Which enterprise objectives depend on this team?
Are our priorities aligned with current strategic direction?
How do our decisions affect other initiatives?
Which risks or dependencies should leadership understand?
Are we helping realize the intended benefits of change?
Where does operational evidence challenge strategic assumptions?
Which issues exceed our authority?
What information should reach the Change Office?
Which questions require enterprise governance?

This perspective prevents team development from being measured only by whether meetings feel better. The team should become more capable of contributing to outcomes that matter beyond itself.

Connect Team Coaching With the GLCM Layers

The GRIFFOX Layered Cake Model™ provides a structured but flexible way to connect team development with organizational change.

The GLCM is recursive. Reflection occurs within every layer, and evidence can lead the team to continue, adjust, wait consciously, or return to an earlier layer. Team development therefore does not follow a rigid sequence in which relationships are addressed once and considered complete.

Foundation and Experience: Understand What the Team Is Carrying

The Foundation and Experience Layer includes context, culture, behavior, readiness, and previous experience.

A team enters change with an existing history. Members remember previous reorganizations, abandoned initiatives, unresolved conflicts, successful collaborations, and leadership commitments that were or were not fulfilled.

Team coaching can examine:

What has this team experienced?
How does that history influence current behavior?
What assumptions do members hold about one another?
How have previous changes affected trust?
What informal practices help the team function?
Where does the team already demonstrate resilience?
What is the current workload and change demand?
How ready is the team for the next stage?
Which customer and stakeholder experiences form part of the context?

The purpose is not to remain focused on the past. It is to understand the foundation on which future work must be built.

Framework: Establish Conditions for Responsible Teamwork

The Framework Layer gives the team a practical structure for action.

This can include:

Collective purpose
Team and organizational objectives
Roles and responsibilities
Decision rights
Working agreements
Meeting and communication practices
Customer commitments
Performance measures
Interfaces with other teams
Feedback routes
Escalation paths
Confidentiality arrangements

A coaching engagement also needs its own framework. The team, coach, and sponsor should agree on the purpose of the work, who belongs to the team, how progress will be assessed, and what information may be shared outside the sessions.

A sponsor needs appropriate visibility into objectives and progress. That should not turn the coach into a private reporting channel on individual team members.

The framework should remain flexible. If coaching reveals that the team needs facilitation, training, technical advice, conflict resolution, or a management decision, that change in approach should be made explicitly.

Implementation: Practice Through Real Work

Team development becomes meaningful when the team applies new practices to actual responsibilities.

A leadership team might practice identifying the required decision before beginning a discussion. A project team might test a clearer approach to dependencies. An operational team might redesign a handoff with a neighboring department.

Implementation activities might include:

Working through a real collective decision
Testing a new meeting or review structure
Clarifying an operational interface
Practicing constructive disagreement
Running a short improvement experiment
Redesigning how decisions are communicated
Conducting a customer-perspective workshop
Testing new role or accountability arrangements
Using agile working cycles
Reviewing actual examples between coaching sessions

The team can test, apply, adapt, expand, and eventually embed more effective practices.

The coach supports observation and learning. The accountable leaders remain responsible for business decisions.

Recalibration: Learn Through Reflection and Retrospectives

Reflection should occur at every GLCM layer, but the Recalibration Layer brings evidence together and asks what should happen next.

Retrospectives offer a useful recurring method. The official Scrum Guide describes the purpose of a Sprint Retrospective as planning ways to increase quality and effectiveness. Teams outside formal Scrum environments can use the same underlying discipline: inspect recent experience and select practical improvements.

A team retrospective might ask:

What were we trying to achieve?
What actually happened?
What helped us?
What created difficulty?
Which assumptions proved accurate?
Which assumptions were challenged?
What did customers experience?
What did neighboring teams experience?
What do performance indicators show?
What are team members noticing that the measures do not show?
What should we continue?
What should we adjust?
What should we test next?
What requires a decision outside the team?

The team should avoid turning retrospectives into general conversations that produce no action. Choose a small number of changes, assign ownership, and examine their effect during the next cycle.

Recalibration can lead to four responses:

Keep the course: Current progress is appropriate.
Adjust within the current layer: Maintain the direction but change the approach.
Wait consciously: Pause or reduce speed because capacity, timing, evidence, or a decision is missing.
Return to an earlier layer: Revisit the foundation or framework because experience has challenged an important assumption or design choice.

These options connect agile team coaching with disciplined change management.

Goal: Connect Development With Meaningful Outcomes

The Goal Layer asks whether team coaching contributes to outcomes that matter.

Possible indicators include:

Clearer collective decisions
More consistent communication
Stronger accountability
Earlier identification of dependencies
More reliable follow-through
Better operational handoffs
Improved customer outcomes
Progress toward departmental objectives
Contribution to corporate priorities
Greater ability to adapt without losing direction
More sustainable working practices

Measures should be interpreted carefully.

Fewer escalations could mean the team resolves more issues itself. They could also mean that people have stopped raising concerns. Faster decisions could indicate improved clarity or insufficient examination. Better business results may reflect several developments occurring at the same time.

Combine behavioral observations, team experience, operational measures, stakeholder feedback, and customer evidence. Team coaching should not be treated as the only possible explanation for a change in performance.

When effective practices continue after the engagement, they become part of the team’s Foundation and Experience Layer for the next challenge.

Use Workshops, Retrospectives, and Agile Approaches Purposefully

Team coaching may include or connect with several forms of support. They should not be treated as interchangeable.

Team coaching

Team coaching helps the team develop its collective ability to observe, learn, decide, coordinate, and act. It normally occurs across multiple working and reflection cycles.

Retrospectives

Retrospectives provide a recurring opportunity to learn from recent experience. They can become part of the team’s normal operating rhythm and support reflection within every GLCM layer.

Workshops

A workshop creates concentrated time to address a defined question. It may clarify purpose, examine stakeholder perspectives, resolve an interface, establish working agreements, or design an experiment.

A successful workshop can produce an important result, but one workshop rarely creates sustained behavioral change by itself.

Facilitation

Facilitation helps a group conduct a productive discussion or complete a defined task. The facilitator supports the process without necessarily entering a longer-term coaching relationship.

Training

Training develops knowledge or skills. A team may need training in decision-making, conflict management, agile methods, change leadership, or another defined capability.

Consulting

Consulting provides analysis, expertise, or recommendations. It is appropriate when the team needs knowledge or an assessment that cannot reasonably be generated through coaching alone.

Management action

Some conditions require leaders to make a decision, assign authority, change priorities, provide resources, or correct an organizational design problem.

Team coaching can help people recognize the need. It cannot take responsibility for the decision.

Team Coaching Across Change Units

Within the GLCM Enterprise Change Architecture, teams, departments, business units, and other organizational areas can function as Change Units. Each Change Unit applies change within its own context and retains appropriate local ownership.

Team coaching can help a Change Unit understand:

What it is experiencing
What it can resolve locally
How it is performing
Which experiments are producing useful results
What customers and stakeholders are experiencing
Which dependencies cross its boundaries
What requires support or a wider decision

Operational Integration becomes necessary when activities and consequences extend beyond one Change Unit.

Examples include:

Several teams depend on the same system release
Multiple initiatives compete for the same resources
A local process change affects customer work elsewhere
Departments receive conflicting priorities
A team’s improvement transfers workload to another unit
An enterprise policy prevents a workable local solution

A team should not be expected to absorb these problems through greater cooperation or personal effort. It should make the evidence visible and use the appropriate organizational decision route.

This connects team coaching with Operational Integration in Change Management.

Move From Team Reflection to Enterprise Action

Some discoveries belong within the team. Others have enterprise implications.

A Change Office can integrate signals from different Change Units, identify patterns across initiatives, and prepare management options. Enterprise governance can then make decisions involving priorities, sequencing, resources, risk, or strategic direction.

The path may look like this:

A team reflects on its experience.
The team identifies an issue it cannot resolve locally.
The operational consequences and supporting evidence are described.
Related signals from other Change Units are connected.
The Change Office prepares the issue and possible responses.
Authorized leaders make the necessary decision.
Direction returns to the affected teams.
Teams examine whether the response works.

Team coaching strengthens the team’s ability to participate responsibly in this process. It should not create a parallel governance structure or encourage teams to bypass accountable management.

The GLCM Enterprise Change Architecture connects local experience, Operational Integration, decision support, and enterprise direction.

When Is Team Coaching the Right Intervention?

Team coaching is particularly useful when:

The team holds genuine collective responsibility
Interaction patterns contribute to the problem
Members interpret priorities or decisions differently
Important disagreement is being avoided
The team struggles to learn from experience
Functional interests repeatedly override shared responsibility
Customer or stakeholder perspectives receive insufficient attention
Dependencies are recognized too late
Decisions are made but not consistently carried into the organization
The team needs to adapt its practices during continuing change

Another intervention may be more appropriate when:

The group has no meaningful collective purpose
Essential decision authority is missing
Roles or structures require formal redesign
Technical expertise is unavailable
A specific conflict requires mediation
Members need defined skills training
The organization expects coaching to compensate for excessive workload
Leadership is unwilling to address issues that the coaching reveals

In many situations, the appropriate solution will combine coaching with facilitation, workshops, training, consulting, or management action.

Questions for a Team-Coaching Engagement

Before beginning, ask:

Purpose and responsibility

Why does this team need to work as a collective?
What outcomes is it responsible for?
What decisions belong to the team?
What authority does it hold?

Internal experience

How do members experience the team?
Which patterns help or hinder its work?
Can members challenge assumptions?
Where are roles, priorities, or expectations unclear?

Customer and stakeholder perspective

Who depends on the team?
What are those stakeholders experiencing?
How does the team know?
Which customer outcomes should improve?

Departmental and operational perspective

Which teams and functions are connected to this work?
Where are the critical handoffs and dependencies?
What can be resolved locally?
Which problems cross organizational boundaries?

Enterprise perspective

How does the team contribute to strategy?
Which corporate objectives depend on it?
What evidence should reach enterprise leadership?
Which issues require a wider decision?

Learning and evaluation

What practices will the team test?
How will retrospectives be used?
What evidence will indicate progress?
How will improvements become part of daily work?
How will the team sustain learning after the engagement?

Team Coaching Should Improve the Team’s Contribution

Team coaching during organizational change should help a team understand more than its own relationships.

The team must be able to look inward at its culture, behavior, roles, and decisions. It must also look outward at customers, neighboring teams, departmental responsibilities, and enterprise objectives.

The GLCM layers provide a structure for that work:

Foundation and Experience clarify what the team is carrying.
Framework establishes the conditions for responsible action.
Implementation turns learning into practice.
Recalibration connects reflection with adjustment.
Goal links team development with sustainable organizational outcomes.

Retrospectives and agile approaches create recurring opportunities to learn. Workshops provide focused spaces for particular questions. Operational Integration connects consequences across Change Units. The Change Office and enterprise governance address decisions that exceed the team’s authority.

The purpose of team coaching is not simply to make collaboration feel better. It is to help the team become more capable of understanding its environment, learning from experience, improving its performance, and carrying its organizational responsibility during continuous change.

If your team is working hard but still struggling with collective decisions, cross-functional dependencies, or inconsistent follow-through, contact GRIFFOX Consulting to discuss whether team coaching, facilitation, or another form of support best fits the situation.

By Harald Lavric | Founder, GRIFFOX Consulting | Creator, GRIFFOX Layered Cake Model™

About Harald Lavric

Harald Lavric is the founder of GRIFFOX Consulting and creator of the GRIFFOX Layered Cake Model™. His work focuses on the connections among leadership, strategy, organizational change, operational responsibility, and enterprise decision-making. Drawing on more than three decades of experience in the German health-insurance system and work across public- and private-sector environments, he helps leaders make overlapping change more coherent and workable.