DEV Community

Tim
Tim

Posted on

Importance of Data Discovery Spikes

A meeting prior to a data discovery spike tends to use time poorly for everyone involved. In corporate situations (ie: not contract/client based) where you can spike on a data set prior to meeting about the needs, this will save everyone time.

As you first review the data (spike), you can catalog as needed, provided that this isn't already available. If it's available, compare how it's cataloged versus what's actually there (in some cases, data is labeled incorrectly). With this technique, you'll have an understanding of what you're looking at and where the data live. When you meet about the data needs, you'll already have mental links to the data.

This is the point where I'll use pre-built queries/analysis to review the data set.

The result of this is that you'll take much better notes due to the mental links plus you'll ask better questions if you have them. The best part is that you'll save everyone time - there is no shortage of people in the corporate world complaining about the number of meetings they attend!

Image of AssemblyAI

Automatic Speech Recognition with AssemblyAI

Experience near-human accuracy, low-latency performance, and advanced Speech AI capabilities with AssemblyAI's Speech-to-Text API. Sign up today and get $50 in API credit. No credit card required.

Try the API

Top comments (0)

👋 Kindness is contagious

Explore a sea of insights with this enlightening post, highly esteemed within the nurturing DEV Community. Coders of all stripes are invited to participate and contribute to our shared knowledge.

Expressing gratitude with a simple "thank you" can make a big impact. Leave your thanks in the comments!

On DEV, exchanging ideas smooths our way and strengthens our community bonds. Found this useful? A quick note of thanks to the author can mean a lot.

Okay