The Solid Manager: The Two Foundational Pillars Twenty Years of Trends Have Buried

The verdict: the management line, a critical asset left unmonitored

A scale-up of fifty to one hundred people runs three critical assets: the product, the cash, and the management line. The first two are monitored daily. The third rarely is. It gets treated through occasional training, coaching, offsites. It isn't tracked the way cash or product are tracked.

And yet the third one is what decides the trajectory. Product quality depends on the quality of the teams building it. Cash depends on their execution performance. Both flow directly through the management line. When it gives, the other two follow within six to eighteen months.

The standard picture, in a tech scale-up between fifty and one hundred people, is well known: the founder still carries operational pilot two years after structuring management. The best people leave in waves without anyone naming the cause. Team meetings drift into bad vibes or empty out of substance. The ExCo burns time on issues that should be settled two levels below. The climate is heavy, with no identifiable incident.

What is happening is that none of the managers along the line carries a solid authority. Each one improvises a way to hold the team. Some compensate with charisma, others with technical expertise, others still with a dose of kindness that quickly tips into avoidance. None of these compensations survives the operational pressure of sustained growth.

The phenomenon isn't new, and it's deeply human. I've watched it without interruption since 2013 with the founders I work with. The problem usually isn't the engagement of the managers in post. In most cases, they are sincere, motivated, eager to do well. The problem is that they don't carry the two pillars that hold managerial authority over time.

The Liquid Manager is that state. Sincere, motivated, with no spine. They manage on feel, shift posture depending on who they are talking to, constantly negotiate what should have been set. Their team learns to handle them from the right angle. Their own management learns to validate everything twice. Their performance moves with their mood. They end up draining their peers, their team, and themselves, without ever understanding why.

The Solid Manager is the opposite archetype. An authority that depends on neither charisma, nor mood, nor affinity with the person across from them. A behavioral consistency that makes their decisions predictable. A structured action system that makes their pilot legible. The performance they produce does not depend on them as an individual. It depends on what they have installed in the team.

Every manager in a scale-up sits somewhere between these two poles. The operational question is how many, across a given management line, are solid, whatever their individual competence. When the honest answer is "few," the right problem is on the table.

The diagnosis: why managers don't hold

The founder's instinctive hypothesis is comforting. My managers don't hold because they lack training, coaching, experience. The fix then looks obvious. Invest, train, coach. A few years later, the problem is still there, sometimes worse.

The hypothesis is wrong. Training has its uses, it simply doesn't address the cause. It adds tools, frameworks, vocabulary. It doesn't rebuild what is actually missing.

What the managers in post lack is two indivisible pillars: a codified behavioral posture and an action system structured around objectives. Missing one, the other, or both, always produces the same result: a manager who improvises.

Without a codified behavioral posture, the manager shifts day to day. Their decision depends on their fatigue, on who speaks first, on recent events. Their team learns to ask them things at the right moment rather than in the right way. Behavioral consistency is absent. So is operational trust.

Without a structured action system, the manager pilots on feel. Vague objectives, miscalibrated rituals, missing or useless indicators. They know something has to happen, but neither in what order, nor based on what signals. Performance drifts, they notice too late, react in bursts. Their team is thrown around.

Without either, you get the dominant profile in today's scale-ups. A manager who is technically competent and motivated, piloting their team as best they can. Their successes depend on a favorable context, and their failures get blamed on bad luck, on the market, on their people.

This is why classical training fails. It tries to muscle up a manager who has no spine. It teaches the tools without setting the frame in which those tools make sense. The founder buys content, the managers come back happy, but solid authority never appears.

The diagnosis is hard to hear but it is liberating. None of these managers was ever taught to build the two pillars. Nobody showed them. That is precisely the function of the Behavioral Codex and the Operating System, which I lay out below.

The teardown: why contemporary methods make the problem worse

The past twenty years have produced a dense catalogue of management methods. Agile, OKRs, manager-coach, servant leadership, kindness culture, liberated companies, holacracy, employee experience. All of them promise a more human, more effective, more aligned management. All of them have been bought at scale by scale-ups whose management line was failing.

In theory, these methods aren't bad. The trouble is that they all address peripheral symptoms, never the two foundational pillars. Worse, some of them (deployed on Liquid Manager terrain) accelerate the dissolution of authority instead of solidifying it.

I take apart here the six registers most widely deployed in tech scale-ups:

1. The manager-coach and servant leadership
2. Distorted Agile
3. OKRs without a managerial culture
4. Forced benevolence
5. Liberated companies and holacracy
6. HR bullshit

For each one, I explain on the facts why it often produces the opposite of what it promises.

The manager-coach and servant leadership

The promise is seductive. The manager no longer commands, they develop. They listen, they ask open questions, they let the team's solutions emerge. They serve their team instead of running it.

What actually happens inside a scale-up under pressure. The manager-coach gives up on calling shots. They wait for the team to reach agreement. When the team doesn't, they send the decision upward. The arbitrations climb. The founder picks them up.

On the hard topics (an underperforming team member, an interpersonal conflict), the manager-coach goes silent. They don't want to be seen as directive. They ask open questions while the issue rots. The team eventually loses faith in their judgment, because they no longer judge.

The manager-coach is a fine concept. It just doesn't apply to a manager who has no spine. On a Liquid Manager, servant leadership becomes the perfect alibi for abdicating arbitration. The manager stops doing management. They forget that what is expected of them is to hold a frame, take decisions, and own them.

Distorted Agile

Agile, in its pure form, is a rigorous frame. Short sprints, precise rituals, defined roles, shared indicators. A scale-up that deploys it properly gains velocity and transparency.

What has spread under the name of Agile across tech scale-ups is something else entirely. It is the absence of frame rebranded as flexibility. Reorgs every quarter. Roles change because "context shifts." Committees are dropped because they "slow things down." Teams are left to "self-organize" because it's more "agile." It's just chaos under another name and the result is well known. No one understands their scope. Decisions get taken three times because no one knows who decides. The management line becomes illegible. The founder spends part of their time explaining who does what, because agility has erased the contracts.

Distorted Agile is the perfect excuse to avoid the framing work. Framing a role and setting its limits gets dismissed as rigid and old school, so nobody does it. You end up with an organization that changes every three months for the same reasons: no one had set the previous contract.

OKRs without a managerial culture

OKRs swept through tech scale-ups because they promised alignment through objectives. Three ambitious objectives, three to five measurable key results per objective, cascaded from the ExCo to the teams. The promise is clean, the mechanics are simple.

What happens in the vast majority of scale-ups that deploy them. OKRs get produced once a quarter in a shared spreadsheet. The manager presents them to the team in a plenary meeting. Everyone nods. No one revisits them. At quarter's end, KRs get scored, partially hit, partially missed, and a new cycle begins.

The problem, when it shows up, is that no daily arbitration is actually driven by the OKRs. When the manager has to choose between two operational priorities, they don't look at their OKRs. They call it on feel, or default to the most urgent topic. OKRs become a quarterly ceremony, disconnected from real pilot.

OKRs are an objective framework, but in no way a managerial system. Without that system to operate them daily (rituals, intermediate indicators, pilot modes), they turn decorative.

Forced benevolence

Managerial respect is baseline. Treating people with dignity, listening, not humiliating, not instrumentalizing: that's the minimum of an adult-to-adult frame. It is non-negotiable.

Benevolence is something else. It is the positive a priori on the intent and value of the team member. As a principle, it is healthy. The problem starts when it becomes a cultural injunction that forbids frank disagreement. When a manager can no longer tell someone they are underperforming without softening the sentence to the point that the message disappears. When an ExCo member can no longer flag the poor quality of a deliverable without risking a toxicity accusation.

Forced benevolence produces a well-documented perverse effect. Real issues stop being addressed in time, underperformance settles in, and conflicts smolder without ending. The good people, who see things without being asked, eventually lose faith in the manager who names nothing, and they leave. That accounts for a meaningful share of A-player departures in scale-ups.

The Solid Manager knows how to separate the dignity owed to each person (non-negotiable) from the frank disagreement on the work (necessary). They place the critique without degrading the person. They name underperformance without humiliating. That is precisely the behavioral consistency that forced benevolence prevents from forming. By outlawing critique in the name of benevolence, the system produces managers who no longer know how to critique at all.

Liberated companies and holacracy

Liberated companies, holacracy, sociocracy, the flat organization. These models start from a strong intuition. Traditional hierarchy slows decision-making, dampens engagement, infantilizes people. Strip the levels and you release collective energy.

These models rest on a prerequisite no scale-up ever meets in practice: a team made entirely of real professionals, with a high work ethic, capable of collectively owning arbitration, conflict, and underperformance without a formal frame compelling them to. Without that prerequisite, the model warps at the first friction.

The accumulated experience of scale-ups that attempted these models is instructive. In practice, the flat structure works on the easy and false-naïve topics. It collapses the moment there's a conflict, an unpopular decision to take, a difficult prioritization between two teams, an underperformance to address.

Without formal hierarchy, those topics don't vanish. They climb. They climb to the founder, who ends up arbitrating in real time the issues they had specifically wanted to delegate by removing the levels. The flat structure makes the founder carry what formal hierarchy would have absorbed two levels below.

The paradox is mechanical. The flatter the organization, the more the top gets pulled into operational arbitrations. Founders who have deployed these models discover this the hard way. Many revert to a classical management structure after two to three years, following a period of high tension.

The Solid Manager does not need a liberated organization to produce autonomy in their team. They produce that autonomy by delegating properly, by training their relays, by owning their role. That is exactly what the flat organization claims to achieve by removing the role. Except that without the role, autonomy does not happen.

HR bullshit

The last register I take apart is harder to hit because it hides behind virtuous vocabulary. Employee engagement, employee experience, purpose, meaning at work, employer brand, well-being. These terms aren't false in themselves. They become problematic when they replace arbitrations instead of complementing them.

The warning sign is simple. When a scale-up hands its HR department an "employee engagement" program that consists of measuring eNPS each quarter, running purpose workshops, publishing values charters, you are inside HR bullshit. None of these deliverables addresses the operational question. None challenges a manager who isn't holding. None equips the N-1s to hold their management line.

HR bullshit is the corporate sibling of forced benevolence. It turns managerial issues into communication issues. People talk about engagement instead of framing. They talk about meaning instead of pilot. They talk about experience instead of performance. HR produces slides, the managers don't change, the A-players keep leaving.

The point is to put the question back where it belongs, not to push HR out of the management conversation. Managerial performance is built in the daily life of managers, not in communication rituals. As long as the founder buys an HR program instead of setting a managerial frame for their N-1s, they are funding the symptom and feeding the cause.

The doctrine: the Solid Manager rests on two indivisible pillars

After the teardown comes the doctrine. A Solid Manager is a manager whose authority holds because it rests on two distinct and indivisible pillars. The first is a codified behavioral posture. The second is a structured action system. Either alone does not make a Solid Manager. Together they build an authority that survives the operational pressure of a scale-up.

These two pillars are architectures, not "best practices." You deploy them the way you deploy an information system: with intent, with structure, with the demand of application. A best practice you can pick or skip. An architecture you respect.

The Behavioral Codex

The Behavioral Codex codifies the posture of the Solid Manager into ten observable attributes, grouped in three families. Each attribute describes a specific behavior. Its absence produces a recognizable failure that fragilizes the whole managerial posture.

The Clarity family groups four attributes that make expectations legible and action visible:

1. Tracker. Turns every managerial act into written trace. A manager who doesn't trace loses the memory of their decisions. Their arbitrations contradict each other, their team doesn't know what has been settled.
2. Framer. Sets non-negotiable boundaries with no ambiguity. A manager who doesn't frame leaves their team guessing what is expected. Roles drift, contracts get renegotiated continuously.
3. Clear-Sighted. Reads informal power dynamics. A manager blind to internal dynamics is carried by games they don't control. They are repeatedly surprised by the resistance they meet.
4. Decisive. Creates momentum through action. A manager who doesn't call paralyzes their team. Decisions climb to the level above, issues rot waiting for an arbitration.

The Resilience family groups three attributes that hold under pressure and preserve the capacity to act:

5. Steady. Keeps their composure under tension. A manager who doesn't hold under pressure transmits their tension to the team. The team pilots their mood instead of the objective.
6. Protective. Shields the team from destructive demands. A manager who doesn't protect lets every external request through. Their team is thrown around, can no longer focus.
7. Prepared. Anticipates contextual shifts. A manager who doesn't prepare reacts in emergency mode, never in strategy. They absorb reversals instead of anticipating them.

The Strategic Trust family groups three attributes that build authority over time:

8. Accountable. Owns outcomes and names gaps. A manager who doesn't own avoids hard conversations. Underperformance settles in, gaps go unnamed, the climate degrades.
9. Respectful. Treats each person with dignity and fairness, independent of affinity. A manager who doesn't respect fairness treats their people according to their preferences. The best identify the bias and eventually leave.
10. Cultivator. Develops their people through delegation and challenge. A manager who doesn't cultivate keeps their best on execution tasks, doesn't grow them. They stall, they leave.

These ten attributes are observable and operable behaviors, not a menu or a program to run through. A Solid Manager embodies all ten, not three out of ten. Missing one produces a localized failure that ends up weakening the whole.

The Codex is built. It does not emerge from personality. That is what separates this frame from the approaches that talk about born leaders, natural style, managerial personality. The Solid Manager is an installed behavioral repertoire, not a human type.

The Operating System

The Operating System codifies the action system of the Solid Manager. It applies to any manager who pilots a team against an objective, regardless of hierarchy or function.

The system follows four non-negotiable phases:

1. SET defines mission and metrics: final objective, key indicators, measurable priorities, non-negotiable limits, value delivered to internal clients.
2. ARCHITECT structures execution: who delivers what, with what resources, on what management calendar, communicated to the teams.
3. OPERATE pilots execution day to day, across three modes described below.
4. LEARN embeds improvement at the end of the cycle: successes and root causes, failures and root causes, capitalization for the next objectives.

The OPERATE phase is itself structured in three modes, depending on the state of operations:

1. HOLD when performance is good. You stay the course: active monitoring, fast decisions on blockers, quality standards held.
2. RESIST when performance is poor. Diagnosis, targeted mentoring, ownership reinforced, priorities adjusted.
3. ELEVATE when performance is excellent. You invest the slack in training, development, and systems.

This structure is an action frame, not a dressed-up agile ritual. It tells the manager what to do, in what order, in response to what signals. A Solid Manager doesn't wonder how they are going to manage this week. They know which phase and which mode they are in, what they must produce, what they must watch.

The Operating System is tool-independent. It runs equally well with OKRs or with classical annual plans, with agile sprints or with a quarterly cadence. What matters is the logic of action, not the tooling. A manager who moves from one organization to another keeps their system. They adapt it to the tools in place, not the other way around.

Why the two pillars are indivisible

A manager with the Codex but no Operating System improvises with dignity. Their posture is stable, their team knows what to expect behaviorally, but their pilot drifts. Objectives are vague, rituals are miscalibrated, execution is erratic. They hold their team but do not make it perform.

A manager with the Operating System but no Codex executes mechanically and loses the team. Their rituals are in place, their indicators are tracked, but their posture wobbles. They negotiate their decisions, dodge hard topics, treat their people according to affinity. Their team pilots performance but disengages humanly. Within six to twelve months, the best leave.

The two together produce a manager whose authority holds. Their posture is consistent, their system is legible. Their people know what to expect, understand what is expected of them, see their development trajectory. Their performance no longer depends on context. It repeats.

That combination is what defines solid managerial authority: two architected and installed pillars that survive time and pressure, independent of charisma, experience, or technical mastery.

The 9/9 doctrine: performance and development, simultaneously

The Solid Manager doesn't choose between performance and development. They hold both axes to the maximum, simultaneously. On the classical Blake and Mouton grid, that's the 9/9 position. Maximum concern for results, maximum concern for people, both axes held to the maximum at once.

This posture excludes two symmetrical drifts. The first is hard productivism, which sacrifices people for results. It produces teams that perform for a while and then collapse. The second is benevolence that sacrifices results for the comfort of people. It produces calm teams that no longer deliver.

9/9 is a doctrine of demand. You ask everything of your people in terms of results, and you give them everything in terms of frame, development, respect. Performance and development are the two faces of the same managerial work. When development is done well, performance follows. When performance is demanding, development accelerates.

Explicit guardrail: the relationship is adult-to-adult, oriented toward collective advancement, inside a clear contractual frame. It has nothing to do with "care" at any cost, nor with a victim-narrative reading where the manager plays the oppressor and the subordinate the exploited. Development is the manager's function, not a gift they bestow. Performance is a reciprocal commitment, not an act of violence.

What The Solid Manager offers, and what it doesn't

The Solid Manager is not an organizational transformation consultancy, an executive coaching program, an online training publisher, or a team-offsite shop. All of these formats exist elsewhere, some of them done well.

The Solid Manager is a diagnosis and uninstallation apparatus. We surface the blind spots of the management body, we uninstall the postures that block it, we install the two foundational pillars over time. The Solid Manager is built by uninstalling the postures that block them and by methodically installing the two pillars, in long-haul work, not by accumulating best practices.

Concretely, the work runs on the real managers of the organization, in their daily operations, on the situations they are living right now, with no generic case studies or artificial role-plays. The managers work on their teams, their topics, their arbitrations, alongside a senior operator who has carried operational management before them.

The entry point is a 30-minute Clarity Call. A contact call where you walk through your context and stakes, and I lay out the method. The objective is to see whether we can work together, not to run an exhaustive diagnosis. No commitment to follow up.

What The Solid Manager will never do: sell a program a founder doesn't need, guarantee outcomes no one can guarantee, coach managers so they feel better without changing their impact, or produce slides that describe what should happen in the organization without installing anything.

If you recognize your managers in this text

The validity test of this manifesto is simple. Reading it, you recognized some of your managers, enough for the grid to operate.

If that is the case, you hold the right problem. Your management line fails because it was never architected. Your managers improvise, because no one ever gave them the two pillars that would make them solid.

The good news is that those two pillars are buildable. They depend on methodical work on behavioral posture and action system, conducted by a senior operator, at the cadence of your tech scale-up or tech SMB daily life, not on innate talent or accumulated experience.

The bad news is that this work happens in the operational mesh of your managers, on their actual arbitrations, with demanding and constant feedback, not in an offsite, a detached coaching, or a remote training course.

This manifesto speaks to tech scale-up founders, and to executives of tech SMBs of sixty to one hundred people facing the same symptoms. What decides things is the quality of the management line that drives execution, whatever the exact size.