PerchIQX: Space (Scope)
"From the high perch, the cormorant sees not just one fish, but the entire school. See the full scope."
PerchIQX is the scope dimension of the 3D lens. It measures how widespread an impact is — how many people, customers, systems, or processes are affected.
What is Space/Scope?
Core question: How widespread is this impact?
Named for: The cormorant's elevated perch — the vantage point from which it surveys the entire hunting ground, assessing the size and density of fish schools before diving.
In business context: Scope determines resource allocation and response scale:
- Wide scope (8-10): All-hands, enterprise-wide initiative, C-suite ownership
- Medium scope (4-7): Cross-functional team, department-level response
- Narrow scope (1-3): Individual contributor, single-team fix
The Space Scale (1-10)
┌──────────────────────────────────────────────────────────┐
│ PERCH IQX SCALE │
├──────────────────────────────────────────────────────────┤
│ │
│ 10 │ MARKET-WIDE / UNIVERSAL │
│ │ • All customers affected │
│ │ • Entire company impacted (all departments) │
│ │ • Industry-wide visibility │
│ │ • Systemic across all systems │
│ │ Response: CEO ownership, board notification │
│ │ │
│ 9 │ ENTERPRISE-WIDE │
│ │ • Most customers affected │
│ │ • All or most departments impacted │
│ │ • Multiple interconnected systems │
│ │ • Cross-functional coordination required │
│ │ Response: C-suite ownership, all-hands │
│ │ │
│ 8 │ BROAD ORGANIZATIONAL │
│ │ • A large share of customers │
│ │ • Multiple departments │
│ │ • Core business systems │
│ │ • Major product lines affected │
│ │ Response: Executive steering committee │
│ │ │
│ 7 │ SEGMENT-WIDE │
│ │ • Entire customer segment (e.g., all enterprise) │
│ │ • Several departments affected │
│ │ • Critical business system │
│ │ • Key product line │
│ │ Response: VP-level ownership, cross-team │
│ │ │
│ 6 │ MULTI-TEAM / MULTI-CUSTOMER │
│ │ • Several customer groups │
│ │ • A few departments │
│ │ • Multiple related systems │
│ │ • Product feature set │
│ │ Response: Director-level, tiger team │
│ │ │
│ 5 │ DEPARTMENTAL / CUSTOMER SUBSET │
│ │ • A subset of customers │
│ │ • One department, multiple teams │
│ │ • Business-critical subsystem │
│ │ • Single product line │
│ │ Response: Manager-led, dedicated task force │
│ │ │
│ 4 │ TEAM-WIDE / CUSTOMER COHORT │
│ │ • A customer cohort │
│ │ • One team │
│ │ • Supporting system │
│ │ • Product module │
│ │ Response: Team lead, sprint allocation │
│ │ │
│ 3 │ SMALL GROUP / FEW CUSTOMERS │
│ │ • A few customers │
│ │ • A small group of people │
│ │ • Non-critical system │
│ │ • Feature subset │
│ │ Response: Individual contributor, backlog item │
│ │ │
│ 2 │ INDIVIDUAL / SINGLE CUSTOMER │
│ │ • One customer │
│ │ • One person affected │
│ │ • Isolated system component │
│ │ • Edge case scenario │
│ │ Response: Standard support, ticket workflow │
│ │ │
│ 1 │ ISOLATED / THEORETICAL │
│ │ • Hypothetical scenario │
│ │ • No one currently affected │
│ │ • Test environment only │
│ │ • Not yet deployed │
│ │ Response: Log for monitoring, no action │
│ │ │
└──────────────────────────────────────────────────────────┘The scale is a judgment rubric, not a formula. Earlier versions of this page converted percentages into Space scores and applied timing, detection and business-hours multipliers. Those conversions and multipliers were invented and have been removed. Count what you can, write the count down with its source, and pick the level that fits.
Space Scoring by Dimension
D1: Customer (PerchIQX)
Population metric: How many customers are affected, and how much revenue they carry
| Space | Customers Affected | Example |
|---|---|---|
| 10 | All customers | Platform outage affecting all users |
| 9 | Most customers | Core feature failure |
| 8 | A large share of customers | Major product line issue |
| 7 | One whole segment (e.g., all enterprise) | Enterprise-tier bug |
| 6 | Several customer groups | Feature used by a subset |
| 5 | A subset of customers | Product module issue |
| 4 | A customer cohort | Integration affecting some customers |
| 3 | A few customers | Small cohort problem |
| 2 | One customer | Individual account issue |
| 1 | None yet (potential) | Hypothetical scenario |
Revenue concentration: In some businesses, a few customers carry much of the revenue. If the affected customers are few but large, score Space higher than the head count suggests, and say why.
D2: Employee (PerchIQX)
Population metric: How many employees and teams are affected
| Space | Employees Affected | Teams Affected | Example |
|---|---|---|---|
| 10 | All employees | Entire organization | Company-wide policy change |
| 9 | Most employees | Most departments | Benefits system outage |
| 8 | A large share of employees | Multiple divisions | Shared service disruption |
| 7 | One division | All teams in division | Division restructuring |
| 6 | Multiple teams | A few departments | Cross-functional tool failure |
| 5 | One department | Multiple teams | Department-specific issue |
| 4 | One team | Single team | Team morale issue |
| 3 | A small group | Subset of team | Project-specific stress |
| 2 | One person | Individual | Single employee issue |
| 1 | No one (potential) | N/A | Hypothetical workforce scenario |
Critical roles: If the affected people hold critical roles (a single point of failure, an executive, a rare specialist, a high-visibility customer-facing role), one person can carry wide scope. Score Space higher and record the reason.
D3: Revenue (PerchIQX)
Population metric: How much of the revenue base is at risk
| Space | Revenue at Risk | Example |
|---|---|---|
| 10 | Company-wide revenue | Existential crisis (bankruptcy) |
| 9 | Most revenue streams | Payment processing failure |
| 8 | A major revenue category | Core product line defect |
| 7 | A significant segment | Enterprise customer concentration |
| 6 | Material revenue | Product line underperformance |
| 5 | Moderate revenue | Feature set revenue impact |
| 4 | A small revenue subset | Minor product revenue |
| 3 | Minimal revenue | Niche offering |
| 2 | A single deal or customer | One contract at risk |
| 1 | Hypothetical revenue | Future opportunity (not yet revenue) |
Timing: Revenue at risk this quarter is a wider problem today than revenue at risk next year. Note when the exposure lands; trajectory over time belongs to the Time lens.
D4: Regulatory (PerchIQX)
Population metric: Scope of compliance impact (processes, systems, jurisdictions)
| Space | Regulatory Scope | Example |
|---|---|---|
| 10 | All operations, all jurisdictions | Company-wide license suspension |
| 9 | Multiple jurisdictions, core operations | Multi-state regulatory action |
| 8 | One jurisdiction, all operations | State-level enforcement (all facilities) |
| 7 | Multiple facilities/divisions | Regional compliance failure |
| 6 | One division, multiple processes | Division-specific audit failure |
| 5 | One department, core process | Critical process non-compliance |
| 4 | One process, multiple locations | Standard process deviation |
| 3 | One location, one process | Isolated compliance gap |
| 2 | Single instance, remediable | Documentation missing (one record) |
| 1 | Hypothetical exposure | Proactive gap assessment |
Public disclosure: A regulatory issue that becomes public reaches further than one that stays internal. Peers knowing, a public filing, and media coverage each widen the scope. Score Space higher as visibility grows, and cite the disclosure.
D5: Quality (PerchIQX)
Population metric: Units or systems affected, and customer exposure
| Space | Quality Scope | Example |
|---|---|---|
| 10 | All production, all customers | Systemic design flaw, recall |
| 9 | All production, most customers | Manufacturing process failure |
| 8 | Major batch/release | Release version defect |
| 7 | One product line, all customers | Product-specific issue |
| 6 | Multiple batches/releases | Batch defect |
| 5 | One batch/release | Release-specific bug |
| 4 | Subset of production | Configuration-specific defect |
| 3 | Small batch | Lot-specific issue |
| 2 | Single unit, one customer | Individual unit failure |
| 1 | Test environment only | Caught before release |
Detection point: A defect caught in internal QA has reached fewer people than one found by customers in the field. Score the scope that actually reached people, and note where it was caught.
D6: Operational (PerchIQX)
Population metric: Systems, processes, departments affected
| Space | Operational Scope | Systems Affected | Example |
|---|---|---|---|
| 10 | Entire operation halted | All critical systems | Complete infrastructure failure |
| 9 | Most operations affected | Core systems + dependencies | Data center outage |
| 8 | Cross-functional impact | Multiple core systems | ERP system failure |
| 7 | One division, all processes | Division-critical systems | Division-wide system outage |
| 6 | Multiple departments | A few shared systems | Collaboration tool outage |
| 5 | One department, all processes | Department-critical system | Department system failure |
| 4 | One department, one process | Supporting system | Reporting system outage |
| 3 | One team, multiple processes | Team-specific tools | Team productivity tool issue |
| 2 | One team, one process | Single tool/system | Individual app malfunction |
| 1 | Test/dev environment | Non-production | Sandbox issue |
Timing: An outage during peak hours reaches more people than the same outage during a planned maintenance window. Score who was actually affected.
Scope Measurement Techniques
Population Counting
Direct count: Count the affected people, customers or systems, and the total. Write both down with their source. The count is evidence; the Space score is your reading of it.
System Coverage
Dependency analysis:
┌──────────────────────────────────────┐
│ System A (affected) │
│ ├── Used by: Dept 1, Dept 2, Dept 3│
│ └── Dependencies: System B, System C│
│ │
│ Reach: 3 departments │
│ 2 downstream systems │
│ Space Score: 6 │
└──────────────────────────────────────┘Revenue Weighting
For customer and revenue dimensions, look at both the head count and the revenue those customers carry. When they point in different directions, say which one drove your score.
Multi-Dimensional Scope
When a problem affects multiple dimensions, score Space for each separately:
Example (hypothetical): Billing system outage
Customer (D1):
All customers unable to view invoices
Space = 10 (all customers)
Employee (D2):
Finance and support teams involved
Space = 4 (two teams)
Revenue (D3):
Payment processing delayed across all revenue flow
Space = 10 (all revenue streams)
Operational (D6):
Billing system + dependencies (CRM, reporting)
Space = 7 (core business system)Don't average. Each dimension has its own Space score.
Scope Amplification Over Time
Scope can expand if not contained:
First: System outage (Space 5, one department)
Then: Dependencies fail (Space 7, cross-functional)
Later: Customers notice (Space 9, most customers affected)Lesson: High Space scores demand containment to prevent further spread.
Scope vs. Urgency
Space (PerchIQX) is NOT the same as Sound (ChirpIQX):
| Scenario | Sound (Urgency) | Space (Scope) | Interpretation |
|---|---|---|---|
| CEO resignation | 9 | 2 | Urgent but isolated (1 person) |
| Company-wide email outage | 7 | 10 | Moderate urgency but everyone affected |
| Single customer lawsuit | 9 | 2 | Urgent but narrow scope |
| Gradual quality trend | 4 | 8 | Low urgency but broad impact |
Strategy:
- High Sound, Low Space: Rapid response, narrow team
- High Sound, High Space: All-hands, war room
- Low Sound, High Space: Systematic improvement, long-term plan
- Low Sound, Low Space: Backlog, standard workflow
PerchIQX Scoring Checklist
□ How many customers/people/systems are affected? (Count)
□ What percentage of total population? (Calculate %)
□ Is there revenue concentration? (Consider it and say why)
□ Are critical roles/systems involved? (Score higher and note it)
□ Is this publicly visible? (Score higher and cite it)
□ What's the timing? (Peak hours vs. off-hours)
□ Has scope grown since detection? (Rescore if expanded)
Base Space: ___
Reasons for the score: ___
───────────────
Final Space: ___Common Space Scoring Mistakes
| Mistake | Impact | Correction |
|---|---|---|
| Confusing count with share | Overestimates scope | Compare the count with the total population |
| Ignoring revenue concentration | Misses concentration risk | Look at revenue as well as head count |
| Ignoring critical roles | Underestimates impact | Note when one person carries wide scope |
| Averaging across dimensions | Loses dimension-specific detail | Score each dimension separately |
| Static scoring (not updating) | Misses scope expansion | Rescore as scope changes |
Next Steps
Remember: The cormorant doesn't dive for a single fish when the whole school is there. Assess the full scope. 🪶