Skip to content

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

SpaceCustomers AffectedExample
10All customersPlatform outage affecting all users
9Most customersCore feature failure
8A large share of customersMajor product line issue
7One whole segment (e.g., all enterprise)Enterprise-tier bug
6Several customer groupsFeature used by a subset
5A subset of customersProduct module issue
4A customer cohortIntegration affecting some customers
3A few customersSmall cohort problem
2One customerIndividual account issue
1None 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

SpaceEmployees AffectedTeams AffectedExample
10All employeesEntire organizationCompany-wide policy change
9Most employeesMost departmentsBenefits system outage
8A large share of employeesMultiple divisionsShared service disruption
7One divisionAll teams in divisionDivision restructuring
6Multiple teamsA few departmentsCross-functional tool failure
5One departmentMultiple teamsDepartment-specific issue
4One teamSingle teamTeam morale issue
3A small groupSubset of teamProject-specific stress
2One personIndividualSingle employee issue
1No one (potential)N/AHypothetical 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

SpaceRevenue at RiskExample
10Company-wide revenueExistential crisis (bankruptcy)
9Most revenue streamsPayment processing failure
8A major revenue categoryCore product line defect
7A significant segmentEnterprise customer concentration
6Material revenueProduct line underperformance
5Moderate revenueFeature set revenue impact
4A small revenue subsetMinor product revenue
3Minimal revenueNiche offering
2A single deal or customerOne contract at risk
1Hypothetical revenueFuture 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)

SpaceRegulatory ScopeExample
10All operations, all jurisdictionsCompany-wide license suspension
9Multiple jurisdictions, core operationsMulti-state regulatory action
8One jurisdiction, all operationsState-level enforcement (all facilities)
7Multiple facilities/divisionsRegional compliance failure
6One division, multiple processesDivision-specific audit failure
5One department, core processCritical process non-compliance
4One process, multiple locationsStandard process deviation
3One location, one processIsolated compliance gap
2Single instance, remediableDocumentation missing (one record)
1Hypothetical exposureProactive 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

SpaceQuality ScopeExample
10All production, all customersSystemic design flaw, recall
9All production, most customersManufacturing process failure
8Major batch/releaseRelease version defect
7One product line, all customersProduct-specific issue
6Multiple batches/releasesBatch defect
5One batch/releaseRelease-specific bug
4Subset of productionConfiguration-specific defect
3Small batchLot-specific issue
2Single unit, one customerIndividual unit failure
1Test environment onlyCaught 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

SpaceOperational ScopeSystems AffectedExample
10Entire operation haltedAll critical systemsComplete infrastructure failure
9Most operations affectedCore systems + dependenciesData center outage
8Cross-functional impactMultiple core systemsERP system failure
7One division, all processesDivision-critical systemsDivision-wide system outage
6Multiple departmentsA few shared systemsCollaboration tool outage
5One department, all processesDepartment-critical systemDepartment system failure
4One department, one processSupporting systemReporting system outage
3One team, multiple processesTeam-specific toolsTeam productivity tool issue
2One team, one processSingle tool/systemIndividual app malfunction
1Test/dev environmentNon-productionSandbox 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):

ScenarioSound (Urgency)Space (Scope)Interpretation
CEO resignation92Urgent but isolated (1 person)
Company-wide email outage710Moderate urgency but everyone affected
Single customer lawsuit92Urgent but narrow scope
Gradual quality trend48Low 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 ​

MistakeImpactCorrection
Confusing count with shareOverestimates scopeCompare the count with the total population
Ignoring revenue concentrationMisses concentration riskLook at revenue as well as head count
Ignoring critical rolesUnderestimates impactNote when one person carries wide scope
Averaging across dimensionsLoses dimension-specific detailScore each dimension separately
Static scoring (not updating)Misses scope expansionRescore as scope changes

Next Steps ​

⏱️ WakeIQX (Time) — Analyze trajectory and momentum

🔊 ChirpIQX (Sound) — Understand urgency scoring

📊 Scoring Methodology — Apply Space in full 3D scoring

🔍 Observable Properties — Detect signals across scope levels


Remember: The cormorant doesn't dive for a single fish when the whole school is there. Assess the full scope. 🪶