sh-notion/notion_data_team_no_files/Q4 Data Achievements 1570446ff9c980b0a094ccfc9533bee4.md

# Q4 Data Achievements

The official Data OKRs are located here: [Data OKRs](https://www.notion.so/299e4da6e92043899646d11609c051ae?pvs=21) 

# **Q4 Recap: Achievements and Status Update**

As we approach the end of Q4, we want to take a moment to reflect on our progress and key achievements over the past quarter. Below is a summary of the Data OKRs we set for this quarter, along with the current status and any pertinent comments.

## Support Finance Team With Invoicing Initiatives

- **P1: Support during accounting/invoicing tooling changes**
    - Status: **Achieved**
    - Comments: Pablo has been supporting the invoicing tooling changes to Hyperline as a representative of the Data team.
- **P1: Cancellation API invoicing support**
    - Status: **Not Started**
    - Comments: Lack of clients in Cancellation API have encouraged Data Team dedicating effort pragmatically into other areas with greater impact.
- **P1: Check-in Hero API invoicing support**
    - Status: **Achieved**
    - Comments: With the first client expected to appear by beg. December, we’ve created a first report available in API Reports Power BI Application that contains an Overview and the Details of the CheckIn Hero records.
- **P1: Screening API invoicing support**
    - Status: **In Progress**
    - Comments: Lack of clients in Screening API have encouraged Data Team dedicating effort pragmatically into other areas with greater impact. By the EOY, Data Team has started working on a report for S&P to be ready for the next invoicing cycle.
- **P1: New Dash invoicing support**
    - Status: **In Progress**
    - Comments: Even though Data Team is not expected to invoice users in the New Dash, the fact that some of these come from Old Dash requires modifications on the current Invoicing Exporter tool to avoid double-charging clients. Final requirements have not been in place before EOY, but it’s likely New Dash users get invoiced by January.
- **P1: Guesty invoicing support**
    - Status: **Delayed for future Qs**
    - Comments: Similarly as Q3, lack of a proper stable set-up to invoice Guesty has blocked the capacity to automate its invoicing.

## **Provide Business KPIs Reporting**

- **P2: New Dash KPIs and Reporting**
    - Status: **Partially Achieved**
    - Comments: Further improvements on the Reporting of the New Dash have been made iteratively as new releases have been deployed. KPIs needs for New Dash are gathered and will start to be implemented once the main features of New Dash have been fully delivered, in order to prioritise the main New Dash Reporting first. Carried over to Q1 25.
- **P2: APIs KPIs and Reporting (Cancellation, Check-in Hero)**
    - Status: **Partially Achieved**
    - Comments: A new report for Screen and Protect has been created. Additionally, we’re expecting to have Check-in Hero reporting to be available in the coming days. No usage of Cancellation APIs has led us to prioritise other subjects. KPIs needs for APIs are gathered and will start to be implemented in the coming weeks. Carried over to Q1 25.
- **P2: Resolutions KPIs and Reporting**
    - Status: **Delayed for future Qs**
    - Comments: The lack of ownership on Resolutions product has lead to uncertainty on this subject and blocking us to move forward with the integration of Resolutions data and further reporting. However, the requirements for the KPIs are gathered and should be ok to re-launch the initiative once we have more clarity on this subject.
- **P2: Guest Journey KPIs and Reporting**
    - Status: **Achieved**
    - Comments: A brand new KPIs report to track the Guest Journey has been created, allowing for much dedicated detail on this product line.

## **Support Product Team With New Products & Data-Driven Features**

- **P1: Run First A/B test to drive Guest Journey experience decisions**
    - Status: **Achieved**
    - Comments: A major collaboration with Guest Squad, we managed to implement and validate a proper set-up for A/B testing purposes. An initial A/A test has already been conducted to ensure the technical implementation is correct from both Engineering & Data perspective. A/B test released beg. December and aiming to be finished by mid January.
- **P2: Support New Pricing transition**
    - Status: **Achieved**
    - Comments: Support granted to the New Pricing transition, with a great amount of modelling happening within DWH to adjust to the new backend structure. Also, several support has come through Data Requests and additional ad-hoc analysis on client pricing before and after an expected migration.
- **P2: Support New Dashboard transition**
    - Status: **Achieved**
    - Comments: Support granted to the New Dash transition, collaborating with the Dash squad to provide reporting on the New Dash. While there’s some improvements that could be done in the reporting areas, the most important areas are tracked and we continuously iterate over it.
- **P2: Provide support for data-driven features in apps**
    - Status: **Not Started**
    - Comments: Lack of ownership in the initiatives for part of the interested products has resulted in no action being taken by Data Team towards this initiative. Even though we acknowledge the value it can provide to our clients, we expect further refinement on the need to clarify the scope and viability of this project.

## **Improve Data Capabilities**

- **P1: Hire a Data Engineer (pending validation)**
    - Status: **Delayed for future Qs**
    - Comments: No final go to hiring within 2024 Q4. This puts pressure in the Data Team specially in Q1 with the lack of Data Engineering capacity and will reduce overall capabilities. Expecting to re-launch initiative in the following months.
- **P1: Software upgrades (dbt, airbyte)**
    - Status: **Delayed for future Qs**
    - Comments: No blocking point to move forward on these subjects, upgrade still pending.
- **P2: Orchestration engine deployment**
    - Status: **Delayed for future Qs**
    - Comments: A first assessment has been conducted with Dagster. However, due to the lack of Data Engineering capacity in the following months, we decided to avoid making drastic infrastructure changes to avoid potential downtimes. To be retaken likely in 2025 Q2.
- **P3: Perform assessment of visualization tools (PBI alternatives)**
    - Status: **Delayed for future Qs**
    - Comments: The decision of Orchestration Engine will likely affect the Visualization Tool assessment. We decided to pragmatically focus on more priority subjects due to the lack of capacity to launch this initiative. To be retaken likely in 2025 Q2.

## Extend Data Accessibility Capabilities

- **P3: Start Domain Analysts program**
    - Status: **Achieved**
    - Comments: Jamie D. and Alex A. successfully trained in SQL and with access to the DWH. Training plan proceeds accordingly.
- **P3: Power BI in-house training**
    - Status: **Achieved**
    - Comments: An in-house training session has been conducted before EOY. Additionally, reference documentation has been created.

## Grant Continuous Support To Business Teams

- **P1: Ad-hoc requests handling (Data Captain Requests, capped 10h/week)**
    - Status: **Achieved**
    - Comments: A total of 39 data support tickets have been handled in the period of Q4 2024.
- **P2: AM reporting with churn detection capabilities**
    - Status: **Achieved**
    - Comments: A new Account Managers report has been created with client aggregated data with a monthly categorisation of how the account is performing, being widely used in the RevOps team. Additionally, 3 new Churn Rate metrics have been made available in Main KPIs.

# Beyond Planned Objectives

Additional work that has been done or needs to be done that is not in the direct scope of the objectives we set at the end of September. The following list aims to exemplify the kind of unplanned work that we are handling in our day-to-day, grouped by domain:

## Incidents

- **Invoicing incident November 2024**
    
    We faced a massive invoicing incident on the export of November. At this stage it has been resolved, with December exports running ok, but the criticality of the subject needed further implementation on the Invoicing Exporter tool that Data Team manages. All details on the incident can be found here: 
    
    [20241104-01 - Booking invoicing incident due to bulk UpdatedDate change](20241104-01%20-%20Booking%20invoicing%20incident%20due%20to%20bu%2082f0fde01b83440e8b2d2bd6839d7c77.md) 
    
- **Check-in Hero price duplication incident November 2024**
    
    A second incident affecting Check-In Hero reporting put some unplanned effort in order to fix it, with a root cause being very similar to a previously experienced incident. You can check the details here:
    
    [20241119-01 - CheckIn Cover multi-price problem (again)](20241119-01%20-%20CheckIn%20Cover%20multi-price%20problem%20(a%201430446ff9c98088b547dfb0baff6024.md) 
    

## TMT

- **Analyse claims patterns for Guesty to support negotiation**
    
    During October, the Data provide an in-depth analysis on the claim payouts for Athena (Guesty) and had shown that these were quite similar to the revenue, concluding that we were not making money from Guesty. Most of the payouts came from 5 partners that accounted for far less volume of protected bookings.
    
- **Estimated MRR for new onboarded deals**
    
    In order to support investor’s needs for insights, we did some support in order to estimate the revenue a new client will likely have in average per month depending on the number of listings they manage. After a first extraction and discussion about the accuracy of the figures obtained, a second deeper analysis has been conducted in order to try several approaches to settle a definition of a new metric that will need to be shown in Main KPIs. The details of the analysis are available here:
    
    [Onboarding MRR Definition](https://www.notion.so/Onboarding-MRR-Definition-f1bada4ea5b942568d5c6b2c7917fc5c?pvs=21) 
    
- **ICE score support to prioritise initiatives**
    
    In order to help prioritising initiatives in a more accurate manner, the Data team has invested some time around December on helping Product teams on how to settle a good scoring system for Impact and Confidence, to be ready to use by beginning 2025.
    

## Dashboard

- **Data inconsistency issues on New Dash tables**
    
    We’ve faced many data quality issues since the launch of New Dash and the resolution of these have not been always prioritsed, leading to data alerts being raised consecutively for many days, such as in the case of BookingToProductBundle issues. Lately, we’ve encountered some additional inconsistencies within BookingViewToService and further logic that effectively reduces our capacity to provide accurate reporting in a timely manner.
    
- **Removal of already existing backend fields**
    
    We’ve had some data removals on existing tables, such as Accommodation and SuperhogUser. In order to avoid breaking any report or DWH logic we needed to remove the dependency and any existing modelling in our side.
    
- **Adaptations on New Dash user tracking through Claims**
    
    During the reporting of New Dash initiative, there has been several evolutions on how to track which user is in New Dash and since when. Due to the fact that the report has been existing since a few weeks after the MVP was released, we needed to iteratively modify the logic of user tracking many times to ensure there was no report downtime.
    

## Guest Journey

- **Address Validation Removal**
    
    As part of the initiative to remove Address Validation coming from Guest Squad, we were forced to do some adaptations to the Power BI reporting of Check-In Hero, as well as remove any modelling and dependency on Address Validation within DWH.
    
- **Planning for Guest Products & Multi-service single payment**
    
    The new Q4 initiative on Guest Products will require adaptations on the modelling on DWH once available. Additionally, this new initiative raises the point on allowing one payment for many services, which is currently not the case. Even though this has not been released yet in Guest Squad side, we’ve conducted several sessions with the Guest Squad to align on the architecture of the final solution.
    

## APIs

- **Athena Cosmos DB migration (Guesty)**
    
    Similarly as we did for E-deposit, we needed to modify our Cosmos DB ingesting tool in order to point towards the new Cosmos container that contains Guesty verifications. This has been done beg. December with no further impacts on the reporting.
    

## Engineering

- **Currency rates architecture design**
    
    As part of a new need from Engineering to have the currency exchange rates, we had some discussions on possible designs to share currency rates among systems while keeping the same price plan with Xe.com. We’re expected to provide this information from DWH to the Superhog backend for further use, with the development planned for beg. Q1 2025.
    
- **Networking issues to access MS SQL**
    
    By the end of Q4, we faced some issues Data team wide to be able to access the MS SQL, namely, the backend. While this is not absolutely critical for our systems, it makes it impossible for Data team to read directly from the backend, reducing the efficiency in initiatives such as New Dash. Resolving the issue requires in-depth Data Engineering skills, thus highly prioritised above other lines of work to remove the block.