How it works

Start with the physical problem. Establish the boundary. Choose the useful path.

The process is designed to avoid two common mistakes: destroying value too early and building more than the problem requires.

01

Describe the situation

What exists, what is wrong, what has to move, or what needs to be built. Plain English is enough.

02

Establish the boundary

Ownership, authorization, access, safety, data, timing, handling, transport, and any required disposition controls.

03

Choose the smallest useful path

Reuse, repair, modify, dismantle, recover, fabricate, prototype, recycle, or combine those paths.

Pilot first

When uncertainty is high, prove the process on a small scope.

A controlled first batch can establish actual labor, recovery value, access constraints, handling needs, and documentation requirements before anyone commits to a larger operation.

01

Define a contained sample. Enough material or work to expose the real constraints.

02

Measure what happened. Time, value recovered, reusable items preserved, disposal avoided, and blockers found.

03

Decide from evidence. Expand, change the process, refer specialized work, or stop.

Start here

Use the project intake before writing a long email.

It converts a short description into a useful first brief.

Open project intake