Today we defined the work-to-be-done to address the need for a top-down schema of the survey, so today let’s focus on how I’m thinking about our first xAPI Profile.
Now that I seem to be back in the writing groove, I feel like it’s time to commit with some intentionality to how I want to learn and grow my own skills, and what I want to have shared through writing or producing another way, this year.
This is the fourth in a series. In my last post, I identified at least two work-streams for the team to pursue in coming up with our analytics strategy, which for all intents and purposes is our integration strategy
In my last post, I shared a bit of background on the Casey-Fink Graduate Nursing Experience Survey, which I’m using in an ongoing case-study on how to approach analytics strategy. Today’s post will get further into the details of how to set up the work-to-be-done, in terms of data modeling.
The words “analytics strategy” can be scary, but really it’s just a) identifying what we want to know about content and how it gets used; and b) defining clearly how we’re going to do that.
Much like any content or media with which we engage users, with a survey we need to prioritize more than just the survey results; we should be improving the survey and the survey experience. Here’s how I approach it.