liveBook · Manning

Prototyping

As explained in Decision Engineering

The creation and evaluation of preliminary versions of a product, system, or process.

A proof of concept (PoC) is a working prototype used to evaluate a technology hands-on. It can reveal how the technology feels to use and how quickly a team member can make a working change. section 4.2.3

Start with prioritized make-or-break questions, then build prototypes to test them. A quick demo that avoids the concerns under evaluation offers little evidence. When comparing candidates, rebuilding the same prototype with a different technology helps hold the use case constant. section 4.2.3

Comparing candidate technologies

Try the actual editing experience and measure how long it takes someone on the team to make a working change. A greenfield “Hello world” demo may run successfully while leaving the important evaluation questions unanswered. section 4.2.3

How Decision Engineering covers it

How deep it goes
Defines a question-led process: prioritize make-or-break questions and build prototypes that stress them, rather than merely running a greenfield demo.
Examples
Compares technologies on the same use case and checks editing experience and time to a working change.
What you can do after
Evaluate technologies by using prototypes to test prioritized concerns and compare candidates on a constant use case.
How it connects
Links rapid prototyping to technical decision-making, technology evaluation, and proof-of-concept work.

Also explained in

Compare how 11 books explain prototyping →

Related concepts

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