Hours to understand. Days to blueprint.

It started with listening

The owner came to us with his own diagnosis: my systems are distributed and don't meet my needs. An expansion was coming. This was his dream business.

Understanding it took hours. Then the honest decision: help him build it.

Seven links, each producing the next

1. 1Listening. A sourced debrief, evidence separated from interpretation.
2. 2Synthesis. Who the program serves: players, guardians, coaches, administrators, the owner, donors.
3. 3Idealized design. The program as it should work, unconstrained by current tools.
4. 4System map. What each person needs, sees, does, and has authority over.
5. 5Ontology. One shared language for the whole program.
6. 6Context graph. How it connects, and how an agent reads it.
7. 7Blueprint. A reviewable design, presented and accepted.

No stage answers a later stage's question. Each begins from an approved source. That discipline made days possible.

The process, drawn with its own method

What an ontology is

Before software, the business needs a dictionary. The ontology is that dictionary: a list of the things Better Hoops runs on, with each one defined once and agreed on. A player. A team. A registration. A payment. What each means, who can change it, and what history it keeps.

It was built because software guesses when words are loose. Agreed definitions mean the owner, the families, and the agents building the system mean the same thing. Three examples:

Two graphs, two readers

The first shows the owner his program: people around the boundary, the operating spine inside, governance over it.

The program context graph

The second shows how an agent works inside it: read context, test authority, act narrowly, record changes, stop and route to a human when policy has no answer.

The agent context graph

“Read broadly to understand, act narrowly within human authority, never itself a Better Hoops role.”

The blueprint confirmed understanding

The blueprint was not the final design. It was where the owner, the architect, and the agents building the system came to hold the same understanding, and that understanding got tested.

The owner read it, questioned it, accepted it. The first screens built from it matched the intended design on the first pass. They were not asked to invent the system, only to reveal decisions already made.

Read the product blueprint

The blueprint shows how families, players, coaches, and program administrators would use one shared system. It connects the proposed screens to the information and decisions each person needs.

Models helped agents interpret the source material and draft the design. The software around those models supplied the instructions and tools. The owner reviewed the direction before the design moved forward.

Open the Better Hoops blueprint

Sign-in required for the client review site.