A foundational principle that guides decisions
A strategic pillar is one of the small number of enduring focus areas a strategy stands on, durable enough to survive several planning cycles without rewriting. Where a goal expires every quarter, a pillar holds for years, naming a domain the organisation has decided to be good at. Its value is compression. A company with dozens of goals and hundreds of projects can describe its whole strategy in three or four words a new hire remembers on day one. The riskRiskComplianceA risk to the product or businessView reference → is the inverse: a pillar so broad it could justify anything has chosen nothing.
Unlike OKRs or value streamsValue StreamStrategyAn end-to-end flow delivering value to the customerView reference →, the strategic pillar has no single inventor or founding text. It emerged from general strategic-planning practice as a convenient name for the layer between a company's missionMissionStrategyThe purpose and reason the product existsView reference → and its quarterly goals. Strategy consultancies, planning tools, and operating-model frameworks adopted it independently, which is why its synonyms multiplied: strategic priorities, focus areas, mission-critical objectivesObjectiveStrategyA strategic goal (OKR)View reference →, and in some shops simply "pillars."
Practitioner literature converges on a stable definition even without a canonical source. Pillars are described as the three to five priority areas that define where an organisation will focus to achieve its mission, sitting between the visionVisionStrategyA long-term aspirational statement of the future stateView reference → and the OKR layer and providing a framework that does not change every quarter. The recurring claim is that pillars simplify complexity by grouping many goals and projects into a few coherent areas, making strategy easier to communicate and to remember.
The relationship to strategic themesStrategic ThemeStrategyA high-level strategic focus area for a planning periodView reference → is where usage diverges. Some frameworks treat the two as synonyms; others, and the Unified Product Graph among them, place the pillar above the themeThemeProduct SpecificationA strategic grouping of related featuresView reference →, with the pillar holding a multi-year horizon and the theme holding the focus for a given cycle underneath it. The settled idea across all variantsVariantGrowthA variant in an A/B testView reference → is one of altitude and durability. A pillar is the highest-level, longest-lived organising unit a team can act on directly, below the vision but above anything that gets measured each quarter.
A consumer fintech writes its three-year strategy as three pillars: "Trust," "Effortless money movement," and "Reach the underbanked." None mentions a featureFeatureProduct SpecificationA product capability or featureView reference →, a metricMetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →, or a date, on purpose. Each carries an owner at the executive level and a narrative success indicator: for Trust, "regulators and users treat us as the safe default."
The pillars route decisionsDecisionStrategyA recorded decision with context, rationale, and consequencesView reference → for years, not weeks. A proposed crypto-trading feature is exciting and on-trend, and it fits none of the three, so it is declined without a long debate, because the pillars already encode that this is not who the company is trying to be. Underneath "Reach the underbanked," themes rotate each year (this year, no-fee accounts; next year, cash-deposit access) while the pillar holds steady. That steadiness is what lets teams plan multi-year capabilityCapabilityStrategyAn ability that enables value deliveryView reference → investment without fearing the strategy will move beneath them.
In the Unified Product Graph, Strategic PillarStrategyA foundational principle that guides decisions is the hub of the Strategy & OutcomesOutcomeStrategyA desired business or user outcomeView reference → region, the point where enduring strategy fans out into action. It is supported from above by strategic_pillarMissionsupported byStrategic Pillarhierarchy and mission_supported_by_strategic_pillarProductstands onStrategic Pillarsemantic, and it organises everything below through product_stands_on_strategic_pillarStrategic PillarorganisesStrategic Themehierarchy, strategic_pillar_organises_strategic_themeStrategic PillarenablesCapabilityhierarchy, and strategic_pillar_enables_capabilityStrategic PillardeliversValue Streamhierarchy. strategic_pillar_delivers_value_streamStrategic Pillardecided viaDecisionhierarchy records the reasoning that set it, and strategic_pillar_decided_via_decisionInsightvalidatesStrategic Pillarcross-domain lets evidenceEvidenceValidationData supporting or refuting a hypothesisView reference → from research confirm or challenge it. Modelling the pillar as the layer above themes encodes the durability distinction structurally: pillars persist while the themes beneath them rotate, and the graph shows which long-lived bet a short-lived theme is serving.insight_validates_strategic_pillar
Type-specific fields on BaseNode
ownerstringOwning person or team
descriptionstringNarrative of the pillar's intent
scopestringWhat this pillar covers
time_horizonstringPlanning horizon. Typically multi-year. @example "3 years", "2026-2028"
success_indicatorstringHow the business knows the pillar is on track. Narrative, not a metric edge.
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
3 phases — initial: proposed
8 edge types connected to this entity.
mission_supported_by_strategic_pillarstrategic_pillar_organises_strategic_themestrategic_pillar_enables_capabilitystrategic_pillar_delivers_value_streamstrategic_pillar_decided_via_decision