Fill in the fields below, then save as PDF or print at A2 landscape.
Role
Platform Architect
Level 1
Unsatisfactory
Low
Individual
Impact
Fails to define or maintain the enterprise platform architecture - reference architectures, cloud-native standards, and technology governance are absent or incoherent.
Significant architectural decisions are made by senior platform engineers without Architect review, creating divergence and systemic risk across the platform estate.
Does not translate platform architectural concerns into business resilience or security risk language for executive audiences.
Examples
No platform technology radar produced in six months; senior engineers making independent tooling adoption decisions without governance.
Four cross-team architectural decisions were made without Architect review over the quarter, creating incompatible cloud account structures.
Dampeners
Was given an unclear mandate and no executive sponsorship, making it difficult to establish architectural authority.
Progression Signal
Produces a first version of the platform technology radar and establishes an architectural review process.
Begins engaging senior engineers in a governance conversation to restore architectural coherence.
Business Impact
Impact
Platform architectural incoherence creates technical debt and operational risk that compounds across every engineering team building on the platform.
Divergent cloud structures increase security compliance risk and make cost attribution and management difficult at organisational scale.
Examples
Incompatible cloud account structures created a compliance audit finding that required eight weeks of retroactive remediation work.
Dampeners
The compliance finding was resolved before external audit; the structural risk remains if the governance gap persists.
Progression Signal
Architectural governance re-established; new cross-team decisions are reviewed and aligned to enterprise standards.
Mid
Individual
Impact
Defines platform architecture standards but does not drive adoption or close the feedback loop between architectural intent and engineering implementation.
Security architecture is present on paper but not validated against engineering team implementations; security debt accumulates undetected.
Developer experience vision is articulated but not measured or tied to engineering team outcomes - DORA metrics, deployment frequency - in a way that drives investment decisions.
Examples
Zero-trust networking standard defined 12 months ago; no adoption reviews had occurred and only two of ten engineering teams were compliant.
Developer experience vision document existed but no metrics had been defined or tracked; platform investment decisions were made without developer experience evidence.
Dampeners
Adoption and measurement require engineering leadership partnership that may not have been fully established.
Progression Signal
Initiates an adoption review against the zero-trust standard and uses findings to drive a remediation plan.
Defines developer experience metrics and begins tracking them as a regular input to platform investment prioritisation.
Business Impact
Impact
Zero-trust non-compliance across engineering teams creates a security posture gap that represents material organisational risk.
Platform investments made without developer experience evidence may not address the friction points that most affect engineering team delivery speed.
Examples
Security review found that six engineering teams were non-compliant with network security standards, requiring an emergency remediation programme.
Dampeners
Remediation programme was funded and delivered; the process gap driving the non-compliance needs structural resolution.
Progression Signal
Security compliance tracking becomes continuous and automated; non-compliance is caught through tooling rather than periodic review.
High
Individual
Impact
Consistently avoids taking positions on difficult architectural decisions; defers to senior engineers or design-by-committee approaches that produce incoherent outcomes.
Does not engage with cloud provider and vendor relationships at a strategic level, missing opportunities to influence roadmaps or negotiate favourable commercial terms.
Creates a culture of architectural timidity; engineering teams receive ambiguous guidance that does not enable confident technical decisions.
Examples
Four consecutive architecture reviews concluded without a clear decision, leaving engineering teams to make their own incompatible choices.
Cloud provider contract renewal negotiated without Architect input; the organisation missed an opportunity to align commitment strategy with architectural direction.
Dampeners
May be operating without sufficient executive authority to take and enforce architectural positions; mandate clarification may be needed.
Progression Signal
Takes a clear, well-reasoned architectural position in one domain and drives it to adoption despite initial resistance.
Business Impact
Impact
Architectural indecision results in divergent engineering team implementations that create interoperability, security, and cost management problems at scale.
Divergent Kubernetes platform implementations across teams created a platform security review burden estimated at 40 engineer-days per quarter.
Dampeners
The divergence is addressable; the cost of retroactive standardisation is high but manageable if addressed promptly.
Progression Signal
Clear architectural positions are being made and maintained; engineering teams report that platform guidance is unambiguous and actionable.
Level 2
Development Needed
Low
Individual
Impact
Defines enterprise platform standards but without the precision needed for engineering teams to implement them confidently without further interpretation.
Cloud-native architecture patterns cover Kubernetes and IaC but do not address GitOps, progressive delivery, or service mesh strategy coherently.
Technology selection decisions are made but without a documented evaluation process that builds confidence in the outcomes.
Examples
Platform networking standard was ambiguous on multi-region connectivity, leading to three different engineering team implementations.
Service mesh adoption decision was made without a formal evaluation; two engineering teams subsequently challenged the choice based on operational overhead concerns.
Dampeners
Growing into the full enterprise architecture scope; precision in standard-writing and evaluation rigour are developing.
Progression Signal
Revises the networking standard to be unambiguous and tests its clarity with engineering team leads before publishing.
Produces a documented service mesh evaluation against defined criteria and uses it to rebuild confidence in the decision.
Business Impact
Impact
Ambiguous platform standards create engineering team implementation variation that defeats the purpose of standardisation.
Challenged technology decisions without documented evaluation create perception of arbitrary governance, reducing engineering team trust in architectural authority.
Examples
Three different networking implementations required retroactive harmonisation, costing an estimated 15 engineer-days across the affected teams.
Dampeners
Harmonisation cost is manageable; the process gap driving the ambiguity is the structural issue.
Progression Signal
Platform standards become sufficiently precise that engineering teams implement them consistently without seeking clarification.
Mid
Individual
Impact
Engages executive audiences on platform architecture but struggles to connect architectural decisions to board-level concerns - business resilience, regulatory compliance, competitive capability.
Software supply chain security strategy is defined at a policy level but not translated into implementable platform architecture that engineering teams can execute.
Platform architecture roadmap exists but is not maintained as a live document with clear investment requirements and delivery sequencing.
Examples
Board presentation on cloud architecture focused on technical detail rather than resilience, compliance, and productivity outcomes; limited engagement from board members.
SBOM and artifact signing strategy defined in policy but no Terraform or Kubernetes implementation pattern existed to operationalise it.
Dampeners
Executive communication of technical strategy is a skill that develops with deliberate practice and executive audience feedback.
Progression Signal
Rewrites the board cloud architecture presentation in terms of resilience outcomes, compliance posture, and engineering productivity ROI.
Produces an implementable supply chain security architecture with reference Terraform and CI/CD pipeline patterns.
Business Impact
Impact
Board and executive disengagement from platform architecture means platform investments are approved without strategic alignment, risking misallocated investment.
Supply chain security policy without implementation creates a compliance gap that represents regulatory and reputational risk.
Examples
Platform investment proposal was deprioritised at board level because its resilience and productivity value could not be quantified from the presentation.
Dampeners
The deprioritisation was recoverable with a revised proposal; the communication gap is the primary concern.
Progression Signal
Platform investment proposal approved at board level following a revised, outcome-focused presentation.
High
Individual
Impact
Technically excellent but does not operate at the full enterprise strategic scope of the Platform Architect role - influence is strong within the engineering organisation but limited at executive and board level.
Does not build the external architecture community presence expected at this level - no conference contributions, limited peer network, inward-looking perspective.
Platform architecture evolves in response to technology changes but not proactively in response to shifting business strategy or regulatory environment.
Examples
Has not represented the organisation at any industry forum or cloud provider advisory board in 18 months.
Three regulatory changes affecting the platform architecture were identified reactively through compliance review rather than proactively through environmental scanning.
Dampeners
External representation may require executive sponsorship and dedicated time allocation that has not been provided.
Progression Signal
Participates in one external industry forum or cloud provider advisory discussion and brings insights back to inform the platform roadmap.
Establishes a process for proactive regulatory environment scanning that feeds into platform architecture planning.
Business Impact
Impact
Limited executive influence means platform architecture decisions do not receive the board-level investment and sponsorship needed for strategic change.
Reactive regulatory response creates compliance remediation cost that proactive architecture planning would have avoided.
Examples
Reactive compliance remediation for a regulatory change cost an estimated 30 engineer-weeks that proactive architecture adjustment would have avoided.
Dampeners
Remediation was completed successfully; the planning process gap is the structural issue.
Progression Signal
Proactive regulatory scanning becomes embedded in the platform architecture planning cycle, reducing reactive remediation cost.
Level 3
Consistently Delivers
Low
Individual
Impact
Defines and governs the enterprise platform architecture - cloud-native standards, reference implementations, technology radar - with sufficient precision for engineering teams to implement confidently.
Designs the organisation's security architecture - zero-trust networking, workload identity, supply chain security - and drives adoption through review and enablement.
Communicates platform architecture to executive audiences in terms of engineering resilience, security risk, and productivity investment.
Examples
Published a platform technology radar with clear adopt/trial/hold/retire positions; adopted by engineering leadership as the standard for technology decisions.
Zero-trust architecture design reviewed and approved by CISO; implementation roadmap adopted across all engineering teams.
Dampeners
Operating consistently within the Platform Architect scope; growing in strategic breadth and executive influence.
Progression Signal
Begins influencing product and business strategy through platform architecture insights, not just responding to engineering organisation needs.
Business Impact
Impact
Technology radar reduces engineering team tooling proliferation, lowering operational overhead and improving platform supportability.
Zero-trust architecture delivers a quantifiable improvement in the organisation's security posture with measurable compliance benefit.
Examples
Technology radar adoption decommissioned four redundant tooling stacks, saving significant annual licensing and operational overhead.
Dampeners
Impact is strong within the engineering organisation; growing into cross-organisational strategic influence.
Progression Signal
Platform architecture contributions begin informing business strategy, product delivery model, and regulatory compliance decisions.
Mid
Individual
Impact
Owns the developer experience architecture - platform API contract, self-service model, internal developer portal design - with measurable engineering team outcomes.
Drives the platform architecture community of practice, connecting senior engineers across teams and creating shared ownership of enterprise standards.
Evaluates and selects platform tooling with documented, evidence-based evaluation processes that build engineering team confidence.
Examples
Internal developer portal design they led reduced new service onboarding from five days to eight hours across all engineering teams.
Platform technology evaluation process they established became the organisation's standard for significant tooling decisions.
Dampeners
Operating consistently and effectively at full Platform Architect scope.
Progression Signal
Platform architecture influence extends to board-level technology strategy discussions and external industry engagement.
Business Impact
Impact
Developer experience architecture improvements deliver measurable business value through engineering team velocity and quality improvements.
Technology evaluation rigour reduces the risk of poor tooling decisions that create long-term operational overhead and vendor lock-in.
Examples
Developer portal adoption correlated with a 40% improvement in deployment frequency and a 30% reduction in new service setup errors.
Dampeners
Impact is organisation-wide and measurable; contributing to strategic business outcomes.
Progression Signal
Platform architecture strategy begins being referenced at board level as a driver of organisational technology investment.
High
Individual
Impact
Shapes the organisation's full platform architecture with the highest standards of technical rigour - security, reliability, developer experience, and cost efficiency treated as co-equal requirements.
Translates complex architectural trade-offs into clear business investment decisions that engage board and executive stakeholders.
Builds platform architectural capability across the engineering organisation through coaching, governance, and community leadership.
Examples
Multi-cloud strategy design presented to the board with clear resilience, cost, and sovereignty trade-offs; funding secured for the recommended approach.
Senior platform engineers developed through architectural coaching programme; two promoted to principal-level roles.
Dampeners
Operating at the full scope and standard of the Platform Architect role.
Progression Signal
Platform architecture thought leadership begins generating external industry recognition and influencing the broader field.
Business Impact
Impact
Multi-cloud architecture investment delivers strategic resilience and sovereignty benefits with a clear, quantifiable return.
Platform capability development creates a self-reinforcing cycle of improvement that compounds across the engineering organisation.
Examples
Multi-cloud resilience investment reduced unplanned availability impact from cloud provider incidents by 80% within 12 months of implementation.
Dampeners
Impact is at full enterprise strategic scale.
Progression Signal
Platform architecture influence extends beyond the organisation to shape industry patterns through publications, speaking, or standards contribution.
Level 4
Leading
Low
Individual
Impact
Platform architecture authority is recognised at board and executive level; platform investment decisions are made with confidence in the architectural foundation.
Drives industry-leading developer experience architecture with measurable business outcomes - engineering team velocity, quality, and autonomy.
Cloud-native standards they define are adopted across the full engineering estate without enforcement, because they are demonstrably better than the alternatives.
Examples
Developer experience architecture programme resulted in DORA Elite classification for three engineering teams within two quarters.
GitOps and progressive delivery standard adopted voluntarily by all engineering teams; zero mandated adoption required.
Dampeners
Operating at leading level with full enterprise strategic influence.
Progression Signal
Platform architecture thought leadership begins influencing industry patterns through published work, standards contribution, or cloud provider advisory engagement.
Business Impact
Impact
DORA Elite outcomes deliver measurable competitive advantage through engineering velocity and quality improvements.
Voluntary standard adoption confirms the platform architecture delivers genuine engineering value, not just compliance.
Examples
DORA improvements correlated with a 25% reduction in time-to-market for new product features across DORA Elite teams.
Dampeners
Impact is transformative within the organisation; growing external industry influence.
Progression Signal
Platform architecture approach begins influencing industry practice through external engagement and publication.
Mid
Individual
Impact
Platform architecture thought leadership shapes industry practice beyond the organisation - through KubeCon presentations, open source contributions, or cloud provider advisory engagement.
Security and compliance architecture leadership is recognised by external auditors and regulators as exemplary, reducing audit overhead and compliance risk.
Builds the next generation of platform architects within the engineering organisation through structured coaching and architectural development programmes.
Examples
SLSA implementation pattern they designed was contributed to open source and adopted by 12 external organisations.
Security architecture recognised by ISO 27001 auditors as exceeding the standard; audit scope reduced as a result.
Dampeners
Operating at the highest level of Platform Architect contribution.
Progression Signal
External recognition and influence grow to the point of shaping standards bodies, cloud provider practices, or regulatory frameworks.
Business Impact
Impact
External recognition of security architecture excellence reduces audit overhead and creates commercial advantage in regulated markets.
Open source security pattern adoption creates community goodwill and positions the organisation as a platform engineering leader.
Examples
ISO 27001 audit scope reduction saved an estimated significant cost in annual audit fees and preparation overhead.
Dampeners
Impact is at enterprise and industry level - a genuinely exceptional contribution at this role level.
Progression Signal
Industry and regulatory engagement deepens into standards influence and advisory participation.
High
Individual
Impact
Operating as a principal platform architect in all dimensions - enterprise strategy, security governance, developer experience vision, and industry thought leadership.
Platform architecture programme they have built is a model for the discipline, recognised externally and internally as defining what excellent platform architecture looks like.
Builds and develops other platform architects, creating lasting architectural capability that persists beyond their individual contribution.
Examples
Platform architecture methodology published as a book and referenced in leading cloud-native architecture courses.
Platform architecture capability programme resulted in four internal Platform Architects developed over three years.
Dampeners
Operating beyond the standard Platform Architect scope in both impact and industry influence.
Progression Signal
Distinguished Fellow or Principal Architect designation is appropriate recognition for this level of sustained, industry-shaping contribution.
Business Impact
Impact
Enterprise platform architecture programme delivers transformative, compounding business value across engineering velocity, security posture, and delivery confidence.
Industry thought leadership creates talent attraction advantage and positions the organisation as a technology leader.
Examples
Platform engineering reputation directly attributed with attracting multiple senior engineering hires over two years who cited the organisation's architectural approach as the reason for joining.
Dampeners
Impact is at a level beyond the standard Platform Architect role scope.
Progression Signal
Principal or Distinguished recognition is the appropriate next acknowledgement of this level of sustained contribution.
Level 5
Transformative
Low
Individual
Impact
Performing beyond the Platform Architect role scope in strategic reach, industry influence, and enterprise impact.
Platform architecture work has become a reference for the broader cloud-native community, cited in industry publications and adopted by external organisations.
Builds platform architecture discipline within the organisation so effectively that it functions without dependence on their individual involvement.
Examples
Multi-cloud resilience framework contributed to CNCF and adopted as an industry reference architecture.
Platform architecture review process they designed operates independently, run by senior platform engineers without Architect involvement.
Dampeners
The transformative contribution at this level reflects genuine industry-shaping impact; Principal recognition is the appropriate response.
Progression Signal
Principal Architect or Distinguished Fellow designation should be under active consideration.
Business Impact
Impact
CNCF contribution creates community recognition that influences the organisation's talent pipeline and technology partnership opportunities.
Self-sustaining architectural governance reduces the organisation's dependence on a single individual for platform architectural quality.
Examples
CNCF framework adoption by external organisations created partnership discussions that generated significant commercial value.
Dampeners
Impact is at a level that clearly exceeds the standard Platform Architect scope.
Progression Signal
Principal recognition is appropriate and overdue.
Mid
Individual
Impact
Anomalously strong for a Platform Architect - operating at principal level in organisational influence, industry impact, and architectural depth.
Platform architecture programme shapes the cloud-native discipline more broadly - through standards bodies, cloud provider relationships, or widely adopted open source contributions.
Raises the organisation's profile in the platform engineering community to a level that creates structural competitive advantage.
Examples
Elected to the CNCF Technical Oversight Committee; brings direct influence on Kubernetes ecosystem direction into the organisation.
Platform engineering approach presented at AWS re:Invent and featured in cloud provider case study materials.
Dampeners
This level of industry impact at Platform Architect is rare; Principal designation is the appropriate and urgent response.
Progression Signal
Principal or Distinguished Fellow designation is overdue; delay risks external offers that exploit the role level mismatch.
Business Impact
Impact
CNCF TOC membership gives the organisation advance visibility of cloud-native direction, creating architectural planning advantage.
Cloud provider case study status delivers marketing and talent attraction value that significantly exceeds the cost of the contribution.
Examples
AWS case study generated inbound interest from 20 senior engineering candidates over the following year.
Dampeners
Impact is at principal level; role recognition must match contribution level.
Progression Signal
Principal designation resolves the mismatch; industry influence expected to continue growing.
High
Individual
Impact
Performing at a level that effectively defines what the Platform Architect role can be - an outlier across the entire industry, not just the organisation.
Platform architecture contributions shape cloud-native standards, influence cloud provider roadmaps, and are studied by practitioners globally.
Creates an organisational platform engineering legacy that will outlast their individual tenure.
Examples
Kubernetes enhancement proposal they authored became a core feature of a major release, improving workload scheduling for the entire ecosystem.
Platform engineering framework they created is used as a curriculum reference in university-level cloud-native architecture courses.
Dampeners
Keeping this individual at Platform Architect title is a severe retention risk and an organisational failure to recognise exceptional contribution.
Progression Signal
Distinguished Fellow or equivalent recognition is the only appropriate acknowledgement; the performance process has failed to keep pace with this individual's impact.
Business Impact
Impact
Kubernetes ecosystem contribution delivers long-term platform capability improvements for the organisation at zero marginal cost.
Academic and industry recognition positions the organisation as a principal contributor to cloud-native practice, with compounding talent and partnership benefits.
Examples
Kubernetes enhancement shipped in a major release; organisation adopts the feature six months ahead of general availability, gaining a delivery advantage.
Dampeners
This situation represents a recognition failure; immediate Principal or Distinguished Fellow designation is required.
Progression Signal
Distinguished recognition resolves the mismatch; continued contribution expected at the highest levels of the discipline.