You are accountable for what you cannot see.
The conditions that will decide your most important initiative are invisible from where you sit. We make them visible, while there is still time to do something about it — and what changes stays after the work ships.
“In situations where you could just replace a washer, Jim will always look at everything around that washer and ask one question: can I make this better?”
The things that decide business outcomes do not appear in the plan.
Everything that reaches you has passed through the organization first. Summarized, reconciled, and made presentable. What arrives is usually accurate, and still not the whole picture.
Meanwhile the conditions that will actually decide an initiative's outcome — where decisions really get made, what information travels and what quietly does not, what people believe matters, what the organization protects without ever discussing it — are not addressed in the plan. They are not being hidden from you. They have not been made visible at the time the plan is designed, or during its execution.
Four signs this is happening today.
Each one is ordinary enough to explain away on its own. Together they describe a condition, not a bad week.
- 01
Decisions that should be settled below you keep landing on your desk.
- 02
Multiple teams are all doing the right thing, against different definitions of right.
- 03
What you needed to know arrives a week after you needed it.
- 04
The status report is green every week, and what the project will actually deliver keeps shrinking.
None of it means your people are incapable.
This is not resistance — it’s the organization doing what it learned to do at an earlier time, for specific needs.
The strength of an organization isn’t found in its org chart. It’s woven into the fabric of how its people think, decide, trust, and create value together.
Strategy is shaped twice.
First in the room where it is decided. Then again in the work, where it quietly becomes something else.
You have felt this. The decision was clear when it was made. Months later what comes back is a version of it, close enough that no one calls it wrong, different enough that it does not do what you needed.
Nothing failed along the way. The strategy simply passed through the way your organization already works, and came out changed. That second shaping is the part you cannot see, and it is where the returns go.
Operating Conditions
How work actually moves in your organization, written down or not.
The Pull
How they quietly pull anything new back toward the result you already get.
What we do
Work inside the initiative and change those conditions.
Value
Now, after it ships, and next time.
Your project plan organizes the work. Your operating conditions decide what the work becomes.
Change those conditions and the same initiative, the same people, and the same budget produce a different result. That is the whole of it. See the architecture underneath →
Your organization is most visible while the work is live.
You are already paying for far more than the work itself. The meetings, the approvals, the coordination, the hundred small decisions nobody logs. Most organizations write all of that off as the price of getting anything done.
But that same activity is the only time the invisible becomes observable. While the work is live, people are deciding in front of you, and the way things really run stops being a matter of opinion. No offsite, survey, or planning cycle shows you that.
Most projects spend all that money and attention and leave nothing behind but the deliverable. We use the same open window to show you how your organization actually runs, and to improve it while everyone is still paying attention.
We are not asking you to fund a transformation. We accelerate an initiative you already have planned.
What you keep after the work is done.
The initiative itself
It performs better than the plan called for, and you see the risk while you can still do something about it.
The practices stay
People know who owns what, decisions settle where they belong, and what you need to know reaches you in time to use it.
The next initiative
Your next one starts on better ground, because what you built this time is still there.
The difference should be visible in three places: in the numbers the initiative was judged on, in how the people around you work once the attention has moved elsewhere, and in how much less of you the next important thing requires.
None of this happens on its own. The gains come from what the work reveals about how your organization runs, and from a few new habits that stay in place after we leave. Without those, you have simply run a better project.
Let’s make this tangible…
What is your most important initiative standing on? Bring us that one. We provide initial working conversations at no charge. You will see what we can find, and its potential value to you, before you decide whether we belong anywhere near it.
How we make it visible, and what happens after that.
We work inside an initiative you are already running, while decisions are still being made and money is still being committed. That shows us things no assessment from the outside ever sees. What follows is what we actually do with it.
Reveal. Focus. Tune. Embed.
The SGE Companion brings what is actually shaping your initiative into view. The people closest to the work decide what it means. Together we introduce a small number of changes where they will matter, and keep what proves useful.
Make it visible
Make visible what is actually shaping your initiative: how you decide, what your systems allow, and what reaches your customer.
Separate noise from cause
Separate temporary noise from the few things most likely to decide the outcome. The Companion proposes. Your people judge.
Change it inside the work
Introduce practices inside the live work, where you can feel whether they help and change them on the spot.
Give it a durable home
Turn what worked into a normal way of working, so you keep it after this initiative ends.
The Companion widens the field. It does not decide.
It reasons from the research behind the Strategic Growth Engine, not from generic pattern matching. It connects evidence across time and function, holds it to its source, and offers more than one explanation for the same event.
Your people bring judgment and intent, so those closest to the work keep the choice of what to do next. Nothing structural changes without someone accountable deciding it should.
AI expands what we can see. People decide what matters.
Four stages, and we do not move to the next one on a calendar.
The four moves run inside every stage. What changes from one stage to the next is how much we are prepared to do with what we can see. That is the discipline that keeps an early hypothesis from turning into a reorganization.
See it together
We work alongside the initiative while it runs, gathering what the work itself shows: where decisions actually settle, where information stops, where real ownership differs from the org chart, and where people are quietly working around your systems. None of that appears in a project review. Your people see it as it is assembled, not in a report at the end.
Before we go further: the picture has to be one your own people recognize as true, not just defensible.
Understand it well enough to choose
Several explanations get put against the same evidence and tested, including what the current way of working is protecting. Then one condition is chosen — the one most likely to decide this result and small enough for the organization to actually absorb.
Before we go further: a named owner, an agreed change, and a way to tell whether it helped.
Move, and let the work test it
One practice enters the recurring moment where the condition shows up, inside work already scheduled. Bounded and reversible. We watch what moves in the initiative, what moves in the condition, and what moves that nobody intended.
Before we go further: evidence it helped under real load, not just in the room where it was designed.
Keep it, and renew it
Something structural changes so the improvement is no longer carried by attention: a role, a rhythm, a system, an agreement, or a decision right. Later, pressure tests whether it held, and the reasoning behind it gets revisited rather than inherited blindly.
What you are left with: a condition that stays changed, and an organization better able to see the next one.
This is not a maturity ladder and you do not have to start at the beginning. Work already underway often enters partway along. And stages are permeable in both directions: if a change does not survive contact with real work, it goes back rather than forward on momentum.
When a project has to give something back, you already know the three options you will be handed.
Every one of them takes something out of the work. Your people feel all three, and they know precisely what each one costs, because they are the ones who absorb it. Worse, none of the three touch whatever created the pressure in the first place. The project gets smaller, the strain stays where it was, and the same conversation comes back on the next initiative.
- 01
Reduce headcount. The work does not get smaller. It just lands on fewer people.
- 02
Lower the specification. Cost comes down now and comes back later as rework, support calls, and a shorter useful life.
- 03
Compress the timeline. People decide with less information, and the risk moves downstream where it costs you more.
There is a fourth option, and almost nobody reaches for it, because you cannot see it from inside a project plan. The delay, the rework, the decision that sat for three weeks: most of that starts in how work moves through your organization. Make that visible and you can treat it directly, which frees up value without taking anything out of the initiative.
The first three take value out of the work. The fourth finds value your work was already losing.
A modest portion of the project, not a program of its own.
There is a cost, and it is a modest portion of the project budget. What keeps it modest is that you are not paying us to create the visibility. Your initiative already does that. You are paying for what gets revealed, the lift that gives each project, and the changes we make that stay behind and compound.
What you are not buying is a second program. No separate governance, no separate timeline, no separate disruption. Doing this work on its own means a transformation program that carries all three, costs several times more, and is built from a framework rather than from what is actually happening on your front line. That is why so little of it ever takes hold.
The initiative performs better now, and you keep what made it possible.
Value shows up in three places: in this initiative, in the practices that stay afterwards, and in how much easier the next important thing turns out to be. None of it is automatic, and the difference between the three is worth understanding before you commit to any of it.
A project should not only deliver value. It should leave you better at creating value the next time.
You did not come here looking for a methodology.
You came because something specific is not working, the obvious fixes have already been tried, and it has not held. Below is where we usually get called in, and what tends to be true when we get there.
What usually gets tried: a tighter process, another checkpoint, sometimes different people. It holds while someone is actively watching it, and decays when their attention moves.
What we look at: what the old pattern was protecting. Something is rebuilding this, and until that is named, the next fix has the same half-life as the last one.
What usually gets tried: a reorganization, because it is the one lever a new leader unambiguously controls. It moves the boxes without touching what made the old shape necessary.
What we look at: which of the inherited constraints are still load-bearing and which are simply undisturbed. They look identical from the outside, and removing the wrong one is expensive.
What usually gets tried: a relaunch, with better communication and firmer sponsorship. The second attempt meets the same conditions that absorbed the first.
What we look at: whether anything structural actually moved — a role, a rhythm, a system, an agreement, or a decision right. If none of those changed, the improvement was being carried by attention, and attention always leaves.
What usually gets tried: pressing harder on adoption, or concluding the advice was wrong. It usually was not.
What we look at: whether your organization can currently receive what you are buying. Good advice still has to travel through the way decisions actually get made here, and that is rarely part of anyone's scope.
What usually gets tried: more governance and more reporting, which increases what you are told without increasing what you can see.
What we look at: what is already pulling it off course while the reporting still looks fine. Drift is visible early in how decisions move, long before it reaches a milestone.
What usually gets tried: moving fast with a capable partner, because the technology feels like the hard part.
What we look at: which part of the opportunity is genuinely yours, and whether the organization around the product can support what it would take to run it.
A company was preparing to sign away the thing that made its AI idea valuable. The agreement looked like a way to reduce development risk. Read against the whole business rather than the product alone, it would have moved nearly all long-term ownership outside the company. The software was never the scarce asset — the industry knowledge was.
It kept the intellectual property and the roadmap, and built internally instead.
Full story →What usually gets tried: better marketing, sharper positioning, a sales push. The assumption is that the strategy is not landing hard enough.
What we look at: whether the strategy is arriving intact. Flat results after real effort are rarely an effort problem.
Two years of flat sales, and leadership was certain it needed better marketing. The strategy was sound. It was changing shape on the way through the organization: leadership had committed to a modular approach while engineering was still building the older all-in-one model. Some of the resistance was never in the processes at all.
Within the year, the business was hiring delivery staff again after nearly two years of flat growth.
Full story →What usually gets tried: more detailed projections, which increase precision without increasing accuracy.
What we look at: whether the reporting matches operating reality, and what the plan assumes about an organization that may not work the way the plan believes.
Two companies were preparing to expand on financial reporting that was materially wrong. In one, billing errors were concealing recurring revenue that was never being collected. In the other, reporting overstated profitability badly enough to point ownership toward an expansion that could not have succeeded.
Both found out while there was still time to act, and before the capital was committed.
Full story →That list is a sample, not a menu.
We could not name them all, and the specific shape of yours matters less than it seems. The test is simpler than a list: is something important having to travel through the organization you already have?
If it is, it is passing through how your people decide, what information moves, who really owns what, and what the organization protects without discussing. That is true of nearly everything a company does that matters. It is certainly true of yours.
Some moments ask more of an organization than its current way of working was built to give.
Read them together and they are the same problem.
In every one, the visible problem is not the real one. The AI decision was not about software. The flat sales were not about marketing. The change program did not fail because people did not care. And in each case the usual fix was aimed squarely at the visible thing, which is why it did not hold.
What they share is that something important had to travel through the existing organization, and the conditions it travelled through shaped what it became. Those conditions are rarely written down, rarely discussed, and almost never appear in the plan.
That is what we work on. Not instead of your initiative — inside it, while it is running, where the conditions are visible and there is still time to do something about them.
The biggest gains rarely come from more effort. They come from seeing clearly before you commit the money.
See what is shaping the work before it determines the result.
Where it helps Protecting the asset
A non-technical company was preparing to sign away the thing that made its AI idea valuable.
It had a working proof of concept and a software partner ready to build. What it did not have was a clear view of which part of the opportunity was actually its own.
What the work found
The proposed agreement looked like a way to reduce development risk. Read against the whole business system rather than the product alone, it would have moved nearly all long-term ownership outside the company, leaving it with a small fraction of ownership for the platform its own knowledge made possible.
The software was never the scarce asset. The company's industry knowledge was. Beneath that, the same review surfaced conditions that would have constrained the product either way: marketing without strategic coherence, operating information fragmented across legacy systems, and sales teams using shared technology in inconsistent ways.
Leadership believed it had a product. What it had was a promising prototype that had never been tested against the real procurement processes, workflows, and cross-functional requirements it would need to support.
What changed
Leadership kept the opportunity and built internally. Attention moved from building everything to identifying the smallest set of capabilities that would create measurable value for customers, and the existing proof of concept became the foundation for an MVP rather than the finished product.
Retaining ownership only became executable because the operating conditions around the decision were addressed at the same time. The choice and the capacity to act on it arrived together.
The company still owns the asset it was about to trade away.
Rather than signing, it retained control of its intellectual property and its product strategy. The MVP approach has since been validated through proof-of-concept engagements with multiple customers in the target industry, producing real feedback before broader development began.
Decision value
Leadership reversed its commercialization approach once the long-term implications were visible.
Initiative value
The company retained ownership of the intellectual property and the product roadmap.
Enterprise value
Domain expertise stayed inside the business as a durable strategic asset rather than a licensed input.
Many organizations believe AI creates competitive advantage. More often the advantage sits in owning the knowledge that makes AI valuable. Technology can be built by almost anyone. Domain expertise, customer understanding, and operational insight cannot.
Where it helps Restoring coherence
Two years of flat sales, and the strategy leadership had chosen was never reaching customers.
Leadership believed the answer was better marketing and sharper positioning. The strategy was sound. It was changing shape on the way through the organization.
What the work found
Interviews across leadership, sales, engineering, implementation, and customer services mapped how strategy, operations, and culture were interacting. The company was not short of ideas. It was short of alignment.
Leadership had committed to a modular, land-and-expand approach. Engineering was still building and promoting the older all-in-one model. Sales, implementation, and long-term services ran as separate groups with little shared ownership of the customer outcome, which put friction at every handoff.
The organization believed it had an execution problem. It had a coherence problem. Some of the resistance was not in the processes at all. It was in leadership dynamics that had never been visible enough to discuss.
What changed
Rather than prescribing isolated process improvements, leadership redesigned the conditions execution had to travel through. Cross-functional responsibilities were realigned and operational ownership became shared rather than siloed.
The modular strategy became executable because engineering, services, and sales were finally working from the same model. The strategy did not need replacing. It needed to arrive intact.
Proof
Specific financial figures remain confidential. What is observable is that sales accelerated enough for the business to expand its services organization through ongoing hiring, after nearly two years of flat growth.
The more durable gain was capacity. The organization did not simply sell more. It became able to grow without its own operating model holding it back.
Where it helps Seeing the real economics
Two companies in different industries believed they understood their own businesses.
Both were preparing to expand. Neither could see how operations, financial reporting, and growth strategy were shaping one another.
What the work found
Conventional planning starts with projections. The work started with how strategy, operating systems, leadership behavior, financial reporting, and internal dependencies were reinforcing one another. That surfaced what the projections had inherited without question.
In one company, billing and expense allocation errors were quietly concealing recurring revenue that was never being collected, while obscuring the true economics of the business. A highly visible expansion initiative had no realistic funding path, and public commitments had already been made.
In the other, financial reporting materially overstated profitability, pointing ownership toward an expansion that could not have succeeded. The same review exposed a significant single-person dependency that would have become an execution risk under growth.
What changed
Financial models were corrected and growth expectations were rebuilt on operating reality rather than optimism. Hidden risks became visible while there was still time to act on them.
Neither engagement ended in a business plan. Each ended with a ranked view of where improvement would pay off most, before any expansion was funded.
Proof
One engagement recovered recurring revenue that had been leaking through billing and tracking issues for long enough that no one questioned it any more. The other found a profitability error large enough to change the expansion plan entirely.
Most consequentially, both organizations avoided committing significant capital on the strength of information that was incomplete.
It does the remembering, the connecting, and the checking.
Your people hold the judgment, the context, and the authority. What they have never had alongside it is something that can keep the whole organization in view at once, keep every signal attached to where it came from, and never tire of asking whether the story still fits.
A skilled facilitator could always read an organization this way, given unlimited time in unlimited rooms. What was never practical was doing it at scale, while the work was still moving. Why that matters to the reading →
Not better judgment. More stamina, and no stake in the answer.
Everyone in your organization sees their own part of it clearly and the rest through someone else's summary. That is not a failing, it is what having a job does. The Companion holds all of it at once, keeps comparing what one part says against what another does, and has no position to protect while it does so.
- 01
Connects the quantitative to the human. Delivery data on one side, what people actually say happens on the other, held against each other rather than reported separately.
- 02
Detects recurrence. Recognizes that this pattern already appeared somewhere else, months ago, in work nobody connected to this.
- 03
Surfaces contradiction. Finds where two parts of the organization describe the same event incompatibly, and leaves the disagreement standing rather than averaging it away.
- 04
Shows contrast and drift. Where experience differs by role or boundary, and where language about priorities has quietly moved away from the documents.
- 05
Flags its own thin spots. Says plainly where the evidence is sparse, stale, or drawn from too narrow a slice to carry the weight being put on it.
It reads across operational signals, cultural signals, relational patterns, the language people use to make meaning, and what previous work already established. Any one of those alone misleads. Together they can be checked against each other.
It detects. It does not conclude.
This is the most important distinction in the whole instrument, and it is easier to show than to argue.
Decision latency rose after a new governance step was introduced.
Observable. Traceable to specific records. Nobody has to agree about why yet.
The governance step caused the delay.
A claim about cause, with consequences attached. It needs context, judgment, and someone accountable for being wrong.
The gap between those two sentences is where every expensive mistake lives. Most tools close it automatically and present the result as a finding. The Companion holds it open, because the second sentence belongs to people who know what else was happening that quarter.
It hands people better questions, not final answers.
Not a dashboard, and not something anyone talks to.
What the Companion finds does not arrive as a report or a screen of scores. It arrives in the room, in conversation, as something worth looking into together. The facilitator does not read its output aloud. They turn a structural signal into an opening.
So in practice it sounds less like a system announcing a finding, and more like someone asking a question the group can actually work with.
“Several teams are describing decision-making delays differently. What might be contributing to that?”
Nobody is told what is wrong with them. The organization gets to see its own contradiction and say the thing out loud, which is the only version of it that ever changes anything.
Every reading can be followed back and rejected at the source.
Every insight names the evidence beneath it and how confident that reading is. Anyone in the room can trace a conclusion back to the observations that produced it, and stop it there. That is an accuracy mechanism before it is a transparency feature: a signal detached from its origin cannot be argued with, and anything that cannot be argued with tends to be wrong eventually.
Contrary evidence is kept rather than dropped. A reading that only ever found support for itself would not be worth having.
Sometimes it tells us to slow down.
The Companion watches the load the work is putting on the organization, not just the work itself. When participation drops, when tone turns brittle, when people start describing things in increasingly incompatible ways, that is a signal the system is taking on more than it can absorb. The cadence slows.
When curiosity rises and contradictions start resolving on their own, it signals the opposite, and the pace can pick up.
An instrument that only ever finds more for you to do is not measuring you. It is selling to you.
This matters more than it sounds. Most of what fails in this kind of work does not fail because the analysis was wrong. It fails because the organization was asked to absorb more change than it had capacity for, and quietly stopped.
It thinks from one body of research, not from everything ever written.
General purpose models answer from everything they have read. The Companion works from one body of research: the Strategic Growth Engine itself, and the science underneath it. So what it tells you is about your company, not a plausible-sounding average of every company.
That limit is deliberate, and it is what makes it useful. You do not get a confident opinion assembled from somewhere else. You get a reading of what is shaping this initiative, in this organization, traceable to what it was drawn from.
It was also built to widen options rather than close them. It would have been easier to make something that hands down answers, and we did not, because when the answer arrives finished the people who have to live with it never get to think it through. Seeing more should give your people more room to act, not transfer authority to whoever is running the software.
AI expands what we can see. People decide what matters.
The initiatives that matter most never stay inside one department.
Foundatia brings strategy, operations, technology, and how people actually work together into one approach, and applies only the parts your initiative needs.
Underneath the Strategic Growth Engine sits a deep architecture of diagnostics, metrics, and practices. It works alongside whatever you already run, whether that is project, product, Agile, Lean, or a consulting relationship. You are not asked to throw away anything that already works.
The point is not to make you dependent on us. It is to help you see more clearly, act more deliberately, and keep more capability from work you are already doing.
The conversation over coffee that takes an unexpected turn. The entrepreneur with an idea that’s still half-formed. The leader trying to navigate uncertainty. The person who asks a question I’ve never considered before. Those are the moments I remember years later — not because they gave me answers, but because they helped me see something differently.
Jim Gehring
Change the conditions your strategy now depends on.
Your organization works the way it does for good reasons. Leaders step in because speed matters. Teams build workarounds because customers cannot wait. People lean on relationships to get things across boundaries. Every one of those was a sensible answer to a real problem. A new strategy is simply asking for something different.
The Strategic Growth Engine shows you how those conditions are shaping your initiative right now: what still helps, what is under new pressure, and what needs to change. The people closest to the work read it with us and shape the response.
The goal is never to fix your people. It is to give them a clear view of what they have been working inside, and more room to change it.
A small team of certified facilitators who work where the decisions actually get made, and a door into a wider network.
Jim Gehring
Founder & PrincipalJim has spent a career in enterprise technology, infrastructure, and large-scale change, and came away with a conviction that shapes everything Foundatia does: most strategies don't fail because they're wrong. They fail because the organization can't feel them. He is the architect of the Strategic Growth Engine, and he works the way he always has: in the room, with the people doing the work, asking the question nobody has asked yet. He is as interested in what the person closest to the work sees as in what the executive team has decided. Based in Cleveland, Ohio.
Beth Schreibman Gehring
Communications & Brand StrategyBeth leads communications and brand strategy for Foundatia, and has spent three years shaping how the work is understood. She turns complex thinking into language that leaders and their teams recognize, the kind that earns trust instead of attention.
Mike Jebber
Principal · Human systemsMike has spent more than twenty-five years helping organizations improve how people and work fit together, across leadership coaching, lean and agile practice, and human-centered change, from startups to Fortune 500s. He starts where the work actually happens: with the people closest to it, the conditions they navigate, and the trust that lets them raise what matters early. That focus is central to how Foundatia turns what it sees into judgment you can act on. Based in Greater Cleveland.
Built where the work is real.
Foundatia is built in Cleveland, a city that has never had much use for polish. Reputations here are earned the slow way, by being what you say you are.
It has also quietly become one of the fastest-growing technology markets in the country, with a particular strength in putting AI to work inside real industries like healthcare and manufacturing. That is the same conviction the SGE is built on: technology creates value only when it lands well in the conditions of an actual organization. Watching that community grow, and having a hand in it, has been one of the real pleasures of the work.
Jim understands each person’s intricacies and differences. He’s one of the most genuine human beings I’ve ever met, someone who listens intently, values others and their unique opinions, and approaches every interaction with kindness, thoughtfulness, and openness. He doesn’t just provide guidance; he encourages you to tread water in the deep end with tough questions, and doesn’t hesitate to dive into those feelings with you fearlessly.
Matt Orloff
You’re a fixer. It’s deeply hardwired into who you are. As a result, in situations where you could just replace a washer, you will always look at everything around that washer and ask yourself one question: can I make this better? It’s more than what you do. It’s who you are. Fighting that will only bring you more stress. Not being that would be harder on you than making you not breathe. Starting Foundatia wasn’t about ego or bragging rights. It was about being who you are. You look at whatever sits in front of you, and ways to make it better arise through you.
David Keith Higgs
His ability to bring teams together to jointly develop deep, long-term technology strategy is why I recommend Jim to anyone navigating real complexity.
Doug Theis
Jim and his Foundatia team exceeded expectations with solid, professional execution. A partner I'd be privileged to work with again.
Daniel DeSantis
Bring us the initiative you are most worried about.
What is your strategy landing on?
We don't charge for the initial working conversation. You should be able to see where the Strategic Growth Engine could create value before deciding whether it belongs in the work. The first conversation should create useful insight, even if it is the only one we have.
Beyond that, the work attaches to an initiative you are already running and is priced as a modest portion of it. We will be specific about that early, not late.
Tell us about the initiative.
Together, we'll explore what the strategy is asking of the organization, begin surfacing the operating conditions most likely to shape it, and share what we see.
Reach Foundatia directly.
See what is shaping the work before it determines the result.
The architecture beneath the work.
An important initiative does two things at once. It creates value, and it reveals the operating conditions deciding how much value your organization can create and keep. The Strategic Growth Engine is built on that second job.
Important work reveals the system carrying it.
You do not start from zero. The work can enter at any point: a metric you already track, a complaint that keeps recurring, an audit finding, an experiment that failed, or a decision leadership has already made.
Three things you get, before you learn anything about the architecture.
See more clearly.
How decisions, information, ownership, meaning, and risk actually move while the work is under way, rather than how the process diagram says they move.
Make better choices.
Separate a bad week from the few conditions most likely to decide the result. Seeing more is not the same as doing more. It should mean choosing better.
Keep more of what the work creates.
Let the initiative leave behind more than its deliverable: a clearer way of deciding, a rhythm that holds, capability that is still there next time.
Each of these comes from the whole system rather than from one part of it, which is why none of them maps neatly onto a single move or a single condition.
Reveal · Focus · Tune · Embed
Four moves, run inside work that is already happening. The Companion widens what can be seen. The people closest to the work decide what it means, choose what to change, and judge whether it helped.
Make conditions visible
Show what is actually happening beneath the performance numbers, in language the people in the work recognize.
Separate noise from cause
Separate a bad week from a condition that will decide the outcome.
Change it through the work
The group puts one practice into the moment where the condition recurs, then watches what moves, including what moves that nobody intended.
Give it a durable home
Something structural changes: a role, a rhythm, a system, an agreement, or a decision right. If none of those five has moved, the improvement is still being carried by attention rather than by the organization.
Running a workshop, a scan, or a sprint proves only that it happened. The condition has changed when the new way of working survives without anyone protecting it. That is why the test happens after the attention leaves, not while it is still there.
Five connected operating systems shape what strategy becomes in practice.
Not five stages, five scores, or five pillars. They are five relationships running at the same time through the same work, and each one changes what the others can do. Which is why a condition is almost never fixed where it is felt.
Circulation, how truth, decisions, work, and value move. Coherence, how strategic meaning holds together as it travels. Momentum, how effort stays connected to value. Direction, how attention becomes grounded commitment. Adaptation, how learning becomes durable without becoming rigid.
Project plans organize the work. Operating conditions shape what the work becomes.
AI expands what we can see. People decide what matters.
This is a rule about authority, not a reassurance about tone. The Companion is built to widen the field of evidence and to stop there. Interpretation, choice, and consequence stay with people, and stay visible.
Connects evidence, holds it to its source, surfaces recurrence and contradiction, and offers more than one explanation for the same event.
Facilitator
Holds the frame, the pacing, and the context, and keeps interpretation away from blame and overreach.
People in the work
Supply the lived reality no dataset contains, and reject a reading that does not match what they actually experience.
Leadership and owners
Hold the intent every reading is measured against, and the authority to change roles, resources, and governance.
The intent is that more visibility gives people more room to act, not less.
Value now, capability kept, and a stronger place to start.
The initiative performs better, because conditions obstructing it have been revealed and tuned.
The improved condition and the practice sustaining it continue in normal work, after the project closes.
Future work begins through a fabric with less inherited friction, and an organization better able to perceive itself.
These are three different things, and they are not a funnel. Direct value does not become retained capability on its own, and retained capability only compounds while the reasoning behind it stays visible and gets revisited.
Part of the return is capacity you are already spending. Compensating for a condition nobody has named consumes leadership time, coordination, decision capacity, and rework effort every day. When the fabric carries more of its own load, some of that comes back.
An initiative that matters becomes the clearest view you will ever get of how your organization actually runs.
Five connected operating systems are read against what this initiative is actually trying to achieve, and several scientific traditions are used to challenge that reading before anyone acts on it. The people inside the system then change those conditions through the work itself. The initiative performs better, capacity that was going into compensation comes back, and the organization is more able to create and renew value after the work ends.
Direct
Better performance now.
Retained
More capability kept.
Compounding
Stronger conditions for what comes next.
Compound return is not automatic. It depends on the conditions the initiative reveals and the practices introduced to treat them.
Go as deep as the question you arrived with.
Nothing below is required to understand what Foundatia does. It is here because a serious reader should be able to check that there is a real architecture underneath the language, and stop wherever the answer is good enough.
A walk through one initiative.
This is a walkthrough rather than a map of the whole system. The five operating systems above are not a stage in it; they run through every part of it.
Swipe the diagram sideways
Nothing here runs on autopilot. Each stage hands its reading to the next, and the next one can throw it out. No conclusion reaches a decision without someone able to stop it.
The Architecture What the SGE acts on
The fabric strategy has to travel through.
Between what an organization intends and the value it produces lies a layer of operating conditions: how decisions move, where information stops, who really owns what, and what people protect under pressure. We call that layer the fabric. It is what the SGE reads and tunes.
A live initiative places the organization under real load, and the fabric becomes observable.
Swipe the diagram sideways
Every initiative begins inside a larger direction.
The SGE does not judge the organization against a generic definition of health. It reads the organization against what its leadership has said it is trying to achieve, what this initiative is meant to accomplish, and what value has to be created.
Mission, vision, values, strategy, and charter are not decorative statements around the work. They are the yardstick every reading is measured against. Without them a condition can only be called unusual; with them it can be called helpful or costly, which is what makes the architecture economic rather than merely descriptive.
- Organizational intentVision · mission · values · goals
- shapes — Initiative intentCharter · outcomes · constraints · value
The question is never whether the fabric is ideal. It is whether the present fabric can effectively carry the organization's current intent.
The same condition can be an asset or a liability depending on what you are asking the organization to do. Tight decision control protects quality when the work is well understood and the cost of an error is high. Point that same control at an initiative that needs fast local judgment and it becomes the reason nothing moves. Strong cohesion coordinates a team quickly, and quietly discourages the dissent that discovery work depends on. Nothing here was built badly. It was built for what the organization was doing before.
The live initiative reveals the real operating system.
Strategy has to become decisions, dependencies, commitments, handoffs, investments, tradeoffs, and customer consequences. Under that load the actual fabric becomes observable, and it shows what an ordinary assessment cannot reach.
How decisions actually move.
Where information stops.
Where formal and practical ownership differ.
Where trust changes behavior.
Where meaning fragments.
Where learning disappears.
Where people quietly absorb the cost of something no one has named.
The initiative is both the work being improved and the instrument doing the measuring. That is why which initiative you choose matters: it needs enough weight to put the organization under real load, and enough reach to cross the boundaries where conditions actually show themselves.
Why the work itself is the instrument.
Conditions make certain behavior more likely. That behavior, repeated, both reveals the condition and reinforces it.
Which is why the useful question is never why won't people behave differently. It is: what makes this behavior sensible here, or protective, or simply the easiest thing to do?
That steady pull on anything new is what we call organizational gravity. It is why sound strategy so often arrives as familiar results.
The Architecture What the SGE reads
Operational data shows what. The SGE reads why.
This is the stage everything else depends on. Change is only as good as the reading underneath it, and most organizations are working from the first explanation that sounded coherent in a room where the most senior person spoke first.
Conditions revealed beneath the visible work, read against what this initiative is trying to achieve.
Swipe the diagram sideways
Reading a live organization at this depth used to be impractical.
Not impossible. A skilled facilitator could always do it, given enough time in enough rooms. What made it impractical was scale: the evidence sits across decision records, delivery data, meeting rhythms, escalation paths, and what people say happens when the process is not looking, and no one could hold all of it in view at once while the work was still moving.
So the reading was usually sampled, done from a distance, and delivered after the moment it could have changed anything.
The Companion is what closes that gap. It is the reason the reading can be this thorough, this fast, and still be happening inside work that is under way.
Detection is its job. Inference is not.
It can establish that decision latency rose after a new governance step was introduced. It cannot tell you the governance step caused the delay. The first is observable and traceable. The second is a claim about cause, with consequences attached, and it belongs to people who know what else was happening that quarter.
So the instrument widens the field and stops. Everything after that point is the work of people who live inside the conditions being described. How the Companion works →
- EvidenceOperational data, human experience, and what earlier work already established
- ConnectionSignals related across time, function, and initiative, each traceable back to its source
- Competing explanationsSeveral plausible readings of the same event, rather than the most comfortable one
- InterpretationWhich reading survives, decided by the people in the work
AI expands what we can see. People decide what matters. On this page that is not a reassurance, it is the division of labour: the instrument is what makes a rigorous reading affordable, and the judgment is what makes it true.
Five relationships, not five departments.
Every initiative moves through the way your organization already decides, carries information, interprets priorities, commits, and learns. Each of these is a question about how the organization behaves under real load. None belongs to a function, and none is owned by anyone in particular, which is part of why they go unexamined.
They are read against what this initiative is actually trying to achieve, rather than against a generic idea of organizational health. See how intent sets the yardstick →
No condition operates alone.
All five run at the same time, through the same work, and each one changes what the others can do. Take one system on its own and it will describe a symptom well and explain almost nothing. Select a strand to see what it asks of the organization, and what it looks like in live work.
A problem is rarely caused where it is felt.
What tends to decide an outcome is the combination: one system doing its job well while another cannot carry what it produces. Which is also why the obvious fix, applied where the pain is, so often moves the problem somewhere else instead of resolving it.
None of these is a verdict. Each is a hypothesis, traceable back to the evidence that produced it, and put in front of the people living the work so they can confirm it or throw it out.
There is no shape the five are supposed to make.
The question is never whether the fabric is ideal. It is whether the present fabric can carry the organization's current intent.
Naming the system is not the same as explaining it.
Placing an event inside circulation tells you which relationship is under strain. It does not tell you why. A handoff that waits could be a queue, a degraded signal, a considered decision not to speak, or a protective response to an earlier failure that nobody has re-examined.
So the reading does not stop there. Several scientific traditions are used to generate competing explanations for the same event, and then to try to knock them down.
One delayed handoff. Seven readings.
The claim is not that the SGE just uses science. It is that seven established disciplines each read the same signal and propose a different cause, and the disagreement between them is the useful part. A single signal is ambiguous by nature. It is groups of signals, read across lenses, that show which condition is actually at work. Each lens below names the body of work it draws on.
The point is not to pick the right lens. It is to see which reading survives when six others are applied to the same event.
The reading is built to be argued with.
Convergence raises confidence; it does not prove cause. An explanation several lenses support can still be wrong, so the work is not finished when a plausible reading appears. It is finished when the reading that survives is one the evidence supports and the people in the work recognize.
- GenerateEvery plausible reading of the event, rather than the first coherent one
- ConvergeWhich of them the available evidence actually supports
- ChallengeWhat would have to be true for each one to be wrong
- FalsifyWhich fail against contrary evidence, including evidence nobody went looking for
- ContextualizeWhich surviving reading fits this organization, judged by the people living inside it
A single metric rarely explains an organization.
One signal shows movement. Two signals that should not co-occur point to a condition. Composite reading is simply this: holding several signals against each other and asking what would have to be true for all of them at once.
A pair shows whether two signals reinforce or contradict each other. A third signal constrains the explanations that can account for both, which is what narrows a reading from plausible to probable. Beyond that, the composite starts describing the fabric rather than any single condition in it.
None of these is a verdict. Each is a hypothesis, traceable back to the evidence that produced it, and made visible so it can be worked on. The value is in the reading the organization could not produce about itself.
Convergence across lenses raises confidence; it does not prove cause. And a reading the people in the work do not recognize is treated as wrong until the evidence says otherwise.
From an invisible influence to its effect on the value you set out to create.
This does not merely show that performance is off target. It shows why capable people, working sensibly inside the current conditions, keep producing the same result. That framing protects dignity, and it also makes the intervention more precise, because you are changing a condition rather than correcting a person.
- Invisible influencesThe systemic conditions in effect
- Operating conditionNamed, situated, and traceable to evidence
- Observable behavior and work patternWhat people repeatedly do inside that condition
- Effect on strategic valueHow the configuration helps, constrains, distorts, delays, redirects, erodes, or protects the value named in the charter
The Architecture Who sees, interprets, and decides
No single participant holds the whole field.
This is not a human process with AI added, nor AI analysis moderated by a human. Four parties see different things, and none of them can see the whole.
The Companion widens what can be seen. Facilitation and lived experience turn that into something the organization can act on.
Swipe the diagram sideways
The division of labor is part of how the system produces accuracy.
This is not an ethical note added after the fact, it is where the accuracy comes from. The Companion connects more signals than any person could hold at once. The facilitator keeps interpretation away from blame, oversimplification, and overreach. The people living the work supply the context no dataset contains. Remove any one of them and the reading degrades in a predictable direction.
- The CompanionWidens perception
- The facilitatorMakes interpretation possible
- ParticipantsGround meaning in lived reality
- Leadership and sponsorsConnect meaning to intent and authorized change
- The organizationRetains judgment and ownership
Built to widen options, not to issue conclusions.
The Companion reasons from the research and structure behind the Strategic Growth Engine rather than from generic pattern matching. It widens what can be seen, then stops there by design.
Retrieve and connect relevant evidence. Identify recurrence, contrast, drift, or contradiction. Correlate quantitative and qualitative signals. Keep every hypothesis traceable back to the evidence that produced it. Show alternative explanations. Identify where evidence is thin. Express uncertainty. Generate questions that widen examination.
Declare a systemic condition as fact without human interpretation. Issue a verdict about a person or team. Choose the leverage point. Prescribe a practice. Decide whether to retain or expand an experiment. Move authority away from the people who generated and live the evidence.
Every insight names the data pattern beneath it and how confident that reading is. Anyone in the room can follow a conclusion back to the observations that produced it, and reject it there.
What only people can contribute.
Human participation is not only the right thing to do, it is the only way the reading can be correct. A condition shows itself in how people are already working, and only the people doing that work can confirm whether the pattern we are seeing is the one they actually live. Leadership sets the intent that condition is measured against. The people in the work hold the evidence. Neither can be replaced by more data.
The Architecture How insight becomes change
The SGE does not stop at diagnosis.
Insight without a change in the work produces clarity, not capacity. The architecture is built to find where a condition can actually be altered, and to alter it inside live work.
The facilitator and the people in that meeting choose one practice and run it at the next occurrence, in real conditions, where everyone can see what it does.
Swipe the diagram sideways
Groups of signals show you which moments actually matter.
Culture is too broad to change directly. What can be changed is the moment a condition is actually enacted, and those moments are specific.
Each one is a specific kind of interface. A decision, where the scope is quietly set before anyone votes. An escalation, where risk information is softened by whoever has to carry it upward. A rhythm, where the gap between priority reviews decides how long a stale priority keeps consuming people. A translation, where customer value becomes local requirements and some of it does not survive the trip.
Change what happens at those interfaces and the culture follows. Address the culture directly and the interfaces stay exactly as they were.
Before choosing one, though, there is a question worth asking: what is the present pattern doing for the organization? A confirmation step that slows every decision is also preventing a class of error someone has met before. Change the moment without accounting for what it was protecting, and the organization will quietly rebuild it somewhere else.
- Current conditionNamed, situated, and traceable to the evidence that produced it
- What the pattern protectsThe value the present way of working is delivering, which is why it persists
- Recurring work interfaceDecision · handoff · rhythm · review · escalation · translation
- LeverageThe one moment the group chooses to change
- PracticeRun at the next occurrence, inside work already scheduled
- EvidenceWhat moved in the work, what moved in the condition, and what moved that nobody intended
Two of the four moves are the part that changes anything.
Reveal and Focus produce a reading. On their own they produce clarity, not capacity. The intervention is not a separate event either: the group agrees on one practice, runs it inside work already scheduled, watches what changes, and adjusts it the following cycle. See all four moves →
Change it through the work
One practice, in the one moment where the condition recurs. Bounded, reversible, and watched for what moves in the initiative, what moves in the condition, and what moves that nobody intended.
Give it a durable home
Something structural changes: a role, a rhythm, a system, an agreement, or a decision right. If none of those five has moved, the improvement is still being carried by attention rather than by the organization.
Running a workshop, a scan, or a sprint proves only that it happened. The condition has changed when the new way of working survives without anyone protecting it. That is why the test happens after the attention leaves, not while it is still there.
Change is only real when the system can carry it under pressure.
A practice may work while the facilitator is present, the workload is manageable, leadership attention is high, or the initiative remains politically protected. The deeper test is whether it still works when pressure increases, attention shifts, leadership changes, priorities compete, or the next initiative begins.
- Question
- Experiment
- Learn
- Embed
- Stress-test
- Retain · Renew · ReleaseThe governing question is whether learning changes the system, remains true, and holds under pressure
The Architecture What the organization keeps Reclaimed capacity
The capacity is already being spent.
The SGE is not only reducing delay or improving coordination. It returns capacity your organization is already spending, every day, on conditions no one has put a name to.
Capacity already spent working around invisible conditions returns to the initiative as usable energy.
Swipe the diagram sideways
Performance loss is what shows up in the numbers. Energy loss is what the organization spends every day to produce it.
The conventional response to pressure is to subtract: headcount, specification, or time. The SGE recovers value the initiative is already losing to delay, rework, and stalled decisions.
The difference matters commercially. Cutting scope buys relief once, and costs you part of the thing you set out to build. Recovering trapped capacity returns it to this initiative now, and the condition that was consuming it stops charging the same toll on everything that comes after.
Where the energy goes.
It does not leave in one place, and it never appears as a line item. It goes in small amounts, many times a day, as people do this:
Route around unclear authority.
Repeat decisions already made.
Recreate context that was never carried forward.
Protect themselves from unsafe escalation.
Reconcile conflicting priorities privately.
Translate strategy differently across functions.
Maintain shadow systems.
Repair avoidable rework.
This is not simply morale. It falls into three kinds. Capacity to think: attention, cognitive bandwidth, decision capacity, discretionary judgment. Capacity to act together: trust, coordination effort, time. Capacity to improve: learning, and the ability to act while information still matters.
Visible expenditure, invisible cause.
The SGE finds energy loss by connecting what is visible (time, rework, delay, workload, escalation, turnover) with the condition producing it (trust, coherence, authority, rhythm, confidence, resilience, purpose). Composite reading matters here, because the same visible cost can come from conditions that have nothing to do with each other. Ten hours of rework is not evidence of anything until you know which condition produced it.
You see it when the compensation stops: a decision reaches the correct evidence and authority in one cycle, a frontline signal travels without defensive translation, a risk can be raised while it can still alter the outcome. That capacity comes back in all three forms.
- Hidden condition
- Compensating behavior
- Energy consumed without equivalent value
- Condition revealed and tuned
- Usable capacity returns to the initiative
- Improved value and retained capability
Released energy does not automatically become value. It has to be directed, through clearer priorities, commitments people can actually meet, better rhythms, and governance that keeps learning attached to intent. Capacity that is freed and left undirected is simply absorbed by whatever was already competing for it. Some of it returns before any intervention at all: clearer perception on its own reduces confusion, personal blame, and unproductive argument about what is actually happening.
Reclaimed capacity is a mechanism, not a separate kind of return.
Capacity that stops being spent on compensation lands in two places. Some of it arrives inside this initiative, as time, attention, and decision capacity available now. The rest arrives later, as compensation the organization no longer has to repeat on the next piece of work.
So it is not a third category of value, and it is not counted twice. It is one of the clearest ways a changed condition becomes visible in ordinary work, which is also what makes it worth measuring.
The Architecture What the organization keeps
The work is not complete when the initiative improves.
An improvement that depends on attention, goodwill, or the presence of a facilitator has not yet changed anything structural. It needs a durable home.
Retention means one of five things has actually changed: a role, a rhythm, a system, an agreement, or a decision right.
Swipe the diagram sideways
How a change gains a durable home.
Until one of those five moves, the practice stays episodic and dies with the project. Embedding is what converts a good quarter into retained capability.
The test is whether the new condition holds when pressure returns, when leadership attention shifts, when the facilitator leaves, and when the next initiative begins.
- Practice
- Reflection
- Governance
- Role · rhythm · system · agreement · decision right
- Changed organizational fabricA stronger way of operating
Seven layers of retained value.
Not all of these appear in every engagement, and they do not appear at the same depth. They are the layers at which value can be retained.
Direct, retained, and compounding value from one initiative.
The initiative performs better, because the conditions obstructing it have been revealed and tuned.
The improved condition and the practice sustaining it have entered the operating system rather than the project plan.
The next initiative runs through a fabric with less friction, and an organization better able to perceive itself.
These are three different returns rather than three stages of one. Direct value does not become retained capability on its own, and retained capability only compounds while it keeps being useful. Each horizon has its own failure mode: a better result that leaves nothing behind, a practice that survives without anyone remembering why, and a starting point that was stronger two years ago than it is now.
The organization keeps the improved practice, and it keeps something larger as well: the ability to notice when its own conditions have stopped serving its intent, and to change them on purpose rather than by crisis.
Everything you retain can eventually become the thing in the way.
Organizational gravity is not a failure of character. It is almost always retained learning that outlived the situation it was built for: a rule that once prevented a real loss, a confirmation step that once caught a real error, still running long after the conditions changed and long after anyone can say why it is there.
Which is why embedding is not the last move. A retained change carries its reasoning with it: what it was for, what evidence supported it, and what would mean it no longer fits. Revisited, it renews and keeps compounding. Left alone, it hardens into the inherited pattern the next initiative will have to work around.
The SGE works with the gravity an organization already has. The obligation is to avoid manufacturing more of it.
The Architecture The technical architecture
Underneath the four moves.
Most people never need this page, and nothing here changes what an organization experiences. It exists so that a sceptical architect, sponsor, or transformation lead can check that there is a real mechanism under the language, and see where the human decisions sit inside it.
This layer runs beneath all six stages rather than at any one of them.
Swipe the diagram sideways
Conditions make patterns. Patterns make outcomes. Outcomes become capacity.
Conditions
How decisions, information, authority, rhythm, meaning, and learning currently work.
Patterns
What those conditions make sensible, repeated until it looks like character.
Outcomes
What the work produces: speed, quality, risk carried, value that reaches the customer.
Capacity
What the organization is then able to do, which becomes the condition the next initiative meets.
It is read in both directions. An outcome you can already see leads back to a pattern producing it, and to the condition making that pattern the sensible thing to do. The SGE works backward from the result to understand what is shaping it, and forward from the condition to change what the system can produce.
The long horizon closes the loop.
Capacity is not the end of the chain. What an organization keeps becomes part of the conditions the next initiative runs through, which is the whole basis of compounding return, and also the reason compounding cannot be promised.
- CapacityWhat the organization can now do
- Retained learningThe part that survives contact with normal work
- Future conditionsThe fabric the next initiative has to travel through
What the engine is willing to do changes as the evidence changes.
Visibility comes before consequence. A reading has to be strong enough, and the organization ready enough, before anything is altered on the strength of it. That is governed explicitly rather than left to enthusiasm, which is what keeps an early hypothesis from turning into a reorganization.
The engine can move back as easily as forward. Evidence that fails, or a change that does not survive real pressure, returns the work to an earlier state rather than being carried through on momentum.
The engine configures only what the work requires.
There is no standard package. The metrics, practices, tools, experiments, and rhythms used on an engagement are selected for this context: this intent, this initiative, this condition, this level of readiness. Most of what the architecture contains is never activated, which is deliberate.
Internally the selection layer is called the Foundry. It is a registry and an orchestration layer rather than a production line: it does not manufacture change, it decides what should be brought to this particular piece of work, and records why.
- Context of useIntent · initiative · condition · readiness
- SelectionWhich metrics, practices, tools, and rhythms this context calls for
- ConfirmationThe facilitator and the people in the work decide what is actually appropriate here
- A configuration this organization can carry
Every reading keeps its receipts.
A hypothesis is only usable if it can be walked back. Each one names the observations that produced it, how strong that evidence is, what would weaken it, and who confirmed or rejected it. Anyone in the room can follow a conclusion back to its source and stop it there.
Underneath sits a sensing and integration layer, a governed record of what the organization has learned, and the relationships between them, so recurrence across initiatives can be recognized rather than rediscovered. Those are implementation names. Nothing about the method depends on knowing them.
A cross-functional decision that takes eleven days.
The same delayed handoff used elsewhere on this site, followed the whole way through the architecture. Four points in it are human decisions, and the sequence cannot continue past any of them without one.
- A visible delayCross-functional decisions take eleven days. Local authority exists on paper.
- EvidenceDecision records, meeting rhythm, escalation paths, and what people say happens before a decision is considered safe
- A current-condition hypothesisAuthority is delegated; the criteria and confidence needed to use it are not
- InterpretationThe people in the work confirm the pattern, correct it, or reject it outright
- What the pattern protectsSenior confirmation prevents a class of expensive error the organization has met before
- The leverage pointThe group chooses one recurring moment where the condition is actually enacted
- A practiceDecision criteria and risk tolerance travel with the delegated authority
- A live testRun at the next occurrence, inside work already scheduled, bounded and reversible
- Evidence againWhat moved in the initiative, what moved in the condition, and what moved that nobody intended
- GovernanceLeadership authorizes the escalation threshold as a normal decision right
- A structural homeThe change enters a role, rhythm, system, agreement, or decision right
- PressureThe next deadline, the next leadership change, the next competing priority
- RenewalThe reasoning is revisited against current context, and kept, changed, or released
- Stronger future conditionsThe next initiative meets a fabric where this decision no longer has to travel
The Companion is present at every step of this and controls none of it. It widens what can be seen and keeps the trail intact. The sequence advances only where a person decides it should.
None of this replaces the four moves. Reveal, Focus, Tune, and Embed are what an organization experiences. Everything on this page exists to make those four defensible.