WeSearch

You Can't Co-Design What You Don't Operate

·5 min read · 0 reactions · 0 comments · 18 views
#highered#aigovernance#humanfactorsengineering
You Can't Co-Design What You Don't Operate
TL;DR · WeSearch summary

An article discusses the challenges of faculty AI buy-in in higher education, framing it as a human factors engineering issue. It argues that effective co-design requires operators to have substantial experience with the tools before they can contribute to governance. The author emphasizes that governance should be developed after sustained use of AI tools in real educational contexts, rather than based on superficial familiarity.

Key facts
About this source

DEV.to (Top) files mainly under programming. We currently carry 4,877 of its stories.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1447774) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Michael Tuszynski Posted on May 20 • Originally published at mpt.solutions You Can't Co-Design What You Don't Operate #highered #aigovernance #humanfactorsengineering #facultydevelopment An article circulating this week argues that faculty AI buy-in in higher education is a human factors engineering problem. The framing is correct. The path the piece describes skips the only two steps that matter, and the reason it skips them is structural, not pedagogical.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)