Best Practices

Tipping points: How individual decisions make big impacts in data careers & data teams | Census

Nicole Mitich
Nicole Mitich November 22, 2022

Nicole Mitich is the content marketing manager @ Census. She's carried a love for reading and writing since childhood, but her particular focus is on streamlining technical communication through writing. She loves seeing (and helping) technical folks share their wisdom. San Diego, California, United States

When you’re working in data for a rapidly growing company, the number of hats you wear can change daily. 🎩 Just ask Emily Hawkins, data platform lead at alcohol delivery service Drizly

When Emily joined Drizly in 2019, the data team included four people – two BI analysts, a data scientist, and a data engineer. But as we know, all of our careers (and the collective careers of our data teams) are the sum of critical decisions made at the right or wrong time. With those crucial decisions and just three short years, that scrappy little team grew sevenfold. 🤯

We explored this rapid growth further in a keynote session titled, Tipping points: How individual decisions make big impacts in data careers & data teams during this year’s Summer Community Days

🎧 To make things even more interesting, this keynote doubled as a live episode of The Sequel Show, exploring:

  • How Emily has navigated tipping points in her career (and how they’ve helped her scale up)
  • How she’s navigating the growing pains of a successful data team
  • How her role within her team has changed since Drizly acquisition by Uber
  • How data process and data sharing have shifted as the team has grown
  • Lessons learned in making decisions that will impact your career, your company, and your customers

Scaling fast (but with control)

Specializations help data folks narrow their focus and avoid being overwhelmed when the company is scaling fast. As the business grew, Emily shifted from general business intelligence to product analytics, then to data infrastructure and engineering, which led to her current role.

“When there were only two of us working in BI, we helped with everything – marketing, product, operations. We had our hands in all the different things,” Emily explained. “As we grew, we were able to specialize.”

The first departments to require their own data specialists are the ones relying most heavily on business intelligence. At Drizly, that meant marketing (which drove the company’s skyrocketing growth) and strategic partnerships (which deliver insights to the alcohol brands partnering with Drizly to sell their products). 📈

For a company to use its BI effectively, data people can help users make good decisions faster. According to the Experian 2021 Data Experience Report, the more we can get relevant insights into the hands of business users, the quicker (and better) a company can adapt to ever-changing business needs.

Helping people use the data

That might sound easy, but there’s a balancing act involved in getting more people to use data while maintaining its integrity. Companies take a lot of paths to getting employees comfortable with their data, from Uber’s open-source query engine to Airbnb’s Data University.

At Drizly, most users view data insights through Looker. Realizing that most roles in the company don’t have an analytics background, the data team created training materials to help people understand the information they consume. 📚

Some pieces of training are held live, while others are recorded for reference later down the road. 🛣️ They also include hands-on, over-the-shoulder training regarding how to read the company’s most important dashboards.

“Everyone should know how to read the OKR dashboard. They should all know our metrics and how we’re tracking against them,” Emily said. “As the data team, we want to encourage curiosity. We want people to be excited about finding data. So we put out learning resources as much as we can.”

Building trust in the data (and the data team)

Teaching people to understand data has another benefit (besides allowing them to act on it quickly and effectively): It builds trust in the data and in the people managing it. 🤝 This actually goes hand in hand with taking quick action – the more trust business users have in the data team, the faster and more confidently they can make data-driven decisions.

“I remember early on when we wanted to move from Redshift to Snowflake, our director brought it to the CEO and CFO,” Emily recalled. “He had this whole presentation ready about why we needed to make the change, and they just asked, ‘Do you think this is what we need to do? Yes? OK, go do it.’ We’re very lucky to have had that level of trust from the beginning.”

Trust comes from relationships, and we can’t build those from ivory data towers. 🗼 Emily said her most effective tactic for educating her colleagues and gaining their trust is clear communication. After all, the data team’s job is not just to deliver impassive numbers; it’s to deliver insights and recommended actions.

“You have to be able to clearly say, ‘This is how we can implement this and see a result,’” Emily said. “You can also find success by becoming an expert in technology and finding ways to optimize it, but you still have to explain what you did and what you improved. You can shorten a model’s time from an hour to less than a minute, but if you don’t tell anybody, nothing’s going to happen for you.”

Emily shared more insights about scaling fast and about the impact of individual decisions on a data career with Census co-founder and CEO Boris Jabes during her keynote. Watch the full discussion and more Summer Community Days talks here. 👈

✨ Then head over to the Operational Analytics Club to share your view and join the conversation.

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps: