Design a Technical Workshop for a Decision

A half day technical workshop looks productive on a calendar. Without a shared decision, specialists often leave with a long discussion, unrelated questions, and no agreed next step. A useful agenda begins before invitations go out. Its purpose is to help a sponsor move one evaluation decision forward.

Meet with the sponsor before choosing speakers or time blocks. Ask, “When this session ends, what should your group be ready to approve, rule out, or investigate?” A broad answer such as “Everyone needs to feel comfortable” needs more work. Ask, “What would comfort allow your group to do next?” The answer might become a decision about security review scope, technical fit, or preparation for a limited trial.

Choose two decision questions where possible. Each question should name an audience and a decision. “Does our identity process have enough information for security review?” is useful. “Show security” is not. “What operating details must exist before planning a limited trial?” gives operations a reason to prepare. A clear question sets a beginning for discussion, identifies evidence worth reviewing, and gives a closeout point.

Do not turn every concern into an agenda section. Architecture, security, operations, and program management all have valid interests. A half day cannot hold an entire evaluation. Ask each attendee what answer they need before a later decision. Then ask which answers block movement now. Put lower priority topics in a follow up record with a reason for deferral. Depth matters more than a catalog of subjects.

Match preparation material to each question. Share current diagrams, process descriptions, approved product material, or a specific question only when those materials exist and a sponsor approves sharing them. “Come prepared” tells attendees nothing useful. A focused request says, “For our identity discussion, bring your current flow and mark areas where your review needs more detail.” Each attendee knows what to bring and why.

Set time blocks as boundaries, not promises. A four hour workshop might use a twenty minute opening, two sixty minute decision discussions, a twenty minute break, a forty minute operating discussion, and forty minutes for closeout. The exact schedule depends on the sponsor’s priorities. If missing material blocks an answer, use the remaining time to define an evidence request and assign an owner. Do not fill time with a broad product tour.

Here is a fictional practice situation. Morgan sponsors an evaluation of a proposed operating workflow. Morgan asks for a four hour workshop with a platform architect, a security lead, an operations manager, and a program manager. Morgan first says, “Cover everything so nobody feels left out.” A solutions consultant asks what must happen after the session. Morgan says the group needs to decide whether security review should proceed and whether operations has enough detail to plan a limited trial.

Those outcomes become two decision questions. The first is, “What evidence does security need before choosing a review path?” The second is, “What operating details must exist before planning a limited trial?” Architecture attends because current integration context informs both questions. The program manager attends because Morgan wants a dated record of open work. A broad overview has no separate slot unless one decision question needs specific approved material.

The solutions consultant drafts an agenda in Morgan’s words. The opening confirms scope and names expected decisions. The first decision discussion covers current architecture context relevant to security review. The second identifies required security evidence and owners. The operating discussion identifies details required for limited trial planning. Closeout records answers, open questions, owners, and dates. Morgan reviews each section and removes future reporting because no present decision depends on future reporting.

Open the workshop with plain scope. Morgan says, “Today we will decide whether security review should proceed and whether operations has enough detail to plan a limited trial. We are not choosing a full rollout plan.” This statement gives participants permission to defer useful but unrelated subjects. A facilitator records each deferred subject in a visible area, names why the group deferred each subject, and asks who should revisit each subject.

At each section, repeat the decision question before discussing evidence. Suppose the security lead asks how access is governed in the proposed workflow. The facilitator asks what material would support a review. If approved material already answers part of the question, the group reviews approved material. If information is missing, the facilitator writes the needed item, an owner, and an expected date. An unanswered question still produces movement when responsibility is clear.

Disagreement deserves separate notes. The architect might say existing systems appear compatible. The operations manager might worry about support effort during a limited trial. Do not merge both views into “a concern.” Ask each speaker, “Which decision does your point affect?” The architect’s view relates to technical fit. The operations view relates to limited trial scope. The closeout record should preserve both views without calling either one group approval.

Use careful language when a participant requests an answer beyond available material. The solutions consultant says, “We do not have enough approved information to answer future delivery ownership. Let us record what operations needs and who will respond.” This is direct and useful. Guessing creates a misleading record. A workshop does not need every future answer before a group decides its next evaluation step.

Closeout begins before people leave. Read each decision question aloud. Label each answer answered, open, or outside scope. For every open item, record needed information, owner, and expected update date. Avoid “Security will follow up.” Instead ask the security lead whether they accept ownership, then record their name after agreement. An absent reader should understand what happened without guessing.

Send the closeout record on the same day. Keep sections in agenda order so readers do not reconstruct discussion from loose notes. In Morgan’s fictional record, security review proceeds after an architect provides an identity flow. Operations needs an approved explanation of escalation handling before limited trial planning. The architect agrees to send the fictional flow on Tuesday. The solutions consultant agrees to respond with approved material by Thursday. Morgan schedules a twenty minute review for Friday.

For roleplay, assign Morgan, a solutions consultant, and people for architecture, security, and operations. Morgan opens with “Cover everything.” Give the solutions consultant six minutes to narrow this request into two decision questions. Each specialist supplies one required input and one concern. A facilitator writes the agenda while people speak, then reads each decision question back for agreement.

Finish the roleplay with Morgan’s closeout record. Leave security’s access evidence open. Assign the fictional identity flow to the architect for Tuesday. Set Morgan’s review for Friday. At the Friday practice meeting, open the record, mark whether Tuesday’s item arrived, and ask the security lead whether the evidence now supports a review path.