What does the Team Reality diagnostic detect?

It detects load concentration, capacity mismatch, and role coverage fragility that constrain execution throughput.

When should founders run Team Reality?

Run it when teams feel overloaded, key operators are single points of failure, or delivery slips despite stable priorities.

How is risk communicated?

Risk is communicated through Status, Confidence, Evidence, Signals, and Next Action to support deterministic execution planning.

Diagnostic module

Execution slips when team capacity does not match the load

Evaluate whether your current team can carry the execution demands of the business.

Run diagnostic

PeopleBooks Team Reality

Signal scope

Is role capacity realistic?

Is work concentrated in a few people?

Are key roles fully covered?

Can execution survive operator absence?

Signal model

Readiness

100

Founder Load

Capacity Allocation

Load Concentration

Role Coverage

Absence Survivability

State bands

85-100

Capacity Matched to Strategy

70-84

Stretched but Viable

50-69

Capacity Misaligned

0-49

Structurally Overloaded

Operator modules

Each module isolates one structural capacity or survivability risk.

Founder Operational Load

Is the founder still carrying critical execution load that should sit in the system?

Open module

Capacity Allocation

Do current time allocations match what each role actually needs to deliver?

Open module

Load Concentration

Is too much execution risk concentrated in too few operators?

Open module

Role Coverage

Is every defined execution role covered by a named operator with real capacity?

Open module

Absence Survivability

Can execution continue when a critical operator is temporarily unavailable?

Open module

System context

Work Design

Structure

Team Reality

Capacity

Alignment

Coordination

Diagnostic module

Execution slips when team capacity does not match the load

Evaluate whether your current team can carry the execution demands of the business.

Run diagnostic

PeopleBooks Team Reality

Signal scope

Is role capacity realistic?

Is work concentrated in a few people?

Are key roles fully covered?

Can execution survive operator absence?

Signal model

Readiness

100

Founder Load

Capacity Allocation

Load Concentration

Role Coverage

Absence Survivability

State bands

85-100

Capacity Matched to Strategy

70-84

Stretched but Viable

50-69

Capacity Misaligned

0-49

Structurally Overloaded

Operator modules

Each module isolates one structural capacity or survivability risk.

Founder Operational Load

Is the founder still carrying critical execution load that should sit in the system?

Open module

Capacity Allocation

Do current time allocations match what each role actually needs to deliver?

Open module

Load Concentration

Is too much execution risk concentrated in too few operators?

Open module

Role Coverage

Is every defined execution role covered by a named operator with real capacity?

Open module

Absence Survivability

Can execution continue when a critical operator is temporarily unavailable?

Open module

System context

Work Design

Structure

Team Reality

Capacity

Alignment

Coordination