A functional prototype connecting campground management, reception and field work — from reservation to lot release.
Five individual views of the functional prototype and interface concepts. These screens illustrate the proposed experience, not measured operational results.
Long screens scroll vertically inside the image.
Occupancy, arrivals and alerts in one management view.
Spatial context for availability and lot allocation.
A progressive flow with the total visible throughout the task.
Reservation context and service shortcuts in a conversational interface.
Tasks and operational alerts for the staff experience.
CampFlow explores how campground teams can keep reservations, lot conditions and service tasks connected across reception and field work. The starting problem hypothesis is that information split between messages, spreadsheets and informal handoffs makes operational exceptions harder to identify and resolve.
I independently shaped the product scope, journeys, UX/UI and functional prototype, using AI to explore scenarios and accelerate implementation. The current evidence is the prototype and its documented flows; this case does not report measured operational gains.
The design problem was to preserve the context of a reservation as it moves between people and channels. A 20A motorhome assigned to a 10A lot, a pending maintenance task or an unconfirmed payment needs a visible consequence and a clear next action. These scenarios guided the design; their frequency and business impact still need validation with campground teams.
How do we give the manager control of the whole without adding bureaucracy to whoever is at the front desk or in the field?
Four perspectives guided the product. Each needed an interface and a level of information compatible with their context.
Wants to see occupancy, cash flow and bottlenecks to decide quickly.
Needs to locate reservations, accommodate walk-ins and complete check-ins without queues.
Executes cleaning and maintenance on the phone, often under sun or rain.
Expects to book, pay and find their way autonomously before and during the stay.
I organized the journey from discovery and booking to arrival, stay and lot release. The decision was to treat these as one lifecycle with shared reservation context. The trade-off is a broader product scope: each handoff needs clear ownership and exception states rather than another isolated screen.
Get to know the campground and compare options.
Choose a lot, pay and receive confirmation.
Identify the reservation and check in.
Consume services and receive support.
Check out, inspect and prepare the lot.
I established reusable tokens and component rules for the prototype, combining deep greens and sand tones with Fraunces headings. Operational states pair color with a label and dot. Visible focus and generous touch targets guide the design; a complete accessibility audit across the implemented product remains a separate validation task.
#26673C#3B9555#E69C3A#C9302D#193220The dashboard puts occupancy, arrivals, revenue and exceptions in one overview, with actions attached to alerts. I prioritized signals that can lead to a decision rather than giving every metric equal weight. Testing should establish whether managers can identify the most urgent issue without scanning the whole workspace.
The arrivals list connects each reservation to its lot and current status. Keeping the overview separate from the guided check-in supports two tasks: scanning the day's arrivals and completing one guest's process. Whether this separation reduces errors or waiting time remains to be tested.
The visual map represents zones, infrastructure and lot status, so compatibility can be considered alongside availability. This adds spatial context but also requires status and filter rules to stay consistent with the list and check-in flow.
The five-step flow moves from guest identification through reservation, services, payment and confirmation. The key decision was to expose compatibility exceptions before confirmation while keeping the total visible. A guided sequence adds steps, so validation should check whether the added structure helps staff handle exceptions without slowing routine arrivals.
The conversational concept places confirmations, maps and guest support in WhatsApp rather than requiring another app. It illustrates continuity before arrival; the screen alone does not demonstrate a deployed messaging integration or its reliability.
The staff-app concept turns service requests into a queue with zone, responsibility and status. The design goal is to keep reception and field teams working from the same operational context. Outdoor readability, connectivity constraints and the timing of alerts need validation in actual field conditions.
A reconstructed example of fragmented channels contrasted with the proposed shared operational state. This comparison illustrates the design hypothesis; it is not a measured before-and-after result.
Duplicate information · invisible tasks · no shared status
After: connected operation
Complete a simplified check-in and see the operation update. Fictional data; interaction derived from the functional prototype.
A-12 matches vehicle size and electrical requirements.
Lot A-12 is now occupied. The dashboard and field team received the same status.
The following examples connect the design decisions to their supporting exploration. Original prompts are available on demand.
The analysis filtered out generic hotel pain points and focused the product on campground-specific operational risks: lot compatibility, distributed field work, occupancy and maintenance.
Act as a market research specialist for alternative hospitality in Brazil...
Each critical exception was split into a system response and a human decision. This shaped the guided check-in, compatibility checks, maintenance alerts and shared operational status.
Design the detailed front-desk check-in and field-team operation flow for CampFlow. Do not create an idealized happy path...
AI expanded the scenario space and made exceptions visible early. Prioritizing which risks deserved product behavior — and where human judgment must remain — was a design decision.
AI supported scenario exploration and functional prototyping. I defined the campground-specific scope, prioritized operational exceptions and decided where human judgment was necessary.
The result so far is a functional prototype connecting management, reception and field-work scenarios, supported by a shared design system. It makes the proposed operating model tangible. Reduced queues, fewer allocation conflicts and better coordination remain impact hypotheses, not measured outcomes.
Unified view of occupancy, revenue and operation
Less conflict between reservation and lot capacity
Guided check-in prepared for additional sales
Continuity between reception and field team
Results presented as impact hypotheses of the prototype; metrics should be validated in a pilot.
Proposed pilot tasks: locate a reservation, detect the 20A/10A mismatch, choose a compatible lot, complete payment and confirmation, then hand a service request to the field team. Observe completion, time, errors, requests for help and how participants explain the current status. These are planned checks, not completed usability findings.
The design work made one dependency explicit: a shared operational state is useful only when each role understands who acts next and why. The map, guided check-in and task queue express different views of that same context. The next learning cycle should test those handoffs with real teams before expanding the scope.