Every engagement leaves something behind — an observation, a shift, a question that stayed open. Field Notes are where we record those things.
 

C O N T E X T The company had, by most visible measures, arrived. A Series B funding round. Headcount that had more than trebled in eighteen months. A product gaining genuine market traction. From the outside, this looked like a team executing well under pressure. Inside, something corrosive was taking shape. Our work here began through a co-founder who reached out with a question: why did it feel harder to lead now than it did when there were twelve people? The organisation had grown to nearly 90. The processes were being built. The roles were being filled. And yet the leadership team — five people who had known and trusted each other through their education years — felt, in his words, 'strangely far away from each other.' The setting was in a South India state. The sector was enterprise SaaS. The pace of growth was the kind that looks triumphant in pitch decks but feels relentless inside conference rooms. W H A T B E G A N E M E R G I N G Early conversations with leadership team members — conducted individually — revealed something that doesn't show up on dashboards: an erosion of psychological safety at the very top of the organisation. Each person spoke with care — diplomatically, even — but the themes across conversations were striking in their consistency. People felt that honest disagreement in meetings had become harder. Decisions were being made, but not always in the room where they were nominally being discussed. A few key relationships had accumulated unspoken grievances that were now shaping behaviour more than anyone was acknowledging. One co-founder described feeling 'managed' by his own colleagues. Another said she had stopped raising certain concerns because the emotional cost of navigating the aftermath wasn't worth it. There was also a subtler dynamic: as the company had grown, each founder had necessarily become the leader of a larger function. Former peers were now, in some sense, interdependent executives. The informal mechanisms that had once kept them aligned — shared meals, spontaneous whiteboard sessions, a culture of blunt honesty — had disappeared. The external performance was real. But the internal friction that was surfacing was beginning to cost the organisation in slower decisions, in duplicated efforts, in a middle layer of managers who could sense the tension at the top and were navigating around it rather than through it. K E Y D I S C U S S I O N T H E M E S 1.Trust, when examined closely, is rarely one thing. In this leadership team, what had eroded was not affection or respect — those remained — but something more specific: the confidence that one's perspective would be received without consequence, and that what was said in one room would not be subtly deployed in another. 2.Accountability had become complicated. As the organisation scaled, informal accountability had given way to formal structures. But the emotional contracts between co-founders — the unspoken agreements about how decisions were made, who had authority over what, how disagreement was expressed — had not been renegotiated. There were recurring tensions about ownership, about credit, about who was building what and whether it was being seen. 3.Role identity was shifting in ways that hadn't been named. Several founders were privately grappling with what it meant to lead at this scale — not as inventors or builders, but as organisational stewards. For some, that transition was happening faster than it felt comfortable to admit. 4.There was also loneliness — not dramatic, but present. The higher you sit in an organisation, the fewer people you can speak freely with. And for founders who had once had each other for that, the growing distance was felt as a kind of quiet loss. N A T U R E O F T H E W O R K We began with individual conversations — unhurried, exploratory, without agenda. The goal was not to diagnose but to understand: what each person was carrying, what they needed, what they found themselves not saying. From there, a series of facilitated leadership conversations were designed — not off-sites with agenda slides, but structured spaces for honest reflection. Ground rules of decorum were established before everything else. Some of the most productive work happened in mapping the informal decision-making landscape — understanding where decisions were actually being made, and whether that matched where people thought they were being made. There was also careful work around role clarity — discussions about authority, ownership, and the unspoken agreements that had been carrying the team and were now beginning to strain under new pressures. The approach drew lightly on adaptive leadership thinking — particularly the distinction between technical problems and operational challenges — and on group dynamics frameworks that helped the team understand some of what was happening between them as systemic and relational, not merely interpersonal. D U R A T I O N & E N G A G E M E N T S T R U C T U R E This engagement, began with individual conversations over the first six weeks, followed by a sequence of facilitated leadership sessions — initially fortnightly, then monthly as the work deepened and the team developed more capacity to sustain the inquiry themselves. The scope evolved over time. What began as a co-founder's question about leadership difficulty became a broader engagement with how the organisation's culture at the top was being experienced throughout. Mid-way through, a parallel stream of individual coaching was added for two leaders navigating significant personal leadership transitions. W H A T S H I F T E D The change was not dramatic. What shifted was more like texture: a slightly greater willingness to name what was true, a few previously unspoken things that were spoken, a renewed — if fragile — habit of checking in with each other before and after significant decisions rather than simply informing. Some of the unspoken grievances found language though a couple of tensions remained structurally embedded in how the organisation was shaped, and naming them did not dissolve them. But there was value in no longer pretending they weren't there. One described the shift by saying that he had stopped feeling like he was managing a performance for his colleagues and had started feeling like he was working with them again. That is a modest outcome, according to him. It is also not a small one. The middle layer of the organisation also began to feel more settled. R E F L E C T I O N –Trust erodes in high-growth organisations without notice and incrementally — rarely through a crisis, almost always through accumulation. –Proximity does relational work in early-stage companies. As organisations grow, that work doesn't disappear — it has to be done more deliberately. –Middle layer absorbs leadership tension before leadership acknowledges it. Settling the top changes the temperature lower down. –Unspoken grievances between founders don't stay contained — they shape decisions, slow alignment, and eventually cost the organisation. –Naming a tension honestly is often more stabilising than resolving it quickly.

C O N T E X T The organisation was a mid-sized NGO working in livelihoods and rural development — the kind of institution that runs on mission more than margin. The work is meaningful enough that the people doing it tolerated conditions they would not accept elsewhere. The founder had built it over 14 years. From a small pilot programme in two districts to an organisation with staff across seven states, funding relationships with international donors, and a name that was beginning to carry weight in the sector. She was, by most accounts, a remarkable leader: intelligent, deeply committed, instinctively empathetic, relentlessly energetic. She came to this engagement at the recommendation of a peer, a fellow founder. She arrived, presenting issues named as “decision fatigue” and “succession planning”. W H A T B E G A N E M E R G I N G What became apparent fairly early was the degree to which the organisation's emotional architecture had been built around her. Not by design, and not without her awareness — she had noticed it, had even tried to address it — but the pattern had taken hold in ways that went beyond any individual relationship. Staff brought her not only operational decisions but emotional ones. Senior programme managers sought her reassurance before acting on plans they had themselves authored. Conflict between teams was routinely held in abeyance until she could mediate it. Donors expected her presence at conversations where her presence was not technically necessary. Board members were deferential to a degree that had effectively removed one of the few sources of external accountability she could have leaned on. She had become, in a very real sense, the container for the organisation's collective anxiety. And the container was almost overflowing. What was less visible — and what she herself had not fully named — was the toll this was taking. The decision fatigue she mentioned was real. But underneath it was something closer to a slow grief: a sense that the work she had loved — the field work, the design work, the thinking — had been almost entirely displaced by the work of holding everyone else together. There was also loneliness of a particular kind. At the top, there is no peer. Also she was not someone who found it easy to acknowledge her own needs, and the culture she had built had, in some ways, made that harder rather than easier. K E Y D I S C U S S I O N T H E M E S 1.The concept of the 'emotional container' emerged early and stayed central. In organisations with strong founding figures this is often unconscious, and it is also welcomed by the founder when it feels like care, unique rather than a burden. 2.The question of dependency ran through the work. Not just the organisation's dependency on her, but a subtler pattern: her own relationship with being needed. Recognizing that the pattern had costs did not immediately make it easy to change. 3.Succession was present throughout, but not quite in the way she had initially framed it. The question was not simply who might lead after her, but what kind of organisation she wanted to lead now — and whether the organisation as it currently functioned could survive the redistribution of emotional weight that real delegation required. The relationship with her own wellbeing — and the way the organisation's culture implicitly discouraged her from claiming it. N A T U R E O F T H E W O R K Much of the early work involved simply making the invisible visible: naming the dynamic, creating language for what she was experiencing, and giving her permission — which she had to extend to herself — to take it seriously rather than push through it. There was reflective inquiry into the origins of the pattern: how the organisation had come to function this way, what needs it was serving on both sides, and what had made it difficult to interrupt. Transactional Analysis offered a useful, lightly-held frame — particularly around the relational patterns that had become habitual between her and various members of the team. Gradually, the work turned to practical questions: which dependencies were most costly, and what would be needed — structurally and relationally — to begin distributing them. This was crucial work, because it involved neither abandonment nor overhaul, but a slow and thoughtful transfer of capacity and confidence to others. There were also conversations about what she wanted to reclaim — specifically, which parts of the work had sustained her and could do so again. D U R A T I O N & E N G A G E M E N T S T R U C T U R E It ran across approximately nine months, with coaching sessions held fortnightly, each ninety minutes. There were two longer reflective retreats — one at the three-month mark and one near the close — that allowed for slower, less structured inquiry. Towards the later months, a small number of conversations with senior team members were introduced — not as a parallel intervention, but as a way of beginning to make the organisational shifts visible in shared language. W H A T S H I F T E D The shifts were gradual and, in places, still in progress at the engagement's close. Some structural changes were made — including a revised decision-rights framework and more deliberate investment in the senior team's capacity to work through conflict without escalation. An interna shift was noticed: a growing ability to observe when she was absorbing something that wasn't hers to hold, and some developing confidence in setting limits on that — not coldly, but as a different kind of care. She also began reclaiming some of what she had lost: some field visits, working with younger programme staff. It was a beginning, she felt confident about. The loneliness remained, to an extent. What changed was her relationship to it: less denial, more acknowledgement, and a small but growing network of peers she had begun to trust with it. R E F L E C T I O N –Founder-centred organisations don't self-correct — the very qualities that make a founder effective also make it easy for the pattern to persist unexamined. –Being needed and being well are not the same thing. Many founders conflate them for years before the distinction becomes visible. –Succession planning is premature if the organisation can't yet function without routing its anxiety through one person. –In mission-driven institutions, the founder's own needs are often the last to be named — and the culture of the organisation can make naming them feel like a betrayal of mission. –The most important thing a founder sometimes needs to build is not the next programme — it is a more distributed organisation.

C O N T E X T The team was inside a large corporate in the speciality chemicals sector — a significant business unit that had undergone four major transformation programmes in six years. Restructuring, process redesign, compensation change, a digital systems overhaul, and most recently, a post-merger integration that had brought in new leadership, new processes, and, in the phrase used with some frequency in leadership communications, 'a new way of working.' By most performance metrics, the team delivered. They met targets. They adapted. They implemented. From a distance, they looked like a team that knew how to navigate change. The Head of Business Operations brought us in because her leadership team was what she called 'unresponsive' to the latest change agenda. In her words: 'I know they're capable. But it's like talking into a room with no echo. Nothing comes back.' There had been workshops. There had been town halls. There had been a team away day. Very little had moved. W H A T B E G A N E M E R G I N G Initial conversations with the team — conducted in a format that was explicitly not an assessment — surfaced something that had been entirely absent from the change management narrative: people were exhausted - something cumulative and more systemic. Several people described a particular kind of tiredness that comes from having invested fully in change processes that did not, ultimately, deliver what they promised — and then being asked to invest fully again. One team member, with remarkable precision, called it 'the fatigue of hope.' What had been read from the outside as disengagement or passive resistance was, on closer examination revealed a protective posture. People had stopped investing emotionally in change initiatives because the pattern was familiar: significant noise and effort in the first few months, then gradual dilution as competing priorities arrived, then a quiet redefinition of success, then — eventually — a new change agenda. There was also a grief of sorts, which had not been acknowledged or named. Several long-tenured employees had loved aspects of the culture and ways of working that had existed before the successive transformations. Those things were gone. No one had mourned them. The language of organisational change did not make space for loss. And underneath all of this: a deep ambivalence about leadership. Not hostility, but a kind of careful, watchful caution. People had seen enough transitions to know that leaders shift. They had learned… to wait. K E Y D I S C U S S I O N T H E M E S 1.Four transformation programmes. Six years. The team had delivered through every one of them. What they hadn't been given was time to recover. By the time the fifth initiative arrived, the emotional reserves that change actually runs on — trust, hope, willingness to try — were gone. That isn't resistance. It's depletion. 2.The question of psychological safety in change processes surfaced repeatedly. People were not safe to say that the last initiative had not worked, or that they were exhausted, or that they needed something different before they could re-engage. The absence of that safety did not produce rebellion — it produced compliance with low investment, which is perhaps more insidious. 3.Several people named the same thing, in different ways: not that they distrusted the current leadership, but that they'd watched the organisation's stated direction bend too many times to believe it would hold. The strategy that had been worth sacrificing for two years ago had been replaced. The one before that too. No explanations offered. They weren't disengaged from this leader. They were disengaged from the organisation's relationship with its own commitments. N A T U R E O F T H E W O R K The initial request — “help us get the team on board with the change programme” — was reframed: before the team could re-engage with the change agenda, something had to be acknowledged. We facilitated a series of team reflective sessions — not structured workshops with change management frameworks, but slower conversations: what has it been like, these last few years? What did we lose that we haven't named? What would it take for us to believe that this time is different? These were not easy conversations. Some of what emerged was difficult for leadership to receive. There was frustration, some quiet anger, several moments of surprising candour. But the act of creating that space — and of leadership being willing to listen without defending — was itself a significant shift. What emerged from these conversations was not just a shift in how the team was being understood — it began to alter the organisational structure itself. An existing senior person was given a formal mandate as Internal Coaching Partner, creating a sustained internal presence for the kinds of conversations that had previously had no home. Quarterly working committees were also established across the functions and processes that had seen the most change — not as governance bodies, but as spaces where people doing the work could surface what was and wasn't holding, before it accumulated into something harder to address. None of this was designed in advance. It grew out of what the facilitated conversations kept pointing to: that the organisation needed new infrastructure for honest dialogue, not just another change initiative. D U R A T I O N & E N G A G E M E N T S T R U C T U R E This engagement is representative of the kind of work that has shaped Solution ONE's approach to change and transformation contexts. It ran across approximately 5 months — beginning with individual conversations over a three-week period, followed by three full-team reflective sessions spaced approximately six weeks apart. Parallel to this, monthly coaching sessions with the Head of Business Operations provided continuity and a space to process what was emerging across the broader work. The work is ongoing, but now paced to suit the rhythm of recovery as much as the rhythm of progress. W H A T I S S H I F T I N G The most significant shift was in the framing. The team was no longer ID-ed — internally or by leadership — as resistant. That change in language, which might sound small, had material consequences: it changed how leadership approached the team, which changed how the team responded. Several team members described feeling, perhaps for the first time in years, that their experience had been taken seriously. Not solved — they were appropriately cautious about that word — but acknowledged. A few said they were willing to try again. Some were not yet there. The change agenda was not abandoned. But it was adjusted, slowed, and re-sequenced in ways that took into account the team's actual current capacity. The Head of Business Operations made that decision herself, and communicating it honestly to the team had more impact than any workshop had managed. The work intentionally left some things unresolved. There are structural dynamics within the business unit — specifically around resourcing and recognition — that are contributing to the fatigue and were outside the scope of what we could directly address. R E F L E C T I O N –Organisations rarely pause to ask whether their people still have capacity to give to the next change initiative — absence of overt resistance is taken as readiness. –Labelling exhausted people as resistant is both inaccurate and costly. It forecloses the more important question. –Repeated transformation, each arriving before the last has been metabolised, produces learned self-protection in a workforce — not cynicism, not character failure. –The emotional work of change is where most initiatives lose ground. Process design alone cannot compensate for depleted trust. –When a leader stops defending the past and listens to what the room is actually carrying, something shifts — usually faster than any structured intervention.

C O N T E X T He was, by the usual measures, successful. General Manager in a railway engineering third-party vendor firm, a company that supplied specialised components and technical services to infrastructure projects across the region. Sixteen years with the organisation, the last four in his current role. A reputation for analytical rigour and operational reliability. A team that performed. A peer group that respected him. He came to this coaching engagement — initially framed as executive coaching — at the nudge of the company's MD and Founder, who had noticed a flatness in his engagement over the previous year and, knowing him well enough to be direct about it, had suggested he might benefit from a conversation outside the organisation. He was, he clarified early, not in crisis. He was not unhappy in any way he could precisely name. He was simply, in a word he returned to several times across early sessions, 'somewhere else.' W H A T B E G A N E M E R G I N G What emerged, slowly and with considerable precision on his part — he was someone who chose his words with care — was a description of incremental estrangement. Not from the company, exactly, or not only that. But from the version of himself that had been engaged, motivated, genuinely interested in his work and responsibilities. He could still do the work — he was doing it — but the internal quality of engagement had changed. Problems that had once absorbed him now felt like things to be dispatched. Decisions that had once felt consequential now felt routine. He was also, he said, less curious than he used to be. And curiosity, it became clear as these conversations developed, was for him an indicator — something that marked whether he was genuinely interested or performing it. K E Y D I S C U S S I O N T H E M E S The question of identity at senior levels in mature organisations is often unspoken and underexplored. When roles are well-defined, when performance is strong, when external markers of success are abundant, there is little structural permission to ask whether the role still fits the person — or more precisely, whether the person the role was built for still inhabits the individual carrying it. What he was navigating was something close to an identity transition — a mismatch between an external role that had continued to develop and an internal sense of self that had been quietly evolving in a different direction. He had grown; the role had also grown; they had not necessarily grown together. There was something around mastery and its complications. He had become very good at what he did. And in becoming very good at it, some of the aliveness had drained out of it. This is a recognised phenomenon in high-performing individuals who reach a level of competence at which the work no longer asks them to stretch — but it is rarely talked about plainly in most organisational cultures. The question of meaning surfaced regularly: not in a philosophical or abstract sense, but quite concretely. What, in the daily texture of his working life, felt like it mattered? That question turned out to be harder to answer than he had expected. N A T U R E O F T H E W O R K Through coaching there was inquiry into the history of his engagement with work: not a career review, but something more like an archaeology of what had animated him at different points, and what those threads suggested about what mattered now. Discussion also went into the distinction between work that engages and work that depletes — and the degree to which the balance had shifted in his current role. This opened a question he had not previously allowed himself: whether the role could be reshaped, or whether what he was experiencing was pointing toward something more fundamental. There was also work around what he described as 'the parts of himself he had parked' — interests, capacities, inclinations that had been de-prioritised in the upward trajectory of his career and had never quite been reclaimed. What this work deliberately did not do was rush toward a decision. The question of whether to stay, leave, or reshape was premature for most of the engagement. The more urgent work was developing clarity about what was actually happening — naming the experience accurately — before beginning to respond to it. D U R A T I O N & E N G A G E M E N T S T R U C T U R E The engagement has been running for approximately eight months, with fortnightly sessions of approximately ninety minutes each. There were two extended sessions midway through, where more structured reflective material was worked through over a half-day. The scope remained primarily individual throughout, though towards the end a few conversations touched on how some of this emerging thinking might be articulated within the organisation. W H A T I S S H I F T I N G Mostly internal, and it would be premature to call it resolved. What changed was the quality of his relationship to his own experience: a movement from a vague, unlocated discomfort to a clearer, named understanding of what was happening. He identified two or three specific aspects of his role that were most depleting, and began a process of redistributing some of those responsibilities to juniors he has been grooming. He also identified a project area — technical innovation in a component category the company had underinvested in — where his genuine curiosity now lay, and negotiated with his Manager to take a more direct role in its early-stage development. By the end of the engagement, he described himself as 'more present.' Not transformed, not resolved, but more present. He attributed this less to any specific change and more to the simple act of having taken his own experience seriously for a sustained period. He had not, by the time the work closed, decided whether to stay in his role long-term. That question remained open — and we had worked hard to ensure it felt like an open question rather than a problem requiring immediate resolution. R E F L E C T I O N –High performance and internal aliveness are not the same thing — organisations rarely distinguish between them, and individuals rarely feel permitted to. –Mastery without stretch produces a particular kind of slow disengagement that is hard to name and harder to admit to. –Competence as an emotional necessity — rather than simply a professional quality — is worth examining carefully. It carries its own costs. –The most useful early work in cases like this is often not direction-setting, but accurate naming: what is actually happening, without it being immediately converted into a plan. –Some questions need to be held before they can be answered. Premature resolution closes off what longer inquiry would have found.