--- title: "Tandem, a Studio Concept" description: "Studio concept: Tandem turns a group chat's dates and budgets into comparable weekend options, then waits for every person to agree before anyone books." kind: concept kindLabel: "Concept" status: "Concept — no client, nothing shipped, no metrics." concept: true year: "2026" location: "Mobile web, Canada" sector: "Travel / consumer app" services: ["Product UX and UI", "Mobile app design"] dateCreated: 2026-10 canonical: https://uxpro.ca/work/tandem publisher: "UXPro Design Studio" license: "Quote freely with a link to the canonical URL." --- # Tandem (Concept) — What can the whole group say yes to? **Concept.** Concept — no client, nothing shipped, no metrics. > No client commissioned it and no business has been measured against it. Any figure on this page is a projection, and its assumptions are printed with it. The hard part of a weekend away is getting dates, budgets and preferences out of a group chat without making one friend reconcile them all. This mobile concept gathers dates and private limits, compares options on the same facts, and records a plan only when everyone says yes—so the group can see what fits before anyone books. Canonical page: https://uxpro.ca/work/tandem ## Project story at a glance - **The challenge:** Dates, budgets and preferences stay buried in a group chat, leaving one organiser to reconcile them and a vote that can ignore someone's limit. - **The decision:** Keep each total private, compare every option against the same dates and costs, and count agreement only after each person says yes. - **Why it helps:** The group can see what fits and whether everyone agreed before booking tasks begin. Tandem is a studio concept; nobody has used or tested it. ## Facts | Fact | Value | |---|---| | Our role | Self-initiated study | | Scope | Turn a group chat’s maybe into agreed dates, a budget that fits, a place and a yes from everyone | | Constraints | The hard part of a weekend away is agreeing, not finding another place: dates, budgets and preferences stay buried in a chat, and one organiser does the reconciling. | | Status | Studio concept · nothing shipped · nothing measured | ## The question *What can the whole group say yes to?* The hard part of a weekend away is agreeing, not finding another place: dates, budgets and preferences stay buried in a chat, and one organiser does the reconciling. Shared lists, wishlists with votes and collaborative itineraries already exist, and a vote can still pick a weekend someone cannot afford. So the product protects every person's limits before it counts preferences, keeps each budget private, and treats silence as silence, never as a yes. ## Decisions Three decisions, each as a strike, an insertion and a numbered reason. - Feasibility before popularity. - The budget is private, and it is a total. - Silence never counts as agreement. ## What we did not do - A popularity vote that can override someone's limit. - Showing anyone's exact budget to the group. - Treating no reply by a deadline as a yes. - Booking and payment inside the first version: people book directly with the provider. - Requiring an app install before a friend can add their dates. - Ratings, waitlist counts or testimonials we do not have, on the landing page. ## Why we made this Nothing was shipped and nothing was measured. We design mobile products as well as websites, and the hardest part of most consumer apps is not a screen. It is a rule: who decides, what counts as yes, and what happens when something changes. We wanted to work one of those rules through end to end, from the first message in a group chat to the booking tasks, in a product's own identity, so a founder can see how we turn a messy human moment into a flow, a system and a plan to test it. ## Validation Interviews with organisers and invitees about recent group trips, including ones that never happened, to rebuild the chat-to-decision path. A prototype study with existing friend groups: private input, cost comparison, disagreement and the final acceptance step. A small concierge pilot on real weekend plans with hand-curated options, through the booking handoff and any changes after agreement. The acceptance rule we would hold it to: no agreed plan may break a limit someone submitted. ### The limits - Tandem, the friends, the weekends and every cost on these screens are invented. Nobody has used it and nothing has been tested. - The other three friends in the prototype are scripted; their dates and limits are fixed. - Limits stay private, but in a group of four a Fits all signal can still hint at someone's limit. That needs testing. - Competitor features informed the concept; a gap in the market has not been established. - The screens are our renders; the coastal photograph inside some of them is a generated image. The name has not been cleared. ## Why we made this **So the product protects every person's limits before it counts preferences, keeps each budget private, and treats silence as silence, never as a yes.** We design mobile products as well as websites, and the hardest part of most consumer apps is not a screen. It is a rule: who decides, what counts as yes, and what happens when something changes. We wanted to work one of those rules through end to end, from the first message in a group chat to the booking tasks, in a product's own identity, so a founder can see how we turn a messy human moment into a flow, a system and a plan to test it. | | | |---|---| | Type | Studio concept | ## Credits - Project: Tandem (fictional) - Sector: Travel / consumer app - Disciplines: Product strategy, Mobile UX and UI, Visual identity, Prototype, Validation plan - Type: Studio concept, not a client engagement --- Read the illustrated page: [Tandem](https://uxpro.ca/work/tandem)