Systems tracing
Maps the current state, photographs edge cases, and finds hidden dependencies before work begins.
Studio method
We treat physical technology like an operating system with visible dependencies.
The Cable Lab method combines site observation, electrical discipline, network thinking, and documentation craft. The result is a system that can be maintained by people who were not present for the original decisions.
Team and capabilities
A small crew built for the overlap between hardware, spaces, networks, and people.
Physical rebuilds
Routes cable, improves mounting, separates power classes, and protects service clearances.
Operational memory
Turns install knowledge into diagrams, inventories, restart procedures, and owner-facing guides.
Before and after
The visible difference is order. The business difference is recoverability.
| Area | Unmanaged setup | Cable Lab finish |
|---|---|---|
| Cable paths | Convenient in the moment, difficult to trace later. | Routed by function, length, service access, and failure risk. |
| Labels | Device names, tape notes, and vendor defaults conflict. | Shared naming convention across ports, devices, drawings, and handoff notes. |
| Recovery | Restart steps live in one person's memory. | Documented sequence with dependencies, photos, and expected states. |
| Change control | Small fixes create unknown downstream effects. | Baseline inventory makes future changes reviewable and reversible. |
Specimens
Work examples from the kinds of environments Cable Lab is built to clarify.
Prototype sensor wall
Converted a temporary bench demo into a labeled field test board with restart instructions.
Mixed AV cabinet
Separated signal, control, and power paths while keeping legacy devices available.
Field deployment kit
Packaged gateways, batteries, antennas, and spare leads into a repeatable checkout system.
Support desk bench
Mapped adapters, test devices, labels, and reset flows for faster triage.
Ready for a readable system