From 0e7711771dd0eb3ed6b71ed73945418cc9066f35 Mon Sep 17 00:00:00 2001
From: counterweight <counterweightoperator@protonmail.com>
Date: Tue, 4 Feb 2025 14:20:37 +0100
Subject: [PATCH] start

---
 public/index.html                             |  4 ++
 .../if-i-started-a-data-team-again.html       | 62 +++++++++++++++++++
 2 files changed, 66 insertions(+)
 create mode 100644 public/writings/if-i-started-a-data-team-again.html
diff --git a/public/index.html b/public/index.html
index 3b400b9..0301722 100644
--- a/public/index.html
+++ b/public/index.html
@@ -102,6 +102,10 @@
             <h2 id="writings-header">Writings</h2>
             <p>Sometimes I like to jot down ideas and drop them here.</p>
             <ul>
+                <li>
+                    <a href="writings/if-i-started-a-data-team-again.html" target="_blank" rel="noopener noreferrer">If
+                        I started a Data team again</a>
+                </li>
                 <li>
                     <a href="writings/one-efective-but-risky-way-to-find-the-top-budget-for-the-vacancy.html"
                         target="_blank" rel="noopener noreferrer">One efective but risky way to find the top budget for
diff --git a/public/writings/if-i-started-a-data-team-again.html b/public/writings/if-i-started-a-data-team-again.html
new file mode 100644
index 0000000..a110675
--- /dev/null
+++ b/public/writings/if-i-started-a-data-team-again.html
@@ -0,0 +1,62 @@
+<!DOCTYPE HTML>
+<html>
+
+<head>
+    <title>Pablo here</title>
+    <meta charset="utf-8">
+    <meta viewport="width=device-width, initial-scale=1">
+    <link rel="stylesheet" href="../styles.css">
+</head>
+
+
+<body>
+    <main>
+        <h1>
+            Hi, Pablo here
+        </h1>
+        <p><a href="../index.html">back to home</a></p>
+        <hr>
+        <section>
+            <h2>If I started a Data team again</h2>
+            <p>
+                When starting a data team at a startup, there are several key considerations that can make or break the
+                team's success. One crucial aspect is the existing reporting and dashboard setup. If there are any
+                issues with the current system, it is essential to address them immediately. In my experience, leaving
+                existing problems unattended can lead to significant headaches down the line. For instance, when I
+                joined SuperHawk, the company already had a few reports in Power BI, which had been developed by the
+                development team. However, I was not satisfied with the way these reports were built, as they exhibited
+                bad patterns, were not scalable, and were too closely tied to the application. Despite my reservations,
+                I chose to focus on other tasks, leaving the Power BI reports as they were. This decision ultimately
+                proved to be a mistake, as we continued to build upon the existing system, making it much more
+                challenging to transition to a new platform later on.
+
+                Another critical factor in the success of a data team is hiring. I joined SuperHawk in November, and it
+                took approximately seven months to bring our first data analyst on board. Although we had aligned with
+                the C-level team on the need for additional personnel within the first few weeks, I prioritized other
+                tasks, such as infrastructure setup, team planning, and getting to know the company. In hindsight, I
+                realize that I should have focused more on hiring, as having the right people on board would have
+                significantly improved our efficiency and speed. With the budget and resources available, it would have
+                been feasible to hire talented individuals earlier, potentially within two or three months.
+
+                Involving people from other teams in the data analysis process is also vital. Our setup is fairly
+                standard, with the data team owning a data warehouse and providing reports to other departments.
+                However, there is often a need for additional analysis, which can be time-consuming for the data team.
+                To mitigate this, I would have benefited from identifying and training "domain analysts" or "satellite
+                analysts" within other teams. These individuals would have been capable of working with data, providing
+                insights to their own teams, and potentially even owning certain aspects of data analysis. By empowering
+                these employees, we could have delivered more value and avoided becoming a bottleneck.
+
+                In retrospect, there are three key things I would have done differently. Firstly, I would have addressed
+                any issues with the existing reporting and dashboard setup immediately. Secondly, I would have
+                prioritized hiring and focused on bringing the right people on board as early as possible. Thirdly, I
+                would have involved people from other teams in the data analysis process earlier, by identifying and
+                training domain analysts or satellite analysts.
+            </p>
+            <hr>
+            <p><a href="../index.html">back to home</a></p>
+        </section>
+    </main>
+
+</body>
+
+</html>
\ No newline at end of file
