The working floor of the plaza desk

Hero Sheet Bays

The hero sheet is the first public face of a project. In the bay, the desk takes the rough request that arrived by message, call or sitting and turns it into one clean summary that names the system, the audience, the timing and the outcome that the client wants. Each field is checked against the original material before the bay marks the sheet ready, and any gap is written down plainly rather than papered over.

The bay exists because most integration work fails at the point of shared understanding, not at the point of code. A hero sheet forces the desk and the client to agree on the same words before a wire is run. When the project later grows, the sheet is the fixed point that everyone returns to. It is revised when the scope changes, and each revision is dated so that the history of the plan stays visible.

Deliverables from the bay include the sheet itself, a short list of open questions, and a recommended next station. A client can stop after the bay and take the sheet away, because the summary belongs to the engagement and not to a sales process.

Plaza Note Runs

A plaza note run is the desk walking the ground. The team visits the site, reads the existing network, talks to the people who run it, and writes down what was actually observed. Notes are kept short and sorted into runs that follow the working day, so a reader can follow the route from one observation to the next without losing the thread.

The run separates what was seen from what was decided. An observation is written as a plain fact, a decision is marked as a decision, and an assumption is flagged so that it can be tested later. This discipline matters in computer integrated systems design, where a single inherited assumption about an old switch or a hidden cable often explains a whole class of faults.

The output of a run is a set of notes, a short list of risks, and a recommendation about whether the plan should continue to the next station. If the notes show that the original hero sheet is wrong, the desk says so and explains why.

Seller Letter Desks

The seller letter desk answers the people who supply or resell the systems that a project depends on. Letters arrive at the desk, are logged with a date and a reference, and are matched to the sheet they concern. Wording, prices and dates are kept consistent across all correspondence, which prevents the small contradictions that later turn into disputes.

The desk is a single point of contact on purpose. When several suppliers correspond with several members of a project team, commitments drift. The seller letter desk keeps one voice, one record and one route for a reply. A seller who needs an answer about a delivery, a specification or a warranty gets a reply from a person who has read the whole file.

The desk does not act as a broker unless a separate engagement says so. Its job is to keep the correspondence honest, to flag a seller offer that does not fit the plan, and to make sure that a commitment made in a letter is reflected in the working record.

Network Windows

A network window is a narrow live view of a plan in progress. It is deliberately small: it shows the status, the owner of the next action, and the next scheduled move, and nothing else. The narrowness is the point. A window lets a stakeholder see enough to stay informed without opening a whole file, and it lets the desk publish a status without exposing private detail.

Each window is prepared with the client. The desk and the client agree what will be shown, who can see it, and when it will be updated. The window does not grant access to the underlying records, and it cannot be used to bypass a confidentiality obligation. If a stakeholder needs more detail, the route is a sitting rather than a wider window.

A window is useful in long projects where several parties need reassurance but do not need the working file. It reduces the number of status questions that reach the desk, which in turn keeps the desk free to do the actual integration work.

Link Review Rounds

A link review round gathers every connected link in a project and checks them as a group. Individual links can each pass a test while the group still fails, because a network is a system of relationships rather than a list of parts. The round looks at the relationships: latency between segments, failover behaviour, addressing overlap, and the assumptions that one segment makes about another.

Findings are written plainly and ranked by risk. A finding describes what was observed, why it matters, and what the recommended next step is. The desk does not bury a serious finding in a long appendix. If a link is unsafe to put into production, the round says so at the top of the report.

A review round is an assessment based on the material available at the time. It is not a guarantee that no future issue will arise, but it is a disciplined attempt to find the issues that can be found before a live change is made. The desk records the date, the scope and the people involved so that the review can be repeated later against the same basis.

Plaza Sittings

A plaza sitting is a scheduled hour at the plaza bench where people talk through a plan together. It is a conversation with a purpose, not a general meeting. The desk prepares a short agenda, the participants read the relevant sheet beforehand, and the hour ends with a decision or a clear next step.

Each sitting produces a short record that both sides keep. The record names what was decided, what was left open, and who owns the next action. If a participant believes the record is wrong, they can ask for a correction within the period stated in the record, so that the history stays accurate.

Sittings close a stage. They are how the desk moves a project from notes to a plan, or from a review to a change. A client can request a sitting at any time, and the desk may propose one when it believes that a conversation would resolve a question faster than more correspondence.