Working Prototypes
A build made to answer a question. Real code, real data where it matters, scoped to the decision you are trying to make and no further.
Who it is for
Founders deciding whether something is worth building. Teams stuck arguing about an idea that would be quicker to try.
The problem it solves
Decks and mockups let a disagreement continue indefinitely, because nothing in them can be wrong yet. A running prototype settles the argument in days.
What I do
- 01Agree the single question the prototype has to answer.
- 02Build only the path that answers it, and cut everything adjacent.
- 03Use real data early, since fake data hides the problems.
- 04Say plainly afterward what it proved and what it did not.
What you end up with
- A running prototype you can put in front of people.
- A written read on what it showed.
- A clear call on what to build properly, if anything.
03Also in Web Engineering
- The Bespoke SiteHand coded and precise. No page builder underneath.
- Web App InterfacesDashboards, tools, and the screens behind the login.
- Standing TypeA component set kept standing, so the next page is cheap.
- CMS & Content ModelA content structure your team can edit without breaking the design.
- Performance & AccessQuick on a phone, usable with a keyboard.