{"id":4688,"date":"2026-09-25T15:09:53","date_gmt":"2026-09-25T15:09:53","guid":{"rendered":"https:\/\/www.furman.edu\/faculty-development-center\/?post_type=furman-update&p=4688"},"modified":"2026-09-29T15:08:52","modified_gmt":"2026-09-29T15:08:52","slug":"naming-the-problem-what-workslop-means-for-our-work-and-our-classrooms","status":"publish","type":"furman-update","link":"https:\/\/www.furman.edu\/faculty-development-center\/updates\/naming-the-problem-what-workslop-means-for-our-work-and-our-classrooms\/","title":{"rendered":"Naming the Problem: What \u201cWorkslop\u201d Means for Our Work and Our Classrooms"},"content":{"rendered":"

If you attended Session 2 of the BoodleBox trainings in September, you already heard this term. If you didn\u2019t, it\u2019s worth catching up on, because it names something a lot of us have felt but haven\u2019t had a word for. Missed it? Access all the <\/span>materials from Session 2<\/span><\/a>, including the recorded session, in Box.<\/span>\u00a0<\/span><\/p>\n

And speaking of BoodleBox training, if you missed Session 1, you can catch a repeat on Wednesday, Oct. 14, 2:30\u20133:30 p.m. Zoom link: <\/span>https:\/\/zoom.us\/j\/93600661426?pwd=gGMstBpBkap5gDoQZ0uKJWP1d9nPhZ.1<\/span><\/a>\u00a0<\/span><\/p>\n

Or, catch up by accessing the <\/span>resources from Session 1<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

\"\"What is workslop?<\/b>\u00a0<\/span><\/p>\n

In September 2025, researchers from <\/span>BetterUp Labs<\/span><\/a> and the Stanford Social Media Lab published a study in the <\/span>Harvard Business Review<\/span><\/i><\/a> introducing the term \u201cworkslop\u201d: AI-generated content that looks like real work but doesn\u2019t hold up when you dig into it. Workslop is polished slides with vague numbers, long summaries that miss the true main point, and reports that read smoothly but say very little of substance. The researchers found that 40% of US employees had received workslop in just the past month (based on latest results from an ongoing survey), and that fixing or redoing it costs almost two hours per instance.<\/span>\u00a0<\/span><\/p>\n

The core problem isn\u2019t that AI produced the content. It\u2019s that the human judgment that should have shaped and checked it never showed up. The work looks finished but isn\u2019t.<\/span>\u00a0<\/span><\/p>\n

Why this matters beyond the office<\/span><\/b>\u00a0<\/span><\/p>\n

Workslop is a workplace term, but anyone who has read a stack of essays lately will recognize the shape of it: writing that hits every formal marker of a finished essay (complete sentences, transitions, a confident tone) while the actual thinking underneath is thin or absent. That\u2019s the version we see in our courses.<\/span>\u00a0<\/span><\/p>\n

This is also where this month\u2019s Teaching Tip<\/a> connects<\/span>\u00a0Gary Guillet\u2019s piece on in-class assignments is built around a simple principle that we Writing Studies folks also preach: process matters more than a polished final product, and low-stakes grading protects space for students to think out loud without being penalized for it. Workslop is what happens when that process gets skipped entirely and only the finished-looking product remains. The two ideas are really pointing at the same thing from opposite directions.<\/span> Remember that when you use AI to create materials used in teaching, you should acknowledge that for your students. Using AI in Your Teaching<\/u><\/a>\u00a0provides options for acknowledging and\/or citing such AI use.<\/span><\/p>\n

A skill built to fight it<\/span><\/b>\u00a0<\/span><\/p>\n

At the September 22 <\/span>AI in Action session<\/span><\/a>, Chris Alvin walked faculty and staff through building <\/span>\u201cskills\u201d in BoodleBox<\/span><\/a>: reusable files that encode your own voice, standards, and habits so any bot applies them automatically, without you re-explaining every time. A skill works because it captures how you write and think, not just what task you want done. Check out this <\/span>list of possible uses for skills<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

That\u2019s a direct answer to workslop. Generic prompting produces generic output that looks fine on the surface but falls apart under scrutiny. A well-built skill pushes back against that by holding the AI to your actual standards instead of its defaults.<\/span>\u00a0<\/span><\/p>\n

A place to start on assignment design<\/span><\/b>\u00a0<\/span><\/p>\n

If you\u2019re rethinking an assignment with this in mind, the <\/span>Assignment-Level AI Use menu<\/span><\/a>, developed by Furman\u2019s AI Strategy Task Force (AISTF), is designed for exactly this kind of decision. It walks you through each component of an assignment, understanding the prompt, drafting, getting feedback, and more, and helps you mark where AI use is off-limits, where it\u2019s fine without disclosure, and where it has to be disclosed. The marked-up menu becomes your policy for that assignment.\u00a0<\/span>\u00a0<\/span><\/p>\n

Get involved<\/span><\/b>\u00a0<\/span><\/p>\n

The AI in Action series continues Tuesday, Oct. 20, 3:00\u20134:15 p.m., in Duke Library 043. Trent Stubbs leads a session on designing assignments where students use AI, building on work he developed this summer through the AI Faculty Institute. Bring a laptop. <\/span>Register here<\/span><\/a>.<\/span><\/p>\n

Claude 4.8 in BoodleBox assisted in drafting this article.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

If you attended Session 2 of the BoodleBox trainings in September, you already heard this term. If you didn\u2019t, it\u2019s worth catching up on, because it names something a lot […]<\/p>\n","protected":false},"featured_media":0,"template":"","update-categories":[],"class_list":["post-4688","furman-update","type-furman-update","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/updates\/4688","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/updates"}],"about":[{"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/types\/furman-update"}],"version-history":[{"count":5,"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/updates\/4688\/revisions"}],"predecessor-version":[{"id":4697,"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/updates\/4688\/revisions\/4697"}],"wp:attachment":[{"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/media?parent=4688"}],"wp:term":[{"taxonomy":"furman-update-category","embeddable":true,"href":"https:\/\/www.furman.edu\/faculty-development-center\/wp-json\/wp\/v2\/update-categories?post=4688"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}