[{"data":1,"prerenderedAt":461},["ShallowReactive",2],{"layout-profile":3,"project-product-design-booking-engine-setup-en":13,"project-cards-en":370,"client-hubs-en":455},{"title":4,"acf":5,"featured_image":11},"Pablo Goris",{"actual_job":6,"role":7,"hero_title":8,"headline":9,"description":10},"Designer at Alea","Senior Product Designer","Hello! I'm Pablo","Designing clarity across products, systems and evolving workflows by combining UX, product thinking and AI accelerated execution to turn complex ideas into scalable experiences with real business impact.","",{"url":12,"alt":4},"/media/2026/02/pablo.webp",{"id":14,"title":15,"acf":16,"body":309,"card":314,"company":38,"cover":29,"coverAlt":322,"date":323,"description":324,"encrypted":325,"extension":326,"meta":327,"navigation":34,"path":328,"postType":329,"role":330,"sections":331,"seo":366,"status":367,"stem":368,"subtitle":19,"__hash__":369},"productDesign/product-design/booking-engine-setup.md","Booking Engine Setup",{"hero":17,"projectOverview":31,"challenge":50,"objectives":77,"process":101,"research":124,"lofi":153,"finalUi":193,"handoff":224,"results":246,"learnings":284},{"title":18,"lead":19,"text":20,"tags":21,"imageLayout":26,"images":27},"Guesty · Booking Engine Setup","Redesigning a complex setup flow for self-onboarding","\u003Cp>Guesty's Booking Engine Setup lets property owners publish a direct-booking experience, but the configuration flow was driven more by business and technical considerations than by user understanding. I redesigned the setup to reduce friction, support both beginner and expert users, and enable self-configuration without relying on support.\u003C/p>",[22,23,24,25],"Product Designer","User Research","User Flows","Prototyping & Testing","single",[28],{"src":29,"alt":30},"/media/projects/guesty/hero.webp","Booking Engine Setup interface",{"title":32,"lead":33,"cardsFirst":34,"singleRow":34,"cards":35,"text":49},"Project overview","A focused redesign inside a cross-functional product team",true,[36,40,43,46],{"lead":37,"text":38,"tone":39},"Company","Guesty","subtle",{"lead":41,"text":42,"tone":39},"Period","Jul – Aug 2023",{"lead":44,"text":45,"tone":39},"Role","Research · Information architecture · Visual design · Prototyping & testing",{"lead":47,"text":48,"tone":39},"Team","Domain Lead · Design Lead · 2 Product Managers · Product Designer · 2 Developers","\u003Cp>The Booking Engine Setup lets a property owner create a B2C booking experience within a third-party environment or a Guesty website. The redesign combined a visual refresh with a usability goal: remove obstacles that prevented owners from completing setup and publishing properties for direct reservations.\u003C/p>",{"title":51,"lead":52,"text":53,"groups":54},"The challenge","60% of users did not complete the setup","\u003Cp>The existing system lacked a self-explanatory interface and had usability problems alongside technical limitations. Many users abandoned configuration, so the final setup required support. Dashboard data revealed the problem and provided a measurable starting point for the redesign.\u003C/p>",[55,66,71],{"cards":56},[57,60,63],{"lead":58,"text":59,"stat":34},"60%","of users did not complete the setup",{"lead":61,"text":62,"stat":34},"Support","was needed to finish configuration",{"lead":64,"text":65,"stat":34},"B2C","publishing was blocked when setup failed",{"note":67},{"type":68,"title":69,"message":70},"info","Design opportunity","Turn a support-dependent configuration into a guided, self-explanatory flow that can be completed, paused and resumed without losing progress.",{"title":72,"images":73},"Design challenges",[74],{"src":75,"alt":76},"/media/projects/guesty/design-challenges.webp","Map of the usability problems found in the original setup",{"title":78,"lead":79,"groups":80},"Objectives & constraints","The redesign had to work for both new and experienced operators",[81],{"cards":82},[83,86,89,92,95,98],{"lead":84,"tone":39,"text":85},"Reduce friction","Remove unnecessary decisions and clarify what is required at each step.",{"lead":87,"tone":39,"text":88},"One flow, two skill levels","Support beginner and expert users without creating separate experiences.",{"lead":90,"tone":39,"text":91},"Self-explanatory onboarding","Make the interface understandable without depending on support.",{"lead":93,"tone":39,"text":94},"Save and continue later","Allow work to be preserved across a longer setup process.",{"lead":96,"tone":39,"text":97},"Prepare premium conversion","Keep the flow ready for the future Premium website + Booking Engine plan.",{"lead":99,"tone":39,"text":100},"Respect technical reality","Design within PMS, channel-manager and implementation constraints.",{"title":102,"lead":103,"text":104,"groups":105},"Process","A four-phase Double Diamond adapted to a short delivery window","\u003Cp>The project progressed from requirements and problem definition to validation, prototyping, and delivery. Research hypotheses were checked with the team and internal stakeholders. Regular conversations with developers kept the proposed flow aligned with technical feasibility.\u003C/p>",[106,120],{"cards":107},[108,111,114,117],{"lead":109,"tone":39,"text":110},"01 · Discover","Requirements analysis · problem understanding · usability review · hypothesis generation",{"lead":112,"tone":39,"text":113},"02 · Define","Research · interviews · hypothesis validation · brainstorming · content organization",{"lead":115,"tone":39,"text":116},"03 · Validate","Lo-fi prototypes · iterative developer alignment · task tests with internal users",{"lead":118,"tone":39,"text":119},"04 · Deliver","Hi-fi prototypes · design-system application · materials prepared for implementation",{"note":121},{"type":68,"title":122,"message":123},"Working principle","Validation and technical alignment happened during the design process, not only at the end of it.",{"title":125,"lead":126,"text":127,"groups":128},"Research & definition","Define the user first, then restructure the setup","\u003Cp>Early in the project, I needed a clearer picture of who was configuring the Booking Engine. I combined dashboard information with knowledge from designers who had worked longer with the product. Then I used brainstorming and card sorting with stakeholders to reorganize the content and validate the main architecture.\u003C/p>",[129,143,147],{"cards":130},[131,134,137,140],{"lead":132,"tone":39,"text":133},"Property owners & operators","People responsible for configuring and publishing accommodation for direct booking.",{"lead":135,"tone":39,"text":136},"Revenue managers","Hospitality professionals responsible for pricing, inventory and commercial performance.",{"lead":138,"tone":39,"text":139},"Sales managers","Users with a sales or marketing background who need the booking experience to support conversion.",{"lead":141,"tone":39,"text":142},"Marketing managers","Users focused on presentation, content and how the booking experience connects to the brand.",{"note":144},{"type":68,"title":145,"message":146},"Architecture validation","We treated the initial structure as a hypothesis. A card-sorting exercise with key stakeholders confirmed hierarchy and grouping before moving into detailed interaction design.",{"images":148},[149],{"src":150,"alt":151,"caption":152},"/media/projects/guesty/research.webp","Brainstorming and card sorting used to reorganize the setup content","Content organization — brainstorming & card sorting",{"title":154,"lead":155,"text":156,"groups":157},"Lo-fi & validation","Test the architecture before investing in the final interface","\u003Cp>Once I defined the architecture and information hierarchy, I created low-fidelity prototypes to test the assumptions. Developer reviews were part of this phase because the proposal to save progress at every step revealed technical constraints that needed to be solved before visual refinement.\u003C/p>",[158,169,181],{"cards":159},[160,163,166],{"lead":161,"tone":39,"text":162},"Validate with tasks","Use prototypes to check whether users and internal stakeholders understand the setup sequence.",{"lead":164,"tone":39,"text":165},"Align with development","Review feasibility continuously instead of waiting for a final handoff.",{"lead":167,"tone":39,"text":168},"Preserve progress","Treat save-and-continue-later as a core behavior, not a secondary enhancement.",{"imagesColumns":170,"images":171},3,[172,175,178],{"src":173,"alt":174},"/media/projects/guesty/lofi-1.webp","Low-fidelity prototype of the setup sequence",{"src":176,"alt":177},"/media/projects/guesty/lofi-2.webp","Low-fidelity prototype of the configuration steps",{"src":179,"alt":180},"/media/projects/guesty/lofi-3.webp","Low-fidelity prototype of the review and publish step",{"title":182,"cards":183},"Content status protocol",[184,187,190],{"lead":185,"tone":39,"text":186},"Green · Finished","Content reviewed and ready to move forward.",{"lead":188,"tone":39,"text":189},"Yellow · In progress","Content still being defined or reviewed.",{"lead":191,"tone":39,"text":192},"Black · Not reviewed","Content not yet validated by the team.",{"title":194,"lead":195,"text":196,"groups":197},"Final UI","Apply the Guesty design system to a validated flow","\u003Cp>The high-fidelity phase translated the validated architecture and interaction rules into the Guesty design system. The goal was to ensure visual consistency and make the sequence, current state, and available actions easier to understand throughout the setup.\u003C/p>",[198,212],{"cards":199},[200,203,206,209],{"lead":201,"tone":39,"text":202},"Guided progression","Each step makes the next action and required information easier to identify.",{"lead":204,"tone":39,"text":205},"Clear system state","Users can understand where they are and what is already complete.",{"lead":207,"tone":39,"text":208},"Save & resume","Longer configuration can be interrupted without forcing a restart.",{"lead":210,"tone":39,"text":211},"Preview & control","Configuration choices are connected more clearly to the resulting booking experience.",{"imagesColumns":213,"images":214},2,[215,218,221],{"src":216,"alt":217},"/media/projects/guesty/hifi-1.webp","High-fidelity screen of the setup flow",{"src":219,"alt":220},"/media/projects/guesty/hifi-2.webp","High-fidelity screen of the configuration options",{"src":222,"alt":223},"/media/projects/guesty/hifi-3.webp","High-fidelity screen showing progress and system state",{"title":225,"lead":226,"text":227,"groups":228},"Developer handoff","Document the system, not only the screens","\u003Cp>Technical alignment happened during prototyping. The handoff focused on making implementation decisions explicit: component behavior, states, variants, and constraints imposed by the channel manager and property management system.\u003C/p>",[229,240],{"cards":230},[231,234,237],{"lead":232,"tone":39,"text":233},"Components","Reusable elements and their intended behavior were documented for implementation.",{"lead":235,"tone":39,"text":236},"States & variants","The team could see how inputs, selections and actions changed across the flow.",{"lead":238,"tone":39,"text":239},"Technical constraints","Feasibility was documented alongside the design instead of being discovered after delivery.",{"images":241},[242],{"src":243,"alt":244,"caption":245},"/media/projects/guesty/handoff.webp","Component documentation prepared for developer handoff","Component documentation & handoff",{"title":247,"lead":248,"text":249,"groups":250},"Results & impact","The redesign reduced abandonment and made self-setup more viable","\u003Cp>The new flow addressed the main friction points in the original setup and created a single experience for different expertise levels. The project also reduced dependency on support and improved the path to future premium adoption.\u003C/p>",[251,268,280],{"cards":252},[253,256,259,262,265],{"lead":254,"text":255,"stat":34},"40% ↓","dropout from the setup process",{"lead":257,"text":258,"stat":34},"30% ↑","efficiency during setup",{"lead":260,"text":261,"stat":34},"25% ↑","successful self-setup",{"lead":263,"text":264,"stat":34},"20% ↓","need for customer support",{"lead":266,"text":267,"stat":34},"15% ↑","adoption of premium plans",{"title":269,"cards":270},"Product outcomes",[271,274,277],{"lead":272,"tone":39,"text":273},"Unified setup flow","One process supports both beginner and expert users without splitting the experience.",{"lead":275,"tone":39,"text":276},"Self-onboarding","The interface provides more context and guidance so owners can configure the product themselves.",{"lead":278,"tone":39,"text":279},"Save and continue","Progress can be preserved, reducing the cost of longer or interrupted setup sessions.",{"note":281},{"type":68,"title":282,"message":283},"Business connection","Improving completion of the Booking Engine setup directly supports the ability of property owners to publish inventory for B2C reservations.",{"title":285,"lead":286,"groups":287},"Learnings & next steps","What this project changed in my design practice",[288,299,305],{"cards":289},[290,293,296],{"lead":291,"tone":39,"text":292},"Understand technical constraints","Knowing the limitations of the channel manager and PMS was essential to designing a flow that could actually be implemented.",{"lead":294,"tone":39,"text":295},"Use data to guide decisions","Dashboard evidence helped frame the problem, prioritize friction and create measurable product goals.",{"lead":297,"tone":39,"text":298},"Design for accessibility","The setup has to remain usable for people with different abilities, expertise levels and working contexts.",{"title":300,"list":301},"Next steps",[302,303,304],"Monitor the setup flow after implementation and connect completion to business outcomes such as published properties, bookings and revenue.","Use the implemented analytics events to collect quantitative behavior data and identify remaining friction.","Continue optimizing the experience from real usage while preserving the technical alignment established during the redesign.",{"note":306},{"type":68,"title":307,"message":308},"Key takeaway","A strong setup experience is more than a sequence of screens. It depends on content structure, technical feasibility, clear system state, and shared understanding among design, product, and engineering.",{"type":310,"value":311,"toc":312},"minimark",[],{"title":10,"searchDepth":213,"depth":213,"links":313},[],{"title":315,"description":316,"tags":317,"image":320},"Guesty - New Onboarding Flow","New architecture for the setup of Guesty’s Booking Engine to make configuration easy, removing obstacles so property owners can set it up quickly and start welcoming guests sooner.",[318,319],"UX Research","Product Strategy",{"src":29,"alt":321},"Booking Engine Setup de Guesty","Guesty Booking Engine Setup interface","July 2023","Guesty's Booking Engine Setup let property owners publish a direct-booking experience, but the configuration flow was built around business and technical needs instead of user understanding. The redesign reduced friction, supported beginner and expert users, and enabled self-configuration without relying on support.",false,"md",{},"/product-design/booking-engine-setup","case_study","Product Design, User Research, User Flows, Prototyping & Testing",[332,335,339,342,345,347,350,354,357,360,363],{"id":333,"label":334,"field":333},"hero","Overview",{"id":336,"label":337,"field":338},"project-overview","Project Overview","projectOverview",{"id":340,"label":341,"field":340},"challenge","Challenge & Evidence",{"id":343,"label":344,"field":343},"objectives","Objectives & Constraints",{"id":346,"label":102,"field":346},"process",{"id":348,"label":349,"field":348},"research","Research & Definition",{"id":351,"label":352,"field":353},"lo-fi","Lo-fi & Validation","lofi",{"id":355,"label":194,"field":356},"final-ui","finalUi",{"id":358,"label":359,"field":358},"handoff","Developer Handoff",{"id":361,"label":362,"field":361},"results","Results & Impact",{"id":364,"label":365,"field":364},"learnings","Learnings & Next Steps",{"title":15,"description":324},"published","product-design/booking-engine-setup","HYCT29ioDcd40pWXLs7PEvdwJ1JSOZJbdKWNxnziqTA",{"/product-design/astra-fm-app":371,"/product-design/astra-redesign":386,"/product-design/booking-engine-setup":396,"/product-design/jackpot-ecosystem":399,"/product-design/la-caixa":411,"/product-design/new-client-area":422,"/product-design/new-reservation-details":432,"/product-design/redesign-breast-simulator":445},{"title":372,"description":373,"tags":374,"image":380,"to":383,"status":367,"company":384,"date":385},"Astra.fm Mobile App","A mobile experience intended for the purpose of extending Astra.fm's music ecosystem, drawing in new listeners, and improving audience retention.",[375,376,377,378,379],"Research","Design","Testing","Development","Monitoring",{"src":381,"alt":382},"/media/projects/astra-fm-app/final-home.webp","Pantalla de inicio de la app de Astra.fm","/product-design/astra-fm-app","Astra","August 2026",{"title":387,"description":388,"tags":389,"image":392,"to":394,"status":367,"company":384,"date":395},"Astra Redesign","Rebuilding a multimedia radio platform around streaming, discovery and a clearer visual identity.",[390,391],"Product Design","Design Systems",{"src":393,"alt":387},"/media/2026/02/Captura-de-pantalla-2026-02-13-a-las-18.22.02-scaled.webp","/product-design/astra-redesign","September 2024",{"title":315,"description":316,"tags":397,"image":398,"to":328,"status":367,"company":38,"date":323},[318,319],{"src":29,"alt":321},{"title":400,"description":401,"tags":402,"image":404,"to":407,"status":408,"company":409,"date":410},"Alea - Jackpot Ecosystem","Two products defined from their business rules: an engine where a campaign is configured tab by tab, and a manager for the player-facing template.",[390,403],"UX Architecture",{"src":405,"alt":406},"/media/projects/alea/jackpot/image-home.webp","Template Manager, Content tab, with the opt-in modal previewed on a phone","/product-design/jackpot-ecosystem","private","Alea","2025",{"title":412,"description":413,"tags":414,"image":417,"to":420,"status":367,"company":412,"date":421},"La Caixa","PAC is a private initiative belonging to the La Caixa Foundation. It is a public platform where users can book rooms anywhere in Spain.",[415,416],"Researcher","User testing",{"src":418,"alt":419},"/media/2026/03/image-hero-detail.webp","Plataforma de reservas de La Caixa","/product-design/la-caixa","April 12, 2017",{"title":423,"description":424,"tags":425,"image":427,"to":430,"status":408,"company":409,"date":431},"Alea - Client Area","A design system built from the product's needs and applied to the new Client Area: catalogue, calendar, downloads and RTP.",[390,426],"Design System",{"src":428,"alt":429},"/media/projects/alea/client-area/dashboard.webp","New Client Area dashboard","/product-design/new-client-area","October 16, 2024",{"title":433,"description":434,"tags":435,"image":438,"to":441,"status":442,"company":443,"date":444},"Kigo - New reservation details","The redesign organized the reservation detail to avoid confusion and reduce calls and emails to support.",[436,437],"IA Design","Prototyping and testing",{"src":439,"alt":440},"/media/2026/02/image-hero-detail-v2.svg","Detalle de reserva de Kigo","/product-design/new-reservation-details","wip","Kigo","March 14, 2019",{"title":446,"description":447,"tags":448,"image":449,"to":452,"status":367,"company":453,"date":454},"Crisalix - 3D Aesthetic simulation","Redesign Crisalix's simulation experience so that surgeons would find it easier to create and manage 3D aesthetic procedure simulations based on patient images.",[390,23],{"src":450,"alt":451},"/media/projects/crisalix/hero.webp","Simulador de Crisalix","/product-design/redesign-breast-simulator","Crisalix","July 2019",[456],{"slug":457,"name":409,"logo":458,"logoAlt":409,"summary":459,"description":460},"alea","/media/2026/02/Alea-RVB-Colour.svg","Product design for Alea, from the design system to the products built on it.","Product design for Alea, from the design system to the products built on it. Some details are confidential, so these case studies sit behind one password.",1793895644671]