Kiss & Tell
Kiss & Tell is a responsive webapp with various user roles: host, guest, and vendor. The platform streamlines the tasks of destination weddings and group travel and corrals all group decision communications to one streamlined social feed. Hosts can compare, build, and book their event venue and group accommodations packages in top global destinations and create and manage their guest lists, while their guests can book their own rooms and manage their attendance. Vendors can chat and negotiate their packages with hosts and use the social feed, for example, to gather guests’ meal preferences.
The Social Feed in Action
Whether managing a master guest list or subgroups, guests receive their relevant notifications in one convenient feed.
The challenge is to connect and inform the right guest at the right time- which is achieved with the creation of sublists/subgroups created in the guest list builder, allowing the host to notify only relevant guests.
I studied Facebooks newsfeed to design our version which includes many of the same features: the ability to tag guests, create polls, publish only to certain groups, and comment on posts.
Reducing Friction in a Fragmented Flow
The challenge was creating a seamless experience across disconnected parts of the platform. Adding event packages and rooms required users to jump back to the listings page—a disjointed experience.
I bridged these friction points with dismissible instructional modals and clear visual cues: toast notifications and green indicators that trained users to rely on the notification center in the action bar as their guide through the process.
Guest List & Group Travel Management
The challenge is to connect and inform the right guest at the right time- which is achieved with the creation of sublists/subgroups created in the guest list builder, allowing the host to notify only relevant guests.
One of the first tasks a host needs to do in order to manage their event is to create their guest list and assign guests to a sublist, which allows them to segment their newsfeed communications to only those relevant.
I studied other marketplace guest list creators and adopted the use of a ‘chip system’ which allows guest sublists to be visual and work as filters later when the host needs to sort and manage their guest attendance.
For adding guests, I studied other marketplace tools and decided a drawer is the most modern elegant solutions to adopt for adding the guest, as it allows you to remain on the screen for which you are adding content for a more seamless on the spot experience. The above video demonstrates how once guests are added, the host can filter the table by sublists using the chip system. In addition, they may also edit in place both the chip system in the table’s toolbar and also the guest with the familiar quick-access drawer experience, allowing them to stay in place on the screen they’re working on.
Mapping the Path to Self-Service
When I joined, my goal was to help transform the existing platform—which required heavy manual support from the CEO—into a fully self-service product.
I started by mapping user flows for each role to identify dependencies and edge cases. These flowcharts helped the team understand the full scope of re-engineering needed and plan our roadmap of self-service features.
I used Flowmapp to create these visual maps, which revealed every edge case and showed me exactly how many screen variations I needed to design for a seamless experience.
High-level user journey architecture showing authentication states and role-based pathways.
This map illustrates how different user types—logged in vs. logged out, various subscription tiers—navigate through distinct experiences. Each branching point represents critical decision logic that determines the appropriate self-service flow, laying the groundwork for the adaptive feed system detailed in the next diagram.
Deep-dive into the adaptive feed architecture and content card logic
This flowmap details how the feed dynamically serves different content types (Events, Accommodations, Activities) based on user status and interaction history. It maps every decision point—from guest browsing to authenticated actions—showing how the feed intelligently adapts to guide users toward relevant self-service actions, eliminating the need for manual support intervention.
Technical Specificactions
I document all functionality in outline format before and during hi-fi design to identify edge cases and map out flows. The team uses Google Docs to collaborate, define release scope, and plan future features. It becomes our single source of truth for roadmap planning and group decisions—and serves as the north star for front-end developers during implementation.
