What Is the Best Advice You Have Ever Received? - Issue 203
What changed or transformed your career? Take some advice from data and analytics leaders.
Welcome to the Data Analysis Journal, a weekly newsletter about data science and analytics.
First, a few quick announcements:
I have two in-person events coming up next month:
June 4, San Francisco: Product Analytics Leader's Meetup - I’ll join product analytics leaders from Reforge, Google, Meta, Eventbrite, Pinterest, Dropbox, PayPal, and others to discuss ways to build high-impact product teams, avoid pitfalls in defining KPIs, explore causal analytics, and more!
June 6, San Francisco: Impact of Data Processing Tools on Analytics and Reporting - I will moderate a panel featuring data veterans such as Michel Tricot (CEO at Airbyte), Pete Hunt (CEO at Dagster Labs), David Krakov (CEO at Honeydew), Peter Fishman (CEO at Mozart Data), and celebrities like
and . We’ll discuss ETL tooling, data quality KPIs, the future of ETL, semantic layers, and root cause analysis using metrics decision trees. With such honorable speakers rarely in town, this is an event you won’t want to miss!
This newsletter is a little special ⭐.
Once per year, I reach out to my network of analysts and data experts with one question: What is the best advice you received that changed your career? Today, I want to share some of the wonderful responses I received. I hope they will inspire all of us to grow in analytics and get empowered with data.
What Is the Best Advice You Have Ever Received?
- Data engineer and architect, author, global keynote speaker, professor, advisor, investor, podcaster, and writer of newsletter:
Careers don’t often make much sense. Mine certainly doesn’t. You’ll probably look back on your career and wonder how you got to where you are today. And you’ll be confused about where to go next. This is part of the journey.
Here’s some advice that helped me navigate the challenges and uncertainty in my career.
Reputation matters. People have long memories, and the world is a small place.
Success isn’t so much about being smarter than everyone else; it is about avoiding stupid things that will put your career in the graveyard. Lying, stealing, cheating, and nastiness are a few ways to kill your career. If you look at the graveyard of careers, you’ll find many supposedly smart people buried there. Don’t be one of them.
Continuously learn. Read, talk to people, write, and explore new ideas and skills. Learning compounds over time. The person who continuously learns is a force of nature.
My boss once told me, “When I ask for the time, don’t tell me how to make a watch. Just tell me the time.” He meant that I needed to give a direct and clear answer when he asked a question. Clear and concise communication is key.
Lift others up. The more people you can help, the more they will help you when needed.
Lindsay Murphy - Head of Data at Secoda, advanced dbt instructor, host of Women Lead Data podcast:
“Data is not a technical role. It's a strategic role."
Data people tend to hyperfocus on things like pipelines, what technical skills to learn, and what's the coolest new tool everyone is using. But in reality, data is a strategic asset for a business.
All of the work you do should be to understand and optimize the strategy of the business. Data people should think of themselves as strategic partners to business leaders, not technical partners.
The tech is the means to an end, but if you don't understand how your business functions, what strategic levers your company can pull to succeed, and how data helps them do that, then you're going to focus your limited resources on the wrong things, and have a difficult time being successful.
Chug Abramowitz - Co-Founder at New Agenda Group, ex-Growth Leadership @Spotify, @Belkin, @CurrentHealth, @vidIQ:
A mentor once told me, "overthinking decisions is a waste of time." He was referring to choosing between two jobs or whether to stay in NYC or move to LA and getting stuck in analysis paralysis. The key is to examine your options but then enthusiastically embrace your choice! Most often, committing and giving your all to your choice is far more important to ensure an awesome outcome than the decision.
Carlos Aguilar - Founder/CEO at Hashboard, ex-VP Data @Flatiron Health, Advisor, ex-Amazon Robotics
I worked in supply chain for about five years and the best advice I received from an early manager at the time was to zoom way in and dig deep when troubleshooting a problem. My natural tendency at the time was to look at the data as a whole and miss the human element.
If there was a warehouse that was operating poorly, just go look and see what's going on at the warehouse. Go talk to people, inspect the shelves, look at the actual products. The best data people are able to operate at multiple levels: zooming way out and thinking about the data as a whole and also zooming way in and not losing empathy for what is happening on the ground.
The greatest thing about data is that it can scale empathy, so don't lose sight of the fact that each event could represent a person (or a product, etc.)
Shinji Kim - CEO/Founder at Select Star, ex-CEO of Concord Systems, advisor, investor, and mentor:
"Be yourself" is the best advice I received early in my career.
I had many ideas, thoughts, and questions about how things work but often felt self-conscious about whether I was asking the right questions, making the right decisions, or fitting into my environment. Getting comfortable with the fact that I may look or act differently than others gave me the confidence to push myself further and focus on my goals.
Ryan Janssen - CEO/Co-Founder at Zenlytic, entrepreneur, data scientist, and investor:
Have intentionality.
Early in my career, I asked my mentor to help me choose between two very different jobs. I had a big pro-con matrix and a financial spreadsheet. I talked his ear off for 10 minutes before he interrupted and asked "But how do you want to spend this next 5-year cycle of your career?" And I realized I couldn't answer him clearly.
Many people think they have a good idea what they want to get out of their career, but actually don't. Or they continue on a path that clearly lacks the trajectory they need to get there.
My advice is to take time to introspect. Schedule time if you have to. Write things down. Be deliberate and detailed about what you want to do in your career. Be deliberate about the most important projects you need to work on now to get there. Careers are short and it's easy to let time slip away; for satisfaction and success, have intentionality about your career every single day.
Reflecting on advice I received last year:
- Operating Partner at OpenView, the author of the newsletter:
Look for ways to replace yourself. Early in your career, you get ahead by being the best analyst -- the person who knows the data better than anyone else. That quickly changes. To truly advance, you need to find ways to hand off your responsibilities to someone else.
It'll be painful in the short term. You'll feel uncomfortable. You'll need to rethink your work identity. But it's what unlocks your ability to be proactive, rather than reactive, and to point out opportunities to improve that nobody else sees. If you're not uncomfortable, you probably aren't growing.
- Founder at Deepskydata. Author of the How to fix your tracking eBook, writer of newsletter:
I would say - that I need to focus. I am too curious, so naturally, I dig into 100 topics at the same time.
What it changed - I picked one topic - tracking setup - and spent my energy on investigating it as far as possible. This brought me to a framework for tracking design and gave me plenty of great feedback when I wrote about it.
I stick to this now, that I try to pick one central topic and write about it. It does not always work out 😁
Chetan Sharma - CEO at Eppo, early data scientist at Airbnb, Webflow:
Here's a piece of advice that was useful to me, from my good friend Erik Goldman, founding CTO of Vanta.
"When considering opportunities, reduce your decision space to one "got to have it" thing. Decision quality goes down when you simultaneously consider a composite of factors: wealth creation, technical development, adding well-known brands to your resume, people management opportunities. Far better to condense to one goal: "I want to learn about AI" or "I want to start a company after this". For example, before Eppo I knew I wanted to start a company, and thus indexed heavily on proximity to leadership, reporting directly to the CTO."
For the analyst-specific career path, my big recommendations are:
1. Write, both internally and externally. Give lots of presentations. Doing these will grow your brand and credibility, far more than painfully persuading business stakeholders one by one. Writing one external blog post at Airbnb has done more for my career than years of in-house IC work.
2. Think of analyst work as a stepping stone to another functional domain: product, eng, marketing. This isn't to say that you have to leave data work, but the highest impact analysts will be multi-brained with one of those.
Ergest Xheblati - Author of MVSQL Patterns book, author of newsletter:
I remember this one very well. I had joined a tech company and I wasn’t sure what direction to take in my career. I had been working with SQL and doing analytics engineering for a while and I had also worked on quantitative analytics.
I somehow had this notion that I needed to work on quantitative stuff in order to be closer to the business despite the fact that I didn’t enjoy it much. I enjoyed the engineering aspects much more.
I asked a director-level colleague about what he thought I should do and he plainly said: “Do what you enjoy and are really good at. You also happen to be very close to the business through the work that you do so why change careers? The business also happens to value your work as is since they’re already paying you for it.”
That advice was crucial to helping me continue to build my technical skills and eventually led to me writing my SQL patterns book.
- Co-founder and CPO at Hyperquery, ex @Airbnb, @Wayfair. Author of the newsletter:
The best advice I've gotten came from my skip manager at Wayfair, who told me:
"You should always try to work at places that you're really excited to work at."
At the time, I remember thinking he was just trying to keep me at Wayfair, but in hindsight, I realized this was fantastic advice. When you enjoy your work, everything compounds. You learn faster, you advance faster, you're more creative. Plus, you're happier, which means more of the rest.”
- CEO&Co-founder @Gabe.ai, Investor, Advisor, Shift Operator @Data Quality Camp. Author of the newsletter:
Start with the problem, not the solution. Often times data teams get so wrapped up in complexity that they fail to step back and remember the work we are doing is not academic. If you always root work to clearly defining the problem, you will never have to worry about whether your projects deliver value or not.
Avinash Kaushik - Chief Strategy Officer, BOD at Croud, Best-selling author, writer of the Occam's Razor newsletter:
“Every cutting-edge thing you learned in college will be stale in three years. Hence, take jobs where gaining new knowledge is a key part of being successful.”
Looking back, it has been proven to be true again and again and again. I've done my best in every role to stay close to the real work, and that has forced me to keep learning new skills. The alternative fate is I become yet another director/VP, whose primary success is driven by an ability to suck up or play company politics well.”
- Founder Mode, author of :
For me, the best advice I ever got was to find real problems that I cared about answering.
There are lots of tutorials out there that teach technical skills on toy problems and sample datasets. These problems might teach you a few techniques, but they won't make you a better analyst, because learning to be an analyst requires asking questions, seeing a result, being curious about what that result tells you, asking more questions, and continuing to dig until you uncover something truly interesting and useful. With real data, on real problems that you care about you'll do this naturally; your curiosity will draw you further in. On sample problems, you'll often stop when you get to the answer in the back of the book—which, of course, doesn't exist for most questions you'll want to answer.
Chu-Cheng Hsieh - CTO at SHEIN, ex-CDO at Etsy, Advisory Board Member @Google, Head of Alexa Voice Recognition @Amazon:
The best advice is to always ask oneself: "Do you want to be effective or do you want to be right?" This applies to both data and leadership.
Let's start with data.
This advice reminds me to take calculated risks because speed matters in business. Often the cost of having comprehensive data to make the right decision requires lots of work. For example, one can set the p-value threshold at 0.01 but it means that you need to run A/B tests for an extended period of time – sometimes you probably never hit 0.01 because when you extend the experiment period, you have to also consider seasonality, model drifting, etc. And that's why most companies set p=0.05. Even if such a threshold naturally introduces false positive treatment, the choice is much more effective.
Let's talk about leadership. This question can be applied in different contexts. I'm providing one example here. Often we are facing multi-choice options. Say, there's almost no right answer in designing an organization. When I have to introduce an org change, I often favor consulting only key people (senior leaders, my manager, HRBP, etc.) While it's absolutely possible to consult every manager in the org to gather more information, keeping the group small comes with benefits like speed and alignment. It would take months if dozens of managers are involved in the process. On the contrary, it would be a blind decision to make an org decision without considering different perspectives. The question reminds me to seek a compromise between gathering inputs, achieving alignment, and making timely decisions.
Adam Kinney - VP of Analytics at Mixpanel, ex Head of Advanced Analytics @Twitter, @Google:
The best advice I got was to always ask questions about any request for data, metrics, analysis, etc, until I understand the ultimate decision that the requester is trying to make. All requests like these should ultimately be informing some decision, whether that it is a big one-off decision for the company or an ongoing decision, like metrics that inform a manager on whether their team's execution is on track. When you understand the decisions driving requests, you have an opportunity to figure out how best to inform the decision beyond the specific request and how to formulate it into the format that would be most effective for the decision-makers. It also helps with prioritization since the underlying decisions can usually be sorted for importance and urgency better than specific data requests.
The impact of doing this in my career has been that I moved from a tactical bit player with limited impact to someone who is driving strategy and has huge impact. It has also helped me coach my teams on how to have a bigger impact, which is generally a difficult thing for even pretty experienced data analysts to figure out.
Alex Justman - Vice President, Digital Resiliency at First Republic Bank:
The best lesson I got from possibly one of the worst managers I ever had “Never be victimized by your circumstances”
You have to own your situation. If things turn against you you need to figure out how to assess the position you are in, and identify who you need to work with to provide a solution to your customers!
Naomi Ceder - Chair Of The Board Of Directors for Python Software Foundation, author of the Quick Python Book, speaker, Python instructor:
35 years ago, when I was in my first job as a high school language teacher (in Latin), my first mentor urged me to learn more about computers and programming because he thought it would become important, and getting in on it in the early days would be both interesting and good for my career. He was more right than I think he could imagine since that started everything for me.
The second advice was from my boss was to accept a posting in London to help start a new company about 10 years ago. While there were various hassles for someone older to take a position like that, for me, it was a great opportunity to expand my network and diversify my skills, which was valuable in later positions.
Matt Brattin - Founder TMB Analytics, CFO @Aplos:
I have two pieces of advice that came to me at different times which I've never forgotten:
1) Before I got started, I asked an alumni of my graduate program something he wished he'd known before getting started, and he said to me, "There is no such thing as perfect data". It didn't mean a lot to me at the time, but definitely, as I got out into the wild, it made much more sense that the best you can do is understand your data and "respect your data" so that you can handle it with care knowing there is always going to be some nuance to it.
2) Immediately after getting promoted to my first manager role, I was told by the head of my vertical, "People are unpredictable". This was meant in a way to prepare me for people management and knowing that you can't know everything about the way people work all the time, especially when the team gets large. What I took from this, though, is the importance of communication and creating an environment for openness where you can reduce the unpredictability, but you can never eliminate it fully.
Thanks for reading, and thank you to everyone who shared their learnings ⭐.