Visual Seating Planner for a 200-Guest Dinner Party: Workflow and One-Year Launch Plan

A friend of yours is hosting a dinner party for about 200 guests and is stuck on where everyone should sit at the venue. All of the planning, guest list included, currently lives in a spreadsheet, and your friend has said that a better way to see that information visually would help. Your friend also cares about how the evening feels for guests: the seating should help people form new relationships while still giving them time with people they already know. Design a new, visual product that helps arrange guests so they sit near others who share an interest with them. Deliver two things: a simple workflow showing how your friend would use the product to arrive at a seating chart, and a recommended work plan for developing and launching the tool within one year. ### Clarifying Questions - Is the tool meant only for this one party, or should it serve other hosts and event planners once launched? Does the one-year window need to deliver something usable before this party takes place? - What does the spreadsheet already record about each guest (interests, who knows whom, plus-ones, dietary needs), and what would the product have to collect itself? - How is the venue laid out: a fixed set of tables of one size, or a flexible floor plan? Are there hard rules, such as couples sitting together or certain guests being kept apart? ### Part 1 — Design the seating workflow Walk through the steps from the existing spreadsheet to a final seating chart the host can share. Explain how the product learns about guests' interests and relationships, how it proposes table assignments, how the host sees and adjusts the plan visually, and how it balances meeting new people against time with existing friends. ```hint Two goals pull against each other Seating friends together nurtures existing ties but leaves less room to meet someone new. Decide how the workflow represents both goals at each table and lets the host see the balance. ``` #### What This Part Should Cover - Bringing guest data in from the spreadsheet and filling gaps in interests and relationships. - How table assignments are proposed against hard rules and the two relationship goals. - The visual editing experience and the feedback the host gets while rearranging guests. ### Part 2 — Plan the one-year build and launch Recommend how to develop and launch the tool within a year: what ships first, how each stage is validated, the main milestones, and how you would judge whether the launch succeeded. ```hint A party date does not move A seating chart has a hard deadline. Think about the smallest version a real host could finish a chart with, and what can safely wait until after that. ``` #### What This Part Should Cover - Phased milestones from discovery to launch, with the scope of each phase. - How each phase is tested with real hosts before the next begins. - Launch success metrics and the main risks, including guest data privacy and adoption. ### What a Strong Answer Covers - A clear primary user and the jobs the product does that a spreadsheet cannot. - A workflow that turns spreadsheet data into a visual chart while leaving the host in control of the final decision. - An explicit way to trade off new connections against existing relationships, alongside hard seating rules. - A one-year plan whose phases, validation and metrics follow from the workflow. ### Follow-up Questions - Twenty guests reply late, two days before the party. How does the product absorb the change without reshuffling everyone? - After the party, how would you measure whether guests actually made new connections? - Asking guests about their interests ahead of time involves personal data. What privacy concerns does that raise, and how would you handle them?