Frame a data center diversity workshop

Begin with one decision sentence rather than a broad request for diversity. State the named services, the named locations, and the interruption the group wants to examine. One team might want to examine loss of an outside route. Another team might care about a building entrance, an internal room, or a local utility area. Those are separate questions. Put the decision sentence at the top of a shared working page. Add the meeting date, a source field, and an owner field beside every claim. A visible unknown is useful. Hidden uncertainty turns a later review into a search for missing context.

Invite people who hold distinct records. The network architect often brings a logical view. A facilities contact might bring entry drawings, room names, or access notes. A service contact might bring order identifiers and service records. Site operations staff know local access limits and planned building work. A workload owner describes which business process depends on each location. Ask each attendee to name the record in front of them, its date, and the part outside their knowledge. Do not ask one attendee to represent every source. Separate ownership gives the group a cleaner record and reduces polite agreement around a guess.

Sort every route statement into observed, reported, or assumed. Observed means direct evidence exists, such as a current photograph, an entry drawing, or notes from a visit. Reported means a person or existing record supplied the statement, yet confirmation has not arrived. Assumed means the group needs a temporary placeholder so discussion has a next question. Use these labels beside individual claims, not beside whole documents. A building drawing might support one room name yet leave a route section open. Labels let people discuss evidence without turning uncertainty into a personal disagreement.

Ask for a small route description for each service. Capture the service identifier, both endpoints, known building entrance, known internal handoff location, and every possible shared point. An early workshop does not need a detailed civil map. A statement such as separate paths gives too little material for a decision. When an external segment is unknown, write unknown. When two services show one room, write shared room. When staff remember different wall entries without a current drawing, preserve both observations and record a verification task. Precise gaps invite useful work. Guesses invite a false design conclusion.

Keep route records and workload context on the same page. Ask which operating process relies on each site and what staff do when either location is unavailable. Request descriptions, not impact estimates. A workload owner might say a nightly file process uses one location after 7:00, while another team supports a customer facing application from the second location. Record the procedure owner and the location of relevant operating notes. Do not judge a recovery process during a route discussion. Those details help the group place verification effort around work staff need to perform.

Use consistent nouns during the session. Pick service, route, entrance, handoff, room, and shared point, then keep those labels throughout the page. A change from circuit to link to connection invites people to compare different things without noticing. Ask short questions beside each service. Which entrance has evidence? Which room appears on more than one record? Which source predates a renovation? Who arranges a visit? What missing detail prevents the next design conversation? Record each answer next to the relevant claim. A separate pile of notes usually loses the association between a question and a route.

Use a fictional practice situation to make the method concrete. Harbor Arcade has North Hall and River Hall. Mei brings a page with Service A and Service B between those locations. The architect says, “We need separate routes.” Mei asks, “Are we examining outside paths, building entries, internal handoffs, or more than one of those?” The architect selects outside paths and building entries. The facilities engineer has a drawing from before a lobby renovation. The service contact has two order records and no current entry sketch. Mei labels Service A at North Hall as reported and Service B at River Hall as open.

Mei then asks what work uses each site. A systems lead says a fictional nightly file process starts at 7:00 and uses North Hall. A portal owner says River Hall supports a public service. Mei records both statements without assigning business impact. She asks each owner for the current operating note and names beside their statements. The facilities engineer mentions a locked utility room near both listed handoff areas. Mei writes possible shared room rather than defect. She asks whether access records, a current drawing, or a visit would answer the question. The engineer agrees to search available building records first.

The page now holds useful evidence, yet no verdict. Mei reads the Service A row aloud. Its endpoints come from the logical view. Its North Hall entrance comes from the older drawing. Its outside segment is open. She asks the service contact to match the identifier against order records. Then she reads the Service B row. River Hall has no entry evidence and both internal handoff locations need confirmation. Reading a row aloud exposes incomplete language. “Separate” disappears because the group has not observed enough detail to use such a label with confidence.

Set a validation plan with one owner, one expected record, and one return date per task. For this fictional situation, the facilities engineer searches for post renovation entry drawings by Tuesday. The service contact matches order records by Wednesday. The architect marks logical endpoints on the current diagram by Wednesday. Mei schedules a review for Friday at 10:00 and attaches the working page. Those dates are planning examples, not service commitments. Before the review, Mei asks participants to add new evidence beside the existing claim rather than replace older text. The history helps the group see why a conclusion changed.

At Friday’s review, Mei begins with Service B at River Hall. The facilities engineer supplies a current drawing showing an east entrance. Mei changes the source field and moves the entrance claim from open to observed. The service contact has not found an outside route record, so she leaves the field open. She then asks whether North Hall and River Hall share the named utility room. The engineer requests a walkthrough after checking access. Mei enters the proposed visit owner and date beside both service rows. Her next action is to send the page with those two open route questions to the engineer before the access request begins.