SALES KICKOFF PHOTO CHALLENGE: HOST PACK Gather Shot | Original exercise design | October 23, 2026 For a 45-minute session inside a January 2027 kickoff. Desk checks covered arithmetic, fact coverage and sample answers only. Not participant-tested. Pilot instructions, materials and timing before use. No purchase required. No real customers, faces, screens or badges. PREPARATION Suggested starting size: 12-40 people, teams of 3-5, pre-seated. Assign a lead facilitator/timekeeper and a separate host for remote teams. For each station at each table: print one SHARED SCENARIO AND INSTRUCTIONS block intact, and cut its three labeled fact slips separately. Put the shared sheet and three slips in an envelope labeled A, B or C. Provide three blank answer sheets per table, pens and a table ID. Print one review sheet per table. Keep it covered until minute 31. The examples following the review sheet are optional host reference. Assign three fact holders, a recorder and a checker. Jobs may overlap and anyone may decline. A willing photographer is optional. Supply accessible digital text, including all facts, beforehand when needed. Shared facts can replace separate slips for access. Allow dictation, typing and a supporting reader/scribe. This is not a memory test. All slips become visible to the group after sharing. One willing camera operator per table is enough. Paper-only counts. Offer observing or quiet individual annotation, with optional written feedback. No explanation required. All-observer tables can skip stations. Assign a retention owner for paper, phones, shared documents and gallery. Tell people who sees answers and when each kind of copy will be removed. Deleting a gallery copy does not remove phone copies. FICTIONAL CLOCK: In every scenario, today is January 5, 2027, regardless of your actual kickoff date. All proposed dates are fictional. HOST CLOCK (elapsed minutes) 00-05: Purpose, privacy, choices and output instructions. 05-08: Assign reader/recorder/checker. Practice T04 TEST photo or paper. 08-15: A. Missing decision. 15-16: Open B, switch reader/checker. Stay seated. 16-23: B. Promise boundary. 23-24: Open C, switch reader/checker. Stay seated. 24-31: C. Receiving-team test. 31-35: Reveal review sheets. Tables self-check and correct one omission. 35-37: Silent reflection on one changed assumption. 37-41: Table discussion of the fact and role that changed it. 41-43: Two voluntary examples, maximum one minute each. 43-45: One process habit and volunteer owner. Retention reminder. Close. OPENING SCRIPT We are practicing how different roles build a decision together. These customers are fictional. Hear all three facts before solving. Photograph only your answer sheet, with no faces, badges or work screens. You can write, read, check, observe or pass. We are not ranking anyone. Paper answers count, and uploads must not delay the next round. SEVEN-MINUTE ROUND (same for A, B and C) 0-1: Silent reading. 1-3: Share all three facts, then put them where everyone can access them. 3-5: Decide and write three short boxes. 5-6: Checker challenges the answer. 6-7: Capture. Stop upload attempts at the bell. Keep paper/local photo. Give slips to three people. Extra people record or check. Combine slips if fewer people participate. Read aloud or help with writing on request. Write table ID and station letter on every answer. No speed points. === PARTICIPANT CARD A: THE MISSING DECISION === SHARED SCENARIO AND INSTRUCTIONS (keep this block intact) Assume today is January 5, 2027. Alder Services wants to replace its scheduling software. The operations director says, "If the demo goes well, we can move quickly." Choose the next conversation, not a forecast close date. ANSWER SHEET: Table ID ____ Station A KNOWN: one confirmed fact NOT YET KNOWN: two unresolved dependencies NEXT CONVERSATION: one question and a role who can answer it Check: Have we mistaken interest for purchase or launch approval? END SHARED BLOCK A CUT THESE THREE SLIPS SEPARATELY, ONE PER FACT HOLDER: A1 COMMERCIAL: Operations wants a decision this month. Finance signs purchases and has not attended a meeting. --- cut --- A2 TECHNICAL: A demo can show scheduling. The payroll connection has not been assessed. --- cut --- A3 ADOPTION: Supervisors cannot attend training during the next four weeks. The director's preferred launch falls inside that period. END SLIPS A === PARTICIPANT CARD B: THE PROMISE BOUNDARY === SHARED SCENARIO AND INSTRUCTIONS (keep this block intact) Assume today is January 5, 2027. Beacon Distribution asks whether all eight branches can go live on February 1. RouteDesk is fictional software, not Gather Shot. The customer wants a firm answer today. ANSWER SHEET: Table ID ____ Station B CONFIRMED CAPABILITY: what is supported CONDITION: preserve scope and dependency NEXT COMMITMENT: propose an owner, action and report-back date Check: Did "February 1" swallow the branch limit or data condition? Do not describe your proposed next step as already agreed by a customer. END SHARED BLOCK B CUT THESE THREE SLIPS SEPARATELY, ONE PER FACT HOLDER: B1 COMMERCIAL: February 1 is requested. Your company has not committed. --- cut --- B2 TECHNICAL: Comma-separated values (CSV) files, a spreadsheet export format, are supported. A direct legacy-system connection is unverified. --- cut --- B3 DELIVERY: Delivery can provision a two-branch pilot by February 1 only with a validated CSV by January 20. Eight-branch timing is unassessed. END SLIPS B === PARTICIPANT CARD C: THE RECEIVING-TEAM TEST === SHARED SCENARIO AND INSTRUCTIONS (keep this block intact) Assume today is January 5, 2027. Cedar Fieldworks has signed for a pilot. Sales is handing it to customer success. A signed order is not an agreed success measure. ANSWER SHEET: Table ID ____ Station C OUTCOME AND GAP: desired change and missing measurement SCOPE BOUNDARY: what is included and what requires review OWNER AND CONFIRMATION: who obtains what confirmation by a proposed date Check: A non-writer reads only the card. Can they tell what to do next and what not to assume? Revise if they need an oral explanation. END SHARED BLOCK C CUT THESE THREE SLIPS SEPARATELY, ONE PER FACT HOLDER: C1 SALES: The customer wants fewer missed service visits. No current number or target has been recorded. --- cut --- C2 DELIVERY: Pilot scope is one branch. Other branches need a separate expansion review. --- cut --- C3 CUSTOMER SUCCESS: The coordinator can attend January 12 kickoff. The branch manager must confirm the measure and has not accepted. END SLIPS C === TABLE REVIEW SHEET: REVEAL AT MINUTE 31 === Each table's checker completes its own log. The host answers questions and samples responses, not every card. Ready is not certification. A: One fact, two unknown dependencies, question and a role who can answer. Do not turn interest into approval. B: CSV capability, two-branch scope, validated CSV by January 20, and an owned action with a proposed date. Eight-branch timing unknown. C: Desired outcome, missing baseline and target, one-branch scope, internal owner/action/proposed date. Manager participation and measure remain unconfirmed. Coordinator availability is not full confirmation. Use ready / revise / not attempted. No totals, ranking or winner. Table ID | A check | B check | C check | Correction to revisit ________ | _______ | _______ | _______ | _____________________ Correct one card on paper or in shared text. Optional recapture happens after the session, with permission. No upload troubleshooting now. END TABLE REVIEW SHEET === OPTIONAL HOST REFERENCE: POSSIBLE ANSWERS === Do not read this whole reference during the four-minute self-review. These examples are not the only acceptable answers. Never require participants to match exact wording. A: Interest is not authorization. Need at least two unknowns and a question with a role who can answer it. Possible answer: "Known: operations wants a decision this month. Unknown: finance approval process and feasible training window. Next: Ask the finance director what approval steps are required." Payroll feasibility is another valid unknown. Tempting wrong answer: "Demo next week, then launch this month." Why revise: skips approval and the known training conflict. B: Preserve both two-branch scope and validated CSV by January 20. Possible answer: "Confirmed: CSV import. Condition: two-branch pilot by February 1 only if validated CSV arrives by January 20. Proposed next step: Account lead arranges delivery validation by January 19 and reports the outcome that day. Eight-branch timing open." January 19 is proposed, not an agreed customer commitment. If validated data misses January 20, do not promise the February 1 pilot. Tempting wrong answer: "Yes, February 1 if the data arrives." Why revise: drops validation, deadline and branch limit. Another weak answer: "We will try." It supplies no usable next step. C: Missing baseline and target remain unknown. Preserve one branch. Possible answer: "Reduce missed visits. Baseline and target unknown. One-branch pilot only. Customer success lead proposes contacting the branch manager by January 8 to request January 12 attendance and agreement on how to establish baseline and target. Coordinator available January 12. Manager acceptance and success-measure confirmation remain pending." January 8 is proposed, not an agreed customer deadline. The owner can commit to outreach, not guarantee the customer's response. Tempting wrong answer: "Kickoff January 12, reduce misses 20%, all branches." Why revise: invents a target, expands scope and assumes acceptance. DEBRIEF QUESTIONS Which fact would have disappeared if we had started with a pitch? What wording made the next step usable to its receiver? Which process habit will we try, and who volunteers to follow up? Invite two voluntary examples during table discussion. Read written contributions only with permission. Nobody has to present. Do not name departments as the problem or collect real account examples. ALTERNATIVES AND FAILURE PLAN No camera: keep paper or typed text. Same acceptance standard. No Wi-Fi: no uploads. Review locally. Never extend a round for networking. Remote: accessible shared text, same facts, remote host, same clock. Rehearse breakout entry. Read visual answers aloud or supply their text. Room too large/no writing surfaces: redesign logistics and pilot first. Running late in rehearsal: reduce writing or remove a station and reallocate time explicitly. Protect debrief, do not rush participation. OPTIONAL GATHER SHOT COLLECTION Create three prompts A/B/C. One willing submitter per table. Put table ID and station letter in the photo itself. Disable Public Gallery and turn off automatic approval before sharing. Both default on. Test pending status and hidden shared gallery. Guests can still see their own pending uploads. Do not run a slideshow. Personal completion is not team scoring. Tables keep review logs separately. Budget = tables x three photos, plus test uploads and retakes. Eight tables need 24 station photos. Thirteen need 39, or 52 with one test upload each. The trial's 50 unlocked uploads may not cover that. Uploads need internet. Do not assume automatic offline syncing. Paper-only operation is complete without Gather Shot.