Today’s HBR post about “The Quick and Dirty on Data Visualization” had me looking back through some of the presentation sites and links I’ve collected over the years.
Tips and Tricks
Today, I had a chance to listen to a very bright guy from Gartner Research talk about how to create better metrics for the Infrastructure and Operations of our district IT department. He was on to some good things, some of my highlights:
- We tend to focus on productivity metrics (i.e. number of help desk tickets closed or bug fixes released) because the are easy to quantify, but one dimensional analysis doesn’t help the bottom line.
- We rarely look at more difficult metrics such as efficiency gains, end-user satisfaction, or IT staff satisfaction.
- IT departments need to demonstrate value by redefining metrics in business specific terms.
As my mind wondered, I couldn’t help but think about how this is the same issue with Ed Tech. When technology is introduced into the classroom the metrics are usually focused around productivity. All of my students now have blogs, all of my teachers now have a Twitter PLN, all of my administrators now have a google apps account, etc…
We aren’t doing a very good job asking the critical questions that actually justify the huge investments that schools are making in Ed Tech:
- Is this technology allow teachers to focus more of their time on what they do best, teach, inspire, and motivate?
- Does the technology being used directly effect learning outcomes?
- Can Ed Tech usage be describe and defined by something less ambiguous than giving students 21st century skills?
As more of us are getting heaps of tech to meet the needs of online testing, how are you going to define your metrics to go beyond the number of students that successfully tested online?
Excited about “Hour of Code”?
Learning to code opened doors to me personally and professionally. It also empowered me to become a more effective problem solver and thinker.
Most importantly it drew back the veil on the most fundamental “black box” in modern society.
So, I challenge anybody that reads this to not stop with an hour of code, but to push ahead. 10,000 hours might be to much for you, but 10,000 lines of code might just leave you with a cool app or two.
Get started with these resources: