sh-notion/notion_data_team_no_files/20250505 Retro 1ea0446ff9c98035943ffc3c3f4a6306.md
Pablo Martin a256b48b01 pages
2025-07-11 16:15:17 +02:00

2.5 KiB
Raw Blame History

20250505 Retro

🙌 What went well

  • Org
    • It seems like dust is finally settling after RIF
    • New DevOps project to track Data Quality issues
  • Deliveries and WIP
    • Nice project on the pipeline: data-driven flagging
      • +1
    • Good work with A/B testing
      • +1
    • Very nice updates in our reports (KPI targets, growth score, new dash adoption, resolutions payments,..)
    • Domain analysts growing
  • Company
    • Last months were much better than previous ones from a financial perspective
  • Pura vida
    • Loved Nepali food and all our comilonas
        • infinite
    • Things are chill
    • Some holidays!
  • A lot less data alerts recently

🌱 What needs improvement

  • Disorganization, misalignment
    • Feeling like current lines of work are not really impactful
    • I feel company has become very disorganized. Management runs in circles in meetings, ICs do business as usual in complete disconnect.
    • Being pulled in in some mostly waste of time meetings
    • API team feels a little lost, its lacking a clear leader and communication
  • … which is causing …
    • Things are too chill, routine is kicking in
    • Were losing communication output (Data News not being sent on time, didnt do training sessions on new reports, unclear output of illustrations A/B test)
      • And also quarterly planning and lookback
  • Technical
    • The goddamn CI server is a headache
  • Missing someone like Joan who kept us more in the loop with the guest team
  • Finance new tracking of Host Resolutions broke Business Targets for a few days
  • Massive involvement on HTVR invoicing discrepancies that should not really be on our scope

💡 Ideas for what to do differently

  • Should we take the chance of the teams anniversary to fully review our ways of working, rituals, systems, etc?
  • Self-run with lines of work that we can lead independently

✔ Action items

  • Think about changing dbt model naming/structure conventions
    • Should int/cross be split into… something?
  • Request TMT clarity on org. structure again
  • Read Shape-up (https://basecamp.com/shapeup/) and discuss next retro
  • Document all the config references (URLs, DB connection strings, credentials, etc)
  • Agree with Ben R. on a different way to manage permissions PBI
  • Make a cleaning day for Data Catalogue docs
  • Document existing invoicing processes, not just new ones