As a #DataAnalyst, your best north star for skills development is... speed! 🧵
Don’t be fooled by a simplistic interpretation of speed. A sloppy analyst who keeps falling for shiny nonsense “insights” will only slow everyone down in the long run. "Speed" means something nuanced. 🧵
Analysts must master many different forms of speed, including:
Speed of getting data that’s promising and relevant. (Domain knowledge.)
Speed of getting data ready for manipulation. (Software skills.)
Speed of getting data summarized. (Mathematical skills.)
...continued...🧵
More kinds of speed for analysts to master:
Speed of getting data summaries into their own brains. (Data visualization skills.)
Speed of getting data summaries into stakeholders’ brains. (Communication skills.)
Speed of getting the decision-maker inspired. (Business acumen.)
🧵
The data landscape is changing rapidly, so you can’t afford to stagnate. The tools you use today won’t stick around for long. Keep sharpening your claws, but don’t chase the buzzwords. 🧵
There are a lot of insecure people who don’t know how to make themselves useful so they put all their effort into titles, certificates, badges and other baubles. You’re better than that. 🧵
Stop asking: “Should I learn this tool/method/technique that all the cool kids are talking about?”
Start asking: “Will learning this make me faster?”
🧵
Learn whatever makes you faster (in all the ways that matter). Since your work involves accelerating others, start by accelerating yourself. 🧵
In a #DataScience project, all paths lead back to #Analytics, often with messy inherited data - here are some helpful skills and traits for it, a thread 🧵
🔥domain knowledge🔥helps data scientists and analysts make sense of the chaos and guide their judgment about how to spend their time and effort. 🧵
🔥data design skills🔥help data scientists and analysts inform data collection efforts based on what they’ve discovered. 🧵
A decision scientist's 2 tips for new year's resolutions involving diet and exercise, a thread. 1/🧵
Diet tip: Calibrate your evaluation window. If you have a resolution to reduce intake of something, don't evaluate your success by comparing today with yesterday. 2/🧵
A day is an arbitrary unit, so why not optimize your evaluation window? A day seems natural, so many people don't ask themselves if it's the best unit. But if you use a shorter window, your chance at a "fresh start" comes sooner. 3/🧵
2/🧵 Allow your approach to be sloppy at first and burn some of your initial time, energy, and data on informing a good direction later. That's right, you're supposed to start sloppily ON PURPOSE.
3/🧵 Have a phase where the only result you’re after is *an idea of how to design your ultimate approach better.*