LAYERED LOGIC / SPRING 2026 / LL-061 / PROCESS CASE STUDY

Designing a system, not a gadget.

Eleven weeks turning an infinity mirror into a near sellable product. Three lanes running at once, the work shown in public, and the dead ends left in.

The three lanes

  • Product  engineering & design
  • Business  the venture
  • Customers  research & service

Each node

  • Shipped
  • Iterated  found the answer by trying
  • Friction  where I struggle
  • Still open

How to read it

  • The axis is real time, top to bottom. Tap any node to see the decision behind it.
11wks
research to near-sellable
4
phases, three lanes in parallel
32
milestones in the sprint record
10
stage end-to-end service blueprint
17
failure modes documented for repair
1,476
soak iterations, 0 errors
−46%
control latency after hardening
SHOT 01 / 16:9 / HERO PHOTO TO CAPTURE The mirror lit, at dusk, in a real room. Shot slightly off axis so the tunnel depth reads. Ambient presence in a styled space, not product on white. Indigo default pattern, quiet headroom for the title.
TIME ↓
Product ENGINEERING & DESIGN
Business THE VENTURE
Customers RESEARCH & SERVICE
// ARTIFACTS

A few of the things the process produced.

Layered Logic nested-L logo
Brand mark · nested-L, indigo
Home / controls wireframe
App wireframe · home + controls
Settings / wi-fi wireframe
App wireframe · settings + wi-fi
Packaging dielines
Packaging dielines · mailer + insert
Custom-tile fabrication preview
Custom-tile fab · cut + plug geometry
// WHAT I LEARNED ABOUT HOW I WORK

Where I am strong, and where I hit friction.

A process is only honest if it names its own weak points. Here is what came easily this quarter, and what did not, with what I am doing about the parts that did not.

Strengths

Engineering verified on real hardware.

Every firmware change ran build, flash, boot capture, and on device measurement against a live mirror before it counted. The resilience work was proven with a soak test of 1,476 iterations at zero errors, not asserted.

Systems thinking.

The ten stage service blueprint, the stakeholder map, and the failure mode catalog treat the product as a system of interactions. The blueprint is the proof of the thesis, not a slide about it.

Automation and tooling.

Parametric generators turn one customer SVG into a laser job, a 3D print, and a packaging dieline with no per order CAD. The instinct is to build the machine that builds the thing.

Documentation discipline.

Decisions are captured with their rejected alternatives, so the reasoning survives. This page exists because the process was written down as it happened.

Friction, and the plan

Outreach.

My weakest lane by a distance. The contact list sat stale for weeks, and pitching myself fights my instincts.

MITIGATINGTightened the cold message templates to one anchor idea and a peer tone, set a five a day cadence, and built a verified contact pipeline so that sending is a mechanical batch task instead of an emotional one.

User interviews keep slipping.

The interview agenda has been ready since week 4, but talking to strangers about my own work is the part I most avoid, so the design rationale is still founder intuition more than validated fact.

MITIGATINGReframed interviews as ongoing and impromptu against a fixed agenda, with a venue sourcing method, rather than a milestone to schedule and dread.

A backlog of visual checks.

I am fast at logic and slow to look. Plenty of UI verification got deferred to my next session.

MITIGATINGBuilt a scripted browser automation loop that injects test inputs and compares renders before any push. It already caught two rendering bugs that would have shipped.

Business and legal confidence.

I am stronger on the technical side than the legal and financial side of running a company.

MITIGATINGPolicy drafts ship with an explicit needs counsel review gate, and compliance is tracked as a living checklist with advisor check ins, so nothing is mistaken for settled.

// THE STORY IS NOT DONE

One switch flip from live.

By design, the quarter ends ready to sell, not sold. The goal was flip the switch readiness: every system in place so the only thing left is the decision to begin. These are the pieces still open, and they are roadmap, not shortfall.