counterweight/sh-notion
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
sh-notion/notion_data_team_no_files/2025-03-05 - Data Planning 1ad0446ff9c9807aa104ef7a24b97d9e.md
Pablo Martin a256b48b01 pages
2025-07-11 16:15:17 +02:00

4.1 KiB
Raw Blame History

2025-03-05 - Data Planning

Done

  • Incident - Verification Bulk Update (resolved) - Available here
  • KPIs - Main KPIs overview (YTD+MTD) - Second delivery - Available here
    • Targets for FY 2025 hidden to avoid misconceptions
  • OKRs & Business Strategy
  • Resolutions - New Resolutions reporting - Available here
  • Power BI Truvi Rebranding
  • New Dash - Configure Guest Agreement service for New Dash after release
  • Finance - Ensure proper month attribution of Hyperline invoicing for invoiced revenue reporting purposes (affects Main KPIs, AMs Reporting, Accounting Reports)
  • Data Captain requests as usual
  • Guests - Start discussing on the implementation for Guest Products and Single Payment - Multi Service refactor.

In Progress

  • Power BI Truvi Rebranding - rest of reports
  • Guests - A/B test monitoring ongoing (launched 25th Feb)
  • Excel training session (scheduled)

Stopped / No advancement

  • KPIs/New Dash/AM reporting - Exclude known test accounts to increase data quality (won’t remove all of them) - Engineering to built it properly for us to exclude it properly

To Do (does not include critical subjects)

  • Guest Products - Single Payment / Multi Service refactor - Starting Tuesday 11th March
  • Finance/Resolutions - Automate manual tasks for Finance (waiting for specs)
  • Re-visit targets for FY2026 (need Nathan input)→ Talk to Guy / Matt / Nathan - Meeting on Monday
  • Update automation project backbone data
  • Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price + Deal id
  • Idea - Improvements on AM reports
    • Rework Score so it captures projected revenue rather than last month revenue (i.e., gain ~1 month trend visibility). In other words - be able as of 1st of March to detect that February was bad for HTVR, instead of 1st of April as is now.
    • Include Price Plans / Offering - New Dash vs. Old Dash
    • Include API/New Dash/Old Dash category
    • Include rank and share per Revenue Retained Post Resolutions
    • Add a per Account Manager “welcome” page with the main indicators / alerts of the accounts per Account Manager.
      • potentially other ideas available below (Churn - Kayla, Cohorts - Alex)
  • Idea - Resolutions KPIs
    • Blocked - We need to capture all Resolutions to be able to build proper metrics
    • Modelling KPIs data
    • Main KPIs exposure
    • Specific reporting
  • Invoicing Incident - Further automation improvements: Xero (for source of truth in actual invoiced amount) + Hubspot (for churn/onboarding/AM info) + Backend (for what we should have invoiced, New Dash mostly)
  • KPIs - Payment Count and Average Amount per Payment Count (Waiver/Deposit Fee/etc)
  • RevOps (Kayla) - Churn prevention: alerting system if user had a PMS and no longer has it, if recent created bookings per account is decreasing, display last time account was contacted. This could be potentially the first step towards a “Account Manager KPIs” for AM teams
  • RevOps (Kayla) - Churn tracking: see if we can automate manual monthly Churn reports and enhance it with other data (revenue last 12 m, etc)
  • RevOps (Alex) - Client Cohorts: explore retention + key metrics to understand if it’s valuable for further client understanding
  • Idea - Guest Journey A/B test report
    • Avoid manual runs on Data side
    • Provide deeper level of detail