From the book On Readiness

These excerpts from the book On Readiness: From Strategy to Behavior at Scale explain the thinking behind exIQtive: why readiness matters more than headcount, and how Hats, badges, checklists, and simple math turn it into something you can manage.

​

Readiness beats resources

In 1967, the Israeli Air Force (IAF) went to war outnumbered. Arab forces had more than 600 modern Soviet-made jets; Israel had barely 200 operational aircraft, many patched together from World War II scrapyards. But Israel had something more valuable than planes: people who were ready. The man behind this was Moshe Bar, a farmer turned fighter pilot, who thought about air warfare the way he thought about a farm:

“Instead of buying a new tractor, you run the one you already have in two or three shifts.”

NATO considered three sorties per aircraft per day the maximum; Arab air forces trained for two. Bar redesigned the sevev (Hebrew for “turnaround”) process, mapping every action down to who touched which wrench, in what sequence, and for how long. Each crew member had clear responsibilities, practiced until they became muscle memory. By the time the war started, the IAF could turn a fighter around in six to eight minutes, five times faster than most air forces. Israeli pilots flew five or six sorties a day. On paper Israel had a third of the planes; in practice it had the equivalent of three air forces. IAF Commander Mordechai “Motti” Hod later credited simplicity and Ein Breira, “no alternative”: “When you don’t have alternatives, you achieve such achievements as we did in this war.” Southwest Airlines later applied the same principle to commercial aviation. While competitors bought more planes, Southwest asked how to get more flights from the planes it already owned. Ground crews were trained for readiness with clear roles, cross-training, and practice until automatic. Where competitors accepted 45–60 minute turnarounds, Southwest consistently hit 25 minutes or less: fewer planes, more output, higher profitability.

​

What readiness really means

Most companies confuse hiring qualified people with having a ready workforce. Someone can have the right experience, degree, and attitude and still not be ready to perform in your organization. Readiness is not about potential. It’s proven, repeatable capability, measured against specific responsibilities.

​

Why job descriptions fail

Job descriptions are written to get people hired, not to make them successful once they’re in the seat. “Own strategic initiatives.” “Manage cross-functional stakeholders.” What does that mean on a Tuesday afternoon? Breaking positions down usually reveals dozens, even hundreds, of specific responsibilities that were never written anywhere, and many are shared across positions. “Running interviews,” for example, isn’t just for HR: department heads, team leads, and senior individual contributors all do it. That’s the shift from thinking about jobs to thinking about Hats.

​

The Hats model

Instead of making people decode a vague job description, break every position into Hats, and every Hat into specific, observable responsibilities:

• The Recruiter Hat: sourcing candidates, interviewing them, and closing offers.
• The Budget Owner Hat: tracking expenses, forecasting, and justifying spend.
• The People Leader Hat: coaching, giving feedback, and running performance reviews.

An employee may wear several Hats, but each has clearly defined responsibilities. Now you can say: “You’re wearing this Hat. Here’s exactly what it means. Here’s how we’ll know you’re ready.” It also gives employees language: instead of “I don’t know what’s expected of me,” they can say “I’m not sure what’s included in this Hat,” and you can fix that fast. In exIQtive, a Hat is a Role.

​

The language of readiness: badges

Clarity on responsibilities still leaves one problem: how do you talk about how ready someone is, objectively, without ego or politics? Vague reviews (“You’re doing well,” “You need to step up”) don’t mean the same thing to everyone. You need a shared language of readiness. This system:

• Removes emotion from the conversation. Not “You’re not good at this,” but “You’re at Apprentice here, which is exactly where you should be at this stage.”
• Creates ownership. Employees ask “What do I need to do to get to Proficient?” instead of waiting for vague feedback.
• Makes growth visible. People take pride in earning badges because they’re a clear sign of contribution and expertise.

​

Why badges work

Aviation, the military, and sports already use this principle. A pilot earns a certification because they’ve demonstrated specific, observable skills; a martial artist earns a belt by performing techniques reliably under pressure. Because badges are tied to responsibilities, not titles, they reveal the real story: two people with the same title can have very different readiness profiles.

​

Behavior you can see, not opinions you can argue

In the Israeli Armored Corps, no one said “I think this soldier is ready to operate the tank under fire.” Readiness was proven by doing: load the shell in X seconds, communicate over the radio in Y format, navigate the formation without breaking position. If you couldn’t do it consistently under stress, you weren’t ready. Business is the same: readiness is observable behavior performed consistently, not how good someone sounds in a meeting.

​

Turning tribal knowledge into checklists

Most companies have informal experts who just know how to do things, with almost nothing written down. Knowledge passed on by watching, guessing, and asking works for a team of five, not fifty or five hundred. To scale, turn tribal knowledge into organizational knowledge, and the simplest way is checklists. The person who performs a responsibility consistently at a high standard (in exIQtive, the Architect) documents exactly what readiness looks like: actual steps, tested in practice. A checkpoint should start with “Can…”, “Does…”, “Demonstrated…”, or “Proved…”, and come with instructions for how to inspect for that behavior. When you write readiness checklists for every Hat, you:

• Define what “expected” looks like
• Remove ambiguity from coaching conversations
• Make readiness teachable, observable, and transferable

​

Learning in the age of information overload

Training used to be a scheduled event: a classroom or a Learning Management System (LMS) module, consumed in bulk and hopefully remembered later. That no longer holds. Attention is scarce, knowledge has a short shelf life, and Hermann Ebbinghaus’s Forgetting Curve shows that without reinforcement, people forget most of what they learn within days. Traditional LMS learning struggles because it’s:

1. Too much, too soon: people learn processes they won’t use for weeks or months
2. Low relevance: content is generic, not tied to the task at hand
3. Poorly retained: one-off events don’t build capability without practice
4. Slow to update: libraries can’t keep pace with changing tools, policies, and customer expectations

The most effective learning happens in the flow of work:

• Microlearning delivers one concept, step, or principle in under 5 minutes.
• Micro-experiences embed learning in real tasks, applied immediately.
• Performance support (checklists, guided workflows, short videos) gives just-in-time clarity.

The readiness model fits this reality: every responsibility has a clear checklist, learning is chunked by responsibility, and coaching happens in real time. The question shifts from “Has this person completed the module?” to “Can they perform this responsibility independently, consistently, and with clarity, right now?” That reduces Time-to-Readiness, minimizes training waste, and keeps learning in step with reality.

​

From expert to many: cloning expertise

Even with clear checklists, the experts themselves become the bottleneck: they’re too busy doing the work to train others. The fix is to train and certify experienced employees as Coaches who can inspect, coach, and award badges. This is how the FAA scales pilot training: the standards are written centrally, and certified examiners (Designated Pilot Examiners) multiply the capacity to evaluate. In business, it creates a readiness engine:

• Architects codify what readiness looks like.
• Coaches certify others against it.
• Employees own their readiness, knowing exactly what’s expected.

​

Building effective checklists

A readiness checklist is a structured set of checkpoints grouped by readiness level (Apprentice, Proficient, Coach, Architect). To earn a badge, an employee must pass the checkpoints for that level and all prior levels. A good checkpoint meets three criteria:

1. Clear pass/fail standard. It states what success looks like in observable, testable terms:
   • “Can…” (capability)
   • “Does…” (consistent behavior in normal work)
   • “Demonstrated…” (behavior shown in an observed setting)
   • “Proved…” (behavior under pressure or variable conditions)
2. Inspection instructions. Explicit instructions on how to inspect it. For the inspector, they ensure consistency; for the employee, they make it clear how they’ll be evaluated so they can prepare with confidence.
3. Sequential validation. Levels build on one another. No one should earn Proficient without first passing every Apprentice checkpoint.

With checklists this clear, inspections become developmental, not punitive. Passing a checkpoint is a milestone and earning a badge is recognition. The checklist is the bridge between expectation and trust: you trust people to act independently because they’ve proven they’re ready, and they trust the system because the rules are clear.

​

The math of readiness

Performance tells you what happened yesterday. Readiness tells you what will happen tomorrow, because ready people perform consistently even when circumstances change. And readiness is measurable with simple math.

​

The individual readiness KPI

Every responsibility under every Hat gets a badge, and every badge has a readiness value: Novice 0%, Apprentice 50%, Proficient 100%, Coach 125%, Architect 150%. The book’s basic method has two steps:

1. Average readiness within each Hat (across its responsibilities).
2. Average across Hats.

This keeps Hats with more responsibilities from outweighing others unless you intend them to. Example: a Production Manager with three Hats Individual readiness = (75% + 112.5% + 25%) ÷ 3 = 70.8%.

​

Adding importance

Not all responsibilities are equal; some drive most of a role’s value. So each responsibility gets an importance from 0 to 3:

• 3 – Very important: critical for success
• 2 – Important: contributes significantly to outcomes
• 1 – Somewhat important: nice to have
• 0 – Not currently relevant: assigned but inactive

Each responsibility’s readiness is multiplied by its importance before averaging, first within each Hat and then across Hats (a Hat’s weight is the sum of its responsibilities’ importance). Weighted individual readiness = (4 × 87.5% + 5 × 110% + 3 × 16.7%) ÷ 12 = 79.2%. A low-readiness responsibility in a critical Hat now meaningfully lowers the KPI, while low-importance gaps don’t create misleading noise. The KPI becomes a true reflection of the employee’s value to the role right now.

​

Weighted average readiness across employees

Leaders also need readiness across employees. Give each employee an importance from 0 to 3 reflecting their impact on the business, then take the importance-weighted average of their individual readiness. Titles are ignored entirely: readiness measures demonstrated competence, not what someone is called.

​

Organizational readiness

A company can have many ready employees and still fail if critical positions are unfilled or staffed poorly. Organizational readiness measures the structure itself:

• Occupied positions take the individual readiness of the person in the seat.
• Vacant positions count as 0%, because no one is doing that work.

Give each position an importance from 0 to 3:

• 3: mission-critical; failure directly impacts strategic execution
• 2: significant to operations; contributes directly to outcomes
• 1: supportive; important but not critical
• 0: non-critical (unused or temporarily inactive)

Then multiply each position’s readiness by its relative weight (its importance ÷ total importance) and add them up. In the book’s example, organizational readiness is 45% + 27% + 0% = 72%: even though two people are individually ready, the vacant marketing seat pulls the company down. Organizational readiness:

• Reveals structural weaknesses: a strong team can still fail if critical positions are empty or under-ready.
• Prioritizes hiring and training: you see where a vacancy or low readiness in an important position threatens execution.
• Tracks strategic capability over time: as you fill key positions with ready people, it rises, a leading indicator of whether you can deliver your strategy.

​

Agile readiness

Responsibilities evolve, not because titles change, but because the behaviors needed to meet them must adapt: new compliance rules, a product update, upgraded equipment. The real test of readiness is how quickly employees adjust their behaviors to new requirements, and how reliably they keep them. The badge system is designed to keep readiness a living state that evolves with the business.

​

Closing new gaps fast

Checklists aren’t static. When you discover a gap, you can add a checkpoint:

• Badges affected by the new checkpoint no longer reflect current expectations.
• Employees get a grace period to pass the new checkpoint and keep their badge.
• If the grace period ends without passing, the badge is removed, so metrics always reflect current standards.

​

Minor vs breaking changes

When a checkpoint itself changes:

1. Minor changes (small clarifications) don’t require re-inspection; badges stay in good standing.
2. Breaking changes fundamentally change what readiness looks like for that checkpoint. Inspections for it are reset and affected badges must be re-earned within the grace period.

​

Maintaining readiness over time

Skills decay, especially for rarely used responsibilities. Like pilots’ recurrent certification, some checkpoints are re-inspected periodically: inspections reset ahead of expiration, employees get a window to re-certify, and a badge not renewed in time expires. A badge earned months ago means little if the way the work must be done has fundamentally changed. Whenever requirements evolve, employees re-prove their readiness, so you know people are ready for the current reality, not yesterday’s.

​

Time-to-readiness

Most leaders track time to hire; few track how long it takes a new hire to become ready: to perform independently, consistently, and with clarity. That’s Time-to-Readiness (TtR), one of your most powerful scaling levers. Every day an employee isn’t ready, you pay full salary for partial output. Cut TtR by 30% and you can grow faster with fewer hires; improve it even 10% and the gain compounds across the team. The sooner someone reaches Proficient, the longer you benefit from their full contribution.

​

Measuring time-to-readiness

​

Accelerating time-to-readiness

• Clear Hats tell employees exactly what’s expected.
• Checklists define what good looks like and how to inspect it.
• Coaches speed up feedback loops and catch mistakes early.
• Badges motivate employees to level up.

When your organization can ramp people twice as fast, you need fewer people for the same results. That makes TtR a strategic growth KPI, not just an HR metric.

​

An internal marketplace for readiness

Many employees are already ready for responsibilities outside their formal job, but those skills are invisible. When gaps open from promotions, attrition, or new initiatives, companies default to slow external hiring. If readiness were visible across the organization, you could treat it like a marketplace: a live inventory of capabilities where managers find skills inside the company first. Employees eager to grow can raise their hand for stretch assignments, which reduces time-to-readiness for new roles, improves retention, and deploys people by capability rather than title.

​

Commitment to a position

Readiness isn’t only about today’s job. It’s also about preparing for the job you want next. In exIQtive, this is your commitment to a position.

​

Primary: occupying

Your primary position is the job you’re hired and paid to do. You’re expected to consistently demonstrate Proficient readiness or higher on all its responsibilities.

​

Preparing for a future position

Career growth should be a measurable journey. With a Preparing for commitment, you take on selected responsibilities from a future position, one Hat at a time. Aiming to be a department manager? You might start by coaching a small team or running one performance cycle while still in your current job. As you earn Proficient or Coach badges on those responsibilities, you build a data-backed case for promotion. By the time the title changes, you’re stepping into a position you’ve already proven you’re ready for.

​

Why this matters

• For employees: transparent career paths and personal agency.
• For the organization: bench strength and agility; vacancies can be filled by people already preparing for those positions.
• For leadership: promotions become a simple math problem, because promotion-ready employees already have measurable readiness in the future position.

​

Implementation strategy for success

A key success factor is appointing someone responsible for the implementation. Using the exIQtive method, they make sure every employee has clarity on their roles and responsibilities and is demonstrably ready to perform them, driving readiness in line with your company’s strategic intent. They:

• Drive clarity of roles and responsibilities by maintaining a living catalog of roles and responsibilities
• Develop Architects who create effective inspection checklists with videos and quizzes
• Ensure coaching capacity, ideally two Coaches per responsibility (for example, the Architect also coaches and certifies at least one more Coach)
• Report on readiness across the organization

Success indicators: at least 80% of positions with clearly defined roles and responsibilities, and employee readiness of at least 90%. See Keys for success.

​

How exIQtive puts this into practice

exIQtive manages the whole readiness process. It tracks active employees and positions and assigns employees to positions. When an employee is assigned to a position, all its Roles (Hats) and their responsibilities, plus any responsibilities attached directly to the position, are assigned automatically. Those assignments are matched to the badges the employee has earned, and individual readiness is calculated in real time from assignment importance and the employee’s readiness per responsibility. exIQtive also calculates the average readiness across your employees in real time. Roles and responsibilities live in a catalog you reuse across the organization. You define positions by attaching roles (and, where a responsibility belongs to one position only, attaching it directly), and roles reflect the responsibilities attached to them immediately.

​

Related