liveBook · Manning

Experimentation

As explained in Effective Platform Engineering

Experimentation is the systematic evaluation of alternative designs or implementations under realistic conditions to inform decisions.

Experimentation systematically evaluates alternative platform designs or technologies under realistic conditions so measured results guide decisions. It replaces abstract preference with evidence from the actual engineering platform. section 8.2.1 section 2.4

Apply experimentation before committing to platform capabilities:

  • Build a proof of concept on the actual engineering platform infrastructure, especially when installation, upgrades, or maintenance may vary in a Kubernetes context. section 8.2.1
  • Measure expected value against software selection criteria instead of accepting a vendor or technology choice without implementation evidence. section 8.2.1 section 2.4
  • Test the experience with alpha users early, introducing fundamental capabilities before complex implementations and using feedback to shape the next step. section 2.4

Choosing a platform service

Before adopting a service or extension, the platform team installs it in the real platform environment, evaluates operational effort and expected value, and observes how early users experience the capability. The team can then refine the design or reject the choice before it creates handoffs, ticket queues, or friction. section 8.2.1 section 2.4

How Effective Platform Engineering covers it

How deep it goes
Requires proof-of-concept implementation and alpha-user testing, emphasizing incremental evidence rather than abstract technology selection.
Examples
Uses actual-platform proofs of concept, Kubernetes service evaluations, and early tests of fundamental features with alpha users.
What it assumes
Assumes software selection criteria, an engineering platform environment, and awareness of the product delivery lifecycle.
What you can do after
Evaluate platform technologies and feature designs before commitment, using implementation results and user feedback to guide the next decision.
How it connects
Connects proof of concept, software selection, service interfaces, alpha users, observability, and evolutionary architecture.

Also explained in

Compare how 16 books explain experimentation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.