--- title: "North Star & Cloud Goals" description: "How to define a strategic North Star that aligns investment decisions, priorities and governance across the entire transformation." sidebar: order: 1 label: "North Star & Cloud Goals" source_url: "https://framework.stackit.cloud/advisory/cloud-vision-and-strategy/north-star/" source_file: "docs/advisory/cloud-vision-and-strategy/north-star.mdx" --- ## Cloud drivers: why does the need for action arise at all? Before a North Star can be formulated, there needs to be honest clarity about the factors forcing or triggering change. These drivers are often not controllable — they come from the outside or arise from internal developments that can no longer be ignored. Typical external drivers include expiring data centre contracts, end-of-life systems without vendor support, increasing regulatory requirements (GDPR, NIS2, DORA), geopolitical developments raising sovereignty questions, and competitive pressure from technological change. Internal drivers frequently arise from growing capacity demand, rising infrastructure costs, operational burden of legacy IT, or the inability to respond quickly to new business requirements. Why is this analysis important? Because the dominant driver determines which North Star is credible. An organisation primarily driven by compliance pressure has different urgency than one driven by innovation goals. The driver analysis protects against formulating a cloud strategy that misses the actual problem pressure. ## Cloud motivation: which goals are to be achieved? From the identified drivers, strategic objectives are derived. These objectives are the link between the pressure to act and the North Star: they describe what the organisation specifically wants to achieve with the cloud. Typical strategic objectives include improving the IT cost structure, increased innovation capability, reduced time-to-market, enabling new digital business models, improved global availability of IT services, reducing IT landscape complexity, and building experimentation capability. These goals are not abstract — they must be concrete enough to be translated into measurable KPIs. ## Cloud principles: guiding rules for all decisions Cloud principles are fundamental guiding rules by which architecture, technology, and implementation decisions are made. They create consistency: when a team faces a decision, the principles provide clear orientation without every situation needing individual escalation. | Principle | Meaning | | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **Cloud First** | New applications are implemented as cloud solutions unless there are compelling reasons against it. | | **Prefer Managed Services** | Managed services reduce operational effort and improve scalability — they are preferred by default over self-operated alternatives. | | **Standardisation over Customisation** | Cloud services are used in the most standardised way possible to reduce complexity and increase reusability. | | **Automation First** | Infrastructure and platform components are provisioned and operated through automation — not manual clicks. | | **Infrastructure as Code** | Infrastructure is defined declaratively as code, versioned, and automatically provisioned. | | **Security & Compliance by Design** | Security and compliance requirements are integrated into architecture and implementation from the start, not added retroactively. | These principles are not recommendations — they are binding guardrails by which the CCoE evaluates architectural decisions and demands justification for deviations. ## The Cloud Vision Statement The Cloud Vision describes the target state of the future IT landscape. It is derived from the business and IT strategy and defines the role of cloud technologies in the evolution of the organisation's IT capabilities. > The cloud will serve as the central platform for the development and operation of the organisation's digital applications and services. Applications will primarily be operated on automated and scalable cloud platforms using managed services and standardised platform services. The use of open technologies, standardised platforms, and automation enables reduced operational effort and increased flexibility. This creates a secure, scalable, and future-ready IT landscape that supports digital business models and innovation. This vision statement is more than a technological description — it is a strategic positioning. It answers why the cloud is chosen and creates the connection between IT decisions and business objectives. Leaders at all levels must understand this target state and actively represent it for the transformation to succeed. A Cloud Vision Statement has three essential functions: it aligns the organisation on a common target state, creates legitimacy for investment and prioritisation decisions, and serves as a benchmark against which progress can be regularly assessed. ## What is a cloud North Star? The North Star is a single, precise statement that answers: _why are we doing this?_ It is not a technology description — it is a business strategy statement. **Weak North Stars (technology-focused):** - "We will migrate 80 % of our workloads to the cloud." - "We will use Kubernetes for all applications." **Strong North Stars (business-focused):** - "We will become the most digitally sovereign automotive supplier in the DACH region — and use that as a differentiator against competitors dependent on US cloud." - "We will reduce our time to market for new digital products from 9 months to 6 weeks." - "We will create the technical foundation to bring our data platform to production-readiness within 24 months." The difference: a strong North Star is understandable to the CFO without technical explanation. ## The cloud strategy framework: four levels The strategy framework has four levels. Level 1 — Why (North Star): what business purpose does the cloud transformation serve? This answer must be expressible in one sentence. Level 2 — What (Strategic Goals): 3–5 measurable goals that operationalize the North Star and can be translated into KPIs. Level 3 — How (Strategic Decisions): sovereignty strategy, provider selection, operating model — the foundational decisions that shape all downstream choices. Level 4 — Who and When (Roadmap): workload prioritisation, phase planning, resource plan — the operationalization of the How. ## Strategic goal categories Every cloud strategy serves a combination of four goal categories: | Category | Example goals | Primary stakeholder | | ---------------------------- | ----------------------------------------------------------- | ------------------- | | **Agility** | Time-to-market reduction, shorter deployment cycles | CEO, CDO | | **Cost efficiency** | TCO reduction, CAPEX→OPEX shift, FinOps maturity | CFO | | **Sovereignty & compliance** | GDPR compliance, Cloud Act immunity, TISAX certification | CISO, DPO, Legal | | **Resilience & stability** | SLA improvement, disaster recovery capability, availability | CTO, IT Operations | **Important:** Every organisation has a dominant goal category — this determines which cloud decisions are prioritised. An organisation primarily pursuing sovereignty makes different provider decisions than one primarily pursuing agility. ## KPI framework: how do you measure transformation success? Without measurement, cloud transformation is an act of faith. The KPI framework makes it an accountable investment. ### Level 1: Strategic KPIs (Board/CEO) | KPI | Baseline measurement | 24-month target | | ------------------------------------------------------ | -------------------- | ---------------------------- | | Time to market for new digital features | Measure today | 50 % reduction | | IT operating costs as % of revenue | Measure today | 15 % reduction | | Share of workloads on sovereign cloud | 0 % | Organisation-specific target | | Compliance incidents (data protection, audit findings) | Measure today | Trend: declining | ### Level 2: Transformation KPIs (CIO/CTO) | KPI | Baseline measurement | 24-month target | | ---------------------------------------- | ---------------------- | ---------------------------- | | Deployment frequency (deployments/week) | Measure today | 5× improvement | | Lead time for changes | Measure today | 70 % reduction | | Cloud cost efficiency (spend vs. budget) | Baseline after month 3 | ±5 % budget accuracy | | Employees with cloud certification | Measure today | Min. 1 per 5 technical staff | ### Level 3: Operational KPIs (IT Operations/Platform Team) | KPI | Baseline measurement | Target | | ---------------------------- | -------------------- | --------------------- | | Mean Time to Recovery (MTTR) | Measure today | 50 % reduction | | Guardrail compliance rate | N/A (baseline) | >99 % | | Resource tagging compliance | 0 % | 100 % new resources | | Unused resources (waste) | 0 % (baseline) | \<5 % of cloud budget | ## The cloud vision statement template A strong cloud vision statement answers three questions in 3–4 sentences: what we want to become (target state), why this matters for our business, and what distinguishes our approach (e.g. sovereignty). > "[Organisation] will by [date] become a cloud-native organisation that [achieves business goal]. We will use primarily sovereign cloud infrastructure [provider/approach] because [strategic reason — e.g. regulatory requirements, competitive differentiation, data protection]. We measure our success by [2–3 top KPIs]." ## The Cloud Strategy Board: who decides? A cloud strategy without a decision-making body is a document without mandate. The Cloud Strategy Board is the governance body that adopts and regularly reviews the cloud strategy, serves as the escalation path for architecture decisions with strategic relevance, takes investment decisions above the CCoE mandate, and evaluates transformation progress against KPIs quarterly. Details on the Strategy Board are in [Cloud Strategy Board](/advisory/cloud-vision-and-strategy/strategy-board). ## Practical steps 1. **Cloud vision workshop** (1 day, C-level + IT leadership): develop North Star and strategic goals together 2. **Establish KPI baseline**: all starting measurements for the KPI framework in the first 4 weeks 3. **Adopt the cloud vision statement**: formally resolved by the Cloud Strategy Board 4. **Communicate internally**: CEO communication to the entire organisation