Case Study 05 · Hospitality Integrations

Delivering Hospitality IoT & Third-Party Integrations

How I translated client requirements into integration user stories, coordinated developers and external technology teams, prepared a test environment, and supported integration testing and client delivery.

Product Delivery Integration Testing Cross-functional Coordination
Role Product Delivery Manager
Project focus Hospitality IoT and third-party integrations
Systems involved PBX, voicemail, Wi-Fi, and external platforms
Delivery scope Requirements, testing, coordination, and go-live
On this page · Jump to a section
01

Project Overview

Connecting hospitality workflows with external technology

Hospitality properties often rely on multiple systems working together to support their day-to-day operations. These may include property management software, telephony, voicemail, Wi-Fi services, and other third-party platforms.

My work involved helping deliver integrations between the hospitality platform and external systems. This required understanding client expectations, documenting requirements, coordinating implementation, and validating that integrations behaved as expected before delivery.

The work spanned several integration types and external providers, each with its own requirements and coordination needs.

My focus Bridging the gap between what the client needed, what the product was expected to do, and what the technical teams needed to deliver and validate.
02

The Challenge

Keeping business requirements and system behaviour aligned

Third-party integration delivery required business requirements, product behaviour, and external system expectations to be aligned. Issues could arise from unclear requirements, differences between systems, configuration dependencies, or unexpected behaviour during testing.

  • Understand the client's intended workflow and translate it into clear product requirements.
  • Coordinate development work with internal engineers and external technology providers.
  • Establish a suitable test environment for validating integration behaviour.
  • Investigate integration issues and coordinate resolution before delivery.
  • Support go-live and follow-up troubleshooting when required.
03

Interactive Delivery Workflow

Select a stage to explore how I contributed

My delivery work followed a practical sequence from understanding client needs to validating integrations and supporting delivery. Select each stage below.

From requirements to go-live

5 connected stages

01 · Requirements gathering

I worked with clients to understand the intended business workflow and the expected behaviour of the integration before translating those needs into requirements.

Illustrative workflow based on my delivery responsibilities; individual integrations could differ in their implementation.

04

My Role and Contributions

Expand each area to see the responsibilities involved

01 Requirements Gathering & User Stories Turning client needs into actionable work
  • Worked with clients to understand integration requirements and expected business behaviour.
  • Translated requirements into user stories and actionable tasks for the development team.
  • Clarified requirements and answered questions that arose during implementation.
  • Helped align client expectations with the intended behaviour of the integrated systems.
02 Internal & Third-Party Coordination Managing communication and dependencies
  • Coordinated with developers and third-party teams to progress integration work.
  • Followed up on dependencies, technical questions, and issues affecting delivery.
  • Helped maintain alignment between the business requirement and technical implementation.
03 Test-Environment Setup & Validation Checking integration behaviour before delivery
  • Set up the IoT test environment required to validate integrations.
  • Tested integration behaviour before delivery to the client.
  • Investigated unexpected results and coordinated with relevant technical teams to resolve issues.
  • Supported follow-up testing where changes were required.
04 Delivery, Go-Live & Troubleshooting Supporting delivery through post-go-live issues
  • Coordinated integration delivery to the client.
  • Supported go-live activities and helped address integration issues when they arose.
  • Worked with developers and external teams during post-delivery troubleshooting.
05

Integration Areas

Examples of hospitality technology covered by my work

My experience covered multiple types of hospitality technology integrations, including:

PBX & Telephony

Integrations involving hotel phone systems and the related workflows that support hospitality operations.

Communication systems

Wi-Fi & Connectivity

Connectivity-related third-party integrations that needed validation within the test environment.

Connectivity services

Voicemail

Integrations involving voicemail functionality and its expected behaviour alongside hospitality systems.

Guest communication

External Platforms

Coordination and validation involving external hospitality providers and platform-specific requirements.

Third-party ecosystems

Examples of external providers

Canary Virdee Toast Other third-party systems
Scope clarification These examples describe integration areas and providers I worked with. They do not imply that every provider used the same technical implementation or integration workflow.
06

My Delivery Approach

A repeatable approach to coordinating integration work

  1. Understand the workflow: Gather client requirements and identify the expected behaviour of the integration.
  2. Document requirements: Convert the requirements into user stories and clear implementation expectations.
  3. Coordinate implementation: Work with developers and third-party teams to clarify dependencies and progress delivery.
  4. Prepare and test: Set up the test environment, validate behaviour, and investigate discrepancies.
  5. Support delivery: Coordinate client delivery and assist with go-live or post-delivery troubleshooting.
07

Contribution and Delivery Impact

How my work supported cross-team delivery

My contribution helped connect business expectations with technical delivery across multiple integration workstreams.

✓ Translated client requirements into structured user stories for implementation.
✓ Coordinated internal developers and third-party teams throughout integration delivery.
✓ Established a test environment and performed integration validation before delivery.
✓ Supported investigation and resolution of integration issues.
✓ Helped coordinate client delivery, go-live, and post-delivery troubleshooting.

No numerical performance improvements are claimed because verified measurements are not available for publication.

08

Key Learnings

Lessons from coordinating cross-system delivery

  • Integration projects require a shared understanding of expected behaviour across clients, internal developers, and external providers.
  • Clear user stories reduce ambiguity during implementation and testing.
  • A dedicated test environment helps identify integration issues before client delivery.
  • Successful delivery includes coordination and troubleshooting after implementation, not just completing development tasks.
09

Skills Demonstrated

Capabilities applied throughout this project

Product Delivery Requirements Gathering User Stories Third-Party Integrations Hospitality Technology IoT Integration Testing Test Environment Setup Stakeholder Coordination Issue Investigation Go-Live Support Cross-functional Delivery
10

Confidentiality

Respecting client and company information

This case study summarizes my experience at a high level. Internal system configurations, customer information, proprietary integration logic, credentials, and technical implementation details have been omitted.