What is the problem that has led to this request?
Having some kind of background is much more helpful than just 'give me a dashboard that does xx'. Taking the business problem, turning it into a data problem, coming up with a data solution then presenting back a business solution is an art form in itself.
What will solve the problem? one grid? five pages of grids? a chart? A number?
No point making a beautifully responsive, interactive dashboard if they are just going to download the raw data into a spreadsheet or pick a number out and put it in a slide deck.
What external data do you have that we need to align to?
Nothing worse than finding out there is logic you should have used or another dataset they are checking yours against. The words no one wants to hear ... 'er ... your numbers look a bit wrong'
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
✨ Fabulous as always @helenanders26
! All three are stunning responses with so much wisdom behind them.
I have slowly pulled back to start with some sort of compiled dataset for MANY requests for reasons highlighted in #2. Most folks seem to enjoy being able to touch the data a little bit as long as they don't have to spend days recompiling reports. There is always room to riff off of their ideas when jumping to the next level with responsive interactive graphs.
You're absolutely right, folks like being able to tinker around and 'drill down' at certain points. It's important to take an iterative approach so you don't aggregate away everything only to find they need more detail than you thought.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If I'm asked for data I generally ask:
What is the problem that has led to this request?
Having some kind of background is much more helpful than just 'give me a dashboard that does xx'. Taking the business problem, turning it into a data problem, coming up with a data solution then presenting back a business solution is an art form in itself.
What will solve the problem? one grid? five pages of grids? a chart? A number?
No point making a beautifully responsive, interactive dashboard if they are just going to download the raw data into a spreadsheet or pick a number out and put it in a slide deck.
What external data do you have that we need to align to?
Nothing worse than finding out there is logic you should have used or another dataset they are checking yours against. The words no one wants to hear ... 'er ... your numbers look a bit wrong'
✨ Fabulous as always @helenanders26 ! All three are stunning responses with so much wisdom behind them.
I have slowly pulled back to start with some sort of compiled dataset for MANY requests for reasons highlighted in #2. Most folks seem to enjoy being able to touch the data a little bit as long as they don't have to spend days recompiling reports. There is always room to riff off of their ideas when jumping to the next level with responsive interactive graphs.
You're absolutely right, folks like being able to tinker around and 'drill down' at certain points. It's important to take an iterative approach so you don't aggregate away everything only to find they need more detail than you thought.