Maya Was Told She Needed More Experience. Three Years Later, She Was the CEO.
She Had Been Carrying More Than Her Title Suggested
Maya had worked in the nonprofit sector long enough to understand how easily responsibility could outgrow a job description. She had joined her organization in a mid-level program role, but over time the work around her expanded. When a senior manager left, Maya absorbed several of the responsibilities while leadership decided what to do with the position. She began managing budgets she had never formally been assigned, coaching newer staff, dealing with increasingly complex funder expectations, and representing the organization in community conversations that once would have belonged to someone several levels above her. She learned quickly because she had to, and because she cared deeply about the mission. The organization was doing work she believed mattered, and Maya was willing to stretch when the work required it.
People noticed that she was capable. They told her so regularly. She was described as dependable, resourceful, committed, and someone who could always be counted on when things became difficult. Compliments came easily, but advancement did not. Whenever a leadership opportunity appeared, Maya seemed to be valued most for how useful she was exactly where she already sat. Her capacity had become convenient. Moving her upward would have created a gap somewhere else, and nobody seemed particularly motivated to solve that problem.
For several years, Maya interpreted that pattern generously. She assumed there would eventually be a conversation about progression. She thought the additional responsibility was evidence that senior leadership was preparing her for something larger, and she continued saying yes to opportunities that allowed her to learn. The problem was that development without recognition can eventually become something else. Maya was growing professionally while the organization continued describing her through a title that no longer reflected the level at which she was operating.
Ambition Became Something She Felt She Had to Hide
Maya wanted to lead an organization one day. She had known that for several years, although she rarely said it aloud. In the nonprofit world, ambition can sometimes become complicated because people are expected to speak primarily about service, mission, and community rather than their own professional aspirations. Maya cared deeply about all of those things, but she also wanted responsibility. She wanted to influence strategy, shape organizational culture, manage resources well, and sit at the table where decisions were actually being made. She did not see a contradiction between wanting to serve and wanting to lead.
Still, she learned to soften the way she talked about her goals. When someone asked where she saw herself in five years, she said she hoped to continue growing rather than saying she wanted to become an executive director. When she asked about leadership development, she framed the conversation around how she could better support the organization. She worried that naming her ambition too clearly would make her appear impatient or self-important. She had watched talented people become labelled as “too ambitious” when what they had really done was acknowledge that they wanted more responsibility.
The irony was that leadership was already using Maya's ambition every day. Her willingness to learn was the reason she could be handed unfamiliar problems. Her drive was the reason she stayed late to understand budgets, funding agreements, policy requirements, and human resource issues that were technically beyond her role. Her curiosity was the reason she wanted to know why decisions were made rather than simply carrying them out. The organization benefited from those qualities while offering her little evidence that they saw them as executive potential.
The Opportunity She Thought Would Change Everything Did Not
When a director-level role eventually became available, Maya applied. She had already been performing parts of the work and believed the opportunity might finally formalize the progression that had been happening informally for years. She prepared carefully for the interview, speaking about the programs she had strengthened, the partnerships she had built, and the operational problems she had helped resolve. She also talked about the organization as a whole, because by then she had learned to think beyond her own department. She left the interview nervous but hopeful.
The job went to someone from outside the organization. Maya was told that the successful candidate had broader leadership experience and that she should continue developing because her potential was clear. The feedback was delivered kindly, but one phrase stayed with her: she needed more experience. She drove home that evening trying to understand what kind of experience they meant. She was already managing work above her level, already helping solve organizational problems, and already carrying responsibilities that had once belonged to more senior positions. If that experience did not count, she wondered where she was supposed to get the experience that would.
For several weeks, Maya continued working exactly as she had before. She congratulated the new director, helped with the transition, and answered questions because she knew the organization well. She did not become resentful or withdraw. What did change was the story she was telling herself. Until then, she had assumed the organization simply had not found the right opportunity to advance her. For the first time, she considered the possibility that they might never see her beyond the role in which they had first learned to depend on her.
Rebuilding Began When She Looked at Her Capacity Instead of Her Position
The turning point came through a conversation with someone outside the organization. Maya was attending a community meeting when a senior nonprofit leader she had worked with on several initiatives asked why she had never considered an executive role. Maya laughed and explained that she still had experience to gain. The leader looked genuinely confused. She had watched Maya manage complicated partnerships, navigate competing stakeholder expectations, speak confidently with funders, and keep projects moving when other organizations were struggling. From her perspective, Maya was not someone waiting to develop leadership capacity. She was someone whose current organization had not yet named what was already visible to others.
That conversation unsettled Maya in a useful way. She began documenting what she had actually been doing rather than relying on her title to describe it. She had participated in budget planning, contributed to strategic discussions, supervised staff informally and formally, represented the organization externally, managed risk, responded to crises, and interpreted contractual requirements. She understood frontline service because she had worked close to it, but she had also developed a systems view of how governance, leadership, funding, people, policy, and community expectations interacted. None of those experiences made her automatically ready to be a CEO, but together they showed far more executive capacity than the title on her résumé suggested.
Maya also became more honest about what she did not know. She had limited direct experience working with a board. She had not carried final accountability for an organizational budget. She understood government funding agreements but had never been the person signing them. Instead of treating those gaps as evidence that she was not ready, she began treating them as areas she could deliberately learn. That distinction mattered enormously. Capacity does not mean already knowing everything a future role will demand. Sometimes capacity is visible in how quickly someone understands complexity, how thoughtfully they identify what they do not know, and how deliberately they prepare to carry greater responsibility.
Becoming a CEO Required More Than Believing in Herself
Maya did not resign impulsively and declare that everyone had underestimated her. She spent the next year preparing. She joined a committee that gave her greater exposure to governance. She asked an experienced executive director to mentor her and began learning more deliberately about board relationships, financial oversight, organizational risk, human resources, and the loneliness that can accompany senior leadership. She read budgets differently, listened more carefully during strategic conversations, and began asking herself what she would need to know if the final decision stopped with her.
That preparation changed the kinds of jobs she considered. She stopped applying only for positions that looked like a modest step above her current title and began examining smaller organizations where the executive director role required broad leadership capacity rather than a perfect history of having already been an executive director somewhere else. One organization caught her attention because it was at a genuine turning point. The mission was strong, the staff cared deeply about the work, and the board knew the organization needed clearer systems, stronger internal communication, and someone capable of connecting operational reality with strategic direction.
Maya applied for the CEO position and approached the interview differently from any she had done before. She did not spend the conversation trying to convince the board that her title understated her experience. She talked about the work itself. She described how she thought about mission, people, sustainability, risk, culture, and accountability. When she was asked about something she had never directly managed, she did not disguise the gap. She explained what she understood, what she would need to learn, and how she would approach the responsibility. The board was not looking for someone who had already lived their exact future. They were looking for someone with enough judgment, humility, drive, and capacity to lead the organization into it.
They offered her the role.
The Title Changed Overnight. Becoming the CEO Did Not.
Maya quickly discovered that being capable of becoming a CEO and actually sitting in the CEO's chair were two different experiences. On her first morning, there was no magical transfer of certainty. There were staff expecting leadership, a board expecting information, funders expecting compliance, community partners expecting continuity, and a budget that looked very different when she became the person ultimately responsible for understanding it. Decisions that once would have travelled upward now stopped with her. Some days she left the office exhilarated by the opportunity. Other days she sat in her car for a few minutes before driving home because she needed time to absorb the weight of everything she was carrying.
The experience taught Maya that executive capacity is not loud. It is not the confidence of someone who always knows what to do. Much of leadership is the ability to remain thoughtful when information is incomplete, to ask better questions before making consequential decisions, and to resist using authority as a substitute for understanding. She drew on years of being closer to frontline work because she knew how executive decisions eventually arrived in employees' lives. She also learned to resist the temptation to solve everything herself, recognizing that the habits that had once made her indispensable could become dangerous if she carried them into the CEO role unchanged.
For emerging and experienced nonprofit leaders, this is where resources such as The Executive Director’s Bridge and the broader leadership and governance work of Mission Matters Studio can become valuable. Becoming an executive director is not simply a promotion into a larger job. It is a shift in accountability, perspective, relationships, and responsibility, and leaders benefit from understanding the bridge between being highly capable within an organization and becoming responsible for the organization as a whole.
What Maya Had Been Rebuilding Was Her Understanding of Her Own Potential
Years later, Maya could look back at the organization that had passed her over without needing to make them villains in the story. The director they hired may genuinely have been the stronger candidate for that particular position. There were things Maya still needed to learn, and some of the disappointment she experienced had pushed her to prepare more deliberately for executive leadership. What she no longer accepted was the conclusion she had quietly drawn at the time: that because one organization did not see her as ready, she was not capable of becoming ready.
That is the part of being undervalued that can follow people long after a particular workplace ends. The greatest damage is not always the missed promotion, smaller salary, or title that failed to keep pace with responsibility. Sometimes it is the gradual internalization of someone else's assessment of your ceiling. When a capable professional spends enough time being valued primarily for what they can carry rather than what they could become, they can begin mistaking organizational convenience for an objective measure of their potential.
For someone emerging from that kind of professional experience, Rebuild™ is not about manufacturing confidence or pretending every career disappointment was unfair. It is about examining the wider evidence: the responsibilities entrusted to you, the people who have experienced your work, the capabilities that have developed beyond your title, the gaps that still deserve attention, and the ambitions you may have learned to make smaller in order to remain acceptable where you are.
Maya became a CEO because she had capacity, but capacity alone was not enough. She had to recognize it, test it, develop it, and eventually take it somewhere that had room for it. The organization she left had seen a highly dependable employee. The organization that hired her saw an emerging executive. Both were looking at the same woman at roughly the same point in her career. What changed was not her potential overnight. What changed was the size of the opportunity through which that potential was finally allowed to become visible.
