Skip to main content

Reducing the Administrative Burden Means You Need to Help Us

My AD forwarded yet another article today (this one in Science Magazine) about the increased administrative burden placed on faculty and researchers. To quote:
A 2007 survey by the U.S. Federal Demonstration Partnership... found that 84% of faculty in the United States believe that the administrative burden associated with federally funded grants has increased significantly in recent years. Most notably, the study indicates that of the total time that faculty devote to research, 42% is spent on pre- and post-award administrative activities. [Here's the report]

First, this is a perception that is widely shared up and down the research structure. Central offices, research assistants, and researchers alike are being asked to complete more paperwork, submit to more reviews, and respond to more and deeper questioning than ever before. And, with good reason.

Headline-making conflicts of interest and the need to protect subjects, both human and animal, and security concerns in a "post-9/11 world" (what a stupid phrase) demand that regulations tighten to prevent or discover abuses.

My entire job revolves around this issue. The work done building and integrating systems is all done in the name of reducing the need for faculty and staff to redo duplicate forms, assemble printed proposal packages, or manage a paper trail that fills an entire floor (no joke). Our mantra is "do no harm."

But, here's our challenge. I can get hundreds of staff people, from research administrators to central office folks, to volunteer their time for months to design a form or automate a business process. What I can rarely get, and never with any commitment of time or extended effort, is a faculty member to do the same.

6,000+ faculty members are represented in the report linked above. 84% believe that their burden has increased in recent years. Yet, over two projects and 4 years, we've had to conscript, at most, a dozen faculty members to work with (not "on") our projects. Of that dozen, none of them are willing or able to commit to more than an hour a quarter specifically to a project.

And so, my plea and promise. I promise, we really do hear your concerns and we really do want to reduce your burden. But we need your help. Not just at my institution, for this is a problem I've heard from many other institutions. When we ask--and we'll ask--we're not there to disrupt your life. We're not there because we picked your name out of a hat (in fact, a senior administrator probably pointed us your way with a "they're always helpful" sort of comment). We're there because we have questions about how you want to use the system, how you work on a day-to-day basis, how you think the best way could be.

If you don't give us your time, we understand. But the contract goes both ways; you, by not giving of your time, have to understand that we did our best with the information at hand. We are not psychic. We do not see what happens in your office all day long; we suspect neither does your research administrator, but they're the only ones giving us information.

So, please, please, when we show up in your office (and we will take the time to come to you), give us a chance. Consider that your time is spent not only in furthering your own work, but the work of hundreds of other researchers around campus. I pledge to not waste your time, to deliver the best product I can, and to credit you every chance I get.

We'll even get you a T-shirt.


Popular posts from this blog

Happy Retirement Pat Sweeny!

In a previous life, I was an active member of the West Michigan Shores Chapter of the STC. I met a lot of really cool people there and learned a lot about what it meant to be not just a technical writer, but more about how technical writers can break out of the mold and accomplish things.

One of the people who did that was Pat Sweeny. Pat is (or was, by this point) the President and owner of The Bishop Company, a contract do-it-all house; they document, streamline and illustrate your process, and they do it damn well. Pat was one of the first people in that chapter to "get it", which is to say, he and his company understand that technical writing isn't going to be a department for very much longer, it's going to be a business.

He had the foresight to actually make it a business, but he also had something else. Pat was forever trying to better those around him. He would come to meetings (which was a big step beyond most people) and teach you things. Or he would come to …

Google Inbox: A classic Google product

My work domain (an EDU) recently had Google Inbox enabled so I had a good chance to try it out. My personal email is relatively quiet and, I believe, doesn't provide a good Inbox experience. Work is more active and requires actual management, something I've tossed many a tool at over the years. As part of my work life, I supported the Google Apps for EDU installation here and took a pretty extensive presentation to campus about how to manage large amounts of email.

Inbox is a classic Google product: the distillation of a number of excellent ideas into a set of half-complete features built for a use case most people don't meet. We've seen this in the past in products like ChromeVox, Google's Chrome extension for accessibility. ChromeVox works great on ChromeOS devices, but completely ignores the point that most users of accessibility tech (AT) don't have or want ChromeOS devices and come to services with their AT in tow. ChromeVox also ignores decades of convent…


Evernote, for better or worse, is the best note-taking service for my needs. It works across all my devices/computers/modes. It's fairly easy to get stuff into it. Hell, they even have 2-Factor authentication. The Windows app is a little clunky and my girlfriend and I have never been able to get shared notes to work properly (conflicted note! three times in the same grocery trip!), but what service is perfect? At least they have nice socks.

Everything, in fact, is pretty good as long as you don't screw up. And screw up I did. I'm not very regular about making backups, but I do make them every month or so. Once you figure out how to create a backup, that is.

There's a helpful Export Note option (which turns into Export Notes when you select multiple notes HINT). The export process is essentially opening All Notes, selecting every note, and then choosing Export Notes. Or something like that; Evernote never tells you, you're left to figure it out on your own. The file…