Digital Literacies and Technology Proficiencies -- What do our students need to know?

Over the last couple weeks, I've been engaged in conversations with a number of my colleagues about the question of what digital skills and fluencies students need to know to be successful in college and beyond. [The longest and most fruitful conversation was with our terrific director of Teaching and Learning Technologies, Martha Burtis.] What follows is a jumbled beginning discussion of what I feel are priorities as we look toward getting students prepared for success in classes and creating adaptable, responsible, information-literate, global citizens.

First, we need to begin with basic informational and technological competencies and we need to start by defining in a broad sense what we mean by “competencies,” a word that has been gaining a great deal of traction lately without a great deal of explanation. I think (though I'm hardly the first to articulate this) that digital competencies are made up of both technical skills (ranging from changing margins in Word and more advanced MS Office functions to a familiarity with online tools including email, search engines, IM, blogs, wikis, and so on) and digital fluencies (requiring a higher-order deployment of those skills in producing and consuming information in an adaptable, creative, responsible way). [It's also important to note that this definition of "competencies" goes beyond the notion of bare adequacy.]

If we accept this notion of skills versus fluencies, I would argue the emphasis of our digital proficiency goals should be aimed at achieving fluency, not skill mastery. Can we not expect students to come to college with a basic familiarity with the skills of digital life? Can’t basic skills (word processing, email, spreadsheets) be expected? But Jeff, aren't there plenty of entering college students who are familiar with aspects of the digital world, but don't know how to do all of these things? Why, yes, I'm glad you asked. Certainly a focus on fluency over skills would require institutional support in the form of a Technology Center, online guides, brief workshops (no more than an hour or two), and perhaps student tech tutors, so that students not capable of certain skills could find the answers to questions about margin changing or Powerpoint presentations or what ever they needed for a particular class.

There is, I think, an important parallel here with the way we address writing in college. A small percentage of our students have poor grammar skills. [Most are quite good at grammar.] There are resources on campus to deal with those issues, but we don’t send them to a separate class on grammar (nor do we advocate all students take a test on grammar). The school does have a writing intensive requirement, however, that necessitates students demonstrate a number of their writing skills, which of necessity requires familiarity and facility with grammar.

So, can’t we tell new students, “these are the basic computing skills every incoming student should have” and then offer them resources to address the gaps they have? The vast majority of our students do have a broad familiarity with basic computing skills. [We might even have an (optional) placement assessment like we do with foreign languages that would allow them to measure their technical computing skills.]

We can then focus the technology proficiency requirement on fluencies, on an adaptable ability to think, create, and operate within the digital world. And we need to make these fluencies the centerpiece of the requirement (not digital skills or even the classes/fulfillment requirements).

The advantages of focusing on digital fluencies over digital skills are numerous:

• Testing students on basic skill sets makes most of them feel like they are wasting their time on things they already know, or on things they think they'll never use.
  
• Focusing on digital fluencies allows us to expect more technological sophistication from students. [This is as opposed to a kind of low-level investment in a skill-test system that encourages only completion (and that only barely) and not engagement, creativity, or adaptability.]

Broadly stated, what do I see as the key competencies of digital literacy?

• Researching, finding and evaluating primary and secondary sources
• Presenting one’s ideas in a variety of formats (written, oral, formal/informal--online)
  

The next question to ask is how these digital fluencies will be delivered. I think the material should be incorporated into one or a set of class(es), not a separate course on "technology". Integrating digital fluencies into classes (general education and departmental requirements) has a couple of key results. First, it indicates the importance the institution and faculty have invested in those fluencies. Second, it provides students with content-linked opportunities to demonstrate their ability to maneuver and participate in the digital world (locally and globally)

The most recent discussions of our technology proficiency have revolved around a two-tier system, with a foundational level (a course or courses) intended to address those fundamental competencies incoming students need for their college experience in general, and a discipline-specific requirement. The latter would allow departments to integrate those discipline-specific digital skills and fluencies into their curriculum and support plans. [So a psychology department might incorporate SPSS into their methods classes, while Math could include work with Mathmatica or Dynamic Solver.]

In determining the success of the digital fluency approach (and more generally of the technology proficiency program), we need to make sure that the assessments are not multiple-choice, specific skills tests, but rather allow students to demonstrate competencies within a framework of actual activity and usage.

What do you think? Is this an approach that makes sense? Is it an approach that can garner support among faculty, students, and administrators?

E-Portfolios--Part II--A New Hope?

I started to write this post in the comments section of my last post, but realized it was getting prohibitively long to fit in the comments.

I don't disagree with either of the comments raised by Steve and Jerry. Various parts of what I described as e-portfolios could be started without a full-blown university-wide e-portfolio system. [And some of my colleagues at CGPS have already begun to do so.] All that is good. Students could demonstrate competencies in technological proficiency and/or digital literacy (they're different things, a subject for a future post), they could maintain online archives of sorts of their written work using blogs or wikis or some other medium, and even reflect on that work.

But would students do that on their own? Probably not. Will they do so when it's assigned? Likely, and they might even get something out of it. But without other professors doing the same thing they're not likely to connect it to a larger educational experience or broader world.

I guess the real appeal to me of the e-portfolio (beyond the practical function as an accessible place to collect work) is on the grand scale. One place to assemble the work of a college career, one place to reflect on four years' worth of research, writing, even presentations (digitally recorded), one place to make connections between courses and concepts, between science and literature, between language and society. Steve's right in his comment that this reflection could be going on all the time. Heck, it should be going on all the time. But what appeals to me (and what I see as its biggest problem) is the notion of some kind of complete integration of the e-portfolios, a notion that would require grass-roots and top-down support from administration, faculty and students. Since I have trouble envisioning that broad institutional buy-in, I'm having trouble buying into doing this piece meal.

I suppose my pragmatism is blocking my vision in this case.

Maybe this is the kind of thing that might best be tried out at the departmental level. [If any of my departmental colleagues are reading this, rest easy. This is a thought piece, not next meeting's new business agenda item.] A department could decide that it wanted its majors to collect their writings, speeches, and everything else related to the major in one place; that it wanted its majors to be consciously reflective about their courses and the material/concepts/skills learned in them; and that it wanted them to explore the value of that content and those competencies for their own goals in and after college.

A department would be larger than a single professor's desire and therefore would reflect a larger commitment to the concept on the part of a group of faculty within a discipline on campus. On the other hand the issues of scale and practicality I raised in my earlier post would be less problematic with 5-15 professors and 50-250 students than they would be with an entire campus. [Plus, getting buy-in from a single department is more feasible than convincing an entire campus.]

Thoughts?