liveBook · Manning

Experimentation

As explained in Think Like a Software Engineering Manager

Experimentation is the deliberate testing of ideas or changes to learn from observed results.

Experimentation deliberately tests a change so observed results can guide the next decision. It supports flexible, market-specific changes and iterative delivery rather than relying on one uniform rule. section 12.4 section 11.1.3

A practical experimentation pattern includes:

  • Make the proposed change adjustable enough to compare outcomes across different markets or customer groups. section 12.4
  • Deliver a portion of the product, collect feedback, recognize failures quickly, and use the results to guide the next iteration. section 11.1.3
  • Explain the expected benefits alongside the additional development effort and other trade-offs. section 12.4

Marketplace return limits

A return limit that once required code changes and deployments can become configurable per marketplace. Teams can then compare how customers in different markets respond instead of assuming one limit suits everyone. section 12.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains experimentation through workplace scenarios and iterative cycles, stopping short of implementation detail or statistical analysis.
Examples
Uses configurable return limits across marketplaces and partial product delivery followed by feedback.
What you can do after
Apply it via iterative delivery to test changes, recognize failures quickly, gather feedback, and learn from results.
How it connects
Connects A/B testing, configurable systems, feedback, iterative delivery, and risk mitigation.

Also explained in

Compare how 16 books explain experimentation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.