Supplied brief - unverified: Working hypothesis: travellers need clarity on fit, itinerary, inclusions and the next planning step before committing to a customised holiday.
PRODUCT REQUIREMENTS · WORKING DRAFT · 2.1.0
Wanderer Planners
Experience more with Wanderer Planners
Explore the document
Product overview and executive intent
Define the user problem, product outcome and boundaries. The supplied brief is not validated research.
Scope, non-goals and prioritisation
Supplied brief - unverified: Proposed discovery scope: consistent planning information, enquiry handoff and itinerary review. Exclusions until verified: instant confirmation, live pricing, inventory promises and guaranteed visa outcomes.
Separate MVP requirements, later candidates and exclusions. Record priority rationale and dependencies; do not invent delivery dates.
Research evidence and limitations
Supplied brief - unverified: Verified source set: current Wanderer Planners website copy and design tokens; approved logo files; package, service, terms and privacy content; booking-enquiry form; and the versioned company collateral renderer. These sources verify the current assisted-planning experience. No customer interviews, conversion baseline or satisfaction study were supplied. Treat the persona and emotional insights below as hypotheses.
Record source ID, method, recruitment, date, sample size, denominator and limitations for each finding. Separate observation, hypothesis and decision. Do not invent survey results, interviews or quotes.
Audience, persona and jobs to be done
Supplied brief - unverified: Proposed role-based persona: a traveller coordinating a customised holiday for their group. Job: communicate preferences and evaluate a plan. Goals: fit, clarity and confidence; friction: unanswered questions about inclusions and confirmation.
Describe a role, context, goal, motivation, friction and job to be done. Label untested personas as hypotheses; avoid invented identities, portraits, demographic or health details.
Empathy map
Supplied brief - unverified: Says: no sourced quotes. Thinks (hypothesis): does the plan fit our needs? Feels (hypothesis): uncertain until details are clear. Does (hypothesis): compares itinerary options and asks questions. Validate with consented interviews.
Capture Says, Thinks, Does and Feels separately. Quote only sourced statements; label inferred thoughts and feelings. Link each insight to a source ID and validation question.
User journey and opportunities
Verified current entry path: discover
browse packages or services
inspect itinerary, inclusions and exclusions
submit an enquiry
receive personal follow-up. Proposed downstream stages to validate: discuss preferences
review a tailored proposal
confirm itinerary, terms and payment in writing
prepare
travel/support
follow-up. At each handoff show what is proposed, confirmed and awaiting action.
Supplied brief - unverified: Verified current entry path: discover -> browse packages or services -> inspect itinerary, inclusions and exclusions -> submit an enquiry -> receive personal follow-up. Proposed downstream stages to validate: discuss preferences -> review a tailored proposal -> confirm itinerary, terms and payment in writing -> prepare -> travel/support -> follow-up. At each handoff show what is proposed, confirmed and awaiting action.
For each stage record action, touchpoint, friction, emotion hypothesis, opportunity, owner and measure. Include before-use, core task and support or follow-up.
Task flow and recovery
Supplied brief - unverified: Verified public flow: explore -> choose a package or service -> submit name plus email or phone, preferences and contact consent -> receive an enquiry acknowledgement. Public copy states that a planner confirms the trip before booking. Proposed recovery and downstream flow to validate: form failure, preference clarification, proposal revisions, availability changes, written confirmation, preparation and support handoff.
Specify entry, prerequisites, decisions, success, empty/loading/error states, retry, cancellation and support. Check branch labels and avoid forcing account creation when the task does not require it.
Information architecture and card sorting
Supplied brief - unverified: Verified public groups include Home, About, Services, Packages, enquiry/contact, privacy and terms. Proposed task groups for evaluation: Explore; Custom planning enquiry; Itinerary and inclusions; Confirmation information; Preparation; Help. Card sorting and navigation usability are untested.
List navigation groups, content labels and relationships. A proposed grouping is not a completed card-sort study: record method, participants and results only when supplied.
Cross-channel strategy and constraints
Supplied brief - unverified: Use existing web and approved collateral channels. Do not assume an iOS/Android app, instant booking, live inventory, payment integration or automated travel support without verification.
Identify supported channels, devices, connectivity, permissions, integrations and fallback paths. Verify actual capabilities; do not infer mobile apps or GPS requirements from a reference.
Success measures and instrumentation
Supplied brief - unverified: Proposed: qualified enquiry completion; time to acknowledge enquiry; itinerary revision count; clarity feedback after review. Define denominators, baseline, targets, data minimisation and operational owner before collecting.
For each measure record definition, baseline, target, event/source, owner and review window. Unknown values stay unresolved; do not invent targets or improvements.
Validation, usability testing and iteration
Supplied brief - unverified: Proposed: ask representative travellers to find the planning enquiry, explain what is included, identify the next action and find help. Test mobile, keyboard, form errors and confirmation wording. Record observed issues and retest.
Proposed plan: recruit representative users with consent; test the primary task and one recovery path; record completion, errors, time and feedback. Set acceptance thresholds before testing, document findings and retest fixes.
Evidence to requirement traceability
Supplied brief - unverified: E-01 public terms and booking-form copy -> N-01 understand enquiry status -> R-01 explain the next step without implying a confirmed booking -> AC-01 acknowledgement labels enquiry status and a support route. E-02 package-detail structure -> N-02 understand scope -> R-02 separate inclusions, exclusions and items awaiting confirmation -> AC-02 a reviewer can identify each without inference.
Use E-01 evidence -> N-01 user need -> R-01 requirement -> AC-01 observable acceptance -> M-01 measure. Record source, priority, owner and unresolved questions. Missing links require review; this draft is not approval.
Functional requirements and acceptance
Supplied brief - unverified: E-01 public terms and booking-form copy -> N-01 understand enquiry status -> R-01 explain the next step without implying a confirmed booking -> AC-01 acknowledgement labels enquiry status and a support route. E-02 package-detail structure -> N-02 understand scope -> R-02 separate inclusions, exclusions and items awaiting confirmation -> AC-02 a reviewer can identify each without inference.
For every R-ID record actor, trigger, preconditions, expected result, data changes and Given/When/Then acceptance. Include permissions, validation, duplicate submission and recovery.
Non-functional requirements and data
Supplied brief - unverified: Use existing web and approved collateral channels. Do not assume an iOS/Android app, instant booking, live inventory, payment integration or automated travel support without verification.
Agree accessibility, performance, security, privacy, retention, reliability and support requirements. Define collected data, permission boundaries and failure handling; unknown numeric budgets remain open.
Delivery, dependencies and release readiness
Supplied brief - unverified: Brand owner, travel planning owner, customer support and content approver: to confirm. Prices, terms, availability and destination information require responsible owner approval.
Proposed phases: discover -> define -> ideate -> design -> test -> release. Record owners, dependencies, risks, rollout, rollback, support and review decisions. Validate locally, then integration, then production separately.