diff --git a/datos_fiscales_superhog.md b/datos_fiscales_superhog.md new file mode 100644 index 0000000..1e5b6cf --- /dev/null +++ b/datos_fiscales_superhog.md @@ -0,0 +1,4 @@ +Datos fiscales para pedir facturas a nombre de la empresa + +Address: Superhog Spain SL, AVDA Diagonal, 484 3 1a, Barcelona, 08006 +NIE B09926403 \ No newline at end of file diff --git a/log.md b/log.md index 04d5e9e..7ce4f8b 100644 --- a/log.md +++ b/log.md @@ -624,7 +624,6 @@ Collaboration for Data Sources and Data Catalog. PBI report. Can I access Airtable? - # 2023-12-04 - [X] Start a Data Board in devops and stop using this for non-personal tasks @@ -739,7 +738,6 @@ Small fish "We are very good at selling" - # 2023-12-05 ## Dashboard tour meeting @@ -779,22 +777,356 @@ Is Accounts the only relevant tab on Wilbur? READ THE PRODUCT MAP and the Superhog features Do I have access to KYG-lite? +# 2023-12-07 + +## Express meeting with Matt + +Map customer journey + +- [ ] Sharing board +- [ ] Sharing with Product team + +# 2023-12-11 + +- [X] Pick up Amazon package +- [X] Buy milk bottle for Superhog: https://www.ikea.com/es/es/p/korken-bote-tipo-botella-tapa-vidrio-incoloro-50541374/ +- [X] Announce lockers + +- [X] Manage to read from CORE + - Instructions: + - VPN https://guardhog.atlassian.net/wiki/spaces/DEVELOPMEN/pages/92831745/How+To%3A+Configure+the+Azure+VPN+Client+to+talk+to+the+SQL+Server+Jump+Box + - DB https://guardhog.atlassian.net/wiki/spaces/DEVELOPMEN/pages/93159433/How+To%3A+Connect+to+SQL+Server+via+the+Jump+Box + - I'm stuck at the RDP permissions + - I also need authorization to read the credentials + +## Product Weekly + +- Lourdes + - She will be doing interviews with resolutions and account management + - Will Airtable live long enough that it needs to be documented? + +- Louise + - Get invited to check Mixpanel afeter Louise fixes existing issues + + +- Me + - Last week + - Finished my first round + - Started Data Catalogue, Confluence, etc. + - This week + - TMT and Data kickoff + - Get hands-on with Robinson, Hubspot, Finance + - Keep building Data Catalogue + - Questions + - Lourdes, Airtable docs, is it worth it? Yep. + - Do we have a job description? + - Veriff integration? +- Share link Notion and Confluence + - https://www.notion.so/knowyourguest-superhog/Data-Homepage-0ac0a2e52a8940c7ba4f31e5ffcc33e8?pvs=4 + - https://guardhog.atlassian.net/wiki/spaces/Data/overview?homepageId=152731908 + +# 2023-12-12 + +- [X] Say hi to Amanda + +## Meeting with Ben C. around Product Ownership in Data + +My briefing to him: + +--- + +The Data Team is going to be a slightly different squad with a few members capable of doing technical work and building stuff. As all squads, is going to have a limited capacity and an infinite demand. Hence, like any other team, we will have to build a backlog, groom it, and prioritize it. + +Because of this, I strongly believe that Data requires Product Management and its mindset. I’ve seen many companies fail at this, providing PO to most squads but not to Data “because it’s different”. + +Nevertheless, I think Data it’s truly different. I think Product Management looks a bit different for Data than it will for the other tech squads for the different product domains. This is because of things like: +- In my experience, building data products like dashboards or one-shot, adhoc analysis is very different than building “regular” software products. There are commonalities, but also quite a few differences. +- There is a lot of foundational work that is necessary, yet doesn’t really fit nicely into one single product (like grunt work in the guts of a Datawarehouse, which is necessary to support many different reports for many different areas). +- The cross-functional nature of the team means that it has many different clients with different needs. This is challenging from a product management POV because you are fighting a multiheaded hydra. +- Data is less free than many other tech teams because it depends a lot on existing systems and teams to build it’s own stuff. We build on top of other’s work, and so have to manage these dependency relationships. + +Those where some thoughts. All of this leads me to ask myself: +- Should there be a dedicated PM for Data? Is this an impossible task because it’s simply too much for a single brain? +- Should instead all PMs be able to add stories to Data’s backlog? What about needs that go across domains/teams? And about areas that don’t have a PM (like Finance)? +- Perhaps Data should have multiple backlogs? Or perhaps it’s an overkill? +- Should I simply act as the Data PM for now? How sustainable will that be? + +I’m asking myself these questions because: +1. Well, it’s an important topic, it should be well thought and I think your take on it is vital. +2. If there are headcount implications, we need to agree on them and get things rolling. Whatever we decide, I would like to bring to the Data Kickoff meeting on the 14th. + +--- + +Ben: +- Internal Data team manages internal work independently +- Important need for a roadmap +- Product Board: make a data roadmap there +- Data Analyst with a strong product view acting as a product owner +- Begin with 3 and add more by justifying with a roadmap + +## Meeting with Andrew about headcount + +My notes: + +--- +Hi Andrew, + +On the Data kick-off meeting for the 14th, I would like to present some plans in terms of what the data team should look like, people wise. I think it would be unwise to wait until then to show my cards, because hopefully that meeting is more about aligning visions that about discussing a lot. So, I would like to share my current thoughts to see how they align with yours and with overall budget/headcount constraints and plans. + +@Ben Cotte, @Ben Robinson also looping you in for transparency, feel free to chime in. + +My thoughts: +- I think there is a lot of Data work to get done (which is great news because it’s a lot of good coming for the company). +- I’m obviously not gonna get much done on my own. I see backlog for a nice 4 heads (including myself). I would look for another Data Engineer and a couple of Data Analysts. +o The additional Data Engineer would be more on the strong code, modelling, infra side of things. This is important because we have a lot to build in this area, and because solely relying on me is a terrible idea for many reasons. +o The Data Analysts would be sitting closer to Product/RevOps/Finance/etc, working on top of. +o Nevertheless, there is some degree of overlap between the skillset and capabilities of both profiles, and I would like to get people with a good multi-hat attitude for these early stages. +o I would also be in favour of going for experienced profiles at this point. I don’t think this is a good time for someone to learn on the job. More junior profiles might provide better value/cost when the team is more mature and things have settled a bit. +- BTW, I’m aware there was an open search for an experienced analyst but, from the lack of news, I’ve assumed that’s not progressing or at least not close to completion? +- Besides this, I see the need for some extra work to be done in Product (somehow closer to Ben C.) and Infrastructure (somehow closer to Ben R.) The lines here are fuzzy. This doesn’t need to necessarily be part of the Data Team strictly speaking, but the Data Team will need some of this. I’m planning on discussing with both Ben’s next week to align. + +So, converging, @Andrew Boldt: +- Does this make sense to you? +- Is going out and hiring 3 extra people now aligned with what you are planning/willing to invest in Data? + +Please, feel free to provide feedback and tear it to the ground if necessary. We can sit and talk whenever if needed. I would like to have some, even if it’s rough, we have agreed on for Thursday. + +--- + +- Thursday plan + +Senior Data Analyst (the brains: sitting closer to the business) +Let's adjust the third position depending on what we find for the Senior Data Analyst + + +For the meeting: Matt Ben Ben Andrew +Humphrey is just flying around +Leo goes off the hook + +## Surprise meeting with Iplicit + +We meet with Tim Coles. + +My points: +- API seems rather limited. Are there any other export systems? Couldn't find anything in the documentation. +- Integration plugins with any data sync tools like Fivetran, Airbyte, etc. + +--- + +Reason of the meeting: what would the implementation project look like: + +1. Contract signed, no resources assigned until that happens +2. Kickoff (couple hours) +3. Solution Design Meeting (a few hours) + - they help us determine how to configure Iplicit + - Someone to handle integration + - PID -> Document with the outcome +4. Sandbox environment + - Start moving data +5. Training and testing phase + - Training over Teams +6. Go live +7. A bit of extra support from their side afterwards + +- Can I have some material on Data Migration +- Do we keep sandbox environment? + +Andrew expects me to take care of this Data migration. + +Andrew: "We will import data to Iplicity on a monthly basis" + +Some thoughts: +- Exporting data out of Iplicit doesn't seem very important. We are going to end up doing the billing and charging logic outside of the system and then dump it in through the API, so it will be out anyways. + +## Meeting with Beth + +- Marketing website +- New strategy atm +- More aligned with Account Management and other RevOps + + +Email marketing +Hubspot + +- I don't have a full picture of customer lifecycle +- See details on active user in Dashboard +- Integration between + +- Number of guests that we screen, screen funneling +- CLV + +Her Santa Claus list: +https://docs.google.com/spreadsheets/d/1xpaEaDvOO69gxsSNYpYT8z0yFzF3iuIe/edit?usp=sharing&ouid=104451810415666214282&rtpof=true&sd=true + +# 2023-12-13 + +- [X] Get a locker +- [X] Get a lock for my locker 760 + + +## Meeting with Amanda + +- How are you going to organize work in the finance team? Should I go to you or Elaine? + - Situation is up in the air + - +- Invoicing process + - I'm here to help with the data side of things +- Besides, I have an interest in Stripe and Acquired, Data wise +- Can I steal Jamie freely, should I channel it through you? + +## 14th Presentation Notes + + +Goals +- Project that I'm in control +- Impress with my calm and thoughtful planning +- Secure my headcount +- Secure my rights over other teams +- Ensure my vision is shared by the TMT + + +Script +- Agenda + - What I've seen + - What I propose + - Next actions + - Discuss, debate and agree +- Past few weeks + - I've been doing my little tour + - I've started working on cataloguing our data and data products +- Diagnostics + - General vibe: we are in a sweet moment. The child is turning into a man, and we are starting to see some cracks in his clothing (Hulk picture) + - Concerns + - Operations issues: non-standardized process, hard to measure, hard to improve on + - Product issues: common-sense is the only driver, no analytical approach. No mature pricing strategy. + - Sales: nose driven methodology. Lack of basic data to drive marketing and sales (CLV, segments, analytics on channels, sales agents performance metrics, etc) + - Finance: invoicing. + - Technology: lack of data infra. People are integrating data with blood, sweat and tears. + - Good stuff + - Product works + - Good tech culture, mature engineering team + - Human capital is looking great to me + - Strong bet on product management feels promising + - Sales is nose driven, but it seems to be a very good nose given the results + - Do you think I've missed any important points? Any disagreements +- Data Team vision + - Responsibilities + - Supervise data across the org: catalogue and document all relevant items + - Build and own infrastructure to service needs that don't fall nicely within anyone's domain: DWH, integration of external data sources, etc. + - Build stable data products: reports, dashboards, APIs, etc + - Provide brainpower for highly complex analysis + - Build data literacy across the company + - Not: + - Own every little reporting need and become a blocker + - Act as a release valve to product short-comings + - Overcome bad process and system designs with miracles + - What does success look like + - Data is easily accessible for those who need it + - We have capacity to build data products with speed and quality + - Production systems run with good uptime + - We have the foundations to attempt more sophisticated projects (ML/AI, advanced statistical and optimization models, etc) + - Powers + - Be involved early when needed + - Impose certain standards on data owners in terms of documentation and practices + - Enforce agreements with upstream dependency owners (Robinson, don't break my columns please) + - Other parts of my philosophy + - We have a backlog, limited capacity and thus we need to prioritize, like any other team + - Not every question deserves being answered + - I'll be annoying on my dependencies + - Tell me if my vision fits what you expect of my team +- Plans + - Short-term (weeks) + - First batch of cataloguing and documenting + - Take control of important reports + - PBI + - Hubspot + - Global KPIs + - etc. + - Assist in the invoicing issue from the data side of things + - Get into important loops to provide the data point of view + - Product design + - Standardization of operational processes + - Company software decisions: stripe vs acquired, new accounting software, etc. + - Perform a first approach at grooming a data products backlog + - Start hiring + - Mid-term (months) + - Build new data products to cover different areas + - Build data infrastructure: DWH, integration solutions, better reporting tools + - Data trainings outside the data team + - Future + - Maintain and scale + - Advanced Data Products: ML&AI + - I don't know what else, I don't like looking that forward unless strictly necessary. Life's just too messy. + - Hiring + - Another data engineer + - 2 Data Analysts + - Seniority. No place for people who don't know what they are doing at this stage. I would rather have a few experienced hands than an army of newbies. + - Some timings and next actions + - Hiring + - Timebox data cataloguing and documenting + - Controling existing reports + - Timebox + - First round of grooming with the different areas to build up backlog + - + +## Product Catchup Meeting + +Survey - What platform are we using? Hubspot, although the team is tempted about Typeform. +They think exporting data from Hubspot is going to be challenging. The Airbyte conenctor seems to support it though. + + +- [X] Ask team for job descriptions + + +# 2023-12-14 + +- [X] Order RAM from PC Componentes + + + # Now -- [ ] Try to access Core -- [ ] Start building data source pages in Notion - - Add Product Map link to Dashboard - - Ask Alex and Lianne to add docs on the Notion page +- [ ] Add RAM invoice to Xero expenses to get it reimbursed +- [ ] Ask IT for data-team@superhog.com mail +- [ ] Place this in Backlog: https://superhogteam.slack.com/archives/C06A52YUDM1/p1702557374922989 + +- Documenting sessions with Ben + - List integrations + - Document + - Control PowerBI + - Discuss architecture proposal + +- Documenting Hubspot + - Document + - Research exports for shor-term problem solving + - [ ] Deep dive into invoicing process + - [X] Provide a heads-up into it to the wise men table + - [ ] What's next? + +- Early stages Data Infra + - [X] Start a repo + - [X] Set up a MSSQL and Postgres instance, load data in both and query team + - [X] Add an Airbyte to the cocktail + - [WIP] Perform sync between MSSQL and Postgres and document findings + - [ ] Perform sync between Hubspot and Postgres and document findings + +- [ ] Start building data source pages in Notion + - [ ] Add Product Map link to Dashboard entry + - [ ] Ask Alex and Lianne to add docs on the Notion page + - [ ] Ask Lourdes to fill in details for Airtable + - [ ] Make page for Stripe and double check details with Jamie and Ben Robinson +- [ ] Book some time with Jamie to check on Stripe and Acquired - Equipment - - [ ] Second screen + - [ ] Second screen -> No use - [ ] Keyboard - - [ ] USB-C hub with several USB A + HDMI - [ ] Second RAM card -> https://www.neobyte.es/memoria-crucial-16gb-ddr4-sodimm-3200-ct16g4sfra3a-8487.html, https://www.pccomponentes.com/corsair-vengeance-so-dimm-ddr4-3200mhz-pc4-25600-32gb-2x16gb-cl22 + - [ ] Additional charger + - [ ] USB-C hub - [ ] Shelves, organizers, stationery and other office goodies - Bookcase for private office https://www.ikea.com/es/es/p/billy-libreria-blanco-00263850/ x 1 - Organizers for private office https://www.ikea.com/es/es/p/tjena-organizador-escritorio-blanco-60395452/ x 4 @@ -804,8 +1136,6 @@ Do I have access to KYG-lite? - [ ] Try to write a stupid Markdown page in notion through Python - - ## Onboarding and Data Kickstart - [ ] Are there any shared folders in Keeper Security where I should be added? @@ -813,15 +1143,8 @@ Do I have access to KYG-lite? - [ ] Get access to staging environment for KYG-lite platform -- Accounting migration - - [ ] Check iplicit content shared by Andrew - - [ ] Check iplicit docs, potentially ask for more - - [ ] Write up my small requirements - - [ ] Read any docs shared by Alex A. -- [X] Get a locker -- [ ] Get a lock for my locker 760 - [ ] Prepare quiz for 15th Dec. Theme must be sent before December 8th @@ -838,57 +1161,6 @@ Do I have access to KYG-lite? - [ ] Review the data exploration efforts made by Cotte -## 14th Presentation - -- Diagnostics - - General vibe - - Operations issues - - Product issues - - Good tech culture - - Lack of data infra -- Plans - - Hire - - Take control of current things - - Build Data Catalogue and culture around it - - Take ownership of existing reports where possible/makes sense - - Help out with the invoicing crisis - - Start building - - Top management report - - Operational metrics (where possible) - - Infrastructure to grow (DWH, integrations, adhoc analysis) - - Rough estimates - - Looking a bit further - - Philosophy - - Cool things in the future - - Pitfalls - - -My proposal on first fronts, domain wise: -- Product: dedicated analyst to dance together with the team running adhoc analysis on new product ideas -- Stable reporting for operational teams and processes with the goal of helping Matt, Leo and their managers: - - Sales - - Account Management - - CS Interactions - - Resolutions -- Finance - - Solve invoicing nightmare, at least partially -- Business Management - - High level operational and financial measures. Revenue, user acquisition/churn/activation, # of bookings processed, - -- Pitfalls to avoid - - Data as a shadow IT - - Unrealistic prioritization. Not all questions deserve to be answered - - Overly strict centralization in Data team: if someone owns the data, has the data, and knows what to do with the data, the Data team is there to review but doesn't need to act - - Spaguetti architecture - -My proposal on first fronts, deliverables wise: -- Data catalog with the most important databases, ownership, docs, etc. -- Take control of existing reporting - -My proposal on first fronts, team wise: -- Get another data engineer and two data analysts in place. Senior people that know what they are doing, not the right place and time to develop junior guys - - ## dbt course - Just continue where I left.