My daughter said something about transitions being hard.

We were walking into a sushi restaurant on her birthday, talking the way we often do about life and what we notice in it. I responded that transitions are natural, inherent in the human experience, and that we get two practice sessions every day — we wake to greet the day and we sleep beneath the moon and stars. Morning arrives and invites us into creation, movement, and connection. Evening comes and asks something entirely different: relaxation, restoration, recovery.

She looked at me with wide eyes and a bit of exasperation. “Yes, and those transitions are hard for me too!”

Sometimes she stays up too late reading because she is completely engrossed in a book. She is well aware the following morning will be rough. She knows she needs to sleep well in order to function. But she doesn’t want to stop reading. And when morning arrives, she struggles to wake and greet the day cheerfully because she wants more sleep.

I smiled with appreciation and nodded with understanding. These are the moments I adore as a parent — the very human struggles we face and tend to overlook, spoken aloud.

I have been thinking about that conversation ever since. She was spot-on. Something can be completely natural and also be quite challenging.

Maybe I had been thinking about transitions backwards for most of my life. Which led me to a question: how many times do we transition in a lifetime?

I started with the most obvious. Every morning we move from sleeping to waking; every evening, from waking to sleeping. Two transitions a day is 730 a year. Add the four seasonal crossings many of us experience and we are at 734. Add a birthday — the annual passage from one age into the next — and we are at 735. Over an 80-year lifetime, that is 58,800 transitions.

Which is a comically conservative number.

It doesn’t include leaving home and returning, the beginning and ending of work, being alone and joining other people, starting a meal and finishing one, departing on a trip and coming back. It doesn’t account for weekdays becoming weekends and weekends becoming Mondays. It leaves out adolescence, graduation, falling in love, marriage, parenthood, children leaving home, career changes, moves, menopause, retirement, and aging. It doesn’t include illness and recovery, or the all-encompassing grief that accompanies loss.

And it certainly doesn’t include the transitions no one else can see — changing your mind, outgrowing a belief, no longer wanting something you spent years pursuing, realizing someone isn’t who you thought they were, or realizing you aren’t who you thought you were. The cycles of forgiving, releasing, and beginning again.

I suspect the real number across a human lifetime is not in the tens of thousands but in the hundreds of thousands.

Yet we reserve the word transition for the ones we can easily identify. Divorce, retirement, a new job, a move, a birth, the death of someone we love. As though the rest of life happens on stable ground.

But what if it doesn’t? What if life itself is the transition, and stability is only the interval we perceive between them?

I am not the same woman who woke up yesterday morning. The difference is almost imperceptible, because one day rarely changes us enough to notice. But put 50 beside 40, or 40 beside 20. Put the person you are today beside the person who once believed she knew exactly what her life would become, and the transition becomes visible. We are continuously becoming while experiencing ourselves as continuous.

What has changed in you so slowly that you didn’t realize it was changing until you looked backward?

The natural world is constantly transitioning. Morning becomes afternoon, day becomes night, the tide comes in and goes out, the moon waxes and wanes. Summer becomes autumn and the leaves change color before they release their hold and fall. Seeds wait while fields lie fallow. The cycle of bloom, death, and decay prepares the ground for what will grow once conditions become amenable. Nature doesn’t seem particularly concerned with remaining what it was.

I am not attempting to romanticize change. Not every transition in nature is gentle — storms come, rivers flood, forests burn, trees fall. Birth itself can be violent. Nature isn’t teaching us that change should always be peaceful. It may be teaching us something else entirely: that transition is the mechanism of growth, of evolution, of life itself.

What fascinates me most is that nature gives transition something we rarely give it — time, space, and a threshold. Dawn doesn’t instantly become noon. Autumn doesn’t arrive one morning with every leaf simultaneously orange. There is an in-between, a period when something is no longer quite what it was and isn’t yet what it will become.

We treat that in-between as the part to hurry through, as though the real transition happens on either side of it. I am no longer convinced. The in-between is the transition.

Which returns me to the book. My daughter knows she needs to sleep. But she is still inside the story. She wants five more pages, another chapter, a little longer to extend the pleasure. Sleep requires her to relinquish something she is enjoying. And then morning makes its own demand: leave the warmth, leave the bed, leave sleep behind and begin.

Maybe that is what makes transitions hard. They require us to leave something. And sometimes the hardest things to leave are the things we love. A beautiful season ends as the next one emerges. A wonderful trip concludes with a flight home. Children grow up even when we would happily freeze certain versions of them forever. Relationships, bodies, and dreams change. We change.

So perhaps the question isn’t whether you are resisting where you are going, but whether you are grieving what you have to leave in order to get there.

Maybe our work isn’t to become people who never struggle with transition, but people who recognize the season they are in. Who allow themselves to inhabit the threshold. Who know when to hold on and when holding on has become resistance. Who trust that not knowing what comes next doesn’t mean they are lost.

So I am curious. What transition are you in right now? I mean the one sitting beneath what other people can see, the one you may not yet have words for. And what would change if, instead of trying to get through it as quickly as possible, you allowed yourself to be unfinished?

I keep returning to my daughter and her book. There she is, completely engrossed in a story she isn’t ready to leave. I understand that. I think most of us can relate. Sometimes the chapter we are in is wonderful. Sometimes we desperately want to know what happens next. Sometimes we are simply not ready to close the book.

But eventually night asks us to surrender the page. We close the cover. We turn out the light. We sleep.

And somehow, without any effort from us, morning comes. Our eyes open, and we begin again.

Somewhere in the next few weeks, a leadership team will sit down to review the fall quarter. The plan is not being written — it was written last October, in an offsite or across a handful of afternoons, and it has been sitting in a deck ever since. September is the checkpoint. Someone will say a version of ‘now that everyone’s back, let’s get ahead of this,’ and no one in the room will question it.

The premise beneath that sentence is that people are coming back restored. The summer months are considered the right season for the earned time away, and the unspoken assumption is that people have taken it — that some of them traveled to destinations believed to inspire, or to lift a weariness that has settled deep within. From the standpoint of the organization, they were given the time, and the time did what it was supposed to do.

It’s a reasonable premise. It is also, in most organizations, wrong in three distinct ways at once — and the September review, which is the one moment in the calendar structurally positioned to catch the error, is pointed at a different variable entirely.

What the evidence says about coming back

Across thirteen studies of roughly fourteen hundred employees taking vacations averaging eleven days, well-being improved measurably — and returned to statistically indistinguishable-from-baseline levels within the first week back at work. In a separate longitudinal study, the gains peaked on the eighth day away and had collapsed to pre-vacation levels within days of returning.

The eighth day. Then a week.

Which means the restorative effect of a two-week vacation has, in most cases, a shelf life shorter than the vacation itself. It behaves less like a battery being recharged and more like a room being aired out — genuinely better while the window is open, and reverting to the ambient condition of the building almost as soon as it closes. The building was the variable the whole time.

One further detail deserves attention, because it forecloses the obvious rebuttal. The vacations in the meta-analysis ranged from four days to twenty-three, averaging eleven — and the fade-out held across the range. The instinct to solve this with more days off is solving for the wrong variable.

Let me be clear that this literature is not unanimous. A more recent meta-analysis argues the effect is larger and more durable than the earlier work suggested, and that psychological detachment — the capacity to stop mentally working — is what determines whether any of it holds. That correction is worth taking seriously. But notice what even the most generous reading grants: a temporary elevation that decays on a schedule determined by the conditions people return to. The disagreement is about how many weeks. It’s not about whether the return undoes it.

The three ways summer was not restorative

Before the fade-out even begins, there is the question of whether restoration occurred.

The vacation was bracketed by two intensifications. There is a sprint before… the compression of three weeks of work into one so that leaving is permissible. And there is the backlog after… waiting with interest accrued. Many people spend more energy purchasing the absence than the absence returns. The organization allowed time for the recovery and then charged for it on both ends.

Someone was always covering. In a team of six taking rotating time off across ten weeks, the person present in the third week of July is carrying two roles, sometimes three. Coverage is a redistribution of load, not a reduction of it. Every vacation in an under-resourced team is financed by a colleague, and the ledger is rarely examined.

And for many, summer is a second job. Childcare dissolves in June and returns in late August, and the improvisation in between is far from restful. Neither is caregiving for aging parents, which does not observe a seasonal calendar. The assumption that time away from work is time spent recovering describes a narrower slice of any workforce than most planning assumes.

So the fall plan is often built on a surplus that never accumulated, that would have decayed within a week if it had, and that no one has thought to verify.

The plan is a forecast about people, made a year ago

This is the part worth sitting with, because it’s where the timing bites.

In most organizations, the work landing in September was committed to eleven months earlier. It was built in a room — an offsite, a week away, a series of afternoons — by people making a projection about capacity a full year out. That is an unremarkable way to run a fiscal year. It is also, in total transparency, a forecast about human beings whose conditions between then and now nobody could have known.

The quarterly review exists to correct for this. But watch what a review of that kind examines. Progress against targets. Variance. What slipped and what is at risk. It is an accounting of the work that, unfortunately, contains no field anywhere on it for the state of the people expected to deliver the remainder.

So the plan passes through its own checkpoint intact, because the checkpoint was never designed to ask the better question. The load is confirmed. The capacity is assumed. And the two have been drifting apart, unmeasured, for eleven months.

Vacation is a sustainability mechanism, not a regenerative one

This is the distinction I keep returning to, and it’s the whole argument compressed.

A sustainable practice delays collapse. It extends the runway. It permits the current arrangement to continue a while longer without visible failure. A regenerative practice does something categorically different — it restores capacity, and over time it produces more than it consumes.

Vacation, as most organizations deploy it, is squarely a delay to collapse. It is a pressure-release valve attached to a system whose pressure is generated continuously by design. Nothing about the design changes while the person is gone. The meeting load is the same meeting load. The decision bottleneck is the same bottleneck. The role with eleven direct reports still has eleven direct reports. The person returns to the identical set of conditions that depleted them, and the conditions resume their work immediately, which is exactly what the fade-out data is measuring.

You cannot vacation your way out of an extractive design. Although the rest is real, it is simply not addressing the cause of the problem.

What a leader has to see

Here is where this stops being an observation about organizations and becomes a question about the person doing the planning.

The capacity to catch this is not a scheduling skill. It is a perceptual one — and it is what SEED™ (Self-awareness, Emotional regulation, Ego-maturity, Developmental stage) is specifically designed to address within the Regenerative Leadership Model.

At the level of the team, it shows up as the ability to sense what is genuinely in the room rather than what the calendar dictates. A leader with that capacity walks into the first September meeting reading the actual state of the people in front of them, and adjusts. A leader without it reads the date, assumes energy, and sets a pace against a resource that does not exist.

At the level of the system, it shows up as the ability to see the annual plan as a set of assumptions rather than a set of facts. A ratified plan acquires a peculiar authority. It stops reading as a projection someone made under uncertainty and starts reading as a description of what is true, and the further it travels from the room where it was built the more solid it appears. Most of what constrains an organization is inherited rather than chosen, and inherited constraints are invisible precisely because no one remembers choosing them. Seeing an assumption as an assumption is the beginning of being able to alter it.

What to do in the next three weeks

Not gentleness. Something more precise than that.

Ask before you assume. In your first conversation with each person, ask what their summer actually held. Not as pleasantry — as data. You are gathering the input your fall plan requires and does not currently have.

Make the September review a capacity review as well as a progress review. The agenda is already set and it’s about the work. Add one question to it: is the load we committed to a year ago still matched to the people who have to carry it? If three initiatives land in the same six-week window because that is where they fell when the calendar was drawn, that sequencing was never a capacity decision. The review is your one sanctioned opening to reexamine it, and it closes fast.

Look at who covered. The person who held the team together through July is often the person the fall plan leans on hardest, and is the most depleted person in the room. This is how organizations lose their most reliable people in October and describe it afterward as a surprise.

Change one condition, not one calendar. Recovery that is not accompanied by an altered condition is a delay. Pick the single structural thing — a meeting block reclaimed, a decision right pushed down, a deliverable removed — and change it before the load arrives.

The practice we kept

There is a reason the September-reset instinct runs so deep, and it’s not organizational at all.

For most of us the reset was once structurally real. A new grade and a different teacher. A room we had not sat in before, and a genuinely blank record — last year’s difficulties did not follow us into it. September was once a true discontinuity, and we learned in our bodies to expect that it would be.

Organizations inherited the ritual and dropped the structure. Nothing resets. The backlog we left behind is the same backlog we return to. The unresolved conflict from June is waiting in the same form it was left in. The only thing that is new is the set of expectations now stacked on top of everything that was already there.

The fall does not begin anew. It resumes.

In a few weeks you will be in that room, and someone will say a version of ‘now that everyone’s back.’ It costs almost nothing to ask what they mean by back. It’s also the last point on the calendar where the question can change anything.

Subscribe now

This piece condenses findings across the studies below. Full methods and effect sizes are in the originals.

References

de Bloom, J., Geurts, S. A. E., & Kompier, M. A. J. (2013). Vacation (after-) effects on employee health and well-being, and the role of vacation activities, experiences and sleep. Journal of Happiness Studies, 14(2), 613–633. https://doi.org/10.1007/s10902-012-9345-3

de Bloom, J., Geurts, S. A. E., Taris, T. W., Sonnentag, S., de Weerth, C., & Kompier, M. A. J. (2010). Effects of vacation from work on health and well-being: Lots of fun, quickly gone. Work & Stress, 24(2), 196–216. https://doi.org/10.1080/02678373.2010.493385

de Bloom, J., Kompier, M., Geurts, S., de Weerth, C., Taris, T., & Sonnentag, S. (2009). Do we recover from vacation? Meta-analysis of vacation effects on health and well-being. Journal of Occupational Health, 51(1), 13–25. https://doi.org/10.1539/joh.K8004

Grant, R. S., Buchanan, B. E., & Shockley, K. M. (2025). I need a vacation: A meta-analysis of vacation and employee well-being. Journal of Applied Psychology, 110(7), 887–905. https://doi.org/10.1037/apl0001262

Speth, F., Wendsche, J., & Wegge, J. (2023). We continue to recover through vacation! Meta-analysis of vacation effects on well-being and its fade-out. European Psychologist, 28(4), 274–287. https://doi.org/10.1027/1016-9040/a000518

Share

I didn’t sit down to tighten a few sentences. I sat down to return to a guide I already knew needed to change — the language on these pages had been written for an earlier version of Meraki, one still speaking in the vocabulary of talent optimization rather than the regenerative leadership and systems work I do now. What I found, underneath the update I…

Read more

You woke up already behind.

Before your feet touched the floor, the list had already started running — the thing due today that you didn’t finish yesterday, the person who needs an answer you don’t have yet, the small mountain of dishes or emails or laundry that multiplied while you slept. Your body clocked in before you did. There is a tightness somewhere — the jaw, the neck, the low back — that has been there so long you have stopped registering it as pain and started experiencing it simply as your new normal. You didn’t choose this. You are not lazy, or dramatic, or failing at something everyone else has figured out. Your nervous system has been in survival mode for so long it no longer remembers there was ever another setting.

You are trying to earn enough to have some semblance of a life worth living. Quite possibly you are raising children and even a fur baby or two. Most likely, you are holding a relationship together, or holding yourself together inside of one that costs more than it gives back most days. And somewhere underneath all of it, so far beneath that you may have forgotten to look for her, there is a version of you who is still in there — subdued and waiting to be let out for longer than the length of a hot shower.

If any of this sounds like your Tuesday, I want you to know something before you read another word: you are not alone in it, and there is a way through. I’m not writing this from the other side of it, fully arrived, with my nervous system serene and my healing complete. I am writing this from inside the slow middle of it, which is the only place I have ever actually written from, and the only place I trust enough to write to you at all.

. . .

In the fall of 2023, after kicking the can down the road for far too long, I had a decision to make: undergo spinal surgery or live with relentless nerve pain and eventually the consequences of severed nerves. Two cages and four screws are now holding together what years of carrying too much, for too long, without enough support, had finally worn down. The surgery did what it was supposed to do — the nerve pain that had been radiating and burning and stealing sleep from me for longer than I care to admit is gone. I am grateful for that in a way that is hard to express with words alone.

What the surgery did not do was fix the musculoskeletal pain that still lives in my neck and shoulders most days. I have done all the things… physical therapy, strength work, supplements and anti-inflammatory protocols… the slow rebuilding of what atrophied while I was protecting an injured spine. And still, some mornings, my body simply hurts. I used to think healing was supposed to look like a line moving steadily upward. It does not. It looks like nerve pain resolving while something else lingers. It looks like two steps of real progress and then a week where you cannot lift your arm above your shoulder without wincing, for no reason you can point to. Healing, I have learned, is not a destination you reach. It’s a relationship you keep showing up to, even on the days it doesn’t seem to be reciprocal.

. . .

This is not the first time my body has kept a tally of what I was carrying. If I am fully candid with myself, and with you, the patterns of performing at a level that projects a sense of being okay while carrying too much were set long before I was old enough to recognize them. I was never given an unloaded starting point, and I am building one now, at fifty, for the first time.

I don’t think I’m alone in this, generationally speaking. Mine was a generation raised by parents who were not soft with us, who did not always have the words or the will for gentleness, who expected performance and offered little compassion in return. Many of us who survived that paradigm carry two things at once: a genuine, hard-won capacity to overcome almost anything, and a body that holds the evidence of exactly what that overcoming cost. Both are true. Neither cancels the other out.

In my twenties, I was confounded by what I was experiencing. I only knew that I was tired in a way sleep did not fix and that my skin felt too thin for the world — a shift in temperature, a certain fabric, an unexpected sound could undo me in a way that felt entirely disproportionate to the event itself. I had less and less patience for people who could not keep pace with me, and I did not yet understand that the impatience was not really about them. I was in a marriage that took far more than it gave, carrying an emotional weight that was never evenly shared, with no one around me to hand any of it off to. I didn’t have the word burnout. I only had the exhaustion, the sensitivity, and the low hum of resentment that comes from giving and giving and watching it disappear into an abyss.

That marriage ended. What came after was not immediate relief — it was two jobs, an abandoned plan to go to medical school, days spent substitute teaching and nights spent waiting tables, holding on by whatever thread was left. And even in the relationship that came after that one, the pattern I am only now learning to recognize did not disappear on its own just because the circumstances changed. Some patterns follow you until you do the work of understanding what created them in the first place — and that work does not happen on anyone else’s timeline but your own.

I say all of this not because the details matter, but because I want you to know I am not writing to you from a place that skipped the hard parts. I have been in survival mode for the better part of four decades of my life, not just the two I have described in the most detail here. I know precisely what it costs to keep performing competence while your nervous system is screaming. I know what it is to have no time to stop, breathe, or find your bearings, because stopping feels like it would cost you something you can’t afford to lose.

. . .

The surgery was, strangely, the first real stop I had been given in a very long time. Not a stop I wanted to choose. A stop my body finally forced, because it had run out of other ways to get my attention.

In the time since, I have been doing three things at once, all imperfectly and painfully slow. I have been healing physically — showing up for the exercises and the setbacks alike. I have been exploring my own spirituality in a way I had never given myself permission to before, particularly around the divine feminine — the parts of myself that are receptive rather than productive, cyclical rather than linear, worthy of rest rather than only worthy of output. And I have been rebuilding my business, deliberately, around a framework based on everything I have lived and studied regarding the many facets of leadership that contribute to making it sustainable rather than extractive.

Some days, all three at once feels like entirely too much. Some days the progress is so slow it is nearly invisible, and I have to go looking for evidence that anything is moving at all. I have made mistakes in the rebuilding — miscalculated timelines, trusted the wrong things, pushed when I should have rested. I am still learning the difference between diligence and self-abandonment, and I don’t always get it right.

But here is what I want you to hear, underneath all of it: the quiet mornings working in my home office, putting language to ideas that once lived in my body as pain and pressure — this has become one of the great, unexpected joys of my life. Alongside my children, who remain the truest joy there is, this slow work of rebuilding has given me something I didn’t know I was still capable of feeling. Not in spite of the difficulty, but rather threaded throughout it.

. . .

I don’t have a tidy ending for you, because I’m not at one yet and have come to realize a finish line may not even exist. What I have instead is a new found awareness and respect for the healing process. I have come to realize that healing is not a single doorway you walk through and arrive on the other side of it changed in a profound way. It is a thousand small doors, opened slowly, some days forgotten entirely, and found again the next morning with the option of walking through to explore what lies on the other side.

If you are in the middle of your own version of this — body aching, nervous system exhausted, carrying more than anyone around you seems to notice — I want you to know that the constant struggle is not a life sentence. It is not evidence that you are doing something wrong. It takes time. It takes patience with a body that heals on its own schedule, not yours. It takes grace for the days you cannot do the thing you did easily yesterday. It takes diligence that does not tip toward punishment. And it takes gratitude for the teeny-tiny things… the morning your shoulder does not hurt when you reach for the coffee pot, or the restful night of sleep that bestows enough energy for tomorrow’s lunch with friends.

You are not alone in this. I am not on the other side of it, waving you forward from some finished place. I am beside you in it, still learning, still recovering, still rebuilding — and I wanted you to see that clearly, because I think that is what genuinely helps. Not a picture window that shows you someone who has arrived. Rather, an open door that shows you someone still on the way, and still, somehow, going.

Subscribe now

Every framework worth the name eventually hands you a map. The Regenerative Leadership Model offers one with four territories — Self, Relationship, Team, and System — four nested scales at which leadership takes place. A leader leads inwardly, in relationship to their own interior. They lead in the one-to-one bond. They lead the collective life of a team. And they lead, whether or not they intend to, the wider system their choices ripple through. Four levels, cleanly distinct, each with its own texture and its own demands.

Then there is SEED — self-awareness, emotional regulation, ego-maturity, developmental stage — the metacognitive capacity the model places at the heart of regenerative leadership. And the moment people encounter both at once, a particular instinct fires almost without fail. They go looking for where SEED belongs on the map. Is it a fifth territory? Does it sit beside Self, or above System, or somewhere in the center of the four?

That instinct is worth pausing on — because the answer the model gives, that SEED belongs nowhere on the map because it is not a place, turns out to be the most consequential design decision in the entire architecture.

The pull toward a fifth box

There is a reason the mind reaches to make SEED another domain. Maps invite symmetry. Four clean levels arranged in a row generate a kind of visual gravity — a fifth element wants to join the row, take its place in the sequence, become one more box to understand and master alongside the others. The architecture looks as though it has an empty slot, and SEED looks like the thing that fills it.

I have written elsewhere about the larger version of this same error — the decades spent by leadership science trying to file this capacity alongside the competencies, treating it as one more skill to acquire rather than recognizing it as the capacity beneath them all. The temptation is always to categorize: to find the row a thing belongs in and slide it into place. But some things are not entries in the row. Some things are the condition under which the whole row becomes legible.

A domain is a place; SEED is not

Here is the distinction the architecture turns on.

A domain is a place where leadership happens — a level, a location, a scale of activity. Self is where the leader meets their own interior. Relationship is where two people meet. Team is where the collective forms. System is where structure, incentive, and design exert their subtle pressure. Each is a place you can point to, like a room in a house.

SEED is not a room. SEED is the light by which every room is seen.

Light occupies no particular place in a room; it fills the room, and it is the condition under which everything inside becomes visible and workable. You cannot point to where the light is — it is not a feature among the furniture. It is the medium in which the furniture appears at all. And its quality changes everything about what the room becomes. The same room, the same people, the same table, under harsh and flickering light or under warm and steady light, are not the same room at all.

This is what SEED is to the four domains. Not a fifth place where leadership happens, but the quality of awareness present wherever leadership happens — the steadiness or the reactivity, the presence or the absence, that a leader carries into every level at once.

The same capacity, refracted through every scale

Because SEED permeates rather than occupies, it appears at every level — refracted, each time, through the particular demands of that scale.

In the Self domain, SEED is the leader noticing their own depletion before it hardens into resentment, regulating the inner weather rather than being run by it. In the Relationship domain, the same capacity becomes the half-second of awareness that keeps a difficult conversation from curdling into defense. At the level of Team, it is the regulated presence that sets the emotional tone a group unconsciously borrows. And in the System domain, it is the maturity to design structures that serve the whole rather than the leader’s own appetite for control or certainty.

One capacity. Four expressions. The light is the same light; it is simply illuminating different rooms.

This is also why making SEED a domain would not merely misfile it — it would break the model. A fifth box would seal the capacity off in its own corner, a place a leader visits and then leaves, rather than the quality they carry into all the others. The whole power of SEED is that it does not stay put.

Why this is not a technicality

This may sound like a small technical choice, the sort of thing that matters to model-builders and no one else. It is not. The decision to keep SEED out of the row resolves a problem that has covertly compromised leadership thinking for a long time.

Leadership research has a persistent habit of confusing its levels of analysis — folding individual, relational, team, and organizational dynamics into a single undifferentiated account, as though what happens inside one leader and what happens across an entire system were the same order of phenomenon. The result is frameworks that feel comprehensive and explain little, because they never specify at what scale a given claim is meant to hold.

The Regenerative Leadership Model refuses that blur. It keeps the four levels genuinely distinct — Self is not Team, Relationship is not System — so that each can be understood on its own terms. And it makes SEED the one thing that legitimately crosses all four: not by collapsing the levels into one another, but by being the cross-level capacity that runs through them while leaving their distinctions intact. That is precisely how a multi-level structure is meant to hold together. The light crosses every room without dissolving the walls between them.

What the design asks of a leader

There is a practical inheritance in all of this, and it reframes what development even means.

If SEED were a fifth domain, it would be one more thing to add to the list — master your inner life, then your relationships, then your teams, then your systems, then, finally, your awareness, as though awareness were a separate undertaking with its own place in the sequence. But SEED is not the fifth item on the list. It is the quality you bring to every item on the list. You do not develop it after the four domains. You develop it through them, and it shows up in them, or it does not show up at all.

Which means the architecture is tacitly telling the truth about something most maps cannot. Leadership is not a matter of where you stand — which level you have learned to work. It is a matter of the quality of presence you carry into wherever you happen to be standing. The map shows you the rooms. SEED is whether, or not, the light is on.

There was a stretch of my life when the only place I felt safe was parked in my car in a Target parking lot.

Not my home. Not my work. Not the church I gave my Sundays to, not any room where someone knew my name. Just the car — engine off, windows up, the particular hush of a lot in the middle of a weekday. No one needed anything from me there. Nothing was being taken. I would sit for a while in that small sealed quiet, and then I would go back to the life that was slowly draining me, because that felt like the only choice available.

For a long time I could not have told you why the car felt safe. I only knew that it did, and that almost nowhere else could make the same claim.

. . .

I understand it now. The car was the one place in my life that wasn’t asking for something.

Everything else was. In those years I was teaching physics full time and pursuing a graduate degree — carrying both loads at once, sleeping in brief and broken stretches. I was volunteering at church so my children could attend faith formation at a reduced rate. Everything I earned dissolved into the life we were keeping afloat, while the roles I carried at home returned very little of what they cost. I was giving on every side, to every system I belonged to, and every system took what I gave while relentlessly asking for more.

There were mornings I cried on the way to work — not from any single catastrophe, but from the accumulated weight of being responsible for outcomes I had no power to change. I used to dream about driving past the school to the airport, boarding a plane, and never looking back. The only thing that kept me in my seat was that I could not bear to leave my children behind.

The work itself had no room in it for the parts of me that were alive. I love the classroom — the making of a lesson, the moment a difficult idea finally lands in a young face. But that particular institution did not want innovation. It wanted conformity. It wanted submission. And so the one thing that might have fed me in all of it was precisely the thing I was not permitted to do.

Here is the part I am least proud of and most need to say: I thought it was me. For years I believed I was doing something wrong. That if I were only more organized, more patient, more capable, more grateful, the exhaustion would resolve. I kept absorbing — the demands, the disappointment, the blame — certain that a stronger woman would have absorbed it without complaint. I did not yet understand that some systems are built to extract, that the draining was not a sign of my failure but of their design. So I did the only thing my understanding allowed. I tried harder. I absorbed more.

. . .

The body knows before the mind will admit it.

I was sick more years than not. And at some point the bones in my right foot developed hairline fractures that no doctor could explain — no injury, no fall, no single step that accounted for them. I was fitted for orthotics. I took supplements meant to help the bone knit itself back together. I gave away the shoes I loved and bought ugly, sensible ones, the kind built to absorb shock and distribute weight, because my own body could no longer bear the load it was being asked to carry.

I have thought about that a great deal since. A body absorbing more than it was designed to hold, fracturing quietly under a weight that no one could see. I did not need a metaphor. I was living inside of one.

. . .

I would like to say that I had never known anything different, but that would not be entirely true.

As a child, in the seventh grade, I had a science teacher named Mrs. Lensing. Her classroom was a safe haven long before I had the words to describe what made it one. She was calm, observant, and kind in a way that had depth — she was not soft, she was grounded. I remember a particularly exciting day when we were dissecting a fetal pig. She moved from table to table checking our work, and she paused at mine to watch my hands for a moment and said, “You have steady hands, the perfect touch for a surgeon.”

I have carried those words with me my whole life.

She was elegant, educated, and entirely herself. She embodied a calm confidence that inspired me — proof, to a girl who did not yet know it was possible, that a woman could be brilliant and warm at once, accomplished and safe to be near. In her room I felt seen, understood, and valued. She was the first evidence I ever had that a place could give a person more than it asked of them.

I did not know, at twelve, that I was gathering what I would need much later in life — early proof that the draining was not inevitable, that rooms could be built the other way. I only knew I felt more alive walking out of her classroom than I had walking in.

. . .

In the summer of 2018, I resigned from teaching. And not long after, a loss came into my life that I am not going to write about here — not because it has no place in this story, but because it belongs to another one, and it is not yet time.

What I will say is that it took the little I had left. For a while I was not rebuilding anything. I was mostly in bed, buried beneath the full weight of grief, and the days moved past me without my participation in them.

It was my youngest who reached me. He was seven or eight at the time, and he came into my room one afternoon and asked, plainly, the way children ask the truest things: “Momma, are you sick? Because sick people are in bed all the time, just like you are.”

I am not certain that he knew what he had handed me. But something in that question set a small, solid resolve inside of me — that he would not come home to a mother in a bed. Even if I was still in my pajamas when he walked in, I would be up. I would be moving through the house. It was meager. Though some days it was the entire achievement. And it was the first brick. That is how the rebuilding begins — with one single brick.

. . .

What followed was slow, unglamorous, and mine.

I climbed back into thinking about work, then into working, then into redesigning the whole shape of my life around a principle opposite to the one that had nearly finished me. I built a firm. I built a body of work that asked a different question. Piece by piece, day by day, I began to construct — for myself first, and then for others — the kind of space I had felt only twice: in a car that asked nothing of me, and in a classroom half a lifetime gone.

And here is the part people expect to come first, because it’s the part that sounds like the beginning of the story. It came near the end. Years into the rebuilding, a friend and colleague listened to me describe the way I had come to see leadership and life — holistic, long-horizoned, designed to nourish rather than to drain — and she asked whether I had read Kate Raworth’s Doughnut Economics. She said what I was describing rhymed with it. I bought the book that afternoon, devoured it, and felt the particular relief of being handed a word for something I had already, painstakingly, become.

Regenerative. That was the glue I had been searching for. Not the thing that saved me — I had done the saving, slowly, in pajamas, one raised morning at a time. Just the name for what I had built out of the wreckage of what had emptied me.

. . .

I am telling you all of this because I suspect some of you are sitting in your own version of that parking lot right now.

If you are, I want you to hear the thing it took me half a life to understand: you are not broken. You are very likely doing everything right inside a system that was designed to take more from you than it returns. The exhaustion is not your failure. It is information.

And I want you to know that even when you have been brought all the way down to nearly nothing, you can rebuild. Not in a single triumphant motion — it almost never happens that way — but piece by piece, day by day, one small nourishing choice at a time. Every morning offers the chance to replenish rather than deplete, to build something that gives back rather than something that only takes.

You may find that some mornings the steps of rebuilding are bold and visible. And some mornings it is only this: you wake, and you make yourself a warm drink, and you sit with your breath for a moment, and you find one thing to be grateful for. Maybe only that you are here to feel the sun through the window. Maybe only that this morning, unlike the ones you barely survived, you get to stand in your own kitchen and make a small, free, entirely yours decision…

The choice between tea or coffee.

Some days that is the whole of the work. And on those days, it is enough.

There is a pattern anyone who has spent time inside organizations has witnessed, even if they have never consciously identified it. Two leaders move through the same development pipeline. They take the same course, absorb the same feedback model, read the same canonical books, perhaps even sit through the same MBA. They emerge with what looks, on paper, like an identical inventory of capability. And then one becomes a leader people would follow anywhere, while the other depletes everyone within reach.

We tend to explain this away — a personality difference, a culture mismatch, a matter of fit. But the explanation we reach for least often is the one that should trouble us most: that the competencies themselves may not be the thing doing the work.

This is not a fringe suspicion. It sits at the center of a problem leadership science has been circling for the better part of three decades.

The assumption underneath everything

Nearly all leadership development rests on a single, rarely-examined premise — that effectiveness is a function of competencies. Give effective feedback. Delegate appropriately. Coach toward growth. Manage conflict. Communicate vision. The logic is clean and intuitive: acquire the skill, and better leadership follows. Competency in, effectiveness out.

The premise is so foundational that we have built an entire industry on top of it. Which makes the research findings genuinely uncomfortable. When scholars measure how much variance in leadership effectiveness competencies explain, the number lands far lower than the premise would predict — frequently in the range of twenty to thirty percent. Useful, certainly. Necessary, even. But nowhere near sufficient. Which leaves the larger share of the question unanswered, and the pattern I opened with unexplained.

If competencies were the engine, the two leaders would not diverge. Something else is determining the outcome.

Knowing the skill, and reaching the skill

The missing variable becomes visible the moment you watch a skilled leader under genuine pressure.

Consider the most teachable competency we have — the feedback model. Observation, impact, request. A leader can recite it flawlessly, and has perhaps even taught it to others. And then, in a meeting where the leader is the one being criticized, the model evaporates. They interrupt. They defend. They escalate, or they shut the conversation down entirely. The knowledge did not leave the room. The access to it did.

This is the distinction that traditional models obscure, and it is the crux: the skill and the capacity to deploy the skill are not the same thing. Competence is what a leader holds in calm conditions. What determines whether that competence is available in the moment it is actually needed — when the leader is triggered, threatened, or overwhelmed — is a different order of capacity altogether. And the moments that most define a leader are, almost by definition, the moments of pressure. Which means a leader is most likely to lose access to their skills at precisely the point those skills matter most.

Skill, in other words, is not the same as the capacity to use the skill. That gap is the unsolved problem. And it is the gap the Regenerative Leadership Model was built to address.

Three traditions, each holding part of the truth

Leadership research did not ignore this gap — it simply approached it from separate directions that never quite converged.

One tradition stayed with competencies and behaviors: leadership is what you do. A second, following Robert Kegan and the developmental psychologists, located the answer in meaning-making — leadership is how you make sense of complexity, and leaders operating from more developed structures of mind can hold ambiguity, paradox, and conflict that overwhelm others. A third tradition turned toward awareness itself, finding in mindfulness and attention the conditions for emotional regulation and presence.

Each tradition was correct. Each captured something real. And each, in isolation, left the others out — so the field fragmented into camps that described different faces of a single phenomenon without ever integrating them. Daniel Goleman’s emotional intelligence came closest to a unifying account, yet even emotional intelligence behaves like a cluster of competencies rather than the foundation beneath them. The integrating capacity kept being gestured toward, and kept slipping through the field’s fingers.

What SEED is

This is the work SEED does inside the Regenerative Leadership Model — and its precise nature is worth examining.

SEED is not a fifth competency added to the pile. It is the metacognitive capacity that determines whether the rest of the pile is reachable: Self-awareness, Emotional regulation, Ego-maturity, and Developmental stage. Read those four together and you can see them integrating the three traditions that leadership science kept holding apart — the awareness the mindfulness researchers studied, the regulation the emotional-intelligence work pointed toward, the maturity and meaning-making the developmentalists mapped. SEED is the synthesis the field kept reaching for and could not articulate, because it kept trying to categorize it as one more thing a leader does rather than the quality of consciousness from which all doing arises.

This is why SEED converts a leader’s competencies from inert knowledge into living capacity. A leader with developed SEED can notice the defensiveness rising before it takes the wheel — I am becoming reactive — and that noticing is the whole game. It is the half-second of metacognitive space in which a regulated response becomes possible, in which the feedback model remains available rather than vanishing. Without that capacity, no competency can be applied under pressure, because there is no observer present to apply it. With it, the competencies a leader has spent years accumulating finally become reachable when they count.

The equation we have been using is wrong

Here is where the shift becomes concrete enough to carry.

The traditional model, stated honestly, assumes that leadership effectiveness is roughly additive — skills plus experience, accumulated over time. Acquire more, perform better. But the additive model cannot explain the two leaders, and an additive model never could, because addition is forgiving. Add a low number to a high one and you still land somewhere respectable.

What the evidence actually describes is not addition but multiplication:

Leadership effectiveness = skills × awareness

Multiplication is unforgiving in exactly the way addition is not. When awareness collapses toward zero, it does not subtract from the leader’s skills — it nullifies them. The most sophisticated competency inventory in the organization, multiplied by an absent observer, produces almost nothing, which is precisely what we watch happen when a capable leader comes apart under pressure. And the inverse is just as true and far more hopeful: as awareness rises, it does not add to a leader’s skills, it multiplies them — the same competencies, suddenly compounding, available, and alive.

Which gives us the cleanest possible statement of what the model proposes. Competencies determine what a leader knows how to do. SEED determines whether the leader can actually do it.

What this asks of us

The implication reorganizes how we ought to think about growth, and it is, I think, a genuine relief once you sit with it.

For decades the competency models have only expanded — every passing year adds resilience, agility, systems thinking, and psychological-safety leadership to the list, as though the answer to leadership were simply more. More skills, more frameworks, more to acquire and perform and fall short of. But if effectiveness is multiplicative rather than additive, then the leader drowning in competency frameworks has very likely been solving the wrong variable. The constraint was never the size of the inventory. It was the capacity to reach it.

This is the subtle, more humane proposition underneath the architecture: that the work of becoming a better leader is less about accumulating what you do not yet have and more about cultivating the awareness that makes what you already hold reliably available — most of all in the moments that have always cost you. Not more to carry. More within reach.

The competencies were never the constraint. The capacity beneath them always was.

I want to tell you about something I have been working on for a while — intentionally and with a larger investment in both time and energy than I anticipated when I started.

For years, Meraki offered a GAP analysis tool rooted in talent optimization frameworks. It was useful in its time. It asked good questions about capability, bench strength, retention risk, and leadership readiness. Leaders found it valuable. I used it regularly.

Then something shifted inside of me… slowly and then all at once. I couldn’t stand it anymore.

Not because the questions were inherently wrong — some of them were genuinely good. Rather, the framework underneath them was built on assumptions I no longer hold. It measured gaps as deficiencies. It located problems in people rather than in the conditions surrounding them. It spoke the language of optimization rather than regeneration — and those are not interchangeable words. One asks how to extract more effectively. The other asks how to design systems that restore the capacity they depend upon.

So I rebuilt it. Completely.

The Regenerative Organization GAP Review is now organized across the four domains of the Regenerative Leadership Model — Self, Relationship, Team, System — and its rating scale doesn’t measure gap size at all. It reads organizational signals: the degree to which conditions within the system appear to strengthen or deplete what sustainable contribution actually requires. A rating of one indicates a Structurally Extractive system. A rating of five denotes a system in which Regenerative Capacity is Expanding. And perhaps more importantly, a score of 3 is not a passing grade — it is an honest naming of what moderate coherence with structural friction actually feels like from the inside.

Each domain closes with SEED Reflections — prompts designed to examine not just what is happening, but why it persists. SEED stands for Self-awareness, Emotional regulation, Ego-maturity, and Developmental stage. It is the meta-competency at the center of the RLM, and the reflections it animates are some of my favorite questions in any assessment I have ever designed.

I am sharing this because I think many organizations are operating somewhere between a 2 and a 3 right now — functional enough to keep moving, fragmented enough that the right people are starting to feel it — and they deserve a framework that names that honestly rather than asking them to optimize their way through it.

The review is available now. I hope it surfaces something worth sitting with.

Regenerative Organization Gap Review 2026 Final

6.87MB ∙ PDF file

Download

Download

There is a window in my office, and lately it has brought much delight while also serving as a mirror into my world.

This morning the light came in low and gold, the way it does before the day has decided what it wants from anyone, and I sat with my coffee and watched the small economy of the yard conduct itself entirely without me. A squirrel scurried and jumped along the branches of the tree and then stopped, for no reason I could discern, simply to sit. Two birds negotiated something at the feeder. A dragonfly stitched the air near the glass and moved on. Later the bees would come. None of them, as far as I could tell, were worried about a single thing.

That is the part I keep returning to… the absence of worry. I realize the squirrel has not ever needed to solve for scarcity, because it has never once believed that the morning had to be earned. It does not perform for the light. It pays no dues to some unseen authority for the right to play amongst the trees. It simply trusts — in the marrow of its body — that there will be food, that there will be space, that things will flow as they have always flowed. And so it frolics. It actually frolics, which is a word I had nearly forgotten could belong to a living creature going about its ordinary day.

I watched all of it with something I was slow to realize or define. And when I questioned it, I discovered it was not envy. It was the recognition of a debt I had spent most of my life paying.

You see, I did not always have this window or the time and space to merely sit still and revel in the world around me. Because for the better part of my adult life I bought into the lie that I could not afford to sit at it.

For decades I believed that rest was something you earned, the way you earn a wage — disbursed at the far end of sufficient effort, and never a moment sooner. Joy operated under the same accounting. It was deferred, always, until the deadline was met, until the schedule held, until the month somehow came out even. When my children were small and I was raising them alone, the days were a structure I held up with my own two arms, and I was utterly certain that if I set it down — even briefly, even only to notice the light — the whole of it would come down with me.

I called that responsibility. Some of it genuinely was. But a great deal of it was fear wearing the costume of responsibility, and I allowed that fear to cloud my judgment and let other people’s expectations stand in for my own. So I performed. I performed almost constantly, in the conviction that I had to earn a seat at a table that was never going to pull out a chair for me regardless of how well I behaved. I paid dues — to bosses, to systems, to a vague and demanding higher authority I could not see or translate if you had asked me — as though joy were a privilege to be granted eventually, on the condition that I first prove I had suffered enough to deserve it.

What it cost me was the moment. All of them. Years of ordinary moments I was physically present for and almost entirely absent from, because some part of me was always three tasks ahead, braced for the next thing.

If I could return to that younger woman — the one keeping the schedule with white knuckles, convinced the universe was indifferent and the answers were all somewhere outside of her — I would not tell her to try harder. I would tell her to rest in an inner knowing. That the universe did, in fact, have her back. That the answers she was hunting for in every book and every authority had been inside her the entire time. That the seat at the table was never the point, and the table itself was smaller than it looked.

But I could not have heard any of it then. That is the particular cruelty, and the particular mercy, of this kind of clarity — it arrives only after, never during. The squirrel never had to learn it. I had to lose decades to it.

What I understand now, at fifty, is that I had the architecture of meaning entirely inverted. I thought a life was built of milestones — the launches, the achievements, the arrivals — with the ordinary days serving as filler between them, the unremarkable stretch you simply endure on the way to the next thing worth remembering. I had it precisely backward. A life is almost entirely ordinary days, occasionally interrupted by an event. And meaning does not arrive in the interruption. It accumulates, quietly, like sediment — layer upon nearly invisible layer of small mornings — until one day you look up and realize the thing has been building itself the whole time you were waiting for permission to begin.

The little things, it turns out, were never little. They were the whole thing. The milestones merely flatter us into finally noticing what had been growing all along.

So here is what means the most to me now, and I am no longer the least bit embarrassed to say it out loud. A slow morning. Coffee I drink while it is still hot, because nothing is pulling me up out of the chair. White space on a calendar I now own outright. The sovereignty — and I feel it in my bones — to choose which appointments I take and which clients I serve. A message from a friend that arrives at precisely the right hour. The birds. The squirrels. The bees. The low gold light. The plain fact that I can sit here and watch all of it and feel, before I have accomplished a single thing, entirely enough.

For so long I felt beholden — a prisoner, frankly, of a story that insisted my worth was a balance I would spend my whole life trying to pay down. I no longer believe that story. I am unbothered now by the hustle and the grind, by the relentless gospel that measures a life by its output and a woman by her usefulness. I have stood outside that economy long enough to see it clearly for what it is — a set of lies, beautifully marketed, sold at enormous cost to the very people who buy them.

There is a place outside of all that. It is serene, and far more luxurious than anything the striving ever promised me. And the luxury was never the slow morning itself. The luxury is no longer believing I have to earn it.

The squirrel never paid a single due for the morning. It simply trusted that the morning was its own to enjoy. At fifty, I am finally learning to believe the same about mine.

There is a particular quality of discouragement reserved for this specific moment.

You have done the harder work of honest self-assessment. You have named what the system is actually producing — clearly, without the protective softening of aspirational framing. You have brought something new and true into the organization, something grounded in genuine care for the people operating within it and the conditions shaping their daily experience.

And then the system pushes back.

Not always loudly. Sometimes it is the senior leader who questions the timing. The manager who keeps finding reasons the new approach doesn’t quite apply to her team. The employee survey that surfaces cynicism so layered it suggests something far older than your current initiative. The meeting in which everyone agrees, and then nothing changes.

Most frameworks for organizational change will tell you this is resistance. They will tell you to address it through better communication, stronger sponsorship, more compelling data, or more persuasive framing. Some will suggest that the people generating the resistance simply aren’t the right fit for where the organization is trying to go.

What most frameworks will not tell you is that the resistance is probably the most important information the organization has offered you yet — and that treating it as opposition is almost certainly causing you to miss it entirely.

. . .

Behavioral science has a great deal to say about why human beings resist change, and very little of it has to do with stubbornness, fear of the future, or insufficient vision.

What drives predictable resistance is something considerably more fundamental: the disruption of conditions the human nervous system requires in order to function with stability, genuine contribution, and trust. When change initiatives arrive without attending carefully to those conditions — when they prioritize speed, efficiency, or comprehensive rollout over the slower work of establishing safety, clarity, and relational trust — the people within the system respond with precisely the protective behaviors those conditions have made necessary.

The leader whose drive toward autonomy and authority runs high will not experience uncertainty about the new direction as merely uncomfortable. She will experience it as a direct challenge to her ownership and decision-making capacity — and she will push back in ways that look like opposition but are actually a predictable behavioral response to insufficient clarity about how her role and authority fit within the new structure.

The team member whose need for consistency and certainty runs deeply — whose behavioral wiring makes genuine ambiguity destabilizing rather than merely inconvenient — will not simply need more communication about the change. He will need a fundamentally different quality of information: not the aspirational destination, but the specific, concrete, honest account of what the transition will actually require of him and when.

The manager who has built her entire professional identity around a particular approach to leadership will not experience a new framework as an opportunity for growth. She will experience it as an implicit critique of everything she has done before — and her resistance will be proportional to how directly the new approach threatens the story she has built about herself as a leader.

None of this is opposition. All of it is information — specific, behavioral, and entirely addressable once it is understood correctly.

. . .

But there is a second quality of resistance that behavioral science alone cannot fully explain, and this is the one organizational leaders most consistently misread.

Organizations that have sustained repeated cycles of change — initiatives that arrived with urgency and genuine optimism, generated significant effort and disruption, and then failed to produce the promised results before quietly disappearing — develop something that functions, at the organizational level, very much like a protective response.

Not the resistance of people who oppose change itself. The resistance of people who have learned, through direct and often painful experience, that change in this organization tends to follow a recognizable pattern: significant early investment, inadequate structural support, diminishing leadership attention, and eventual abandonment — leaving them to absorb the disruption without ever experiencing the promised benefits.

When those people encounter the next initiative — even a genuinely different one, even one grounded in something more honest and more systemic than what came before — they respond with the protection that their experience has made entirely rational. The skepticism that reads as cynicism. The guarded participation that looks like disengagement. The quiet waiting to see whether this initiative will still be a priority in six months.

This is not character pathology. It is an adaptation. It is the organizational nervous system doing precisely what it learned to do in response to conditions that repeatedly proved unsafe.

And here is the critical implication: when leaders treat this response as opposition — when they redouble communication efforts, increase pressure, or identify the resistant employees as obstacles rather than as the organization’s most honest narrators — they deepen exactly the conditions producing it. They confirm, once again, that this is not a safe place to be honest, and that change here follows the same pattern it always has: urgency first, followed eventually by abandonment, with the people who expressed doubt blamed for insufficient commitment.

The protective response strengthens. The honesty gap widens. And the next initiative will meet more resistance than this one did.

. . .

What systems thinking offers — and what makes this reframe so practically essential — is this: resistance is not a malfunction within the organizational system. It is a signal produced by the system. And signals, read carefully, tell you something specific about the conditions the system is actually operating within.

When change meets resistance, the organization is revealing something true. The places where implementation demands are genuinely exceeding current capacity. The places where leadership alignment is more fragile than it appeared in the planning conversations. The places where relational trust has not yet been established at the depth the change actually requires. The places where communication has been aspirational rather than honest — and where the people closest to daily operations know the distance between the two with extraordinary accuracy.

Resistance, understood systemically, is diagnostic information about the actual conditions of the organization — offered freely, and usually with considerable precision.

The question is never: How do we overcome this resistance?

The question is: What is this resistance revealing about what the system actually needs in order to move differently?

That reframe changes everything — not because it is philosophically gentler, but because it is considerably more precise. Organizational change efforts built on accurate diagnostic information succeed at meaningfully higher rates than those built on aspirational narratives that treat pushback as a problem of insufficient buy-in. The accumulated evidence across decades of organizational research is absolutely unambiguous on this point.

. . .

None of this is an argument for treating every expression of resistance as equally valid or equally urgent. Some resistance does reflect genuine misalignment with the direction the organization needs to move. Some is rooted in narrow self-interest rather than systemic awareness. Discernment matters enormously — and the capacity to distinguish between resistance-as-information and resistance-as-obstruction is itself a form of leadership sophistication worth developing with care and depth.

But that discernment begins with curiosity rather than judgment. With the willingness to approach pushback as potentially the most honest communication the organization is offering, rather than as an obstacle between you and implementation.

The leader who can sit with resistance long enough to actually read it — who can ask what the system is revealing rather than how to overcome what the system is producing — is doing something far more difficult and far more valuable than most organizational development frameworks prepare them for.

They are treating the organization as the living system it actually is.

Living systems offer information constantly. The question is whether we have developed the capacity to receive it — and the willingness to let what we receive change what we do next.

The Organizational Integration Architecture within the Regenerative Talent Architecture Guide addresses resistance and organizational friction directly — including specific recalibration pathways for the most common friction points. Available below.

Regenerative Talent Architecture 2026 Guide

18.8MB ∙ PDF file

Download

Download

Meraki, from the Greek perspective, is a word that resists clean translation. Which is perhaps the first noteworthy quality of it. The nearest the English language comes to describing its essence is something like this: to do a thing with such devotion, such presence, that you leave a piece of your soul inside it. Imagine pouring yourself into the work — the meal, the garden, the letter, the room you are arranging — so completely that what you make carries something of who you are. The word descends from the Turkish merak, a labor undertaken for love rather than for return, and the Greeks made it their own to describe the particular grace of giving oneself fully to the act of creation.

I chose it deliberately. The word and its etymology is not decorative or aspirational. It is the entire foundation of the vision and the work to bring it forth.

Consider what the word presumes. Meraki assumes that the self left behind in the work is not diminished by the leaving — that to give of oneself, rightly, is generative rather than depleting. And then consider how rarely our organizations are built on that assumption. We have inherited, nearly all of us, an operating logic that runs in precisely the opposite direction: a logic of extraction. We take from people until there is little left to take. We measure their output and call it their worth. We design roles, teams, and entire systems to draw down the resource that human beings represent, and we express genuine surprise when the well runs dry — when the talented leader burns out, when the high performer disengages, when the culture we so carefully optimized begins, almost imperceptibly, to rot from within.

This is not a failure of individual will; it is a failure of design.

The research bears this out with uncomfortable clarity. Stevan Hobfoll’s Conservation of Resources theory describes how loss spirals — how the depletion of one resource accelerates the loss of the next, how systems under chronic strain do not stabilize so much as unravel. Mary Uhl-Bien’s work on complexity leadership names the deeper error: we persist in treating living, adaptive systems as though they were machines — predictable, controllable, reducible to their parts — when the organizations we actually inhabit behave like ecologies, responsive and emergent and alive.

What I have spent years building, and what this publication exists to examine, is the alternative. Nature offers it freely, if we are willing to look: no living system survives extraction. The forest does not strip its own soil. The body does not spend itself endlessly without restoration. Regeneration — the capacity of a system to renew the very conditions of its own thriving — is not a sentimental idea borrowed from ecology. It is a design principle, and it is exacting in the only sense that matters: it works.

Kate Raworth’s doughnut — an economic theory bound by a social floor beneath which no one should fall and an ecological ceiling beyond which we cannot sustainably reach — gave me language for something I had felt long before I could name it. That thriving has an organic shape. That the goal should never be endless extraction in the service of endless growth. It should aspire to a way of living, leading, and organizing that holds people and systems within the conditions where life remains possible.

Meraki Musings is where I think this through in the open. It is the systems-facing room of my work — the place where I develop the Regenerative Leadership Model, where I trace the architecture of extraction and the design of its alternative, where the ideas that inform my consulting are examined with the depth they deserve long before they ever reach a client. At the center of that model sits SEED — Self-awareness, Emotional regulation, Ego-maturity, and Developmental stage — though not as a checklist, and not as a fifth domain to manage. It is the meta-cognitive core of the four domains, the interior capacity that makes regenerative leadership of self, of relationship, of team, and of system possible at all.

You will not find productivity hacks here, nor will you see leadership platitudes dressed up as insight. What you will discover is a sustained argument that delineates the extractive nature in which we were taught to lead and how it depletes us — and that a researched, coherent, living alternative exists.

A living argument asks to be rendered in living language. I refuse to let what is vital stiffen in the telling, which is why I write from vigor rather than rigor — a distinction I hold as foundational. Rigor connotes rigidity, the stiffness of a thing that has stopped growing; vigor is the vitality of what has not. The work I bring to the world is alive, and I intend to keep it that way.

If you lead anything — a team, an organization, a life — and you have felt the quiet exhaustion of giving and giving into a system that only takes, you are who I am writing for. If you suspect there is a more generative way to build, and you want the model and the language to build it, you have found the right room.

To leave a piece of yourself in the work, and to design the work so that the leaving renews you rather than depletes you — this is what meraki has meant all along. Some part of you has likely always known it. Everything I write here is in service of giving that knowledge a place to take root.

The work is waiting. Begin where it calls.

There is a single instruction embedded in the Organizational Talent Architecture Assessment — one line, easy to read past — that I have watched stop leaders completely.

Not the questions themselves. Not the scoring scale. Not the implications of where an organization lands.

This: Choose the response that most accurately reflects your organization’s present reality — not its aspirations, intentions, or isolated moments of success.

Eight words doing an enormous amount of work: not its aspirations, intentions, or isolated moments of success.

Because most leaders, when asked to evaluate their organizations, genuinely believe they are assessing present reality. The aspirational narrative and the accurate one have become, over time, largely indistinguishable from one another. And that convergence — that closing of the distance between what we intend and what we believe is true — is not a character flaw. It is a structural condition, one produced by the very systems leaders are trying to evaluate.

Understanding why it happens is the first step toward doing something more honest.

. . .

Begin with what behavioral science has consistently demonstrated about how human beings assess complex systems — including the organizations they lead.

Confirmation bias does not operate as a conscious filter. It operates as an unconscious one, shaping which information we seek, which we attend to, which we remember, and which we quietly set aside. Leaders who have spent years working toward a particular organizational vision — who have invested substantially in building certain systems, developing certain people, communicating certain cultural values — are not surveying neutral terrain when they evaluate their organizations. They are looking at something they have built, something they believe in, something whose success is inseparable from their own sense of competence and purpose.

The information that confirms the vision is not difficult to find. Isolated moments of success are real moments. Pockets of genuine alignment exist in almost every organization. The danger is not that these things are fabricated — it is that they become, in the absence of more systemic observation, representative. One high-functioning team stands in for the whole. One genuinely excellent hire becomes evidence of a hiring system. One transparent conversation between a leader and a direct report becomes proof of a communication culture.

This is not self-deception in the conventional sense. It is the predictable output of a cognitive architecture that was never designed for accurate self-assessment at organizational scale.

. . .

There is a second dynamic operating alongside the cognitive one — and this is the one that organizational psychologists too often fail to name with sufficient precision.

Organizations that have sustained chronic strain — prolonged periods of operational pressure, leadership inconsistency, inadequate resources, unrealistic expectations, or repeated cycles of change that failed to produce the promised results — develop protective narratives. Not because the people within them are dishonest, but because protective narratives serve a genuine adaptive function.

When an organization has experienced repeated disappointment, the psychological cost of fully accurate self-assessment becomes extraordinarily high. To look clearly at what is actually being produced — the patterns of burnout, the persistent misalignment, the feedback that surfaces only after someone has already left, the distance between stated values and daily operational experience — is to risk something that feels profoundly destabilizing: the acknowledgement that the gap between intention and reality is wider, and has existed longer, than anyone wants to confront.

Protective narratives close that gap — not by addressing it, but by making it temporarily uninhabitable. We are getting better. This is a difficult season. Our challenges are external, not systemic. The people who struggled here simply weren’t the right fit.

These narratives are not lies, exactly. They contain genuine pieces of truth. They simply cannot be the whole story — and organizations that rely on them as though they were eventually find themselves solving for problems they have not accurately described, with interventions built for an organizational reality that does not quite exist.

. . .

And here is where the systems lens becomes essential — because the honesty gap is not simply a product of cognitive bias or organizational self-protection. It is, in many cases, a condition that leaders have been actively and consistently rewarded for maintaining.

Leadership, in most organizational contexts, is still largely selected for and rewarded through narratives of confidence, forward momentum, and optimism. The leader who accurately describes the fragmentation within their organization — who names the communication breakdowns, the pockets of chronic depletion, the structural misalignments that have persisted for years — is often experienced, by boards, by stakeholders, by their own leadership teams, as someone who is struggling. As someone who lacks vision, or capacity, or the particular composure that organizational leadership is assumed to require.

The leader who presents a compelling aspirational narrative, who communicates confidence in the trajectory, who frames persistent organizational challenges as temporary and manageable — is often experienced as steady. As trustworthy. As leadership material.

We have, in other words, designed systems that select for the honesty gap. Then we are surprised when organizations cannot accurately assess themselves.

. . .

None of this is offered as exoneration. The gap is costly, and the cost is real.

When organizations assess themselves against aspirational rather than actual reality, the interventions they design are built for an organization that does not quite exist. Training is introduced for a culture problem that was actually a structural one. Coaching is applied to a leadership issue that was actually a systemic one. New tools and frameworks are layered onto organizations whose existing systems are quietly undermining everything built on top of them.

The improvement efforts that never quite produce what they promised. The initiatives that generate energy in the early months and then dissipate. The assessments that surface important data and are then quietly set aside. The external consultants — and I include myself in this accounting — whose recommendations were sound but whose implementation was built on a foundation that had not been honestly examined first.

This is what the honesty gap actually costs. Not the discomfort of accurate self-assessment, but years of well-intentioned work solving for the wrong problem.

. . .

The instruction I placed at the opening of the assessment — present reality, not aspirations, intentions, or isolated moments of success — is not a small ask.

It requires setting aside cognitive filters that have been operating, and being rewarded, for years. It requires tolerating the discomfort of looking at what the system is actually producing, which is sometimes considerably more painful than what we have told ourselves it is producing. It requires a willingness to be honest in an organizational context that has very often, and very consistently, rewarded the opposite.

And it requires understanding that the gap itself is not a moral failure. It is a structural condition — one that can be examined, named, and addressed with the same care and systemic precision that any other organizational challenge deserves.

What becomes available on the other side of that honesty is not humiliation. It is clarity — the specific, grounded kind that allows organizations to design interventions for the reality they actually inhabit rather than the one they intended to create.

That clarity is where meaningful change becomes possible.

Not before.

The Organizational Talent Architecture Assessment is embedded within the Regenerative Talent Architecture Guide — available below. Approach it with the most honest version of your present reality you can access. That is where the work begins.

Regenerative Talent Architecture 2026 Guide

18.8MB ∙ PDF file

Download

Download

I found the stall at the far end of the airport restroom, and I let the tears come there — quietly, where no one could see. A few gates away, my daughter sat with her best friend, the two of them bent toward one another, laughing, mapping out the shape of a life I was only beginning to understand. A life I had been quietly funding and accommodating and carrying my way alongside for far longer than I cared to admit.

I told myself I was grieving.

And perhaps I was — though not in the traditional sense of the word.

For several days after we returned, I sat with a heaviness I could not quite name. At first it felt like sadness. Beneath the sadness, I found a layer of disappointment. And beneath that, finally, a deep and particular exhaustion — the kind that does not come from a single hard week. It comes from years of a posture held too long.

I turned it over from every angle, looking for the explanation. What story am I telling myself? What expectations am I silently holding? What role do I play in all of this, consciously or not?

Eventually, a quieter truth surfaced.

I was not grieving what had happened. I was grieving what no longer needed to happen.

There is a difference — and the difference is everything.

. . .

There was an hour I spent in a parked car in the heat, the engine running so the air would stay cool for people who had not told me when they would return. I read a little. I checked things that did not need checking. And somewhere in that hour, with the vents humming and the windows going pale with sun, I understood that I had been waiting like this — in one posture or another — for the better part of three decades.

The waiting had a quieter cousin — the watching. One night I sat at the edge of a room while the music played and the people I adore moved through it without me. I had dressed for the occasion. I had even worn the right shoes. And yet when the moment came, it was made unmistakably clear that the dancing was theirs and the watching was mine. So I found a chair. I have become, I am realizing, very practiced at finding the chair.

And when I was not waiting or watching, I was tending. On the last morning, while they walked, I cleaned a kitchen that was not mine, gathered the linens, and finished packing. It did not occur to me to do otherwise. It rarely had. This, I am learning, is the quiet shape self-abandonment takes: rarely a grand sacrifice; far more often a thousand small acts of tending that no one asks for and no one sees.

. . .

Underneath the waiting and the watching and the tending, one question had been running the whole time. That week, I finally heard it — what had I done to deserve the distance? It was never the right question. The truer one came more softly — when had all this carrying begun to feel like love?

Somewhere along the way, I began confusing love with carrying the weight of others. Not intentionally, and certainly not consciously. It happened slowly — one responsibility, one accommodation, one quiet act of service at a time — until I could no longer tell the difference between caring for the people I love and carrying them.

The distinction matters more than I understood. One creates connection. The other only ever creates weight.

A homecoming, I have learned, is not a specific place or time. It arrives instead in a series of small moments. It is the moment you stop organizing your life around responsibilities that were never yours to hold. It is the moment you stop mistaking self-abandonment for love. It is the moment — somewhere at the edge of a crowded room, or in a parking lot in the heat, or in an airport stall with the door latched — when you remember that your own needs and dreams and energy were never meant to be an endless resource for others to draw from. They, too, are worthy of stewardship.

At fifty, I am not becoming someone new. I am returning to the woman who waited, patiently and quietly, beneath all the carrying.

And for the first time in a very long while, I believe she is ready to take her seat at the table.

There is a particular kind of discomfort that arrives not as a sudden rupture but as a slow, accumulating friction — the kind you barely notice until you can’t ignore it anymore.

For me, it arrived while writing.

Not in any single moment of crisis, but across many quiet hours at a desk, when certain words began catching in my throat — words I had used fluently for years, words that had once felt entirely aligned with the work I was doing and the values I was trying to serve.

Optimization.

Performance.

KPIs.

Efficiency.

Scalability.

Each one snagged on something I couldn’t immediately name. And beneath that physical discomfort — the genuine resistance I felt reaching for language that no longer fit — was something equally clarifying and equally unsettling: I was losing interest in the question most of this language was designed to answer.

How do we get more from people?

More output. More performance. More productivity. More resilience. More engagement. More adaptability.

I had spent years helping organizations move beyond management models that treated people as interchangeable and endlessly adjustable — systems designed for industrial-era productivity rather than human sustainability — and I genuinely believed I was doing meaningful work. I still believe that work mattered. But I was beginning to notice that even within frameworks I had helped design, even within language I had personally chosen, the underlying question had remained the same.

And I no longer wanted to answer it.

What I found myself drawn toward instead were questions of an entirely different character.

What conditions are organizations creating?

What kinds of leadership behaviors are being reinforced — and what do they cost the people absorbing them over time?

What happens to human beings operating inside systems of chronic depletion — not across weeks, but across years?

Why do so many organizations attempt to solve relational and systemic problems through individual optimization alone?

What would happen if organizations were designed not simply for performance, but for sustainability, coherence, adaptability, and human thriving over time?

These questions changed the frame entirely.

Because once I began asking them, I could see — with a precision I hadn’t had before — that many of the organizational challenges I was being brought in to address were not people problems waiting for better optimization. They were systems problems. Leadership problems. Relational problems. Communication problems. Structural problems rooted in the design of organizational life itself.

People were not underperforming because they lacked motivation or capability. They were exhausted. Fragmented. Misaligned. Operating inside systems that rewarded urgency over reflection, reactivity over coherence, and short-term output over the kind of long-term organizational health that actually sustains performance.

The problem was never the people. The problem was the architecture.

. . .

And then I had to look closely at something considerably more uncomfortable: the guide I had released the year before.

I want to be precise here, because precision matters more than self-protection.

The guide was not wrong. It reflected a genuine stage of my thinking — an important bridge between traditional organizational psychology and something broader, more relational, more systems-aware. There were sections I was proud of then and remain proud of now: the emphasis on leadership awareness, communication, alignment, and intentional organizational design still holds. That work genuinely helped leaders see their organizations more clearly.

But there were also sections I could no longer stand behind with full conviction. The KPI dashboards. The optimization language. The subtle but persistent framing of people as variables to be managed more efficiently. A certain orientation toward measurement that prioritized outputs while leaving the conditions producing those outputs almost entirely unexamined.

The guide had been built, in part, from the same assumptions it was ostensibly challenging.

I had done what so many of us do in the middle of our own evolution: moved the work further than inherited frameworks would take it, without yet shedding those frameworks entirely. The discomfort I felt while writing — all those words catching — was the evidence of that incomplete shedding. My thinking had been pulling in one direction while some of my language remained anchored in another.

Rather than quietly revising the original and proceeding as though the evolution had never happened, I chose to rebuild it authentically. Not as a version 2.0. Not as a rebrand. But as a reflection of what had actually changed — in the work, and in me.

What emerged is the Regenerative Talent Architecture Guide.

A framework rooted less in optimization and more in organizational coherence. Less in extraction and more in sustainability. Less in performance theater and more in the kind of systemic awareness that asks not only what an organization is producing — but what conditions are producing it, and at what cost to the people sustaining it.

If you are navigating that question — if you are beginning to sense that the tools you have been given were designed for a different set of priorities than the ones you are actually trying to serve — this guide was built for that moment.

. . .

In full transparency, more than the guide changed.

I changed.

And I suspect I am not alone in this. Many of us were trained inside frameworks built for efficiency, acceleration, and control. Many of us inherited organizational models optimized for industrial-era productivity rather than human sustainability. Many of us are now questioning assumptions we once accepted without hesitation — not because we have abandoned accountability, performance, or measurement, but because we have begun to understand that none of those things can be separated from the conditions producing them.

That questioning does not signal instability or drift. It is, I think, what meaningful organizational work ultimately requires of us.

Not certainty.

Not rigid allegiance to old frameworks.

But the willingness to stay honest when deeper truths begin emerging underneath the ones we thought we knew — and to let that honesty reshape the work itself.

The Regenerative Talent Architecture Guide is available below. Begin where it calls you.

Regenerative Talent Architecture 2026 Guide

18.8MB ∙ PDF file

Download

Download

The dashboard was green.

Every metric trending favorably. Productivity up. Revenue targets met. Turnover within acceptable range — which in this industry, at this moment, meant below thirty percent, a number the leadership team had decided to treat as a success rather than examine as a symptom. The quarterly report told a story of an organization performing well, and the people responsible for the quarterly report believed it.

What the dashboard could not show — what no dashboard I have ever seen has been designed to show — was what was happening in the hour before every all-hands meeting, when a specific subset of people gathered in a specific conference room to align on what was and was not safe to say in front of leadership. What it could not show was the high performer in the third row who had stopped asking questions eight months ago, not because her curiosity had diminished but because she had learned, through a series of interactions too subtle to document and too consequential to ignore, that questions were received as challenges and challenges were translated as disloyalty. What it could not show was the team that was hitting its numbers by systematically consuming the goodwill, the trust, and the creative capacity that would have made hitting those numbers sustainable.

The dashboard was green. The people it represented were being consumed.

This is the central paradox of organizational measurement as most institutions practice it: the most dangerous moment is not when the metrics are bad. It is when the metrics are good and the reality they cannot capture is quietly catastrophic. Because bad metrics produce urgency. Good metrics produce complacency. And complacency, in an extractive system, is how the depletion becomes so advanced before anyone names it that the recovery cost is almost always larger than anyone anticipated.

Part 4 is about building the measurement capacity to see what the dashboard misses. Not as a replacement for traditional metrics — those matter, and we will not pretend otherwise — but as the layer beneath them that tells you whether the numbers are being generated by a system that is building capacity or consuming it. Whether the green on your dashboard represents genuine organizational health or an extremely expensive illusion of it.

What Traditional Metrics Are Actually Measuring — And What They Are Not

Let me take a specific example — one I encounter regularly enough that it has become almost a diagnostic shorthand.

A leadership team shows me a productivity metric that has been trending upward for three consecutive quarters. They are proud of it, and they should be — it represents real work, real effort, real organizational output. And then I ask a question that the metric itself cannot answer…

What was depleted to produce that number?

Not rhetorically. Specifically. When productivity increases in a system that has not added resources, something absorbed the additional demand. The question is what. Was it efficiency — genuine process improvement, better tooling, smarter sequencing of work? Or was it capacity — the discretionary energy, the creative bandwidth, the recovery time that people were previously using to stay sustainable and have now redirected into output because the system signaled, explicitly or implicitly, that output was what was valued?

The metric cannot tell you which one it is. And the difference between those two answers determines whether the productivity trend represents organizational strength or organizational depletion borrowing against a future it will eventually have to repay.

This is what I mean when I say that traditional metrics measure what can be extracted, not what is being depleted to extract it. They are extraordinarily good at capturing outcomes and almost entirely blind to the conditions that produce them — and more critically, to whether those conditions are sustainable or whether they are quietly consuming the organizational capacity that future outcomes will require.

The distinction I return to here is the one threaded throughout this series: we have been measuring with the tools of rigor — counting what is countable, tracking what is trackable, reporting what looks clean in a quarterly presentation — when what living systems require is measurement with vigor. Measurement that tracks vitality, not just output. Measurement that asks not only whether the number was achieved but whether the system that achieved it is more capable afterward or more depleted.

The metrics we choose reveal which kind of organization we believe we are building. And most organizations, measured honestly against that standard, are revealing something they have not consciously decided.

The Leading Indicators I Overtly Track

In an active engagement, I am always watching three things that most organizational measurement frameworks either ignore entirely or treat as too subjective to be useful. They are not subjective. They are leading — which means they tell you where the system is heading before it arrives there, while there is still time to change the trajectory.

Energy trajectory

The first is energy — not as a wellness concept but as a systems variable. Is the collective energy of this team building week over week, or is it declining? Are people arriving to the work with something generative to bring, or are they arriving already in deficit, managing their capacity rather than deploying it?

I track this through a combination of direct observation and the simplest possible self-report: a weekly or biweekly check-in that asks people to locate themselves on a spectrum from depleted to energized. Not a survey — a conversation, or at most a single-question pulse that takes thirty seconds to complete and, tracked over time, produces a trend line that tells you more about the actual state of the organization than most annual engagement surveys.

What leaders almost always discover when they start tracking energy trajectory honestly is that the trend has been visible for longer than they knew — that the signals were there, in the quality of the meetings and the texture of the interactions and the subtle withdrawal of discretionary effort, and the measurement practice simply did not exist to make those signals legible.

Capability development

The second indicator I track is whether the people in the system are genuinely more capable now than they were three months ago. Not whether they have attended training — training attendance is an input metric dressed as an outcome metric, and it tells you almost nothing about whether learning has actually occurred. Whether they can do things now they could not do before. Whether their judgment has deepened. Whether the institutional knowledge of the organization is growing and being distributed, or whether it is concentrating in fewer and fewer people and walking out the door at an accelerating rate.

This indicator matters because capability development is the compounding return of regenerative systems — the thing that makes year two stronger than year one and year three stronger than year two. And its absence is one of the earliest signals of extractive drift: when people stop developing, they have almost always stopped having the capacity to develop. The work has consumed the bandwidth that growth requires. The system is extracting present performance at the cost of future capability.

Trust — and the gap most leaders do not know exists

The third leading indicator is the one that most consistently surprises the leaders I work with. Not because they do not believe trust matters — most leaders will tell you, with complete sincerity, that trust is foundational to their culture. But because the gap between what a leader believes about the trust in their organization and what is actually true is, in my experience, one of the most consequential and most consistently unmeasured distances in organizational life.

Most leaders think they are trusted. Most leaders believe they have built a culture of trust. And for most leaders, this belief is the farthest thing from the operational reality of the people around them.

I am not saying this to indict leaders — the gap is not usually the product of bad intentions or dishonest self-assessment. It is the product of a system that filters information as it travels upward, in which the people most affected by a leader’s behavior are also the people with the least structural safety to report on it honestly. A leader can genuinely experience their organization as high-trust while the people around them are operating in a carefully maintained performance of trust that protects them from the consequences of the real thing.

Trust, measured regeneratively, is not a feeling or a cultural value. It is a set of observable behaviors: whether commitments are kept, whether information flows proactively rather than being discovered accidentally, whether people raise concerns or manage them out of sight, whether feedback travels in multiple directions or only downward. These behaviors can be tracked. They can be trended. And they will tell you, with remarkable reliability, whether the trust a leader believes they have is the trust their organization is actually experiencing.

Inseparable from trust — and equally unmeasured in most organizational contexts — is psychological safety. The two travel together and deplete together, and the absence of one makes the other impossible. An organization can have formal structures for voice and feedback and still have essentially no psychological safety if the lived experience of speaking truthfully is that truth is unwelcome. Amy Edmondson’s research on this is definitive and has been available for decades. And yet I have sat across from leadership teams in sophisticated, well-resourced organizations who have never formally measured psychological safety, never asked their people whether they feel safe to raise concerns, never examined the gap between their stated commitment to candor and the actual conditions that either enable or prevent it.

The reason psychological safety is rarely measured is the same reason trust is rarely measured honestly: because the measurement might tell you something you are not prepared to change. And that discomfort — the discomfort of knowing — is precisely what regenerative measurement requires a leader to sit with rather than avoid.

Subscribe now

Behavioral Assessment as a Regenerative Tool

As an organizational psychologist I have seen behavioral assessments used in two fundamentally different ways, and the difference between them is not in the tool — it is entirely in the intention and the sophistication of the person using it.

Used extractively, behavioral assessment is a sorting mechanism. It produces profiles that get used to predict behavior, manage risk, and optimize the fit between a person and a role as the organization has defined it. The data flows to leadership. The person being assessed receives, at most, a summary. The primary beneficiary of the measurement is the organization’s efficiency. The person is the object of the assessment, not its subject.

Used regeneratively, behavioral assessment is something categorically different. It is a tool for self-illumination — a way of giving people data about their own behavioral wiring that helps them understand why certain kinds of work energize them and others deplete them, why they lead the way they lead and what that costs the people around them, and where the design of their current role is working with their natural drives and where it is working against them. The primary beneficiary of the measurement is the person being measured. The organization benefits because people who understand themselves design better — better roles, better relationships, better teams.

Here is what that looks like in practice.

What I see in a profile that most practitioners miss

When I sit with a behavioral assessment, the first thing I am looking at is not the categorical label that places someone in a behavioral archetype. I am looking at the specific configuration of drives and the distance between them, because it is in those distances that the most important information lives.

A leader who is deeply driven to produce results and influence outcomes — and who does their most powerful thinking internally, in depth, without the external processing that more socially-oriented leaders naturally engage in — can appear counterintuitive to the people around them, because we have been conditioned to associate leadership with visible, vocal, outward-facing presence.

In an extractive system, this configuration gets misread consistently: the quietness is interpreted as disengagement, the internal processing as absence of conviction, the preference for depth over breadth as a limitation rather than a strength. The leader gets feedback that tells them to be more visible, more vocal, more present in the ways that high-energy extroverted leaders are naturally present — and the feedback, however well-intentioned, is asking them to perform a behavioral style that is not theirs and that will cost them energy every time they do it.

In a regenerative conversation, that same behavioral data becomes entirely different: here is how you are wired, here is why the misread happens, here is how you design your leadership presence to leverage what you actually have rather than performing what you do not. Here is why the depth of your thinking is an organizational asset and how to make it visible in ways that do not require you to be someone else.

What I say to a client about their own data

The conversation I have with a leader about their own behavioral data consistently includes a moment that I have come to think of as the recognition moment — when the data describes something they have known about themselves for years and have never had language for, or something they have been told is a weakness and now understand, perhaps for the first time, as a drive that has simply been operating without a design that supports it.

I had this conversation recently with a leader whose assessment revealed a strong drive for precision, process, and getting things exactly right — combined with an equally strong drive to produce results and move things forward. In every organization she had worked in, this combination had been received as rigidity. She was meticulous and demanding and unwilling to cut corners, and the feedback she had received, across multiple roles and multiple organizations, was that she needed to be more flexible, more willing to move fast and iterate, more comfortable with ambiguity.

What I said to her was this: you are not inflexible. You are precise in a system that has been telling you that precision is a liability because the system itself is not designed to support it. Your drive for quality is not the problem. The question is whether we can design a role and a set of conditions in which that drive produces excellence rather than friction — and what you need from the people around you to make that possible.

She was quiet for a long time after that. And then she said: “No one has ever said it that way before.”

That is what regenerative assessment sounds like. Not a label or a limitation. An illumination — of the wiring, the context, and the design work that would allow the wiring to contribute what it is naturally capable of.

What I do with team-level data

When I work with team-level behavioral data, I am not looking for the optimal configuration — the mythical combination of drives that produces high performance in the abstract. I am looking at what this specific team, with these specific people and these specific behavioral dynamics, needs to design deliberately in order to work with its actual composition rather than against it.

A team with a high collective drive for results and urgency will move fast, generate ideas prolifically, and struggle with follow-through. An extractive response to that pattern is to label it a weakness and hire for steadiness. A regenerative response is to design the team’s workflow around its actual drives — creating deliberate capture and execution structures, building in the checkpoints that the team will not naturally create for itself, and being transparent about where complementary behavioral strength needs to come in rather than expecting people to consistently operate against their wiring.

The team’s behavioral composition is not a problem to be solved. It is the reality to be designed with. And the design conversation that follows from that reframe almost always produces something more honest, more sustainable, and more genuinely effective than any team development initiative built on the premise that people should be different from how they actually are.

When Measurement Restores Dignity — And When It Strips It Away

Before I implement any measurement practice in an engagement — whether it is a behavioral assessment, an energy tracking protocol, a trust survey, or a performance framework — I run it through a set of questions that I have developed over years of watching measurement used both ways.

The first question is the most important: Who is the primary beneficiary of this measurement?

If the honest answer is the organization — if the data flows upward and the person being measured receives nothing from it, or receives only a summary designed to serve the organization’s purposes — then what is being conducted is not assessment. It is surveillance with better branding. And surveillance, regardless of how it is packaged, strips rather than restores dignity.

Regenerative measurement insists that the person being measured is always among the primary beneficiaries. Always. This does not mean the organization does not benefit — it does, significantly, when people have genuine self-knowledge and use it to design better. Rather, it means that the data belongs, first, to the person it describes. That they have access to it, that they understand it, that they have agency over what they do with it, and that the conversation about what it means is one they are part of rather than one that happens about them in rooms they are not invited into.

The second question is: Does this measurement expand what is possible for the person, or does it constrain it?

Assessments that produce categories tend to produce ceilings. When a behavioral profile becomes a box — when a categorical label becomes the primary lens through which a person is understood by their organization — it has stopped being a tool for illumination and started being a tool for limitation. The profile captures a behavioral pattern. It does not capture the full complexity of a human being, the ways in which context shapes behavior, the degree to which people grow and develop and expand beyond what any single assessment instrument can see.

Regenerative assessment holds the data lightly — as one source of information among many, useful for designing better and understanding more deeply, not sufficient for defining who someone is or what they are capable of becoming.

The third question is the one I leave leaders with, because it applies not just to formal assessment practices but to every measurement decision they make: Would you want to be measured this way?

If the answer is no — if the surveillance would feel violating, if the data collection would feel extractive, if the assessment would feel reductive — then the measurement practice needs to be redesigned before it is implemented. The standard for measurement in a regenerative organization is not whether the data is useful. It is whether the process of gathering it treats people with the dignity they deserve.

What You Now Have — And Where It Goes From Here

Four parts. Four rooms. Four levels of a practice that began with seeing and ends with measuring — which is, in its own way, another form of seeing. The discipline of tracking what matters, of making visible what has been invisible, of refusing to let the dashboard tell the whole story when the whole story is considerably more complicated and more important.

Here is what this series has given you, assembled and held together as a complete framework:

In Part 1, you developed the perceptual frame — the ability to see organizational extraction before anyone has named it, to read what a room is saying without words, to ask the question that creates the conditions for honesty.

In Part 2, you sat with the decision — what it actually costs to lead regeneratively, what the four-level framework reveals when applied honestly to your own practice, and what it looks like when a leader crosses from understanding regeneration intellectually to being willing to practice it.

In Part 3, you entered the design work — the specific, situated, resistance-aware practice of building roles that sustain rather than consume, teams that build collective capacity, and systems whose infrastructure can actually support what you are trying to create.

And in Part 4, you built the measurement capacity to know whether it is working — not just whether the numbers are good, but whether the conditions generating them are healthy, whether the trust is real, whether the energy is building or depleting, and whether the behavioral data you are collecting is serving the people it describes or simply extracting from them in a different register.

This is not a complete map of regenerative organizational design. No series of four essays could be. It is the beginning of a perceptual and operational shift — the kind that does not happen all at once but compounds, one design choice at a time, one honest measurement at a time, one conversation at a time in which someone decides that the system can be different and begins, in the deciding, to make it so.

The leaders who build regenerative organizations are not the ones who had the clearest vision or the most perfect framework. They are the ones who were willing to keep looking at what their system was actually producing — not what the dashboard said it was producing, not what the strategy deck said it was building toward, but what the people inside it were actually experiencing — and to keep designing toward something better.

That willingness, sustained over time, is what regenerative leadership is made of.

The work is waiting. Begin where it calls.

This series is the beginning of something, not the summary of something finished. Meraki Musings is where the Regenerative Leadership Model continues to develop — alongside the talent architecture work that lays the foundation for everything regeneration requires. Subscribe and grow with it.

Share this series if it resonated. Tag a leader who needs to read it. The conversation about regenerative organizations grows one person at a time.

Beyond Extraction explored regenerative alternatives to extractive organizational design across four parts. Written by Nicole Parker-Beggs, M.S., BCC — organizational psychologist and Founding Partner of Meraki Consulting.

Find the Regenerative Leadership Model Executive Summary at www.merakiconsultingpartner.com

There are two sentences I have spent most of my life believing could not share a room.

I love my father.

And…

I do not enjoy spending time with my father.

For years I treated the gap between them as a contradiction to be solved — as though one had to be made false before the other could be allowed to stand. As though loving him obligated me to enjoy time with him. As though not enjoying time with him meant the love had failed somewhere, or worse, that I had.

It took me an embarrassingly long time, given what I do for a living, to understand that both sentences are simply true. Not in tension. Not canceling each other out. Just true, at the same time, in the same daughter.

My father is in his eighties. He drives from North Carolina to Texas to see us — we do not drive to see him, a detail one might think would register as information, and yet it never does. He invites himself. He stays longer than the space allotted in me can hold. And when he is here, the visits organize themselves, as they always have, around him.

He cannot manage a day at a museum or much walking, so the activities that might dilute a one-sided conversation are off the table. What remains is the talking. He talks incessantly while simultaneously lacking the ability to listen, and the content of the talking is, to put it precisely, not good. He complains — about the food, about the staff, and directs it toward the manager he has cornered to explain something no manager needs explained. He takes small jabs and calls me a yuppie because I would rather sit with a thoughtful wine list and a dish with nuanced layers of flavor than drink a beer in a dive bar he finds charming. He drinks the beer while pointing out all of the attributes he admires about the dive bar and finds, somehow, a way to put down the things I love. In essence, he enumerates — tirelessly, almost as a form of devotion — all the ways I am wrong and all the ways he is right.

I could go on. I have stories that are funny now but were far from funny at the time.

Yet, the behavior is not actually the thing I came here to write about. The behavior is the surface. Underneath it is the part that took the tears to reach: there is no mutuality. He does not know me. He has never asked a question with any depth in it, and he does not want to. He loves me the best he knows how — I do believe that — and the best he knows how was never going to be enough for me.

That is the grief. Not his behavior. The absence of mutuality, the one-directional flow, the giving of attention into a space that gives nothing back. The leaving of every interaction a little more depleted than when I arrived.

For a long time I thought the question in front of me was ‘how do I heal my relationship with my father?’ I now think that was the wrong question — a generous, dutiful, slightly self-erasing question, the kind a person asks when she has decided in advance that the work is hers alone to do.

The real question is quieter and far more uncomfortable.

How much of a relationship can I sustain while remaining compassionate without becoming depleted?

That question reorganizes everything. Because it begins from a premise I had not been willing to say out loud, which is this…

My peace matters too.

Not more than his dignity. Not at the expense of basic kindness. And also not last. Not as the line item to be cut first whenever his needs and mine cannot both be met.

So I have been doing the math, energetically speaking. I no longer take the phone calls — they are their own particular drain, and although he is insistent about them, I have stopped anyway. I limit our exchanges to mostly text messages. When he visits, we no longer go to restaurants… we order pizza or I cook, which removes one entire theater of complaint from the evening. I prepare myself before he arrives. I limit the time. I have built, without ever quite naming it as such, a structure that lets me stay in the room without leaving myself there.

I will name the thing this essay has been walking carefully around. He was abusive. He was neglectful — to me and to my sisters. I am not going to catalog it here, because this is not that essay, and you do not need the details to understand what follows. What you need is only this: there was real harm, and it was his.

For most of my life I would have considered this cold. I would have heard, somewhere underneath it, the voice that says a good daughter does not ration her presence. I no longer hear it that way. What I have come to understand is that I owe him nothing — and that this is not the cruelty it might sound like, but very nearly the opposite. Owing is the logic of his relationships, the ledger of debts and credits — who is up and who is down. It is precisely the transactional accounting I have always found intolerable in him. I don’t want to relate to my father through a ledger. I want to relate to him through my values.

So I honor his role in my life — not because I am obligated to, but because honor is one of my foundational values. I extend dignity. I extend compassion. I extend basic human decency. These are not debts I am paying down; they are expressions of the person I have chosen to be, and I would extend them whether he had earned them or not. That is the whole point of a value. It does not wait to be deserved.

And like everything that flows from values rather than obligation, what I extend has limits — chosen, deliberate, and fully mine.

There is one thing I will give myself that he was never able to give me: I do not abandon myself.

That is the boundary I had been quietly breaking. Every visit, every monologue I absorbed while my own experience went unspoken, every time I made myself smaller so his largeness would have somewhere to go — that was a small abandonment. Done out of love, yes. Done out of compassion for the pain he carries, which is real. But an abandonment all the same, and the only one in this entire arrangement that is fully mine to stop.

Here is what I want to say to anyone standing where I am standing, calibrating a relationship with someone they love and find insufferable…

Boundaries are not punishment. They are not the withdrawal of love. They are, more often, the only thing that makes a sustainable amount of love possible at all. Dignity is not the same as access. I can treat my father with genuine care and still decide how much of my time and energy he gets to occupy. The two are not in conflict. They have never been in conflict. The conflict was something I invented to keep from having to choose myself.

I don’t know how much time he has left on this earth. He is in his eighties and I expect, at any moment, the call. When it comes I want to be able to say that I stayed kind to the end without disappearing into the kindness. That I held the love and the limit in the same two hands. That I let both sentences be true.

I love my father.

And:

I will not abandon myself to prove it.

So I will leave you where I am sitting now:

What relationship have you been trying to heal that was never yours alone to repair?

And what would change if the one promise that truly belonged to you — the one you keep breaking — was the promise to not abandon yourself?

It rarely begins with a grand declaration of transformation.

It begins with a role. Or a team. Or a policy that has been quietly breaking people for longer than anyone wants to admit. It begins with a leader who has done the noticing, who has come back from the second conversation with a specific thing they can no longer pretend not to see — and who is now, with varying degrees of courage and varying degrees of ambivalence, ready to do something about it.

The design conversation begins in the specific. It always does. And that specificity — the fact that we are not redesigning “the organization” in the abstract but this role, this team, this policy — is not a limitation of the work. It is the methodology.

Regenerative redesign does not happen from the top down, all at once, in a single courageous organizational overhaul. It happens the way extraction happened — one design choice at a time, accumulating in a direction. The difference is that this time, the accumulation is deliberate. This time, someone is choosing.

What follows is what that choice actually looks like — in the room, in the work, in the moments of genuine progress and the moments of predictable resistance that are part of every design conversation worth having.

Role Design — What I Actually Do

The most common entry point into regenerative design work is a role that keeps breaking people.

A leader comes to me with a version of the same story I have heard many times: we have had three people in this position in four years, each one talented, each one initially excellent, each one diminished and eventually gone. The conclusion the organization has drawn is that the role requires a particular kind of person they have not yet found. The conclusion I draw, before I have seen a single job description, is that the role was designed for extraction and the organization has been blaming the people for the design flaw.

I ask to see the job description. And then I ask the question that almost always produces a long silence:

What does this role exist to create or restore in this organization?

Not what does it do — I can read that in the twelve bullet points of responsibilities. What does it exist to create? What gets better because this role is filled well, and what would quietly degrade if it disappeared? What is the purpose that all of those responsibilities are meant to serve?

Most leaders cannot answer this immediately. Not because they lack intelligence or care, but because most role design never begins with purpose. It begins with need — the organization has work that is not getting done, and the job description is an attempt to find a human being willing to absorb that work. Purpose architecture is not part of the process. And without it, there is no principled basis for deciding what belongs in the role and what does not — which means roles accumulate responsibilities the way surfaces accumulate clutter, and the person inside the role spends an increasing proportion of their capacity managing the clutter rather than doing the work that actually matters.

When a leader finds the answer to the purpose question — and they always do, though it sometimes takes two or three attempts to get beneath the operational language to something true — everything that follows becomes considerably cleaner. Every responsibility can be evaluated against a single standard: does this serve the purpose, or has it simply landed here because there was nowhere else for it to go?

What the comparison actually shows

Let me be specific about what this looks like in practice, because the gap between extractive and regenerative role design is most visible when placed side by side.

Here is a Chief of Staff role as it is commonly designed — meaning, as it is designed by an organization that has identified everything it needs done and is looking for a person willing to do it…

Manage executive calendar and coordinate leadership team meetings. Oversee special projects. Serve as liaison to the board. Manage executive communications. Lead strategic initiatives. Supervise two direct reports. Additional duties as assigned.

I want to draw attention to that last phrase: additional duties as assigned. In extractive role design, this is the tell. It is the organizational equivalent of leaving a blank line at the bottom of a contract. It says, explicitly, that the scope of this role is not actually defined — that it will expand to fill whatever the organization needs it to fill, regardless of what that costs the person filling it.

Now here is the same role, redesigned from purpose:

The purpose of this role is to ensure the CEO’s strategic attention stays where it creates the most organizational value, by managing the operational and coordination functions that would otherwise consume it. Success looks like: a CEO who arrives at every critical decision with the context, time, and clarity to make it well.

From that purpose, the responsibilities become specific and bounded. Calendar and leadership meeting logistics: twenty percent of capacity. Strategic initiative management — two to three initiatives per quarter with defined scope and endpoints: fifty percent. Direct report development: twenty percent. Board liaison for specific, defined deliverables: ten percent.

And then — this is the part most job descriptions never include, and the part that matters most — what this role does not include: executive communications, handled by the communications function. Open-ended special projects without defined scope, which get evaluated and properly staffed before being assigned. After-hours availability, except during pre-scheduled board engagements or genuine organizational crises.

The boundaries are not a reduction of the role’s importance. They are the design feature that makes the role sustainable. And sustainable, in this context, means something precise: it means that a capable person can do this work with excellence for years, not months — because the design restores rather than depletes, and because it is built to be examined and refined rather than simply endured.

When I present this comparison to a leader, there is almost always a version of the same response: that sounds right, but I am not sure we can actually hold those boundaries in practice. Which is an honest and important thing to say — and it marks the beginning of the real design conversation, not the end of it.

Because the question is not whether the boundaries are comfortable to hold. The question is what it keeps costing the organization to operate without them. Three people in four years. Three rounds of recruitment fees, three onboarding investments, three exits carrying institutional knowledge that no one has documented because no one has had capacity to document it. The fourth candidate, interviewing now, has no idea that what they are being asked to accept is a role designed to extract rather than develop.

That is the math of extractive role design. And once a leader has done it honestly, the conversation about whether the organization can afford to hold boundaries tends to resolve itself.

Team Design — What the Energy Mapping Conversation Reveals

The energy mapping exercise sounds, when I describe it, almost straightforwardly simple. I ask a team — or a leader, on behalf of their team — to make two lists. Work that drains energy faster than it restores it. Work that builds capacity and brings something generative to the surface.

What happens when teams actually do this exercise is rarely simple at all.

The first thing that happens, almost universally, is that the high-drain list is considerably longer than anyone anticipated. Not because the team is fragile or the work is uniquely difficult — but because high-drain work has a tendency to become invisible when it is constant. When the depletion is the baseline, it stops registering as depletion and starts registering as just the way this work feels. The energy mapping exercise makes it visible again, which is the beginning of being able to do something about it.

The second thing that happens — and this is the moment I watch for most carefully — is when the distribution of the high-drain work becomes apparent. In nearly every team I have worked with, the distribution is not equitable. The most depleting work has accumulated with a specific subset of people: almost always the most capable, most reliable, and least likely to say that the load is unsustainable. The people who have demonstrated, through years of absorbing whatever the organization needed absorbed, that they can handle it. The people the organization has implicitly decided to trust with the heaviest weight — not as a recognition of their strength, but as a consequence of it.

When a leader sees this clearly — when the map makes visible what the metrics have been obscuring — the response is almost always a specific kind of pained recognition. They knew, in some peripheral way, that the load was uneven. They had not quite let themselves look at how uneven it actually was.

The redesign conversation that follows is not primarily about redistributing tasks, though that is part of it. It is about examining the system that produced the inequitable distribution in the first place — the unwritten organizational logic that routes the most demanding work to the people least likely to push back, and then celebrates their capacity as a culture value rather than naming it as a design failure.

The collaborative norm I typically address first — before meeting structures, before communication protocols, before any of the surface-level interventions — is this one: the norm that equates availability with commitment. The understanding, rarely written anywhere and almost universally operative, that the people who respond fastest, stay latest, and never say they do not have capacity are the most dedicated members of the team. This norm is the engine of inequitable distribution. It makes boundaries professionally inadvisable and depletion structurally inevitable. And it almost always has to be named explicitly — by the leader, out loud, in a context where the team can hear it — before anything else in the design can actually change.

System Design — The Infrastructure Conversation No One Wants to Have

At some point in every sustained design engagement, we arrive at the hardest conversation — the one about whether the organizational infrastructure itself is capable of supporting what we are trying to build.

I ask the question this way: Whose voice is currently missing from the decisions that most affect them?

The room gets quiet in a particular way when this question lands. Not the quiet of resistance — the quiet of people who are actually thinking, possibly for the first time in a formal setting, about the distance between who has power in this organization and who has the most relevant information. Those are almost never the same people. And the gap between them — the decisions being made at the top of the hierarchy about work that is understood most deeply at the edges — is one of the most reliable sources of organizational dysfunction I have encountered.

Extractive organizational infrastructure concentrates power and controls information. It does this not through malice but through design logic: the belief, so deeply embedded in most organizational cultures that it rarely surfaces as a belief at all, that good decisions come from the people with the most authority rather than the people with the most knowledge. This logic produces organizations where the people closest to the work are executing decisions made by people several layers removed from it, where truth travels upward slowly and is edited at every level, and where the organizational intelligence that lives in the people actually doing the work is systematically underutilized.

Regenerative infrastructure moves in the opposite direction. It pushes decision-making toward the edges — not because decentralization is philosophically appealing, but because the people closest to the work almost always have the most relevant information for the decisions that affect it. It treats information as something to be shared rather than controlled. And it designs power not as the capacity to control outcomes but as the capacity to create conditions — which is a fundamentally different use of authority and one that most organizations have never seriously considered.

The policy I examine first, in almost every system-level design conversation, is the one governing how people are expected to be available. Not the written policy — the operative one. The actual understanding, lived in practice, about when people are expected to respond, what constitutes sufficient availability, and what the consequences are for operating within the stated boundaries rather than the implicit ones.

This policy reveals, with remarkable reliability, whether an organization’s stated values and its operational values are the same. An organization that says it values wellbeing and operates with an implicit expectation of constant availability is not a regenerative organization with an availability problem. It is an extractive organization with a messaging strategy. And the design work required in those two situations is entirely different.

Subscribe now

Where Leaders Get Stuck — And What I Do When They Do

The resistance in design work almost never arrives at the beginning. At the beginning, intellectual engagement is high, the vision is compelling, and the cost of change is still abstract. The resistance arrives in the middle — when something specific needs to be fundamentally different, and the full weight of what different requires becomes clear.

Here is where I see leaders stall, reliably and predictably, and what I have learned to do when they hit a wall.

The leader who will redesign everything except the thing that requires giving up control

This leader engages with the design work genuinely and enthusiastically — up to a precise point. They will redesign roles. They will examine team energy. They will talk, with apparent openness, about distributing decision-making authority. And then something specific comes up — a category of decisions, a particular domain, a specific kind of information — and the conversation shifts. The engagement remains. The movement stops.

What is underneath this stall is almost never about the specific domain where the resistance appears. It is about the deeper belief that leadership means having control over outcomes — that distributing authority is, at some fundamental level, an abdication of responsibility rather than an expression of it. This belief was rewarded for the leader’s entire career before this conversation. It does not dissolve because the framework is compelling.

What I do in this moment is not push. I ask a different version of the legacy question: If the people on your team were describing your leadership five years from now, what would you want them to say about how decisions got made? And I let the distance between that answer and the current design speak for itself.

The leader who understands the system is failing but cannot tell their own leadership

This leader has done the work. They see the extraction clearly. They are genuinely committed to redesigning it. And they are operating inside an organization whose own leadership — the board, the executive team, the ownership structure — is not yet having this conversation and may not be receptive to it.

The stall here is not about unwillingness. It is about structural exposure — the very real professional risk of being the person who names the problem in a system that has not yet decided the problem needs naming.

What I do in this moment is help the leader build the business case in language their leadership can receive. Not because the human case is insufficient — it is, in fact, the more important one — but because translation is a leadership skill, and the ability to make the regenerative argument in the register that the existing power structure can hear is what determines whether change actually reaches the system level or stays contained within a single leader’s sphere of influence.

The goal is not to make the case palatable by making it smaller. The goal is to make it undeniable by making it legible.

The leader who wants the regenerative outcome without the structural change that would actually produce it

This leader is, in my experience, the most common. They want the engaged, creative, high-trust team. They want the retention and the innovation and the compounding capability that regenerative design produces. They want all of it — and they want it without changing the role design that is unsustainable, without addressing the power structure that is silencing the voices the team most needs to hear, without modifying the policies that perform care while operationally demanding extraction.

They want the fruit without tending the soil.

What I do in this moment is return to the design. I ask them to name one specific thing — just one — that they are willing to actually change. Not to commit to. Not to explore. To change. And I watch what they choose, because what a leader is willing to change first tells me considerably more about what is actually possible in this engagement than anything they have said about their vision.

The one person who throws a wrench in everything

And then there is the fourth stall point — the one that is the most precarious and the most important to handle well.

Sometimes the leader is ready. The team is ready. The energy in the room is the specific, generative energy of people who have been given permission to imagine something better and have decided, collectively, to try. The design conversation is alive and moving and producing something real.

And then there is one person for whom this is not true.

Sometimes that person is frightened — of the change itself, of what the new design will require of them, of the ways in which their current position of informal power depends on the extractive structures being redesigned. Sometimes they are protecting something they have not yet named, even to themselves. Sometimes they have been burned enough times by organizational initiatives that promised transformation and delivered rebranding that their skepticism is not resistance at all — it is earned wisdom expressing itself as obstruction.

Whatever the source, the effect is real: one person, sufficiently resistant, can absorb enough of the team’s collective energy that forward movement becomes impossible. The design stalls. The momentum dissipates. The leader faces a choice that extractive leadership would resolve quickly and regenerative leadership must resolve differently.

The extractive resolution is to route around or remove the resistant person — to treat them as an obstacle to be managed rather than a human being whose resistance is telling us something.

The regenerative resolution is to find them a way out that preserves their dignity.

What this looks like in practice varies by person and context, and the specifics matter enormously. And yet the underlying principle is consistent: the goal is never to humiliate or expose or force. The goal is to create conditions in which the resistant person can make a graceful exit from the position their resistance has put them in — to find a different role, a different scope, a different contribution that is genuinely theirs rather than a consolation prize. To leave with their reputation intact and their relationships, where possible, preserved.

This is harder and slower and considerably more sophisticated than the extractive alternative. It is also the only approach that does not create a casualty the team has to grieve on its way to building something new.

What I Leave Them With — The Design Assignment

At the end of the first genuine design conversation, I leave the leader with something specific to do before we meet again — not a project plan, not a comprehensive redesign agenda, but a single assignment targeted precisely at the place where the design work revealed the highest-leverage opportunity and, not coincidentally, the most significant resistance.

The assignment is always some variation of: make the smallest change that would signal, unambiguously, that something is different.

Smallest, here, is not a concession to incrementalism. It is a design principle. The smallest change that is actually a change — that is visible, that is felt, that tells the people around you that the system is moving — is the one that builds the organizational credibility for everything that follows. It is the proof of concept. The first demonstration that the design conversation was not another vision exercise, not another initiative that will be named and forgotten, but the beginning of something that is actually going to alter how this organization operates.

That first change, made and held and communicated clearly, is worth more than any number of framework documents or redesign roadmaps. It is the moment the work stops being a conversation and starts becoming a practice.

Where We Go From Here

Part 3 has been about the design work itself — what it looks like to actually build roles, teams, and systems that give more than they take, and where the resistance predictably lives along the way. In Part 4, we arrive at the question that underlies all of it: how do we know if it is working?

Measuring regeneration is not straightforward. The tools most organizations use for measurement were built by extractive systems, for extractive purposes — and using them to assess a regenerative organization is like trying to measure the health of a garden with an oil gauge. The instrument is not wrong, exactly. It is measuring the wrong thing entirely.

Part 4 is about building the measurement capacity that regenerative organizations actually need — and about what behavioral assessment looks like when it is used to restore people rather than reduce them.

The work is waiting. Begin where it calls.

Discussion prompt: What is the role, the team norm, or the organizational policy in your sphere of influence that you have been walking past because changing it felt too complicated? Name it. That is almost certainly where the design work needs to begin. Hit reply — I read every one.

Next week: Part 4 — What the Numbers Miss

Beyond Extraction explores the practical application of regenerative frameworks to organizational design. Written by Nicole Parker-Beggs, M.S., BCC — organizational psychologist and Founding Partner of Meraki Consulting.

Before school. Before work. Before anyone handed you a job description or a performance review or a set of organizational values framed and mounted on a wall that no one actually lived by. You learned it in the first system you ever inhabited — the family — where the rules were unwritten but absolute, where safety was conditional, and where the cost of being fully yourself was higher than a small body knew how to pay.

So you did what intelligent children do when the environment cannot hold what they carry. You went quiet. You watched. You learned to read the room before you entered it — to scan for safety, to locate the threat, to calculate precisely how much of yourself you could offer without triggering what you had learned to fear. You became extraordinarily skilled at a thing no one ever named as a skill — the art of rendering yourself amenable.

That was the first lesson. And the system that taught it to you had no idea it was teaching anything at all.

. . .

By the time you reached school — and for many of us, the particular architecture of Catholic education, with its incense and its silence and its very precise ideas about the role of women in the order of things — the lesson had already taken hold. School did not create the wound. It salted it. It gave the wound an institutional framework, a divine justification, a daily practice.

You were smart. You learned quickly. You excelled — because excelling was the one form of visibility the system would reward rather than punish. You sat quietly in rows, absorbed the curriculum, and gave back on examinations exactly what had been given to you, in exactly the form it had been given. It did not feel true or right. Yet, you were told this was intelligence. What it was, in reality, was compliance. And you were good at compliance because being quiet and playing by the rules had kept you safe long before the school required it of you.

But something in you — something the system could not reach no matter how precisely it was designed — kept seeing. Kept noticing the gap between what was taught and what was true. Kept registering, in the body, the specific wrongness of being told that the most generative, most aware, most spiritually significant aspects of existence were subordinate by divine design. Even as a child, this did not ring true. Even as a child, the body knew.

And so the translation work began in earnest. You learned to take what you saw with crystalline clarity and render it in forms the system could receive without fracturing. You learned to soften the edges of your observations. To ask questions that sounded like curiosity rather than challenge. To write papers that made the opposing argument land so gently that the reader barely registered they had been moved. You became a translator of your own inner wisdom — fluent in the language of your own interior truth and simultaneously fluent in the dialect the system required you to speak.

This is the translation tax. And you have been paying it your entire life.

. . .

The tax is not metaphorical. It lives in the body.

It lives in the careful calibration of tone before you speak — the split-second calculation of how much of your actual conviction you can afford to bring into this particular room with these particular people on this particular day. It lives in the editing that happens between what you think and what you say — the involuntary self-censorship that has become so practiced it no longer feels like censorship at all. It lives in the jaw that tightens when someone describes your clarity as aggression, your precision as hostility, your depth as excess.

It lives in the exhaustion. The specific, somatic exhaustion that has nothing to do with how many hours you worked or how many obligations you carried. The exhaustion that comes from decades of containing what cannot be contained without great cost — of keeping inside a body what was designed to move through the world freely, fully, and without apology.

You have been told you are too intense. Too much. You have watched your most honest observations make people uncomfortable — and then watched the system reframe your clarity as the problem rather than examining what your clarity was pointing at. You have been the villain in stories you did not write, playing a role assigned to women by systems that could not afford to let the seeing stand unchallenged.

Women have been scapegoats for far too long. And the body holds every tally-mark for every role it was forced to play.

. . .

Here is what the system never told you — because the system did not know, and could not afford to know, and was not designed to examine itself with sufficient honesty to find out:

The translation tax is not a personal burden. It is a structural feature.

Extractive systems — systems built on hierarchy over interdependence, on dominance over cultivation, on urgency over rhythm, on performance over presence — do not need to consciously suppress the women who see clearly. They simply need to make clarity costly enough that women self-regulate. The system does not silence you. It trains you to silence yourself. And if you refuse — if the seeing is too revelatory, the knowing too precise, the voice too veracious — the system does not engage with what you are saying. It simply reframes you as the problem.

This is not accidental. It is architectural. It is what systems built on the suppression of the feminine beget — not as a side effect, but as a function. The translation tax is the mechanism through which the most generative, most restorative, most deeply knowing capacities in an organization are quietly consumed rather than cultivated. Every woman who has spent somatic resources translating her inner-wisdom into forms the system can receive without fracturing has subsidized that system with exactly what it needed most and was least willing to acknowledge needing.

The first day of work feels like the first day of school. You are not sure what is safe, who is safe, what the unwritten rules are, or how much of yourself you can afford to bring. You keep your eyes open, your mouth calibrated, you watch and you wait, and you learn the terrain before you risk the visibility. The pattern that formed in childhood — the quiet observation, the careful translation, the strategic smallness — walks into every new system with you, as fluent and as exhausting as it ever was.

And the organization, which has never examined what this costs, continues to wonder why its most perceptive people are depleted. Why the gap between its stated values and its lived culture refuses to close. Why the women who see most clearly are either leaving or going quiet in ways that look like contentment but feel, from the inside, like slow erasure.

. . .

But here is what the tax also produced — and this is the part the system did not anticipate…

Decades of translation work, done with enough intelligence and enough interior integrity, produces a precision that unmediated expression never could. The women who have paid this tax the longest and most consciously have developed a capacity for seeing that is extraordinary — because they have had to understand the system well enough to navigate it, resist it, survive it, and ultimately name it. They have had to hold their own wisdom and the system’s intransigence simultaneously, in creative tension, for long enough that the gap between the two has become itself a source of insight.

The wound, metabolized, becomes the lens.

The silence, broken at the right moment in the right register, becomes the thing that changes rooms rather than merely occupying them.

The translation work, finally turned outward rather than inward — used to make the truth accessible to those who could not yet receive it in its original form — becomes the most generative act available.

This is alchemy. Not in the mystical sense — though the mystical tradition has always known it. In the most literal sense: the transformation of what was designed to diminish into what produces illumination. The lead of the wound into the gold of the sage.

You are not too much. You have never been too much.

You have been in the wrong rooms — rooms built on architectures that could not hold what you carry, designed by systems that could not afford to let you be fully seen, maintained by the accumulated weight of centuries of institutional suppression of exactly the qualities you embody most fully.

The rage you feel when you encounter this suppression is not a liability. It is a signal — the most honest and precise signal your nervous system produces. It is your body telling you that something true is being violated. Do not manage it. Do not translate it into a more palatable form for the comfort of those who have not yet earned the right to receive it. Let it be information. Let it tell you where the imbalance lives. And then — when you are ready, when the integration has gone deep enough, when the alchemy has done its work — let it become the foundation of something the system never saw coming.

Because the women who have paid the translation tax the longest are not depleted. They are prepared.

Prepared to build systems that do not require the tax. To design organizations around the principles that patriarchal architecture has suppressed — the relational, the restorative, the cyclical, the generative. To lead from the interior rather than from performance. To create the conditions in which the women who come after them do not have to choose between being fully themselves and being safe.

This is not about dismantling what exists. It is about building something so much more honest, so much more sustainable, so much more worthy of the people inside it, that the extractive model simply becomes an inheritance no one chooses to perpetuate.

The sisterhood does not need more women who have learned to survive the tax. It needs women who have metabolized it — and are ready to build from what it taught them.

You know who you are.

The work is waiting. Begin where it calls.

The second conversation is different from the first.

In the first conversation, I am listening and observing — reading the room, reading the energy, asking the magic wand question and watching what happens in the space before the answer. The first conversation is diagnostic. It is the careful work of finding out what has actually been happening beneath the language of strategy and optimization and organizational efficiency.

The second conversation is something else entirely. It is the moment where I find out whether we are actually going to do anything about it.

I always begin the second conversation the same way: I ask the person across from me what they noticed. In the two weeks since we last spoke, what was the moment — just one — where someone on their team gave them a signal that the system was costing them something?

What I am listening for is not the story itself, though the story matters. I am listening for the quality of attention behind it. Whether the person in front of me saw the moment as data about the individual — that team member is struggling, that team member needs coaching, that team member may not be the right fit — or whether they saw it as data about the system. Whether they looked at what their organization produced and began, even provisionally, to ask what in the design made that outcome inevitable.

The leaders who arrive at that second conversation having genuinely noticed — having written something down, having sat with it, having let it trouble them in the way that real diagnostic information troubles a person who is paying attention — those leaders are ready for what comes next.

The leaders who arrive with a polished anecdote that demonstrates their self-awareness without actually threatening anything they are currently doing — those leaders need a different kind of conversation first. Not a harder one, necessarily. A more honest one.

This is where the real work of regenerative leadership begins: not in the framework, not in the redesign, not in the new metrics. In the willingness to let what you have noticed actually change something.

What I Say When Someone Hears “Regenerative” and Immediately Thinks “Soft”

It happens in nearly every second conversation, in some form. Sometimes it is explicit — a leader who says, directly, “I appreciate the philosophy, and yet I have a board to answer to and numbers to hit.” Sometimes it is subtler — a slight shift in posture, a careful neutrality in the voice, the look of someone who has decided to be politely open-minded about something they have already categorized as idealistic.

When I encounter it, I do not argue. I agree.

I say… you are right that regenerative leadership is not the easier path. It is, in almost every meaningful way, the harder one. Extractive leadership is straightforward — push harder, demand more, replace whoever breaks, repeat. It requires very little sophistication. It requires even less self-awareness. It produces results in the short term and catastrophic costs in the medium term, and the reason most organizations never fully reckon with those costs is that by the time they arrive, enough has changed — enough people have turned over, enough leadership has rotated — that the connection between the extractive design and the eventual collapse is genuinely difficult to trace.

Regenerative leadership requires something extractive leadership never asked of you: it requires you to hold yourself accountable not just for whether the results were achieved, but for how they were achieved, and whether the system that produced them is more capable afterward or more depleted. It requires you to measure things that are difficult to measure and to redesign things that are uncomfortable to examine. It requires you to question systems you have been rewarded — sometimes handsomely — for maintaining.

And then I ask the question that usually ends the softness objection entirely…

How much is it currently costing you to keep doing it the way you are doing it?

Not rhetorically. Specifically. The turnover in the last eighteen months — what did that cost in recruitment fees, in training investment, in the institutional knowledge that walked out the door, in the team disruption that the remaining people absorbed without anyone ever accounting for the toll? The high performer who has gone quiet — what is the innovation cost of a person who has stopped offering the ideas that don’t get heard? The leader who is running on empty — what is the decision quality cost of someone who is too depleted to think with the full range of their capability?

Regenerative leadership is not soft. It is the only approach that is economically intelligent enough to account for the actual cost of extraction — including the costs that never show up in a quarterly report until they have already been paid.

I have yet to have a leader, once they have done that calculation honestly, continue to describe regenerative leadership as a luxury.

Running the Four-Level Framework — What Actually Happens

When I work with a leader who is genuinely ready to examine their practice, I use a framework that looks at four interconnected levels: Self, Relationship, Team, and System. On paper, it is a taxonomy. In a room, it is something considerably more alive — a diagnostic that almost always reveals something the leader did not know they were carrying.

Here is what actually happens at each level.

Self

I begin with the legacy question. Not because it is the warmest or most comfortable place to start, but because it is the most honest — and because the distance between a leader’s legacy intentions and their current daily practice is almost always where the most important diagnostic information lives.

The question has three parts, and I ask them in sequence, letting each one land before moving to the next.

What words do you want people to use to describe you — as a leader, as a colleague, as the person ultimately responsible for this team’s experience?

Most leaders can answer this fairly fluently. Visionary. Trustworthy. Demanding in the best sense. Someone who develops people. The answers tend to be thoughtful and genuine — these are not aspirations chosen for my benefit. They are the leadership identity the person has been quietly holding onto, often for years.

What impact do you want to have — on this organization, on this team, on the industry you are part of?

This one goes a layer deeper. The answers slow down. People think more carefully. The legacy question at this level tends to surface something that the day-to-day pressure of organizational life has been systematically crowding out — a commitment to something larger than the quarterly number, a vision for what this team could become if the conditions were right, a sense of purpose that predates the current role and will outlast it.

And then the third question, which is the one that almost always produces the longest silence:

What do you want someone to feel when they see a meeting with you on their calendar?

I have asked this question to hundreds of leaders. The silence before the answer is one of the most instructive things I have ever witnessed in this work. Because most leaders — not all, but most — know, in that silence, that the honest answer to that question and the aspirational answer are not currently the same thing. That the person they want to be seen as and the person their calendar is producing are operating at some distance from each other.

That distance is not a moral failing. It is a design problem. And naming it as such is the beginning of the Self-level work.

Relationship

At the relationship level, the diagnostic question I am working with is this: are you building the people around you, or optimizing them?

The distinction sounds subtle and is actually enormous. Optimizing a relationship means managing it — keeping the interaction productive, the communication efficient, the output consistent. It means knowing enough about someone to deploy their strengths effectively and route around their limitations. It is not unkind. It is, in its own way, competent. And yet it treats the person on the other side of the relationship as a fixed variable to be worked with rather than a developing human to be invested in.

Building a relationship means something categorically different. It means that the person across from you is more capable, more seen, and more genuinely themselves at the end of the interaction than they were at the beginning. It means that your investment in them is not contingent on their current productivity but on their potential — and on the fundamental belief that an organization’s greatest leverage point is the ongoing development of the humans inside it.

The pattern I see most consistently at this level is leaders who are genuinely caring people — who would describe themselves as invested in their teams and mean it — who have nonetheless, through the accumulated pressure of extractive organizational systems, quietly shifted from building to optimizing without ever making a conscious decision to do so. They are managing well. They stopped developing somewhere along the way. And the people around them have noticed, even if they haven’t said so.

What I watch for at this level, and what almost always surfaces when I look carefully, is the degree to which a leader’s team feels genuinely safe to tell the truth. Not comfortable — safety and comfort are different things, and a team that is comfortable is not necessarily a team that is safe. Safety means that when something is broken, someone says so. That when a decision is misguided, someone names it. That when a person is struggling, they bring it forward rather than managing it out of sight until the departure letter lands on someone’s desk.

Trauma-informed leadership lives here — at the relationship level — because this is where past harm either gets perpetuated or interrupted. Organizations carry trauma the way people do: in the body, in the reflexes, in the patterns of self-protection that develop when trust has been repeatedly broken. A leader who understands this does not demand openness from people who have learned that openness is dangerous. They create conditions — slowly, consistently, over time — in which openness becomes possible again.

Team

At the team level, I am looking at energy economics — which is a phrase that sounds more abstract than it is.

What I am actually doing is asking a leader to map their team’s energy in the same way a good financial advisor would map a portfolio: what are the high-drain activities, what are the high-restoration activities, and how is the distribution currently working? Who on this team is perpetually in the grind — doing the work that consumes capacity faster than it builds it — and who has access to the work that energizes and develops? Is that distribution equitable, or has it followed the path of least organizational resistance, which almost always means the most capable and least boundaried people absorb the most depleting work while the system calls it high performance?

The thing about energy mapping that consistently surprises leaders is how visible it becomes once you are looking for it. The team member who arrives to every meeting slightly diminished from the last one. The person who used to volunteer for new challenges and has quietly stopped. The high performer who is producing excellent output and is, beneath the output, running on a reserve that will not last another eighteen months.

What the engagement survey will not tell you — what no annual measurement instrument will tell you — is the real-time energy trajectory of the people on your team. Whether they are building toward something or depleting toward something. Energy mapping, done honestly and without the defensive layer that formal assessment tends to produce, will.

System

This is the level that stops most leaders cold, and the fact that it does is itself diagnostic.

The system level is where we examine whether the infrastructure of the organization — the policies, the power structures, the decision-making norms, the unwritten rules that govern what is rewarded and what is punished — is designed to restore capacity or extract it. And what I have found, consistently, across industries and organizational sizes and leadership philosophies, is that most organizational infrastructure was built under extractive logic without anyone deciding that it should be.

The question I ask at the system level is simple and almost always uncomfortable:

If you could not change the people — if everyone on your team stayed exactly as they are — and could only change the design, what would you change first?

The discomfort this question produces is instructive. Leaders who have been trained to see performance problems as people problems often struggle to answer it — not because they lack intelligence or care, but because the perceptual frame that would let them see design as the primary variable has never been fully developed. They have been rewarded, their entire careers, for finding the right people and managing them effectively. The idea that the design might be the problem — that the most talented, committed, well-managed people in the world cannot sustainably succeed inside a system built for extraction — is genuinely new territory.

When a leader sits with that question long enough to answer it honestly, the answer almost always points directly at the highest-leverage redesign opportunity in their organization. Not the one that is easiest to address. The one that would matter most.

What I Watch For When a Leader Is Genuinely Ready

There is a moment in this work that I have come to recognize with something close to certainty, though I could not have described it precisely in the first years of my practice. It is not marked by a particular answer to a particular question. It is visible in the face before the answer comes.

What I see, in the leaders who are genuinely ready to build differently, is a cascade — a sequence of emotions that moves across the face in rapid succession, each one real and each one distinct. First there is something that looks like shame, though it is not quite shame — it is the particular expression of someone who has just understood, at a level deeper than intellectual comprehension, what their system has been costing the people inside it. ‘Oh my god. What have I been doing to my people?’ Not as a performance of accountability. As a genuine reckoning.

And then, almost immediately, relief. The relief of someone who has been carrying a weight they could not name and has just been handed the vocabulary for it. The system is the problem. Not the people. Not their own inadequacy as a leader. The design — and design can be changed.

And then, following the relief with an energy that is unmistakable even when it is tentative — excitement. The specific excitement of a person who has just seen a new possible future and is already, in some part of their mind, beginning to move toward it.

And threaded through all of it, honest and appropriate and not to be dismissed: fear. The particular fear of someone who has been deeply competent inside one operating system and is contemplating the unfamiliar demands of a different one. Of giving up a control that felt like leadership and trusting something more distributed, more alive, and considerably less predictable.

The leaders who choose to continue on the journey — the ones who move from that moment into the actual work of regenerative redesign — always ask the same question next. It is always some variation of:

“Ok. Now what? Where do we go from here, and what will this actually look and feel like?”

That question is everything. It is not a request for reassurance. It is not resistance dressed as curiosity. It is the question of someone who has decided — who is already, in the asking, beginning — and who wants to know what the path looks like from here.

What I Leave Them With After the Second Conversation

The deliverable at the end of the second conversation is not a project plan. It is a single design challenge — specific enough to be actionable, contained enough to be completable before we speak again, and pointed directly at the highest-leverage system-level change their answers have revealed.

It sounds like this: Between now and the next time we meet, I want you to change one thing. Not ten things. One. The smallest possible change that would signal — to yourself and to the people around you — that the system is beginning to move in a different direction.

Sometimes that one thing is a meeting that gets cancelled permanently because it has never produced anything that justified its cost in collective attention. Sometimes it is a decision that gets pushed to the person closest to the work rather than routed back up the hierarchy. Sometimes it is a conversation — a specific, honest conversation with a specific person — that has been deferred for reasons that were about comfort rather than timing.

The one thing is almost never the most important thing. It is the thing that, when changed, makes it possible to see the next thing. Regenerative redesign does not happen in a single courageous decision. It happens in the accumulation of smaller ones — each one slightly expanding what feels possible, each one building the organizational muscle for thinking and designing differently.

What I am leaving them with is not a task. It is the beginning of a practice.

And that distinction — between a task that gets completed and a practice that gets built — is perhaps the most important thing I have learned to communicate clearly in the second conversation.

Because regenerative leadership is not a destination. It is a direction. And the leaders who ultimately build regenerative organizations are not the ones who had the most perfect vision of what they were building toward. They are the ones who were willing, one design choice at a time, to keep moving in that direction even when the system around them was still pulling toward extraction.

That willingness — stubborn, clear-eyed, and absolutely not soft — is the harder ask.

And it is the only one worth making.

Where We Go From Here

Part 2 has been about the decision — what it looks like when a leader is genuinely ready to lead differently, and what the early work of regenerative leadership actually demands. In Part 3, we move into the design itself: what it looks like to build roles, teams, and systems that give more than they take. Not in theory. In practice — with the specific questions, the specific redesign moves, and the specific moments of resistance that make this work both challenging and, when it takes hold, genuinely extraordinary.

The work is waiting. Begin where it calls.

Discussion prompt: What is the one thing — just one — you could change in the next two weeks that would signal to the people around you that the system is beginning to move? Hit reply. I want to know what you choose.

Next week: Part 3 — The Design Conversation

Beyond Extraction explores the practical application of regenerative frameworks to organizational design. Written by Nicole Parker-Beggs, M.S., BCC — organizational psychologist and Founding Partner of Meraki Consulting.

The room is almost always a conference room.

Glass walls, usually. A table that seats twelve, with six or eight people arranged in the half that faces the door. A pitcher of water no one has touched. Someone’s laptop is already open to the agenda.

Before the first sentence of the first agenda item is spoken, I am already learning.

I notice who arrived first and where they chose to sit — whether they placed themselves at the center of the table or tucked into a corner seat that technically belongs to them yet also telegraphs exactly how much space they believe they are permitted to occupy. I notice who entered directly behind the leader, close enough to signal proximity to power. I notice who arranges their notepad before making eye contact with anyone, and I notice who makes eye contact with everyone before sitting down.

And then I notice the pause.

That particular kind of pause — the one that exists between when a question is asked and when anyone answers it. Not the pause of thinking. The pause of checking. Of scanning the room to see whose face will tell them what is safe to say.

This is what I do before the official conversation begins: I read what the room has already been saying for months, possibly years, without anyone using words.

What I am describing is a composite — elements drawn from multiple organizations, several industries, countless rooms across decades of this work. And yet it is also remarkably consistent, because organizational extraction leaves the same fingerprints everywhere it has been. The faces change. The industry changes. The strategic priorities written on the whiteboard change. The fingerprints do not.

This piece is about what those fingerprints look like — and more specifically, about how I find them before anyone in the room has named what is actually happening. Because in my experience, the people closest to an extractive system are often the last to have language for it. They know something is wrong. They feel it in their bodies, in their Sunday-night dread, in the way they have stopped offering ideas in meetings. And yet the vocabulary of extraction — the framework that would let them name it, diagnose it, and begin to redesign it — is rarely available to them.

So we start here. In the room. Before anyone names it.

The First Question I Ask — And Why It Is Not About Culture

Most organizational consultants begin with data. Engagement survey results. Turnover numbers. Productivity metrics. Exit interview themes. These are not useless — and yet they are almost always lagging indicators of something that has already been happening for a long time, something that was in motion long before it registered in a spreadsheet.

I begin differently.

I begin by reading the energy of the person across from me — the quality of their tiredness, whether it is the satisfying exhaustion of someone who has given everything to something that mattered, or the particular depletion of someone who has been running on empty for so long they have forgotten what full felt like. I listen to what they say and to what they do not say. I track the subjects that get approached and then gracefully sidestepped. I notice when language becomes careful and corporate precisely at the moment when something true is about to be spoken.

And then, when the moment is right — when I have established enough trust that honesty feels marginally safer than performance — I ask what is quite possibly the least corporate question in the history of organizational consulting:

“If I had a magic wand and could make your wildest dreams come true — for this organization, for this team, for yourself in this role — what would they be?”

And then I listen. Not for the answer, exactly — though the answer matters. I listen for what happens in the space before the answer. The exhale. The slight dropping of the shoulders. The moment when someone decides, often for the first time in a very long time, that it might be safe to tell the truth about what they actually want.

I have asked this question to healthcare administrators who could quote efficiency metrics with precision and could not remember the last time they felt proud of how their team was treated. I have asked it to nonprofit directors who were working seventy-hour weeks for a mission they genuinely believed in while the organization celebrated their dedication without ever questioning the design that demanded it. I have asked it to tech executives who had reorganized their teams three times in eighteen months, each time calling it optimization, each time watching institutional knowledge walk out the door.

The dreams themselves are almost always the same. Not the specific outcomes — those vary — but the texture of them. People want their teams to feel genuinely supported rather than strategically managed. They want meetings where something actually gets resolved rather than deferred. They want to go home at a reasonable hour without the low-grade guilt that has become so normalized it barely registers anymore. They want to stop losing good people to organizations that are, by most measurable standards, less excellent than their own.

What they are describing — without the vocabulary for it yet — is an organization that regenerates rather than extracts. And what the gap between their current reality and their wildest dreams reveals is the precise shape of the extraction that has been happening.

The magic wand question is not whimsy. It is diagnostic precision in the language of possibility — because possibility is the only register in which people who have been deeply conditioned by extractive systems can initially access what they actually know.

What Extraction Actually Looks Like: Three Portraits

The frameworks for understanding organizational extraction exist — and we will get to them. And yet frameworks are abstract until you can see what they look like at two o’clock on a Wednesday afternoon in a real organization with real people who are trying, genuinely, to do excellent work inside a system that was never actually designed to let them.

Here are three portraits — composites drawn from years of client work, each representing a pattern I encounter with such regularity that I have come to treat it as its own diagnostic category.

Portrait One: The High Performer Who Has Gone Quiet

She was exactly the kind of person this organization had built itself around. Deeply competent, genuinely committed, the one people went to when something needed to get done — not because she was fast, though she was, but because she thought carefully and her judgment was almost always sound.

When I spoke with her colleagues and her manager, the description was consistent: she had been extraordinary in months one through twelve. Creative, engaged, reliably offering perspectives that shifted the conversation. By month eighteen, she was still performing — still hitting every metric the organization tracked — and yet something had changed. She had become, in the words of one team member, “professionally excellent and personally invisible.”

When I asked her about it directly, she said something I have heard in dozens of variations since: “I learned which ideas would actually get heard, and I stopped having the others.”

This is depletion of a particular and devastating kind — not burnout in the clinical sense, not yet, but the slow erosion of the generative quality that made her valuable in the first place. The organization’s metrics were showing a high performer. What the metrics were not showing was the steady diminishment of the person behind the performance, and the degree to which the system itself had trained that person to shrink.

Portrait Two: The Team That Stopped Collaborating Without Deciding To

On paper, this team was functioning. Projects were completed. Deadlines were being met — some of them, most of the time. The collaboration norms were written into the team charter, visible on a laminated page in the meeting room.

What had actually happened — gradually, over approximately fourteen months of successive reorganizations and tightening bandwidth — was that the team had shifted from genuine collaboration to sophisticated coordination. They were not working together so much as working alongside each other with carefully maintained boundaries around their individual portfolios. Information that used to flow freely was now being managed. Not maliciously — no one had decided to stop trusting each other. The decision had been made by the system, for them, through accumulated signals that contribution was not reliably rewarded and that transparency about workload was professionally inadvisable.

When I asked what their meetings felt like, one team member said: “Like everyone is performing collaboration while protecting the thing they actually need to share.”

The extraction here was of trust — something that doesn’t show up in any productivity metric until it is essentially gone, at which point the cost of rebuilding it is almost always catastrophic.

Portrait Three: The Leader Who Has Become the System

He was, by every traditional measure, a successful leader. The business results were real. The board thought highly of him. His direct reports described him as demanding and fair, which in the context of this particular organization was considered high praise.

What no one had named — including him — was the degree to which he had internalized the extractive logic of the organization so completely that he could no longer see it. He celebrated the people on his team who worked the most. He read responsiveness as commitment and boundaries as insufficient dedication. He genuinely believed he was protecting his team from the worst of the organization’s extractive tendencies, and in certain specific ways, he was — and yet the protection he was offering was downstream of a river he was also feeding.

When I asked him the magic wand question, he paused for a very long time. And then he said something that stayed with me: “I’d want my team to feel the way I felt in my first five years — before I learned to mistake optimization for vision.”

He had the dream. He had lost the design. And the work we did together was not about making him a better leader within the existing system — it was about helping him see that the existing system was producing outcomes he did not actually want, and that he had both the authority and the responsibility to redesign it.

Teaching the Extraction Spectrum — What I Actually Say in the Room

When I get to the point in a conversation — or an engagement — where it’s time to name what has been happening, I do not hand someone a framework document. I ask them what they think is happening first, and I listen for the edges of their language: where it gets specific and where it generalizes, where it blames a person and where it almost-but-doesn’t quite blame the system.

Then I offer a distinction that almost always creates a visible shift in the room.

There is a word that organizational culture has treated as a virtue for decades, and that word is rigor. Rigor, in the way organizations use it, means discipline. High standards. Exacting expectations. The kind of systematic, consistent, non-negotiable operational precision that separates excellent organizations from merely adequate ones.

And yet rigor, in its Latin roots, means stiffness. Rigidity. The hardening of something once living into something immovable. Rigor mortis — the unmistakable sign of death.

We have been applying rigor to human systems and then expressing genuine bewilderment when those systems feel lifeless.

The word I use instead is vigor. Vigor, in its roots, means vitality. Life force. The kind of strength that is not brittle because it is alive — that bends without breaking, that grows stronger through use rather than depleted by it. Vigor is what living systems have. Rigor is what systems develop when life has been extracted from them.

When I put this distinction in front of a leadership team, something usually happens that I have come to watch for: someone goes quiet in a way that is different from the checked-out silence of earlier in the meeting. It is the silence of recognition. Of naming something that has been true for a long time and has never had a word.

Extractive organizations operate on rigor: rigid structures, inflexible expectations, consistency enforced through control. The metrics get hit. The compliance rate is high. The culture is predictable. And yet the people inside it are quietly becoming less than they were — less creative, less willing, less capable of the generative thinking that the organization most needs and least rewards.

Regenerative organizations operate on vigor: alive, adaptive, holding high standards through cultivation rather than control. The metrics get hit because the people generating them have the capacity and the conditions to do their best work — not because they are being extracted until the work is done.

The spectrum between optimization and extraction is not a fixed line — it is a trajectory. And most organizations crossed it years ago without a single person in a single meeting making a single decision to do so. It happened through accumulation: one role made slightly too large, one reorganization that reduced headcount without reducing scope, one quarter of pushing harder that became, quietly, the new standard.

This is what I say in the room. Not as an indictment — the leaders I work with are not villains. They are, almost universally, people who wanted to build something meaningful and found themselves operating inside a system that had been designed, long before they arrived, to extract. The question is not whether extraction happened. The question is whether, now that we can name it, we are willing to design something different.

What I Leave on the Table After the First Conversation

Every initial engagement conversation ends with something I leave with the person I have been speaking with — not a proposal, not a scope document, not a follow-up agenda. Something smaller and more generative than any of those things.

I leave them with a question to sit with before we speak again.

The question is this: In the next two weeks, notice one moment — just one — where someone on your team gives you a signal that the system is costing them something. It does not have to be dramatic. It might be the way someone answers a question too quickly, without the pause that genuine thinking requires. It might be the meeting where the most experienced person in the room says the least. It might be an email sent at eleven o’clock on a Sunday that tells you nothing about dedication and everything about design.

Notice the moment. Write it down. Bring it back.

This is where regenerative work actually begins — not in the framework document, not in the org chart redesign, not in the new performance management system. It begins in the capacity to see what has been made invisible by familiarity. To notice, with fresh eyes, the ordinary moments that have been quietly costing people something they are not getting back.

The metrics will not show you those moments. The engagement survey, run once a year, will not show you those moments. The quarterly business review will not show you those moments.

Attention will.

And attention, it turns out, is both the beginning of diagnosis and of something else entirely — the beginning of designing systems that see people as whole humans rather than human resources. The beginning of building organizations with vigor rather than rigor. The beginning of the question that drives everything that follows in this series:

What would this organization look like if it were designed to give more than it takes?

Where This Series Goes From Here

Part 1 has been about seeing — developing the perceptual frame that makes extraction visible. In Part 2, we move into understanding what regenerative leadership actually requires in practice, not as a philosophical posture but as an operational one. In Part 3, we design: roles, teams, and systems. In Part 4, we measure — and we examine how the tools we use for measurement either serve dignity or strip it away.

This is not a series about soft leadership or slower organizations. It is a series about sophisticated ones — ones that understand living systems well enough to design with them rather than against them.

The work is waiting. Begin where it calls.

Discussion prompt: What’s the moment in your organization that you’ve been walking past without naming? Hit reply — these are the most instructive conversations I have.

Next week: Part 2 — The Harder Ask

Beyond Extraction explores the practical application of regenerative frameworks to organizational design. Written by Nicole Parker-Beggs, M.S., BCC — organizational psychologist and Founding Partner of Meraki Consulting.