Define golden paths that guide development teams towards supported, well-governed delivery patterns.
Platform Engineering and Internal Developer Portal Design
Design an internal developer platform with golden paths, self-service infrastructure and a developer portal that measurably reduces cognitive load.
Course Overview
Development teams asked to own their own infrastructure often end up reinventing the same pipeline, the same monitoring setup and the same access request process, each slightly differently, which is exactly the cognitive load that platform engineering exists to remove. This course treats the internal platform as a product with its own users, roadmap and adoption metrics, rather than a shared tooling backlog. Participants define golden paths that guide teams towards approved, well-supported ways of building and deploying services, and design self-service capabilities for provisioning infrastructure, environments and access without opening a ticket. Sessions cover building a service catalogue and software templates that scaffold new services with security and observability built in from the first commit, and designing a developer portal that surfaces ownership, documentation and service health in one place. The course closes with measuring developer experience using cycle time, deployment frequency and platform adoption metrics, and running the platform team itself with a product mindset, including a backlog driven by internal user feedback.
Expected Learning Outcomes
Design self-service capabilities for infrastructure, environment and access provisioning.
Build a service catalogue and software templates that scaffold new services with standards built in.
Design an internal developer portal that surfaces ownership, documentation and service health together.
Measure developer experience using cycle time, deployment frequency and platform adoption metrics.
Run a platform team with a product operating model driven by internal user feedback.
Balance platform standardisation against the autonomy development teams need to move quickly.
Who Should Attend
Platform engineers building internal developer platforms and tooling.
Engineering managers responsible for developer productivity and experience.
DevOps and site reliability teams transitioning towards a platform team model.
Software architects designing golden paths and reference architectures.
Product managers assigned to internal platform or tooling products.
Engineering leaders sponsoring platform investment and adoption targets.
Course Modules
Select any module to see its sessions and points.
01Platform as a Product
2 sessions · 8 points
Session 1Defining the Platform's Users and Value Proposition
- Identify internal developer segments and the specific friction each one experiences today.
- Define the platform's value proposition in terms of time saved and risk removed for developers.
- Distinguish platform engineering from generic DevOps tooling by its product ownership model.
- Set an adoption strategy that earns voluntary usage rather than mandating the platform by policy.
Session 2Running the Platform Team with a Product Backlog
- Establish a platform product backlog prioritised by developer impact rather than internal convenience.
- Collect structured feedback from internal users through surveys, interviews and usage analytics.
- Define a platform roadmap that balances new capability against reliability and technical debt.
- Set success metrics for the platform team distinct from the metrics of the teams it serves.
02Golden Paths and Self-Service Provisioning
2 sessions · 8 points
Session 1Designing Golden Paths for Common Delivery Patterns
- Identify the most common service archetypes and design a golden path for each one.
- Bake security, observability and compliance defaults into the golden path rather than as an afterthought.
- Design escape hatches that let teams deviate from the golden path with informed trade-offs.
- Version golden paths so existing services can adopt improvements without a disruptive migration.
Session 2Self-Service Infrastructure and Access Provisioning
- Design self-service workflows for provisioning environments, databases and compute resources.
- Apply policy as code to enforce guardrails on self-service requests without manual approval bottlenecks.
- Automate access provisioning for common roles while preserving least-privilege principles.
- Set audit logging on self-service actions to maintain traceability without slowing developers down.
03Service Catalogue and Developer Portal Design
2 sessions · 8 points
Session 1Building a Service Catalogue and Software Templates
- Design a service catalogue schema capturing ownership, dependencies and lifecycle stage for each service.
- Build software templates that scaffold new services with pipelines, monitoring and documentation preconfigured.
- Define scorecards that assess services against security, reliability and documentation standards.
- Keep the catalogue accurate through automated discovery rather than manual registration alone.
Session 2Designing the Developer Portal Experience
- Design portal navigation that surfaces service ownership, documentation and health in a single view.
- Integrate the portal with the service catalogue, pipelines and observability tooling for a unified experience.
- Apply search and discoverability principles so developers can find existing services before building new ones.
- Pilot the portal with a small group of teams before rolling it out organisation-wide.
04Measuring and Scaling Platform Adoption
2 sessions · 8 points
Session 1Measuring Developer Experience and Platform Impact
- Track cycle time, deployment frequency and change failure rate to measure delivery performance.
- Measure platform adoption rates and time-to-first-deploy for teams onboarding to golden paths.
- Combine quantitative metrics with qualitative developer satisfaction surveys for a fuller picture.
- Present platform impact to engineering leadership in terms tied to delivery and reliability outcomes.
Session 2Scaling the Platform Across a Growing Organisation
- Plan platform team structure and staffing as adoption grows across more development teams.
- Manage the transition from a small pilot platform to an organisation-wide mandatory capability.
- Handle legacy services that cannot easily migrate onto the new golden paths.
- Sustain platform investment by continuously demonstrating measurable developer impact.
What the participant receives
4 course modules
A structured syllabus
8 training sessions
across 5 days
32 detailed points
Applied, detailed content
Accredited attendance certificate
On completing the programme
Complete your registration
We will contact you within one business day to confirm.
Ready to start?
Reserve your seat and start building the skill.
