Requisite Organization in Practice

Elliott Jaques spent over fifty years studying why some organizations thrive under pressure while others collapse into confusion, politics, and mediocrity. His conclusion - formalized in Requisite Organization - was both radical and obvious once stated: organizations fail not because of bad people, but because of bad structure. Roles are misaligned with the cognitive complexity of the work they contain. Managers exist at the wrong level. Accountability is unclear. Trust breaks down - not from character flaws, but from structural mismatch.

Manageable takes the same view. Not as a Requisite Organization implementation, but because the same principles Jaques identified as necessary - role clarity, accountability matched to authority, precise task assignment, consistent coaching - are what Manageable is built around. This page explores where the two converge, and what that alignment reveals about why Manageable works.

Stratified Systems Theory: The Architecture of Work

Jaques observed that human work organizes itself into natural strata - discrete, qualitatively different levels of complexity. He called this Stratified Systems Theory (SST). Each stratum is defined not by title or seniority, but by the time span of discretion: the longest period over which an employee is expected to complete a task without direct supervision.

A Stratum I role - say, a frontline associate - might operate on a time span of days to weeks. A Stratum III department manager works on a horizon of one to two years. A Stratum V general manager is steering a five-to-ten-year course. The strata are not gradations on a line; they are qualitatively distinct modes of thinking and problem-solving.

In a requisite organization, every managerial role sits exactly one stratum above its direct reports. When a manager is at the same stratum as their team, they can't provide cognitive value-add - they micromanage or duplicate work. When they are two strata above, they become disconnected, abstract, and alienating. One stratum of separation is the condition for genuine managerial leadership.

Manageable's role architecture reflects the same logic. Role definitions capture the scope and time horizon of decision-making authority, making it possible to look at your organization through an SST lens and identify structural mismatches before they erode trust and productivity.

Role Clarity: Designing the Position Before the Person

One of Jaques's most important - and most ignored - insights is that organizations should design roles first and then find people to fill them, not the reverse. When roles are built around individuals, the level of work shifts with each incumbent and accountability becomes personal rather than structural. This is the root cause of most succession failures and the most common source of organizational politics.

Manageable's role definition module supports exactly this discipline. Each role in the system is defined with:

This is not a job description generator. It is a structural tool - a way of encoding the architecture of your organization in a form that managers, employees, and HR can all reference and rely on. When the role is clearly defined, conversations about performance become objective. Expectations are explicit. The ambiguity that produces anxiety and politics is eliminated at the source.

Accountability Hierarchy: Real Authority, Real Responsibility

Jaques drew a sharp distinction between accountability (being answerable for outputs) and authority (the power to act). In most organizations these are misaligned: managers are held accountable for outcomes they lack the authority to produce. This is the structural source of the feeling that "my hands are tied" - and it is corrosive to managerial effectiveness.

Requisite Organization defines a clear set of managerial authorities that every manager must have in order to be genuinely accountable. These include the authority to: select team members, set context and assign tasks, evaluate work, coach performance, and initiate removal from the role. Without all of these authorities, the manager cannot be fairly held accountable - and won't be trusted or respected by their team.

Manageable's team and reporting structure modules make these relationships explicit. Every person in the system has a clearly assigned manager. Every manager's role is defined with the authorities that accompany it. Skip-level relationships - important in Requisite Organization for mentoring and appeal processes - are tracked and supported, but distinguished from the direct accountability relationship.

Task Assignment: Communicating Expectations with Precision

Jaques insisted that managerial leadership begins with the quality of task assignment. A manager who assigns work without clarity on quantity, quality, timeline, and resources is not managing - they are wishing. The inevitable result is disappointment, confusion, and eroded trust on both sides of the relationship.

Manageable's QQTR framework reflects this same requirement. It is a structured task assignment format that ensures every significant piece of work is communicated with the precision Jaques described as essential. QQTR stands for Quantity, Quality, Time, and Resources: the four dimensions that make a task assignment unambiguous.

When every significant task is assigned through this framework, the organization develops a shared language for work. Managers stop assuming their team knows what "good" looks like. Team members stop guessing what their manager expects. The cognitive friction of ambiguity is eliminated, and energy flows toward the work itself.

Jaques held that unclear task assignment is not a minor oversight - it is a moral failure of the managerial role. A manager who assigns ambiguous work deprives their team member of the conditions needed to succeed, then holds them accountable for a result that was never made clear. QQTR addresses that directly.

Coaching: The Manager as Developer of People

In Requisite Organization, a manager's primary obligation to their team members - beyond task clarity - is to actively develop their capability. Jaques rejected the command-and-control model of management not because it was harsh, but because it was structurally inefficient: it concentrated knowledge at the top and left capability underdeveloped throughout the organization.

The requisite manager is a coach. They work with each direct report to understand current capability, identify growth edges, and create conditions in which the person can take on progressively more complex work. This is not performance management as most organizations practice it - a once-a-year ritual of scoring and ranking. It is an ongoing, substantive, two-way conversation about work and growth.

Manageable's coaching module supports this with structured one-on-one frameworks, progress tracking on active initiatives, and space for both the manager and the employee to capture observations and commitments. Coaching conversations are linked to active projects and role accountabilities, so they remain grounded in the actual work rather than drifting into abstraction.

Performance Reviews: Evaluation Against Defined Standards

Jaques had deep skepticism about conventional performance appraisal systems that rank employees against each other or against abstract competency models disconnected from the actual work of the role. His position was that performance evaluation should be simple, honest, and tied to the outputs defined at the time of task assignment.

If the task was assigned clearly - with quantity, quality, time, and resources specified - then evaluation is straightforward: did the person meet the standard? If not, why not, and what does the manager need to do differently to support better outcomes? The evaluation process becomes a learning loop, not a judgment event.

Manageable's review module follows this same logic. Reviews reference the role's key accountabilities and the tasks assigned during the review period. Managers assess outputs against stated expectations. There is no forced ranking, no competency scoring divorced from real work, and no ritual that treats evaluation as separate from the ongoing coaching conversation.

Felt-Fair Pay and Level of Work

One of Jaques's most striking empirical findings was that people have a strong, consistent intuition about what constitutes fair pay for a given level of work - and that this intuition corresponds closely to the time span of the role. He called this felt-fair pay: not what the market pays, not what the person negotiated, but what feels equitable to the person doing the work and those around them.

When pay is misaligned with level of work, people feel it acutely. Someone in a Stratum III role paid at a Stratum II level will feel underpaid and disengaged regardless of market data. Someone in a Stratum II role paid at a Stratum III level will feel anxious, overextended, and ultimately ineffective. Pay equity, in Jaques's framework, is not just a fairness issue - it is a structural issue that directly affects performance and retention.

Manageable's role and compensation planning tools support organizations in mapping role levels to compensation bands, making the connection between level of work and pay explicit and defensible - not just internally fair, but rationally grounded in the structure of the work itself.

The Trust That Structure Creates

Jaques believed - and decades of organizational research have supported - that trust in organizations is not primarily a product of interpersonal chemistry or cultural programming. It is a product of structure. When people have clear roles, clear expectations, clear accountability, and managers who operate at the right cognitive level, trust emerges naturally. When structure is broken, no amount of culture work, team-building, or values posting will produce lasting trust.

This is the deepest insight of Requisite Organization, and one that Manageable reflects in how it is built. Manageable is not a culture platform. Not a pulse survey tool. It is a system that creates the structural conditions in which trust, engagement, and high performance follow naturally - because the underlying management work is being done correctly.

The behaviors Manageable supports - clear task assignment, consistent coaching, honest evaluation, transparent role definition - are not additions layered on top of real work. They are the real work of management. What Jaques called requisite managerial leadership: the behaviors a manager must exhibit to fulfill the accountability their role carries.

Manageable Product Modules Through a Requisite Lens

Each module in Manageable aligns with a core principle of Requisite Organization. Here is where the convergence is clearest - and what Jaques's framework helps explain about why each one matters: