When doing data analysis, investing time with people and the process of analyzing data, as well as it's resources, will allow you to better understand the information. It will significantly benefit the data analysis process as well as the results from that analysis. Exploring your mindset and getting to place of neutrality and purpose while working can help clear the mind to do a more thorough and complete study. Look at the big picture and the small; understand the bias and the purpose. Data analytics is as much an art as it is a science. Anyone with any background can be curious and investigate information to tell a complete story. Data analyst for a large university by day, an instructional designer for a sales training company by afternoon, and a mom/wife/sister/aunt/friend by night. A recent graduate of the online Master of Learning Technology program, she is in the process of changing careers and incorporating her perspective from each of her backgrounds. As a student, she has presented at multiple conferences, both academic and workshop format. And this past year, with a team of her peers, published her first article. This talk was given at a TEDx event using the TED conference format but independently organized by a local community. Learn more at https://www.ted.com/tedx
So when we're plotting our points in life,
either as new parents, new graduates, newlyweds,
we always think that path is very clear and pretty straight.
But we know better.
We know that it's windy and a little confusing
and more like a journey and an adventure.
What we're doing is having experiences
that culminate into the next great thing.
So when I completed my undergrad degree in math,
this is how I felt.
I was searching for jobs with the title analytics in it
because I knew I wanted to work with math,
but I wasn't in the applied math position.
Those first few jobs in analytics
were really putting numbers into spreadsheets
and then doing, brace yourself,
really simple formulas in Excel,
adding up numbers across the row and columns.
The people were great.
The companies were nice.
It just wasn't the right fit.
So I kept looking for work
and eventually landed in higher education.
Now in higher education,
the process of onboarding me
and getting me started into work was slightly different.
Here, they had me sit in on meetings
learning about business processes.
Business processes like how a student
would enroll into a class
and how we would count that enrollment.
And then I would sit in meetings
learning how to take that information out of the system,
that big black box,
and put it into a pretty PDF and send out
so that people could see how many people were enrolled.
It was fine.
It was, again, good work,
but I got a degree in math.
Math to me is beautiful.
Take this agave plant from Tucson where I live.
It represents to me a fractal.
A fractal is a geometric, excuse me,
geometry shape that repeats itself.
And I know it's not a perfect fractal,
so I don't want my undergrad advisor
to come yelling at me,
but it's still beautiful.
Math is also certain.
Two plus two equals four every day.
It never changes.
This is what I love about math.
So here I am putting information into spreadsheets.
No big deal.
And again, like I said, it worked.
It wasn't until our system went through
a complete conversion
that it had a difference in perspective.
And when I say a system conversion,
I'm talking about a legacy mainframe
to a PeopleSoft system.
And if you don't know what that means,
it's essentially switching from Samsung to iPhone
or back and forth.
It's a completely different way
of pulling out your data out of this big black box.
I didn't get drug into a ton of meetings
because I'd only been there a couple years,
but I did know enough about critical information
that needed to be reported
to the state and federal government.
So in our staff meetings,
we would talk about how we're going to report
in this new world.
One of the critical pieces of information
in higher education
is whether or not a student
is a new first year student,
freshman, if you will.
We didn't have a way of recording this
or reporting this in the new system,
so somebody had to spend the time
figuring out how to identify these students.
I was ready for a new challenge.
Let's try this out.
So I approached my boss and mentor
and asked if I could give it a go,
and she said, go for it.
So I met with my colleagues,
Bob and Harry,
and asked them questions.
How does this work in the old system?
How do you think it's gonna work in the new system?
I spent time face to face with these people
really trying to understand
how the data worked
and get that knowledge from them.
In a way, I was collecting data myself
in a different way.
Then I had to meet with different departments
because every department also cared
about how this data went into this big black box
or they cared about how it came out.
So what I learned in this portion
of data analysis path
is that I had to spend time with people
to really understand the data process.
Next, I had to spend time with the data itself
because as much as I'd love to say
that data goes into a system
and it comes out perfect every time,
that's not true.
There's tons of errors and quirks
and exceptions and timing differences.
So I had to spend time with the data
to really understand how it works.
So now let's talk about bias.
This little boy is my seven-year-old son.
He has what I like to call condiment bias.
He has never tried mayonnaise,
but if he has to put it on a knife
and put it on a sandwich
to help me make lunches for the week for his dad,
he holds it as far away as he possibly can.
He's never tried mayonnaise.
My daughter, on the other hand,
will only eat ketchup.
She has a ketchup bias.
So the bias that I brought
whenever I was doing data analysis were a couple.
The first is that if something happened
in a prior report in the prior term,
in the prior year, or even the prior week,
I would assume that I already analyzed why that happened,
and I'm not gonna worry about it anymore and moving on.
You make a lot of mistakes,
you miss a lot of crucial evidence when you do that.
The second thing is when I was a newer analyst especially,
I was raised to make yourself irreplaceable.
The only way you're gonna keep a job,
especially in that job climate that I was in,
was if you couldn't be replaced.
My perception was that if I looked like I could move fast,
do a lot quickly, and I knew what I was talking about,
even though I didn't, I would not be replaced.
So when I needed to spend time face-to-face
with people and ask questions,
I was very hesitant, I kept to myself,
or I did as much research as I could on my own,
when all that knowledge was in the cube right next to me.
But I didn't wanna look like I could be replaced.
I also made really dumb mistakes
because I was rushing through processes and reports.
Dumb mistakes like using a greater than
instead of a greater than or equal to.
Some people may say, so what?
Well, it costs us time, the company time, me time,
other people's time trying to fix this error,
trying to explain this error,
and it costs a little bit of your reputation.
Rushing through and instead of spending 10 more minutes
on this side cost me three more hours on this side
and a little bit of trust.
So after seven, eight years in data analysis,
I started learning new patterns, learning new things to try
based on what I'd learned from other people
and from my own experiences.
So instead of just diving into a project,
I take a 30,000 foot view.
I bother people.
I look at the data and I ask questions.
I look for patterns.
And then I start slicing and dicing.
So it's at this point in my career
that I thought I had a pretty clear path.
I know what's going on.
I know where I'm going.
And I'm pretty good at this data analysis thing.
Well, two years ago,
my husband received this unbelievable offer.
And my family and I picked up
and moved from Columbus, Ohio to Tucson, Arizona.
It was a big change, but it was an exciting change.
And we said to ourselves, you know what?
If we're gonna do this,
we're gonna lay the chips down where we want.
I wanted to go back to grad school.
So why not?
I'll go back to grad school.
I'll work part-time as an analyst.
Well, I was going from full-time worker and parent
and juggling a family and home
to working part-time from home.
It's very different.
It's good, but it's different.
Also a full-time student in an online program
and still a parent and a mom.
Oh, and our family and friends
were all 1,700 miles away in Pennsylvania, Ohio.
Oh, and I was going into a different field completely.
I was going into a Master of Learning Technologies program,
something that had always been a passion of mine,
but I just didn't make the time for.
My first semester
in this Master of Learning Technologies program,
I got to work with some excellent people.
The way that we introduced and met each other
was a little fun, though.
It was through group work.
Everybody loves group work.
We did a project on evaluating a learning management tool.
We formed Team Tank, which is Tim Nunn,
myself, Natalie Gintert, and Kara North.
And when our project was completed,
we spoke with Dr. Ana Paula Correa,
who was our professor for the class,
and she suggested that we present our project
at a conference.
Well, I had never been to a conference,
let alone presented at one,
but this sounded like,
okay, if they're gonna be with me, I can do this.
I immediately became a conference junkie.
I wanted to attend and present and just be a part of this.
I wanted to gather data
and be face-to-face with more people.
I wanted to learn more experiences,
and then I wanted to share what I had to say,
because after you present,
people come up to you because they have questions
and they wanna know.
It's exciting.
At that same conference,
I met a lady named Katie Stroud.
Katie Stroud likes to talk about the power of story.
And like any human being, when I heard her information,
I related it to myself,
and I thought, that's what a data analyst is, right?
You're taking information from this big black box
and you're telling a story with it
based on a question you may be asked
or something that you wanna share.
I also learned at these conferences and in this new world
that instructional designers, teachers, and educators
really don't have a lot of information or data.
When they're trying to make an assessment
of the success of their class
or a tool they're trying to implement
or the teacher themselves,
they really have a hard time measuring that qualitative data.
I really began to appreciate the fact
that I had these massive data points
in my comfort zone job.
And then I started thinking that maybe data analysis
is something that we should all start to embrace.
We should all start to try and figure out
where we can pull this information from.
At another conference that was more academic-based,
I met a lot of graduate students and professors
that were presenting on their research.
Remember that I'm new to the world of graduate school.
So when I would listen to their presentation afterwards,
I would say things like, that was wonderful.
So what's next?
What are you gonna do with this?
Everybody's response was to get published.
And I thought, well, that's awesome.
Let's do this, get published thing.
But what else are you going to do with it?
What problem are you trying to solve?
Who are you trying to help?
What are you gonna look into next?
And I realized I was coming across a bit of a aggressive
and backed off and just stopped asking
and started listening.
One presentation by a Dr. Thomas Reed
started talking about a rift between educational practice
and academic research.
The teachers feel like researchers aren't looking
into the things that they need
or sharing information with them.
And then researchers feel like they provide
all this information and do all this research,
but it's not applied.
And that's when I realized
that I have a different perspective.
I'd been a data analyst all this time
and these pressures from graduate school
are completely different.
And I thought, again, there's a gap here.
This is data analysis.
This is one system and one system
and nothing's happening in between.
This is where I started to think
there's purpose in data analysis
to bring these two people together,
to bring these groups together,
to find a way to share the information.
So when you think about data analysis,
think about spending time with people.
Think about asking questions.
Thinking about lifting the heavy rock
before the presentation.
Look underneath things.
Really appreciate the time that can be spent
and the data that's out there.
Data analysis is as much an art as it is a science.
Anyone from any background can really appreciate its beauty.
And anyone from any background
can really appreciate the power
it can bring to our relationships.
Thank you.