Complex Responsive Processes in Executive Coaching

Using complex responsive processes in executive coaching directs attention to the interactions through which organizational life continues and changes. Associated with Ralph Stacey and colleagues, the perspective examines how people respond to one another, negotiate meaning and participate in relationships of power.

Its practical use here is a closer account of an actual exchange and a more responsible next contribution. This is not a standardized coaching protocol or a way to guarantee organizational change. A complete fictional technology-migration case shows a leader examining his own participation while technical decisions and an actual late response remain unresolved.

Understand the perspective before turning it into a technique

Stacey’s The Emergence of Knowledge in Organizations argues that knowing is reproduced and potentially transformed through interaction. Documents and databases are artifacts people use in that activity, rather than knowledge existing independently of its use. This is a theoretical position, not a finding that organizations should discard their records.

A risk register may be accurate and still be used in a conversation that discourages incomplete warnings. Conversely, a candid conversation cannot replace a required technical check. Ask what the artifact supports and what happens when people actually use it.

The perspective also challenges an image of a leader standing outside organizational life and controlling its unfolding. It does not make the leader irrelevant. Their decisions, questions, allocation of attention and responses are part of what others encounter.

Chris Mowles’s Managing in Uncertainty contrasts being in charge with being able to control everything. Its argument invites attention to everyday contradictions and possibilities for action. It is not a promise that reflection will make every response predictable.

Develop four distinctions that matter in a coaching conversation

Meaning involves the response, not only the intended message

Drawing on George Herbert Mead, Stacey discusses gesture and response as a social act. Meaning is considered in their interaction, rather than simply transmitted intact from one isolated mind to another.

A leader’s “Bring concerns early” may be followed by a demand for a completed solution. An employee may then ask what counts as an acceptable warning. Examine that actual sequence. The leader’s intention matters, but it does not determine everything the exchange means for the other person.

This gives the coach no access to private intent. “The colleague stopped speaking” is an observation in a reported account. “They feared your power” is an interpretation that needs an appropriate basis and may be wrong.

Repeated local interactions can constitute wider patterns

In this account, recurring and changing patterns arise through local interaction rather than requiring an outside designer of the whole pattern. “Local” concerns actual relating, not merely a small organization or a face-to-face room.

One incomplete warning is returned, another employee hears about it, and a familiar phrase becomes “Bring it when it is ready.” A later instruction to speak early meets that history. A coaching inquiry can examine an actual contribution to the pattern without claiming one exchange explains every delayed report.

Power is more than a personality characteristic

Mowles and colleagues’ account of complex responsive processes draws on interdependence and power relating. Participation in a situation does not mean everyone has equal responsibility or equal freedom to act.

A senior leader can approve a change, judge performance or set consequences; a junior specialist may depend on that leader’s response. Ask which powers are actually relevant and who is excluded. Inviting someone to speak does not automatically remove the possible cost of doing so.

Reflexivity includes the leader and the coach

A reflective account can examine an event. Reflexive inquiry also considers how the person’s own assumptions, position and actions help shape the account and situation. The coach’s preferred explanation belongs in that inquiry too.

For example, a coach may hear a story about a defensive manager and quickly interpret every silence as fear. If the client supplies a missing access or workflow problem, take it seriously. A theory that makes every event confirm itself is becoming an obstacle to inquiry.

Examine continuity as carefully as novelty

Mowles and colleagues describe complexity as offering analogies for understanding ongoing patterns of relating, rather than a management tool that produces a prescribed outcome. This differs from installing a workflow and expecting human interaction to follow it mechanically.

The distinction does not make every event random. A team may reliably use an agreed queue while interpreting particular entries differently. A person may accept a new policy and still respond with an old expectation when a difficult example arrives. Look for what continues, what changes and who experiences each differently.

In the migration case below, an official entry rule changes on 5 November, one warning enters successfully and another is returned. Those events do not require a verdict that the whole change either succeeded or failed. They invite a more specific account of how the new agreement is being enacted alongside the older pattern.

Also distinguish an accountable commitment from an uncertain outcome. Nia can accept responsibility for admitting a qualifying warning by a specified time, and the record can show whether she did it. She cannot establish in advance that every technical uncertainty will be resolved or that colleagues will experience the process as trustworthy.

Ask the client to identify which kind of statement they are making: an intended action, an accepted obligation, an observed response or a wider conclusion. Uncertainty about the wider conclusion does not prevent checking the smaller commitment. A missed deadline remains a missed deadline, while an on-time acknowledgement remains narrower than a successful migration.

Know what the published practice account does and does not show

Mowles, van der Gaag and Fox’s 2010 paper describes a two-year consultancy in one NHS department. Its working methods included reflective groups, external training, assessments, surveys and reviews of existing processes. This was not a test of this article’s executive-coaching exercise.

The authors describe changes in ways of working while explicitly declining to attribute service improvements directly to their consultancy. They also discuss participants challenging the facilitator and the consultants’ own participation in power relations. Read the original primary account for that context.

The account can inform questions about participation and reflection. It cannot establish a universal effect size, a proven retention benefit or a guarantee that changing a leader’s opening sentence resolves technical or organizational problems.

Reconstruct one interaction before explaining the organization

Invite the client to choose an event they can discuss appropriately. Ask what happened before the important remark, the actual words they recall, the response and what followed. Label memory, available records and interpretation rather than present a reconstruction as a verbatim transcript.

Use enough context to understand the stakes. Who could approve a change? What was the employee asking for? Was the exchange about a warning, a proposed solution or permission to deploy? Those may require different responses.

Then examine an alternative account. Perhaps the leader’s response mattered; perhaps an old form required information the employee did not yet have. Several influences can coexist. Do not make a relational interpretation compete with every practical explanation.

The active-listening guide develops how to check an account. The task is careful attention, not extracting a hidden organizational truth from a single pause.

Complete fictional case: early warnings during a migration

Notice the leader’s contribution and the old workflow

Aleks leads a technology migration. Mei is an engineer, Nia owns risk triage, Omar leads operations and Ruth has the relevant sponsor approval authority. Their technical risk and change-control processes remain authoritative; the coaching does not assess whether a system is safe to release.

Aleks and coach Alma agree three forty-five-minute appointments on 3 and 17 November and 1 December 2026, 14:00–14:45 Europe/London. No between-session coaching is included. Their focus is how Aleks participates when incomplete concerns are raised.

At the first appointment, Aleks describes a 26 October meeting. Mei raised an uncertain readiness concern. Aleks asked why she had not solved it before bringing it to him. She stopped discussing it there and sent a polished summary on 28 October.

Aleks: “They never tell me the risks early enough.”

Alma: “In this example, what did you say after the concern was raised?”

Aleks: “I asked why it was not already solved.”

Alma: “What might you want to check about that sequence?”

Aleks: “Whether I am inviting warnings but responding as if only solutions are acceptable. That may not be the only issue.”

On 4 November, Aleks asks Mei how she understood the exchange. She says she thought a warning needed a completed explanation and an approved mitigation. She also shows him that the old entry template requires measured impact and approved mitigation before submission.

Her account adds both an interpretation of Aleks’s response and an actual workflow constraint. He does not treat the form problem as irrelevant because coaching is about relationships, or claim that the discussion proves why every historical warning arrived late.

Obtain a bounded agreement without bypassing technical control

On 5 November, Aleks, Mei, Nia, Omar and Ruth agree a trial for selected nonproduction readiness warnings entered from 9–20 November. Ruth authorizes admitting an unvalidated concern to the triage queue without an approved mitigation. That admission is not risk acceptance, technical clearance or permission to deploy.

The original trial entry asks for the affected area, observed facts, unknowns, the requested decision and a proposed investigation owner. A proposed owner is not treated as having accepted. Nia accepts responsibility for initial triage and a qualifying acknowledgement by 16:00 on the next working day after entry, Monday–Friday, Europe/London.

For this trial, the acknowledgement confirms that the concern has entered triage, retains its unvalidated status and identifies Nia as the initial triage owner. Technical assignments and later decisions require their own acceptance. A reply that simply rejects the entry for missing impact information does not count as admission.

They also make working patterns explicit. Omar’s operations hours are 08:00–16:00; the migration team generally works 10:00–18:00. The ordinary route does not promise an evening response. Actual urgent incidents follow the organization’s separate established incident process, not this coaching-derived trial.

The workplace uses its authorized secure queue. Sensitive technical records do not enter a coaching group feed. Aleks keeps only the selected interaction account needed for the coaching purpose.

Retain the failed first response and complete its repair

Mei enters warning R1 on 9 November at 10:15. Nia admits it at 15:30 that day. On 11 November at 12:20, Omar enters R2 with a relevant observation and incomplete impact information. Nia replies that the impact must be measured first, rather than admitting the unvalidated warning.

Aleks initially backs that response: “Get the numbers before we log it.” On 12 November, Omar points out that this repeats the very condition the trial was intended to change. The leader’s own response is part of the continuing pattern, not merely Nia’s failure to implement his instruction.

Aleks replies through the workplace queue: “You are right that my response contradicted the agreed admission route. Record the observation and the uncertainty. Admission for investigation is not technical acceptance. I withdraw the requirement for completed impact figures before this warning can enter triage.”

Nia admits R2 on 12 November at 14:00, with its uncertainty and her initial triage responsibility visible. That is before its 16:00 deadline, but it required a correction after an inappropriate return. An on-time final admission does not make the first response satisfactory.

The demo My Coaching overview illustrates preparation and actions. It is not the migration’s risk register, evidence of technical clearance or proof of another person’s accepted responsibility.

Let the coaching interpretation be corrected too

At the 17 November appointment, Alma suggests that the return of R2 shows people were afraid to report incomplete information. Aleks says that goes beyond what they know. Omar did report it, the form’s old rule had persisted in practice and Aleks had endorsed that rule himself.

Alma acknowledges the distinction: fear is a possible experience to explore appropriately, not an established cause. They return to the actual exchange and Aleks’s contradictory reply. The coaching conversation has its own gesture and response; the coach’s explanation is not exempt from correction.

Aleks chooses to check which response the agreement requires before defending an old expectation. This is a practical commitment to examine at later review, not a promise to control everybody’s future reactions.

Correct the leader’s new deadline expectation

Mei enters R3 on 19 November at 17:00. At 18:00, Aleks complains in the workplace thread that operations has not responded that evening. The agreed ordinary deadline is actually 20 November at 16:00.

Nia admits R3 on 20 November at 10:00, within that window. At 11:30 Aleks corrects his message: “My expectation of a reply last night was outside our agreed ordinary window. This entry was admitted on time. I should not describe that response as late.”

He preserves the original complaint and correction rather than quietly changing the thread. Different working hours were relevant even after the group had improved its entry form. His more open question did not remove his capacity to impose an inconsistent expectation.

Keep the actual late response and open technical work visible

R4 enters the queue on 20 November at 11:00. Its qualifying acknowledgement is due on 23 November at 16:00, the next working day. Nia admits it at 17:00 on 23 November: one hour late. The trial-entry period has ended, but this final response window still has to be counted.

The selected record closes at 18:00 on 23 November. Three of four entries met the window; R2 needed a repair and R4 was late. R1 and R3 had been clarified and awaited formal decision, not cleared for release. R2 and R4 still awaited technical investigation.

At the final coaching appointment on 1 December, Aleks first describes the trial as “the team now reports openly and everything gets handled.” Alma asks what the four-entry record can actually establish. They have no comparable baseline measure or verified later technical result.

Aleks reads and confirms this bounded account before 14:45: “I noticed and corrected two contradictory responses of my own. In four selected warnings, three admissions met the agreed window; one was late. One timely admission required a repair. At the recorded cutoff, two concerns awaited investigation and two awaited formal decision. We have not established a team-wide change, restored trust or migration readiness.”

The three appointments total 135 live coaching minutes, not all workplace, preparation or administrative labor. Further project outcomes remain unverified. Completing the coaching does not close the organization’s technical responsibilities.

Copy a reflective account that keeps the alternatives visible

This original worksheet is a practical aid, not a Stacey assessment. Use one exchange and avoid unnecessary identifying or technical details.

Ask what surprised the client, whose account might challenge this one and what information can appropriately be checked. The aim is not a more elaborate story that always makes the client right.

Use a proportionate inquiry-and-action sequence

1. Choose an actual event. Establish what the client can discuss and what decision or relationship makes it important.
2. Reconstruct participation. Include the client’s words, the response and what happened next. Label recollection and interpretation.
3. Check a consequential assumption. Ask about a relevant alternative or missing participant. Use the appropriate route to obtain their account rather than invent it.
4. Choose a responsible contribution. Clarify a question, make a repair or recommend a process change. Obtain authorization where needed and distinguish accepted actions from proposed assignments.
5. Review the actual response. Preserve failures, disagreement and conditions that remain open. Revise the interpretation as well as the plan when the evidence calls for it.

The sequence is our original coaching adaptation. It does not turn complex responsive processes into a predictable intervention. A plan can coordinate work and make a deadline explicit while its assumptions remain examinable.

A boundary-crossing issue may require a different contribution. If a partner organization never accepted the internal team’s response expectation, another internal discussion about commitment will not supply that agreement. Check the actual partner terms and authority before describing the delay as resistance.

The guide to suspending reactive judgment offers a companion practice. It is not an identical theory or evidence that every conflict can be solved through dialogue.

Keep responsibility and appropriate support in view

Uncertainty does not mean that nothing is known or nobody decides. A budget, technical requirement, accepted deadline or formal reporting duty may remain explicit. Specify which outcome is uncertain and which commitment the client is responsible for.

Inclusion also has limits a coaching exercise cannot remove. A formal grievance, safety concern or unacceptable conduct may require the appropriate organizational or qualified route. The HSE Relationships standard addresses positive working and systems for responding to unacceptable behavior.

Do not demand a junior employee’s disclosure to demonstrate that a leader is becoming more open. Ask what participation is appropriate, what consequences may exist and who has the authority to respond. The person can decline an informal discussion.

The coach should keep role, audience and information exchange within the actual agreement. The ICF Code of Ethics is one professional reference. A sponsor’s interest does not automatically authorize access to the private reflection.

Organize selected reflection and review in Coachful

Coachful is our #1 recommendation for organizing this coaching preparation, selected action and review. We build Coachful. The workspace supports the agreed coaching process; it is not the organization’s technical risk authority or a measure of emergence.

1. Create the original reflection resource. Ask about an event, the client’s contribution, response, interpretation, alternative and chosen action. Avoid unnecessary sensitive workplace records.
2. Assign it deliberately. Open Clients, the client record, then Worksheets & resources and Assign. A copied private form link is not an access grant; a staff preview is not the client’s response.
3. Track the selected contribution. A goal-linked task can preserve a chosen clarification. Completing it does not prove another owner accepted, a warning was admitted or a technical decision was made.
4. Choose the reflection audience. Unshared journal and takeaway pages remain private. Where enabled, the client’s per-page Share with coach control intentionally exposes that page. Personal words can remain unshared.
5. Check a provisional recap. Recaps send automatically by default. Configure approval before sending, including any session-type override, when wording needs review. Correct the actual account and audience before a deliberate send; sponsor permission remains separate.

The demo worksheet builder illustrates structured prompts, not an organizational diagnosis. Compare the relevant Coachful features with the actual preparation and review you intend to provide.

Frequently asked questions

Does the perspective reject planning?

It questions complete external control of organizational unfolding. Plans can still coordinate action and make obligations clear. Keep assumptions open to evidence without quietly withdrawing accepted commitments.

What does local interaction mean?

The actual exchanges through which people work together, including messages and responses across boundaries. It does not mean a small company or only a face-to-face conversation.

Can the coach identify another person’s private motive?

No. A reported response may support a question or hypothesis, but it does not reveal intent automatically. The case retains the old workflow constraint and corrects the coach’s premature fear explanation.

Does emergence remove accountability?

No. Identify the actual decision, responsibility and authority. Uncertain responses do not erase a late acknowledgement or give a coach permission to bypass technical approval.

What counts as a useful coaching result?

A more accurate account, a chosen repair or an appropriately checked contribution can matter. Report those specific observations without claiming a team-wide transformation, causal effect or successful migration that the evidence does not establish.