A Shade Beyond is a custom awning and shade fabrication company in Arizona — a skilled team, a long history, and an owner who believed deeply in what it could become. The goal was to grow it without losing the craft and the people that made it worth running.

The shop was working incredibly hard, and jobs still ran late. From the inside it read as a pace-and-effort problem — as if everyone just needed to push a little harder and catch up. And the owner had no reliable way to see the status and health of every job.

Three days inside the business. We mapped the workflow everyone described — clean, linear, seven steps. Then we mapped the one the work actually followed. They were not the same. Information moved through informal channels; the official process and the real one had quietly diverged.

Seven responsibilities had no clear owner. Three separate records disagreed about a given job’s status, and none was fully trusted. And there was no designed path for exceptions — the work that doesn’t fit the happy path was improvised, every time.

Every handoff ran through one person, who had quietly become the company’s memory and its routing layer. Strong employees were compensating for the gaps — carrying invisible work that kept jobs moving but never showed up anywhere. Jobs went dark while they were actively being worked.

The Findings Report named the few underlying truths beneath the visible symptoms: the official system and the real one had diverged, ownership had never been made explicit, and the business was measuring effort without being able to see the health of the work. Not a lack of effort — a lack of visibility and structure.

One job record as a single source of truth. Explicit ownership on every stage. Stage gates, so work can’t advance until what the next stage needs actually exists — materials ordered on approval, a kitting check before a job can ship. An assignment queue, so requests are tracked rather than carried. A live board, so nothing goes dark. And a designed route for the exceptions.

The build is underway. The first thing live is a private tool for the team — a way for requests and assignments to become visible, assigned, and returned to one system instead of disappearing into texts and memory. The broader operating system is being built against the Blueprint, stage by stage.

This engagement is ongoing, so this section is deliberately incomplete. The Findings Report and Blueprint are delivered and in the owner’s hands; the operating system is being built now. We’ll publish what changes — for the owner, for the team, and operationally — as it lands, including the parts that don’t work the first time. A case study shouldn’t pretend the work is more finished than it is.