the invariant ed-tech sequence

Some company creates a new “killer app” for Academic Task X that is supposed to make the machinery of academic life run more smoothly but is basically a database with a hideous UI;
Some administrator or committee at your university decides that this is just the thing we need to pay $$$$ for because it’s The Future of the University;
Use of the app is imposed on faculty who despise it, because it is manifestly inferior to what they were doing before but far more cumbersome to use;
Administrators, faced with serious faculty pushback, back off on their demands for making the app central to the whole academic enterprise, but only to some degree, because they paid $$$$ for this piece-of-crap-code and feel that they can’t back out now;
The result: the app is forcibly implemented, but only partially, with the result that faculty are still unhappy with having to use the crappy app but have to use it *less*, which means that the task that was performed adequately with previous technologies/means is now performed less effectively and completely. Everyone loses except the people who made the sorry-ass app.
1 like ·   •  0 comments  •  flag
Share on Twitter
Published on January 30, 2018 16:21
No comments have been added yet.


Alan Jacobs's Blog

Alan Jacobs
Alan Jacobs isn't a Goodreads Author (yet), but they do have a blog, so here are some recent posts imported from their feed.
Follow Alan Jacobs's blog with rss.