Whose Work Is It Anyway? Writing an AI Statement Worth Reading
Last year, as the instructional designer for a software engineering course, I knew the instructor had leaned on AI throughout the course’s development. I suggested he be transparent about it with his students. After all, he was asking the same of them. What he wrote back went further than I expected. His syllabus statement opens not with rules for students but with an accounting of his own use. He names Claude the second author of his course, separates his own contribution from what emerged from that collaboration, and only then turns to what students may do. After getting his permission, I shared it with my team. Within minutes, colleagues were asking to keep it as an example. One had just … Whose Work Is It Anyway? Writing an AI Statement Worth Reading