Spine clinics hear myths all day. Patients arrive certain that bed rest cures a bad back, or that an MRI alone will name the culprit, or that surgery is always the endpoint. The people selling internal platforms carry an equally stubborn set of beliefs, and they cost companies real money before anyone notices. Below are the six we meet most often, each corrected against published research and hard-won field lessons. If you recognise your own organisation in any of them, the fix starts with admitting the diagnosis rather than defending it.
Myth 1: PlatformOps Is Just DevOps With a New Badge
The most expensive myth first. A company renames its operations team, updates the slide deck, and declares transformation complete. Consultancy Thoughtworks has warned about this pattern specifically: relabelling without changing how work gets done produces no transformation at all, only letterhead. Real platform engineering is a sociotechnical shift, in the words DORA uses — shared tooling, golden paths, and measurably different delivery behaviour. It also has a prerequisite that skips the queue at your peril: working DevOps basics, meaning CI/CD that people trust, genuine ownership of services, and delivery metrics somebody reads. Attempt PlatformOps without those foundations and you are decorating a house with no wiring.
Myth 2: A Portal Is the Platform
Vendors adore this one because portals are easy to demo. But a portal is only the top layer of a three-part architecture: user interfaces such as catalogs, CLIs and templates sit above a platform core that handles orchestration and policy — the trust boundary holding your provider credentials — which in turn drives providers like clouds, clusters and CI/CD systems. Strip the core away and your shiny portal is a brochure. The graveyard proves the point: AWS Proton lost vendor support on 2026-10-07, and Azure Deployment Environments retires on 2027-02-22. Portal products die. Architectures that separate interface from core survive their vendors.
Myth 3: Mandates Create Adoption
Executives sign a cheque and expect usage to follow. It does not. The Cloud Native Computing Foundation calls platforms optional and composable, and takes that seriously: engineers vote with their feet, daily, without asking anyone’s permission. An internal platform, like an internal product, must be compelling enough that choosing it is the obvious move — that is the framing product people such as Boris Bottcher use. Mandate-as-strategy shows up in DORA’s anti-pattern research repeatedly, and it fails the same way every time: compliance theatre during the audit week, shadow tooling the other fifty-one.
Myth 4: Golden Paths Are Gilded Cages
Here the critics have half a point, then push it too far. An opinionated, supported route through delivery — Spotify popularised golden paths around 2014, Netflix called its version the paved road — genuinely can harden into a one-size-fits-all prison if the builders stop listening. Done properly, though, the contract is explicit: a team may step off the path whenever it likes, and it simply takes its support with it. That is freedom with a price tag, not captivity. The cage only forms when exit is forbidden or when the path was designed once, by people far from the work, and never revisited. Keep the exit door visible and the path stays honest.
Myth 5: The Platform Team Owns All Infrastructure
It should not, and pretending otherwise burns teams out. A platform group owns interfaces and experience — the templates, the catalog, the supported workflows — not raw compute, network or storage underneath, which remain with infrastructure specialists. Application teams keep operational responsibility for their own services; the platform team answers pages for platform components. Get that boundary wrong and every incident becomes a jurisdictional dispute while the pager screams. Team Topologies maps this cleanly: platform is one of four team types, interacting through collaboration, X-as-a-Service or facilitation, always with cognitive load as the budget you are protecting.
Myth 6: PlatformOps Ends at Launch
The launch party is where the real work begins, not ends. The CNCF puts it drily: once a capability ships, the heavier labour starts — upgrades, fielded questions, awkward edge cases, and eventually a graceful retirement. That lifecycle needs to be explicit, with stages from Proposed through Alpha, Beta and GA down to Deprecated and Retired, an owner attached to every entry, and a service level you can measure. Retirement deserves staffing, too: Google’s own engineering guidance notes that warnings alone rarely move users, so plan advisory migrations with real hands-on help rather than hoping a banner notice does the job. Capability without custody is just software litter.
Replacing the Myths With Something Workable
Every serious capability you publish should carry the same five attachments, regardless of what it does:
- a named owner who is a person, not an inbox
- a lifecycle stage that somebody actually keeps current
- a service level written where users can find it
- a support tier that says who is paged, and for what
- a planned exit — deprecation with real migration help, not a farewell banner
Notice what those attachments have in common: boundaries, honesty about cost, and evidence over enthusiasm. That mindset will feel familiar to anyone who has managed a spine condition conservatively — you exhaust the sensible non-surgical options first, escalate on clear indications, and let measurable function guide each step. The same triage logic applies when a team wonders whether it even needs a platform: below roughly three teams with repeated shared needs and two-plus years of funding, the honest answer is usually a good wiki page instead. Diagnose before you operate.
For readers following our clinical threads, the parallels run deeper in why back pain starts in the first place — treating root causes beats renaming symptoms, in bodies and in build pipelines alike. And when escalation is genuinely warranted, both fields agree on method: compare options on evidence first, whether that is weighing treatment choices before any operation or reading a detailed platform engineering reference before your first platform hire. Knowing when specialist help is the right call — for a spine or for a stalled delivery culture — is examined in when to move from general care to a spine specialist.