The Problem
Most organisations cannot articulate why they exist, how they measure progress, what they are doing about it, or what they have produced. Their strategy lives in slide decks reviewed annually. Their metrics live in dashboards nobody checks. Their projects live in task managers disconnected from strategic intent. Their outputs accumulate without coherent narrative.
The result: organisations that are opaque to themselves and illegible to everyone else. Partners cannot reference their approach. Investors cannot verify their progress. Collaborators cannot build upon their work. The organisation cannot cite its own strategic logic because that logic was never made structurally explicit.
CITAble™: The Framework
CITAble™ structures organisational execution into seven bands arranged in two registers. The four content bands (Context, Indicators, Tactics, Artifacts) form the concentric rings visualised on the CITAble Radar. The remaining three (Brand, Legal, Ecosystem) form the internal enablement layer: the expression, the private-internal record, and the network that support and annotate the content bands.
Content Bands: The Strategy Visualised on the Radar
| Band | Question Answered | Contains | Change Cadence |
|---|---|---|---|
| Context | What is the problem, why does it matter, and who is affected? (3W) | Problem definition, stakeholder profiles, evidence of impact. Purely diagnostic; no solutioning. | Quarterly |
| Indicators (Strategy) | Given our context, what direction do we take and how do we measure it? | Strategic positioning, business model, audience segmentation, OKRs, KPIs, derailment signals. Strategy derives from Context and drives Indicator selection. | Weekly/monthly |
| Tactics | When, where, and how do we execute? (2W1H) | Execution plans, campaign schedules, sprint scopes, partnership activations. Time-bounded, goal-linked. | Daily |
| Artifacts | What are we working on, and what has this produced? | All work at any progress stage: active, in-progress, completed, shelved. Curated public-proof artifacts are highlighted within. | Ongoing |
Internal Enablement: What Makes the Content Bands Possible
| Band | Question Answered | Contains | Relationship to the content bands |
|---|---|---|---|
| Brand | How do we present ourselves? | Voice guidelines, messaging hierarchy, brandscripts, pitches, visual identity | Expresses Context externally; shapes how Artifacts are communicated |
| Legal | What are the entity, contractual, and IP details? | Entity structure, agreements, IP filings, corporate records. The private-internal side of the business. | Underwrites Tactics and Artifacts; kept internal, never shared externally |
| Ecosystem | Who is in our network? | People, organisations, and roles: coalition partners, connections, and competitive players, optionally organised by city | Identifies the resources strategy can unlock (Indicators) and the competitive field (where Tactics deploy) |
Context as Problem-First Space
The Context band is strictly a problem-first space. It answers: What is the problem? Why does it matter? Who is affected? No solutioning, positioning, or strategic direction lives here. This keeps the foundational understanding grounded in reality rather than aspiration.
Personas and stakeholder profiles that answer “who is affected by this problem?” live in Context. These are the people whose pain the organisation addresses. The competitive field, coalition partners, and network connections live in Ecosystem (these describe who else is in the space around the problem, not the problem itself). Problem research also lives in Context; broader market and technical research lives in Artifacts as research output.
Strategy occupies the space between Context and Indicators. It derives from the problem understanding in Context and drives the selection of metrics in Indicators. By housing strategy with Indicators rather than Context, the problem-first integrity of the Context band is preserved.
Context Enrichment Progression
The Context layer supports a recommended enrichment progression that deepens problem understanding over time. Each layer builds on the previous, but Strategy can begin at any point once the core Three Ws exist:
| Layer | Methodology | What It Adds to Context |
|---|---|---|
| Three Ws (Core) | Problem observation | What problems/phenomena/patterns exist; why each matters; who is affected |
| Problem-First Research | Four-Dimensional Analysis | Temporal analysis, failure archaeology, causal structure, evidence-backed depth |
| Compelling Questions | Bold Ambition + Constraints | Can’t Because (barriers) and Can If (required conditions for success) |
| Innovation Challenges | Solution-agnostic challenge design | Evaluation criteria, success metrics bridge, public challenge specification |
This progression is iterative, not waterfall. An organisation can formulate initial strategy from sparse Three Ws, conduct problem research that reveals new dimensions, revise strategy accordingly, formulate Compelling Questions from the research gaps, revise again, and so on. The iterative loop between Context enrichment and Strategy revision is a design feature: it mirrors how genuine understanding develops through cycles of investigation and reflection rather than through a single pass.
The enrichment progression also creates a natural content pipeline. Research produces essays and papers (published on the personal research platform). Design briefs compress that research. Innovation Challenges deploy it on organisational platforms. Each piece is independently valuable and independently citable, while together they form a system of increasing precision about the problem space.
Artifacts: All Work, Curated Proof Highlighted
Earlier versions of this framework kept a separate Efforts band for “all work” alongside Artifacts for “the curated public subset.” In practice the two were constantly confused, and the split added overhead without adding clarity. The whole CITAble workspace for a business is itself one large effort, so a separate Efforts band is redundant.
Artifacts now holds all work at every stage. Curated, public-facing proof is highlighted within the band rather than separated into its own folder:
- All work = the internal production record (everything the team is doing and has done)
- Highlighted artifacts = the external showcase (selected pieces that demonstrate capability, credibility, and progress)
This matters because not all work deserves public attention, but all public-facing proof must trace back to real work. An artifact graduates from working-record to public-proof by being marked for visibility, not by being moved. Public proof without work lineage is a hollow claim; work without curation stays invisible to the market. Keeping both in one band preserves the lineage.
The Mirroring of Context and Tactics
Context answers the foundational 3W: What is the problem? Why does it matter? Who is affected?
Tactics mirrors this at the execution layer as 2W1H: When do we execute? Where do we deploy? How do we accomplish it?
Context defines problem understanding. Strategy (housed with Indicators) translates that understanding into direction. Tactics operationalises that direction into time-bound, location-specific, method-explicit action plans. The quality of Tactics is measured by how directly they serve the Indicators, which in turn validate the strategic response to Context.
How Each Band Informs the Others
Context defines the problem. Strategy (in Indicators) responds to that problem with direction and metrics. Indicators reveal which Tactics to deploy. Tactics produce Artifacts. Artifacts feed back into Context: revised problem understanding, new evidence, updated stakeholder relationships.
Brand expresses how the content bands are communicated to the world. Legal underwrites the entity behind the work. Ecosystem maps the network that supplies resources and defines the competitive field.
Context ──informs──> Indicators (Strategy) ──reveals──> Tactics ──produces──> Artifacts [curated proof highlighted]
↑ │
└──────────────────────────── feeds back (new evidence, revised understanding) ─────────┘
Brand ──expresses──> Context + Artifacts (externally)
Legal ──underwrites──> Tactics + Artifacts (the entity behind the work)
Ecosystem ──supplies──> Indicators (resources to unlock) + Tactics (competitive field)The Duality: Running CITAble, Becoming CITAble
The framework operates on two registers simultaneously:
Running CITAble (practising the framework): the seven bands provide operational clarity. Every team member, AI agent, or collaborator can navigate from “what is the problem” through “what strategy responds to it” to “what are we doing about it” to “what have we shipped.” The structure eliminates the coordination overhead that scales with headcount in traditional organisations.
Becoming CITAble (achieving the quality): when all seven bands are running well, the organisation accumulates legible artifacts with clear strategic lineage. These artifacts are what observers can cite: publications traced to problem research in Context, products traced to Tactics informed by Indicators, partnerships traced to the Ecosystem network. The accumulation of legible artifacts with traceable lineage is what produces citability.
A CITAble business does not claim clarity; it demonstrates it through a body of referenceable work with visible strategic logic. The more completely the seven bands operate, the more CITAble the business becomes.
Time Evolution
Business strategy evolves. Contexts shift as markets move. Indicators reveal unexpected signals. Tactics succeed or fail. Artifacts accumulate, stall, or pivot. Networks reconfigure.
CITAble is valuable precisely because it tracks this evolution. A living CITAble structure creates a documented history of strategic intent and its outcomes: why decisions were made, what the indicators said at the time, which tactics were deployed, which network relationships informed those choices, and what they produced.
This historical record becomes a key asset for:
- Knowledge succession: new team members understand not just what the strategy is, but why it evolved to its current form
- Stakeholder communication: investors and partners can trace the logic of strategic shifts
- Honest retrospection: the organisation can audit its own decision-making quality over time
- Scenario planning: understanding how past context shifts affected all downstream bands informs responses to future shifts
The CITAble Radar provides a visual tool for exploring this temporal dimension. Where CITAble structures what information exists, the Radar renders the four content bands as a navigable, time-aware visualisation, with the Brand, Legal, and Ecosystem bands serving as annotations and background for items on the map.
Application to Founder-Led Organisations
CITAble is designed for the emerging category of founder-led organisations where small teams outperform large enterprises through AI-augmented operational clarity. The thesis: AI enables companies of tens to match the output of companies of thousands by eliminating bureaucratic and human-resource overhead.
In a Hybrid Intelligence environment, AI agents need structured context to operate effectively. CITAble provides that structure:
- Agents read Context for problem understanding before producing work
- Agents reference Indicators (Strategy) for direction and prioritisation signals
- Agents execute within Tactics (scoped, time-bounded, goal-linked)
- Agents deposit outputs into Artifacts (tracked, attributed, progress-visible), where selected pieces are highlighted as public proof
- Agents load Brand for voice and messaging when producing external content
- Agents reference Ecosystem for the network of partners and competitors
The framework makes operational assumptions explicit, reduces coordination overhead, and enables asynchronous human-AI collaboration at the organisational level. A single founder with a well-structured CITAble system and an AI agent fleet achieves the operational coherence that traditional organisations pursue through layers of management.
Practical Implementation
CITAble manifests as a folder architecture within each organisational workspace:
{Organisation}/
├── context/ # C — What, why, who (3W). Problem-first; no solutioning.
├── indicators-strategy/ # I — Strategy + derived metrics and signals
├── tactics/ # T — When, where, how (2W1H)
├── artifacts/ # A — All work at any stage (curated proof highlighted)
├── brand/ # B — Expression (voice, messaging, pitches)
├── legal/ # L — Entity, contracts, IP (private-internal)
├── ecosystem/ # E — People, organisations, roles (the network)
│ ├── people/
│ ├── organizations/
│ └── roles/
├── _calendar/ # Support: scheduling
└── _journal/ # Support: reflectionsAll seven CITAble bands are plain folders (first-class citizens in the architecture). Support folders use an underscore prefix (_calendar, _journal) to signal they sit outside the CITAble framework as operational utilities.
Note: Strategy lives with Indicators (not in Context) to preserve Context as a purely problem-first diagnostic space. The indicators-strategy/ folder houses both the strategic direction and the metrics derived from it.
Relationship to the CITAble Radar
The CITAble Radar is the visual exploration tool for a CITAble structure. The relationship:
- CITAble defines the operational framework: what information exists, where it lives, how it flows across seven bands
- CITAble Radar provides the banded visualisation: the four content bands render as navigable, interactive rings; the Brand, Legal, and Ecosystem bands render as thin decorative bands
- The Brand, Legal, and Ecosystem bands serve as annotations and background information for items displayed on the Radar
CITAble is the data model. The CITAble Radar is the instrument panel.
Both share the four-content-band structure and both emphasise temporal evolution as essential to strategic integrity. The CITAble Radar article details the visualisation itself: concentric rings, sector arcs, bidirectional traversal, and scenario simulation.
Key Properties
- Structures organisational execution into seven first-class bands (four content + three internal enablement)
- Produces organisational legibility (internal) and citability (external)
- Tracks time-evolution of strategic intent through documented history
- Designed for AI-augmented, founder-led micro-institutions
- Uses folder architecture as implementation (concrete, not merely conceptual)
- Bridges the gap between “what we believe” (Context) and “what we ship” (Artifacts)
- Scales through AI agents rather than headcount
- Holds all work in Artifacts, with curated public proof highlighted (no separate Efforts band)
- Mirrors Context’s 3W (what, why, who) with Tactics’ 2W1H (when, where, how)