Sergio Lizarazo
@checho.co
🎓 Anthropologist turned Data Scientist | Making data accessible for everyone | 10+ years in development M&E | 🇨🇴 | EN/ES | Writing about career change | Pythonista in training |
Find me @ www.checho.co
Find me @ www.checho.co
10/ The path from service desk to strategic partner isn't easy, but it's worth it.
Both for your career and for the actual value you deliver to your organization.
#DataLeadership #FutureOfWork
Both for your career and for the actual value you deliver to your organization.
#DataLeadership #FutureOfWork
February 6, 2025 at 9:46 PM
10/ The path from service desk to strategic partner isn't easy, but it's worth it.
Both for your career and for the actual value you deliver to your organization.
#DataLeadership #FutureOfWork
Both for your career and for the actual value you deliver to your organization.
#DataLeadership #FutureOfWork
9/ Final thought: Your time and expertise are valuable. The moment you start treating them that way is the moment others will too.
#CareerGrowth #DataAnalyst
#CareerGrowth #DataAnalyst
February 6, 2025 at 9:46 PM
9/ Final thought: Your time and expertise are valuable. The moment you start treating them that way is the moment others will too.
#CareerGrowth #DataAnalyst
#CareerGrowth #DataAnalyst
8/ Remember: You're not being difficult by pushing back. You're being professional.
The best analysts aren't just good with data—they're good at shaping how their expertise is used.
#ProfessionalDevelopment
The best analysts aren't just good with data—they're good at shaping how their expertise is used.
#ProfessionalDevelopment
February 6, 2025 at 9:46 PM
8/ Remember: You're not being difficult by pushing back. You're being professional.
The best analysts aren't just good with data—they're good at shaping how their expertise is used.
#ProfessionalDevelopment
The best analysts aren't just good with data—they're good at shaping how their expertise is used.
#ProfessionalDevelopment
7/ Pro tip: Start every project with a discovery session.
Make it clear that this is your standard process. It signals professionalism and prevents the "quick report" mentality.
#DataTeams
Make it clear that this is your standard process. It signals professionalism and prevents the "quick report" mentality.
#DataTeams
February 6, 2025 at 9:46 PM
7/ Pro tip: Start every project with a discovery session.
Make it clear that this is your standard process. It signals professionalism and prevents the "quick report" mentality.
#DataTeams
Make it clear that this is your standard process. It signals professionalism and prevents the "quick report" mentality.
#DataTeams
6/ Key shift #3: Build relationships before reports.
Spend time understanding the business context. The best solutions often come from conversations, not requirements docs.
#DataCulture
Spend time understanding the business context. The best solutions often come from conversations, not requirements docs.
#DataCulture
February 6, 2025 at 9:46 PM
6/ Key shift #3: Build relationships before reports.
Spend time understanding the business context. The best solutions often come from conversations, not requirements docs.
#DataCulture
Spend time understanding the business context. The best solutions often come from conversations, not requirements docs.
#DataCulture
5/ Key shift #2: Position yourself as a consultant, not a service provider.
That means asking tough questions, challenging assumptions, and sometimes saying no.
#CareerAdvice #DataViz
That means asking tough questions, challenging assumptions, and sometimes saying no.
#CareerAdvice #DataViz
February 6, 2025 at 9:46 PM
5/ Key shift #2: Position yourself as a consultant, not a service provider.
That means asking tough questions, challenging assumptions, and sometimes saying no.
#CareerAdvice #DataViz
That means asking tough questions, challenging assumptions, and sometimes saying no.
#CareerAdvice #DataViz
4/ Key shift #1: Stop accepting vague requests.
When someone asks for a dashboard, respond with "What decision are you trying to make?" Not "When do you need it?"
#DataLeadership
When someone asks for a dashboard, respond with "What decision are you trying to make?" Not "When do you need it?"
#DataLeadership
February 6, 2025 at 9:46 PM
4/ Key shift #1: Stop accepting vague requests.
When someone asks for a dashboard, respond with "What decision are you trying to make?" Not "When do you need it?"
#DataLeadership
When someone asks for a dashboard, respond with "What decision are you trying to make?" Not "When do you need it?"
#DataLeadership
3/ Reality check: Your value isn't in churning out reports.
It's in your ability to understand business problems and translate them into data-driven solutions.
#DataStrategy #DataDriven
It's in your ability to understand business problems and translate them into data-driven solutions.
#DataStrategy #DataDriven
February 6, 2025 at 9:46 PM
3/ Reality check: Your value isn't in churning out reports.
It's in your ability to understand business problems and translate them into data-driven solutions.
#DataStrategy #DataDriven
It's in your ability to understand business problems and translate them into data-driven solutions.
#DataStrategy #DataDriven
2/ The problem: Most business teams see data analysts as order-takers.
"I need this dashboard by Friday" sound familiar?
This creates a cycle of rushed work, missed opportunities, and frustrated analysts.
#BusinessIntelligence
#DataScience
"I need this dashboard by Friday" sound familiar?
This creates a cycle of rushed work, missed opportunities, and frustrated analysts.
#BusinessIntelligence
#DataScience
February 6, 2025 at 9:46 PM
2/ The problem: Most business teams see data analysts as order-takers.
"I need this dashboard by Friday" sound familiar?
This creates a cycle of rushed work, missed opportunities, and frustrated analysts.
#BusinessIntelligence
#DataScience
"I need this dashboard by Friday" sound familiar?
This creates a cycle of rushed work, missed opportunities, and frustrated analysts.
#BusinessIntelligence
#DataScience