deciqAI Resource Integration Hierarchy
Overview
Most organizations operate well below their potential resource access. The limiting factor is rarely that resources don't exist — it's that the problem-solving posture excludes resources not yet allocated. Four fundamentally different mindsets about what is "available" produce categorically different outcomes. Level 4 isn't smarter — it just treats more things as available.
Composition: WITH [three-radius-model] (skills-2) — explains WHY someone is at a lower level. BEFORE [resource-time-compression] (skills-2) — that skill requires Level 4 posture. AFTER [hidden-elite-advantages] (skills-2) — resource integration is one of nine hidden advantage dimensions.
When to Use
- Individual or team repeatedly cannot resolve a class of problems despite apparent capability
- Coaching a manager to identify the specific developmental gap blocking next-level performance
- Designing a capability development program; distinguishing which level each role requires
- Organization's problem-solving culture is consistently reactive rather than proactive or generative
When NOT to use: purely technical skill gap; organizational structure blocks Level 3–4 behavior (fix structure first); near-term output optimization is the goal.
Coaching Novices (Adaptive Front Door)
- Engine mode: concrete case → run The Process directly.
- Coach mode: "I've hit a ceiling" or unfamiliar → guide step by step.
In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.
- What-it-is: four-level map of how people relate to resource availability — Level 4 treats more things as "available," not smarter.
- Check fit: describe your most significant unsolvable problem in the past three months — was the blocker budget, authority, skill, or not knowing external resources existed?
- Elicit real case: specific moment when you felt limited — did you consider resources outside allocated budget or formal authority? If not, why?
[WAIT — do not advance until user responds]
- Run The Process step by step — assess level, identify N+1 behaviors, diagnose blocker, design one experiment.
[WAIT — do not advance until user responds]
- Close: name the blocker and the one Level N+1 experiment they will run in 30 days.
[WAIT — do not advance until user responds]
The Process
Step 1 — Assess current level (behavioral evidence, not aspiration): L1: compliance — executes, reports upward. L2: sees and solves problems with allocated resources. L3: proactively scans before problems materialize; designs solutions in advance. L4: actively seeks, creates, and combines external/unallocated/latent resources into new configurations.
Step 2 — Identify N+1 behaviors absent: L1→L2: identify problems independently. L2→L3: scan before problems manifest. L3→L4: access resources outside budget and formal authority; create new combinations.
Step 3 — Diagnose blocker: Skill (training) | Access (network/structural) | Habit (deliberate practice) | Permission (org change required first).
Step 4 — Design one N+1 experiment (30 days): L1→L2: propose a solution to a self-identified problem. L2→L3: design a prevention mechanism. L3→L4: access one external, unallocated resource (person, relationship, capability, data).
Step 5 — Reflect: Did resource access create value? What made N+1 harder than N? What would make it the default posture?
Gate: Diagnose blocker type before designing experiments. Stop-rule: If the experiment resource is within current budget/headcount, it has not left Level 2–3.
Output: Integration Level Diagnostic
Person/Team:___ Role:___ Date:___ Assessed level: [1/2/3/4]
Behavioral evidence: 1.___ 2.___ 3.___
N+1 behaviors absent: 1.___ 2.___ 3.___
Primary blocker: [skill/access/habit/permission] Addressable at: [individual/structural/org]
30-day experiment:___ Resource NOT in budget/headcount:___ Success metric:___
Reflection: Value created?[y/n] Harder because:___ What would make N+1 default:___
→ Method in Action: Florence Nightingale's Level Transitions at Scutari Hospital (1854–1856)
Integration Hierarchy Packs
Organizational Leadership Development: Most programs address skill gaps (Level 2) without the Level 3→4 posture gap. Roles must explicitly expect resource generation. Contribution: CHROs, leadership development designers, executive coaches. Startup and Founder: Founders must operate at Level 4 as baseline — no resource is pre-allocated. Founders who achieve PMF often regress as the org formalizes; this hierarchy corrects that. Contribution: founders, startup coaches, venture partners. Complex Problem-Solving: Complex problems cannot be resolved within existing resource boundaries — Level 4 posture is required by definition. Most orgs apply Level 2 allocations to Level 4 problems. Contribution: policy designers, systems change practitioners, innovation lab leaders.
Applying It Well
- Assess actual level from behavioral evidence, not aspiration — "what did you actually do last time?"
- Diagnose the blocker type before designing development — skill/access/habit/permission require different interventions.
- Use situationally, not as a personality label — same person operates at different levels in different domains.
- Protect Level 4 time structurally and reward it explicitly — orgs that fill every calendar with L2–3 demands and punish initiative cannot develop Level 4 posture.
→ Primary sources: references/sources.md
Common Rationalizations
[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.
| Fake move | Reality |
|---|---|
| [D] "I don't have budget — I'll escalate." | Escalation is Level 2. Level 4 identifies external resources that don't require budget. |
| [D] "This is outside my authority." | Authority limits are often smaller than the actual permission space. Level 4 uses relationship pathways. |
| [D] "We're using all available resources." | "Available" = current search scope. Level 4 expands it: public funding, uninitialized partnerships, unaccessed data. |
| [D] "Finding external resources takes time I don't have." | Level 3–4 actors invest in resource mapping during stable periods so access exists during crises. |
| [D] "My org doesn't support that kind of access." | Legitimate permission blocker — name it as such. Some access exists even in restrictive orgs. |
| [D] "I tried it but it didn't work." | One failed experiment is a data point. Diagnose why before concluding Level 4 is inaccessible. |
| [D] "I'm a Level 4 thinker." / "We need a bigger budget." | Name three resources from the last 90 days outside budget/headcount. Empty list = not Level 4. Budget is one resource type. |
| → Add [O] entries here after each real use — paste the actual failure pattern | What went wrong and why |
Red Flags
- Every solution involves allocated budget or headcount — Level 2 signature.
- Problems only surface in crisis mode — proactive scanning absent; Level 1–2 signature.
- External resource access always "goes through proper channels" — no direct relationship pathways.
- Resource vocabulary limited to "budget" and "headcount" — Level 4 uses relationships, data, reputation, public funding, narrative.
- Self-evolution framing for structural problems — Level 2–3 tools applied to Level 4 problems.
Verification
- Level assessed from behavioral evidence (three specific examples), not self-report
- N+1 behaviors identified specifically (observable, not "be more proactive")
- Blocker type diagnosed (skill/access/habit/permission) — not assumed to be skill
- 30-day experiment uses a resource outside current budget and headcount
- Stop-rule applied; blocker-specific intervention selected; permission blockers identified before individual targets set
Part of deciqAI Knowledge Skills — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/resource-integration-hierarchy · Built by deciqAI · github.com/deciqAI · Contributions welcome.
Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/resource-integration-hierarchy.json