Platforms for Pedagogy I

First Installment in a Month-Long Project “Information Systems for Pedagogical Productivity”

Are you like me? A college or university instructor whose computer storage is littered with multiple copies of syllabi and lectures and slide decks? “SOC101-Lecture5-2021F.pptx,” “Lecture 7 Slides,” “Lecture 7 Slides – OUTTAKES,” “API Diagram (1),” “API Diagram (2),” etc. Is part of your brain used for remembering which files for your courses are the currently authoritative ones? A teacher proud of how you manage to integrate your references on Zotero, your slides in PowerPoint, your lectures in Google Docs, you screen captures from Snagit carefully cataloged on MyMedia, YouTube playlists for each class you teach?

There’s often real brilliance in the systems we come up with. And many of us are continually improving our workflows as we live and learn and find out about new products and gadgets. And then we have directories with names like PPOL Intro Materials (NEW). And the thing is, everyone has their own system; I don’t think I’ve ever heard an instructor say that their “system” was the same as or derived from that of some other instructor. A million instructors have a million different systems.

As brilliant as our solutions are, in all likelihood, some of us have solved some of the problems, and some have solved other of the problems; most of us still have lots of problems.

Our Pedagogical Palette

A teacher is simultaneously an author, a performer, and an experience designer. What repertoire of materials do teachers draw on in that work? At the core are two things: domain expertise and a sense – innate or learned – of pedagogical technique. But in addition to these there are a lot of things: syllabi, slide decks, videos and transcripts, images and diagrams, references and bibliographies, annotations and summaries, outlines, assignments, whole quizzes and exams and banks of questions, practice problems and solutions, lecture notes, feedback boilerplate, handouts, descriptions of learning outcomes, workbooks, simulations, stories, illustrations, and examples.

How do we keep track of all this stuff? Most of us store things in hierarchical directories. If we’re good, we name things wisely making them easier to identify without having to open them and all our stuff is on one machine or perhaps in the cloud and synced to all our devices. But even if we pull that off, there is ample opportunity for consternation. Is the top level organization in a course the weeks or modules of the course or do we organize by genre (slide decks in one directory, videos in another? Is it redundant for the names of all objects include a course identifier if they are stored in a directory that names that course? Should directories contain only materials that are actively in use to remain uncluttered or should they be full archives of what I have produced for this unit? How to account for the fact that some things are files on my computer, some things (e.g., videos) are on my account on platforms like YouTube, other things are just links to things on other people’s accounts or bookmarks of websites? How do I keep track of documents I have PDFs of and and bibliographical listings for? DO I have a PDF of that?

The question here is not merely one of archival integrity, but also of creativity and performance. By performance I mean me teaching a course right now. By creativity I mean me conceiving, designing, and building a course. The painter who has an enviable array of tubes of paint in their storage room does not have an enviable array of colours with which to paint. The colours they have to paint with are the ones squeezed out and mixed on their palette. The question is not one of archiving, but rather of making the archive as fully available to the creator as possible. And I need to use as little of my brain as possible for the keeping to hand and mind of the contents of my pedagogical palette.

Seeing What You are Doing

In a video lecture from long ago (2012) Bret Victor enunciated a principle: creators need an immediate connection to what they create. He goes on to show some tools he developed that allow coders and visual designers to have an immediate connection to what they create. I’ve interpreted Victor’s principle as arguing that the creator should not use their brain to simulate the medium in which they are creating. A painter would not think up a set of brush stroke instructions, fully imagine what their effect would be, and then implement these on canvas. A programmer should not have to simulate the computer and compiler they are using as they write code. And designers should not simulate the world and the users for the things they design; instead, they build prototypes and let the world have its say.

This is the world I imagine for the teacher. We should have synoptic access to our repertoires, our pedagogical palette, and have an immediate connection to the things we are creating.


New Browser Tool Lets You Copy Text from Images

Project Naptha is a new plug-in for the Chrome browser that lets you do text recognition (OCR) of online images (e.g., photos of documents) and then cut and paste directly from the image in the webpage.  That means no more save-image-as + import-photo-into-Word + save-as-PDF + OCR + copy-paste-into-your-document OR the old standby: transcribe.

That means you can copy the title or legend from a chart and diagrams or a quote on an inspirational Upworthy poster! Life is good. Should even work on old books in the Google books archive.

Anastasia Salter writes about it in the ProfHacker column (28 April) at

Optimal Deployment of Higher Ed’s Most Valuable Resource

I met Steve Mintz when he was a fellow at the Center for Advanced Study in the Behavioral Sciences at Stanford in 2006. He’s a smart historian and serious scholar who also cares about teaching. He teaches at U Texas Austin where he also serves as Director of the UT System’s new Institute for Transformational Learning. He’s a leading authority on the history of families and children, author/editor of 13 books, past president of H-Net, creator of the Digital History website, and was recently inducted into the Society of American Historians.
In this Inside Higher Ed column he suggests we think creatively about “curricular optimization” – not the conventional “fewer bigger classes” approach but one that is grounded in the recognition that faculty represent our most valuable institutional resource and, as such, its best deployment ought to be a top priority.

Other Pieces by Steve Mintz in IHE

Cool Looking Tool for "Grading" with MS Word

As usual, just when you think of something, it turns out someone’s already developed it a few years before.  I haven’t tried this product, but some friends have suggested it (over Facebook, if you are wondering). It’s from “11 Trees,” a company whose tagline is “Solutions for Writers, Teachers, and Editors”

Efficient Evaluation of Student Work

Ask any teacher – at any level of education – about their job and “time stress” and its variants will be a number one complaint.  It’s no surprise; in higher education, at least, there’s been a steady contraction of clerical support for professors along with a steady expansion of the clerical tasks they are given, a stagnation of resources and wages along with an expansion of the roles they are expected to play, and a steady decline in student preparation and steady increase in what students expect from teachers.

That said, I’ve noticed over the years that the average professor (myself included) is sometimes not the model of efficiency in terms of how s/he organizes work.  It’s common to fall into the trap of being busy rather than being productive.  Sometimes when I catch myself being especially inefficient I notice that I feel too busy to do it more efficiently. As illogical as that sounds, it happens a lot.  As an antidote to that vicious circle, I keep yellow stickies that remind me TO be efficient and lists of time-saving tips I’ve discovered or gotten from colleagues.

One activity that absorbs lots of time (and for me at least generates lots of frustration and strongly tempts me toward procrastination) is grading.  And so here’s a list of ideas for making the grading process a bit more systematic, less onerous, faster, more efficient.

I limit this list to things that make the grading process easier for the instructor.  There are other sources out there that focus on fairness, pedagogical effectiveness, and so on. I certainly don’t deploy all of these at once, but sometimes pausing, reading through ideas like these, and thinking about the process is enough to help me spend less energy just spinning my wheels.

  1. At the start of the semester put all of your courses’ due dates on a single calendar.  Have you timed things in a manner that’s going to make you insane (or cause you to delay getting papers back to students) at midterm?
  2. Design assignments with grading in mind.
  3. Budget your time. As early as when designing syllabus allocate time for grading in connection with assignment due dates. Be realistic.
  4. Develop a shorthand for the most common comments and provide students with a key.
  5. Once a comment shows up on a certain number of papers just put it in a “general feedback document,” perhaps giving it a number or abbreviation for use on individual papers.
  6. If you haven’t done it already, before you start grading, or after skimming through a random sample of papers, write down some notes about your grading criteria – what do you want to keep an eye out for, etc.
  7. Be organized about simple stuff like receiving the papers, filing them, etc. Take 3 minutes before papers are due and write down what the process will be.
  8. Require a “I did the basics affidavit” (Proofread, check; spellcheck, check; Spent at least 5 hours, check) with paper. Do not “grade” for these things. List not checked, paper returned.
  9. Don’t copy edit.  Papers that are seriously unproofread are not worth your time.
  10. Consider blind grading not just because it might be fair but because it can save you time and emotional energy of thinking about particular students as you grade and write comments.
  11. Figure out when using a rubric saves time and when it just creates more work for you.
  12. Grade exams and problem sets by questions, and not by complete exams or individual submissions.
  13. Type your comments rather than writing on papers. Develop quick and easy page/paragraph/line system and start each comment paragraph out with student name.  You cut and paste common remarks. Provides a record.  
  14. Using a grading sheet that asks you questions about the paper or exam and forces you to answer concretely. Does the essay or answer do X? Is the title appropriate for the essay? Does the essay say what it will do?
  15. Time yourself.  Develop a realistic allocation of time for each student’s paper and focus on what the most useful feedback you can provide within that time frame so that you prioritize correctly. Be fairly ruthless about that allocation.  Set aside special cases that seem to be taking too long.
  16. Writing final grade on a sticky note, or lightly in pencil. After all papers graded, check for distribution and then “ink them.”
  17. Focus on one skill per assignment. Or tell students your written comments will address, say, only one main strength and one main area for improvement.
  18. Only grade part of an assignment (random sample, most important part, part student says is her best work).
  19. Outsource the grading (swap with a colleague) and tell students. Student performance often goes up when another audience is involved.
  20. Keep a teaching log. Use the papers for feedback on what you need to do a better job at getting across to students – not just as comments on this assignment, but as what they do and don’t seem to be getting at this point in this course.

    Some Sources for the Above

    (STOP) Wasting Time in Meetings

    A simple step colleges and universities could take to increase efficiency would be to stop wasting time in meetings.  In fifteen years at my current institution I have attended maybe two well organized and well implemented meetings.  Interesting, given that we are an academic institution, how much bad meeting behavior mirrors behavior we would flunk students for. Some examples:

    • My colleagues show up unprepared
    • Agendas not formulated, not distributed, or just ever-growing laundry lists
    • Poorly prepared background material not distributed ahead of time
    • Invite lists based inept theories of representation rather than participation
    • Lack of minutes
    • A culture in which any participant can hijack the conversation
    • No shame in contributing uninformed opinions
    • No urge to identify and work out conflicting positions
    • Decisions made by apathetic consensus

    But the worst thing about our meetings is just that they are unproductive and consume gargantuan amounts of our scarcest resource: person hours.  Better meetings would waste less time and produce more/better results.

    The fact of the matter is a lot is known about how to “give good meeting” as one wit once put it.  But as noted by Amy Gallo a post on the Harvard Business Review blog:

    The bad news is that keeping your meeting on track takes discipline, and few people make the effort to get it right. “The fact is people haven’t thought about how to run a good meeting, or they’ve never been trained, or they’re simply too busy,”….

    The really embarrassing thing about colleges as organizations is that we don’t even recognize the problem (even if we bemoan meetings, we do no critical thinking about them) and even if we do, there seems to be no interest in putting in the effort to improve things.  A little ironic that people whose work involves making abstract mountains out of molehill stuff almost no one cares about are unwilling or unable to think there might be some “science” in something so mundane as meetings.

    One idea, described in a blog post by LinkedIn CEO Jeff Weiner is to eliminate presentations.  Instead, meetings begin with participants reading through notes or slides or a memo giving meetings the tone of a study hall.  But it’s time well spent and the participants start the conversation with equal levels of preparation (and no one feels like a chump for being the only one to do her homework) and it forces presenters to make better handouts since folks are going to be reading it right there in front of them.

    It is a technique borrowed from Jeff Bezos at Amazon.  He starts meetings with up to 30 minutes of participants reading multi-page narrative memos scribbling notes in the margin before the talking part of the meeting gets under way:

    Bezos says the act of communal reading guarantees the group’s undivided attention. Writing a memo is an even more important skill to master. “Full sentences are harder to write,” he says. “They have verbs. The paragraphs have topic sentences. There is no way to write a six-page, narratively structured memo and not have clear thinking.” ( 16 Nov 2012)

    Another technique, deBono’s “Six Hats” method, was described in an October post on this blog.

    Not surprisingly, a good source for ideas is the business media, especially around high tech – bad meetings impose significant and discernible costs in those environments.  In a blog post “How To Run Your Meetings Like Apple and Google” Sean Blanda gathers some meeting principles from several much admired organizations.

    Two from Apple:

    1. Every project component or task has a Directly Responsible Individual whose name appears next to all of the agenda items they are responsible for.
    2. Be prepared to challenge and be challenged. 


    1. All meetings should have a clear decision maker.
    2. No more than ten people at a meeting.
    3. Decisions should never wait for a meeting.
    4. Kill ideas, and meetings. Focus more resources on fewer efforts. 
    5. Focus has to permeate every aspect of a company, including meetings.

    From a variety of sources here are a few good ideas that could make a difference college and university meetings. They are simple and concrete:

    • Compute the cost of the meeting
      • Even if only as a thought experiment, multiply the time by the salaries of the attendees and have a clear picture in your head about how much of the institution’s budget you will consume in this meeting.  How many person-days of work will it eat up?  Make sure it is worth the cost.
    • Make purpose of meeting explicit and clear.  
      • Why are you gathering these people together?
    • Control the size.  
      • Invite the people who need to be there to accomplish the purpose.
    • Assign someone to take notes. Tidy them up and distribute promptly.
    • Come with solutions, not questions/problems.  
      • Meeting chair must do her/his homework and put potential solutions in front of meeting for discussion, feedback, evaluation, expansion rather than announcing problem and throwing it open for suggestions.  People do not generate good solutions on the spot.
    • When brainstorming, forbid criticism.
      • Don’t let people waste time with “war stories” (“we tried that back in 1995….”)
      • Don’t waste time flaw-finding until you have narrowed the field of options
      • Don’t encourage people who are lazy negative thinkers
    • Manage ramblers and control tangents.  
      • Model focussed participation and call out lack of focus.  
      • Focus on action, responsibility, and completion.  When conversation rambles, loses focus, bring it back with what can actually be done.
      • Don’t be afraid to call people on being broken records.
      • Structure agenda and your comments to promote focus.
    • Who is responsible? 
      • Every task needs one ultimately responsible individual.
      • Every document has a responsible author and an explicit list of contributors.
      • Invite list should include people who can do things that will be talked about.
    • Be deadline driven.  
      • Make timelines that capture actual priorities.
      • Review what people promised last time and whether it’s been done (don’t just ask for reports, as chair you should already know).
      • Cultivate a “get it done” rather than “delay until it’s perfect” culture.
    • Eschew excuses.  
      • Hold one another accountable rather than understanding why things are not done.
    • Don’t talk about meetings as work
      • Work is what happens in between meetings.  Do not valorize having a schedule that is full of meetings.

    References and Resources

    1. Jeff Weiner.  “A Simple Rule to Eliminate Useless Meetings
    2. Sean Blanda. “How To Run Your Meetings Like Apple and Google
    3. Amy Gallo. “The Seven Imperatives toa post Keeping Meetings on Track
    4. Christopher Wink. “Technically Media meeting style: effective, productive and professional from home