The framework
The whole architecture, free, in one page. Eight phases, four structural tensions, and the diagnostic move that connects them.
Consulting
The problem is not your people.
The problem is not your people.
It is your architecture.
You have capable people. You have invested in them. You have run the culture initiative, funded the leadership training, brought in the coach, and held the offsite — and the same drag is still there, in the same places, doing the same thing to the same quarters.
That is not a failure of effort and it is not a failure of the people you hired. It is what happens when a system’s architecture and its intentions have come apart, and every repair has been aimed at the part you can see rather than the part that is producing it.
Why the conventional fixes did not hold
You have been told what is causing the headache. Nobody has asked why you keep getting them.
The engagements you have already run were not wrong about what they addressed. Communication training does improve communication. A culture initiative does raise the temperature. Coaching does help the person being coached.
They did not hold because every one of them went to work downstream of what was producing the problem.
Your organization is not learning from what you announce. It is learning from what your behavior consistently makes true — what gets escalated and what gets buried, whose judgment gets overridden and whose does not, what happened the last time somebody brought a problem early. That layer is upstream of every initiative you have funded, and it has been quietly overwriting them.
Nothing installed at the wrong layer survives contact with the layer beneath it.
Whether this is your problem
Five things are usually true by the time an organization calls.
One The drag is structural rather than episodic. It returns after every fix, in the same places, and you can predict roughly when.
Two You have already spent real money on it. More than once. With competent providers who did competent work.
Three The people are not the problem, and you know it — you have replaced some of them and watched the pattern reassert itself around the replacements.
Four The problem is easier to feel than to name. You can describe what it costs you and not what it is, which is why the last three engagements addressed something adjacent to it.
Five You are willing to be examined. Not your team — you. The signal source is a person, and an engagement that cannot look there cannot do anything durable.
If four of those five are true, this is the work. If the fifth is not, it is not — and you should know that before either of us spends a call on it.
What happens in an engagement
Six phases. You end up owning the architecture, not renting a consultant.
One Desired Signal Identification — before anything is diagnosed, we establish what the organization is meant to be teaching. Not the values statement. The operating intention: what behavior should be more likely at the end of this than at the beginning, and who has to believe it.
Two Reinforcement Audit — what the organization is currently learning, from observation rather than from self-report. What gets escalated, what gets absorbed quietly, whose exceptions become precedent, and what happened the last several times someone raised something inconvenient.
Three Delta Identification — the gap between the two. This is usually the phase where the problem the organization brought turns out to be downstream of something nobody named, and it is the phase clients tell me about afterward.
Four Distortion Source Diagnosis — where the delta originates. Not where it is felt. The diagnostic descent runs backward through the lifecycle until the fracture stops moving, because the phase that hurts is almost never the phase that broke.
Five Framework Design — the reinforcement architecture that closes the delta. What gets measured, what gets escalated, what carries consequence, and which decisions leave the center. Designed against your authority lines and your people, not against a template.
Six Codified Signal Delivery — written down, handed over, and taught to the people who have to run it. This phase exists so the architecture survives me leaving.
You do not get recommendations. You get architecture. Then you own it.
Shape. Engagements run in months rather than weeks, sized to the organization and the depth of the distortion. Phases one through four are observation and diagnosis and cannot be compressed without producing a confident answer to the wrong question. Phases five and six are design and handover.
What happens when it ends
The engagement ends. The architecture does not maintain itself.
An architecture is not a permanent installation. It is a structure operating inside a system that keeps moving — new people, new pressure, new leaders with their own signal. Left alone, any reinforcement design drifts, and the drift is gradual enough that nobody notices until the old pattern is back.
So the question at the end of an engagement is not whether it worked. It is what maintains it.
That is what the seminars are for. Many clients attend on an ongoing basis after an engagement closes, not as a refresher but as the maintenance layer — the leader keeps developing the diagnostic capability, and the architecture keeps getting read by someone who can read it.
Where this practice is
You will not find a client list on this page. Here is what you get instead.
Leadership by Design is a young practice built on a framework that is not. The framework was thirty years in the making; the consulting practice around it is deliberately early, and I am not going to dress that up.
What that means for you is concrete, and it is worth more than a logo wall.
Undivided access to the Architect. Not a methodology delivered by an associate who trained on it. The person who built the framework does the diagnostic work, and there is no fiftieth engagement dividing the attention.
An engagement that is not a template yet. The methodology is fixed. Its application to your organization is designed rather than adapted, because there is no library of prior deployments pulling it toward an average.
A practice with something to prove. I would rather you understood that than pretended otherwise.
That access has a limited duration. It ends the way it ends for every practice that works — by getting busier.
The first conversation
The calendar opens on the next screen. Questions before then: hello@martratliff.com.
Sixty minutes.
This is not a sales call and I am not going to treat it as one. It is the first sixty minutes of diagnostic work, and the honest outcomes of it include some that do not involve hiring me.
Sometimes the answer is an engagement. Sometimes it is a seminar, because the leader can do this work themselves once they can see it. Sometimes it is a keynote, because the organization is not ready and the room needs to arrive at the question first. And sometimes it is not yet — the drag is real and the organization is in the middle of something that has to finish before this can start.
Before the call, tell me two things: the pattern that keeps returning, and what you have already tried. The more accurately you can describe the drag, the more useful this hour will be — and I read what you write before we speak, so the call starts further along than it otherwise would.
If you are not there yet
Three other ways in.
Not every organization needs an engagement, and some that do are not ready to start one.
The Birds and Bees of Leadership
Where the governing law of Signal is established. Everything in the engagement rests on it.
The Architect
Three decades, and how the framework was built from inside the problems it addresses.