AI Product Engineer & Designer
A5XPH+
WOG%3
Turning vague requirements into full operational flows and working products.
product manager, 20-person dev team
data visualization developer and designer
founder, 20+ business customers
business analyst & project manager, consulting
- YEARS
- 13
- since 2013: design, then data, then product and management, now AI builds
- BUSINESSES ON MY SOFTWARE
- 20+
- Stemwise is the product I designed, built and run nights and weekends
- ROLE EXPANSIONS
- 3 FOR 3
- RezySave, CTG, Press Ganey: every job, within two months
- PM PORTFOLIO
- $5M+
- combined project value across RezySave and CTG
Hearing the requirement nobody wrote down, and building it into the system.
The crew logged 60 installs. The dashboard says 47.
Hearing the requirement nobody wrote down, and building it into the system.
Where is device 1001.18-1.UTNH right now?
- OPS
At Beldon the crew counted 60 done and the dashboard says 47. Which number does the owner get?
- KL
Thirteen are on the wall but have never sent a reading. A sensor that has not reported is not protecting anyone yet.
- KL
So we define installed: a device counts once it sends data, and not before.
Once installed meant reporting, the crew and the owner were reading the same number and the argument stopped. It has held on every property and every crew since.
- OPS
A unit came back from a property and went into a bin. Nobody knows which bin, or whether it was ever swapped.
- KL
The code says where a device belongs: property, building, unit, device type. In inventory it has no unit yet.
- KL
So a device is either in inventory or on a property, and the same code follows it either way.
The code is decided before the crew leaves, so installers arrive knowing what goes where. Any device on any property is findable by its code alone.
THE INSTALL FLOW · REZYSAVE
FIG. 01 · FIVE BUILDS, ONE WAY OF WORKING
Selected work
