The Lab

The Lab

Experiment. Prototype. Learn.

A place for curiosity-driven tests, physical and digital prototypes, and small demonstrations that turn questions into tangible things.

An open workbench. Experiments will be shared here once there is something worth showing.

Halftone illustration of a workbench with a desk lamp, small drawers, a breadboard circuit, a notebook, a pegboard of hand tools and a potted plant.
Fig. 1 Most experiments start with whatever is already on the bench.

Small questions, made tangible.

The Lab follows the same method as every Serpenthink project. Stages appear here only once there is real work to show for them.

  1. The Problem Defined
  2. The Hypothesis Stated
  3. What if? Asked
  4. The Experiment Approach defined
  5. What We Learned Not yet published

01 The Problem

Good ideas stay in the notebook.

Interesting ideas often stay trapped in notes, browser tabs and conversations because they seem too small, too unusual or too difficult to try.

02 The Hypothesis

Learning comes before polish.

Cheap, bounded, visible experiments can create learning before anyone needs a polished product or a defensible business model.

03 What if?

What if?

What if useful or delightful things could be made quickly, tested honestly and improved through direct observation?

Start with the smallest test.

A few working rules keep experiments cheap, honest and safe.

  • Start small. Find the smallest test that could teach something real.
  • Use what exists. Reach for existing tools and available objects first.
  • Write it down. Record costs, assumptions and decisions as they happen.
  • Protect people. Respect the privacy of anyone who takes part.
  • Respect constraints. Every experiment has a cost limit and a time limit.
  • Count failures. A failed prototype is an output with learning value.

How an experiment moves.

Not a bureaucracy. A simple path from a question to a decision.

  1. Question

    Write down the problem, who it affects, and the smallest thing worth trying.

  2. Bound it

    Set a cost limit, a time limit, and what success or failure would look like.

  3. Make it

    Build the simplest version with tools and objects that already exist.

  4. Observe

    Test honestly. Record what happens, including surprises and mistakes.

  5. Decide

    Stop, iterate, share, or propose it for further development. Keep the lesson either way.

Kill Switch / Experiment closed

Stopping is a result too.

An editorial record of experiments stopped, paused or redesigned because the evidence changed the original hypothesis. Each one keeps the same simple rubric.

  1. 01What we attempted
  2. 02What we observed
  3. 03What we decided
  4. 04What we learned

    Nothing recorded yet. Experiments that end because the evidence changed will be documented here, honestly and with dates.