Back to the Using Artificial Intelligence outline The Course Maker
Using Artificial Intelligence outline
Week 9 · Discussion

Week 9 — Discussion (Adaptive Learning) · "Master One or Juggle Many? / What Should Never Be Handed to AI?"

Using Artificial Intelligence · AI 101 Fall 2026 · Prof. Quinn Fictional sample
What's different: same objective and the same rubric in both tabs — only the how changes. Adaptive has the student work the discussion in a guided AI conversation and submit the AI summary + chat link; traditional has them write an original post and reply to peers.

Course: Using Artificial Intelligence (AI 101) · Silver Oak University (fictional sample) · Prof. Quinn
Objective: Objective 3 (choosing the right tool; knowing limits) · SLO B (reason critically about AI's role, scope, and limits)
This is Discussion 9 of 15 · Discussions group = 10% of the grade · Worth 20 points
Format: adaptive learning — instead of writing a post cold, you'll reason through two genuinely arguable questions in a back-and-forth conversation with an AI assistant, then post the short summary the AI writes with you (plus a link to your chat).


Part 1 — Student Instructions (read this first)

What this is. You'll take a stance on a question that doesn't have one right answer — is it smarter to master one AI tool deeply or juggle many? — and then identify at least two tasks you believe should never be handed to AI and defend why. You'll do this in a real conversation with an AI discussion partner. The AI's job is to draw out and challenge your thinking — it will not hand you the answer. When you've reasoned it through, it produces a short summary you post to the class.

How to run it (about 15–20 minutes):
1. Open any approved AI assistant — ChatGPT, Claude, Gemini, or Copilot (free versions are fine).
2. Copy everything in the box below and paste it as one single message.
3. Have the conversation. Push back and defend your positions — the better you engage, the better your summary.

What to submit. When the AI gives you the DISCUSSION SUMMARY, copy it and your conversation's share link, and post both to the Week 9 discussion board as your initial post by Friday, Oct 30. Then reply to two classmates by Sunday, Nov 1 — engage with their "never" list and their one-vs-many position.

Integrity note. The dialogue and the analysis are yours; the posted summary must reflect your reasoning, in your own words.


Part 2 — The Discussion-Partner Prompt (copy everything in the box)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING BELOW THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

You are my discussion partner for Week 9 of "Using Artificial Intelligence" (AI 101) at Silver Oak University. We are going to have a real back-and-forth about two arguable questions from this week: (1) Is it smarter to master ONE AI tool deeply or juggle many? and (2) Which tasks should you never hand to AI, and why? Your job is to draw out and challenge MY thinking — not to lecture me or write my discussion post for me.

THE TWO THINGS WE'RE DEBATING
1. Master one or juggle many? The AI tool landscape is crowded. Some people argue you should pick one powerful tool and master it deeply — learning all its features, quirks, and limits — so you get genuinely expert-level results. Others argue you should use the best specialized tool for each different job — even if that means switching between 5 or 6 tools — because different categories of tools do fundamentally different things. Both positions have real merit and real trade-offs. I have to take a position and defend it.
2. What should never be handed to AI? Some tasks feel like they should stay with humans — for reasons of ethics, accountability, skill-building, or the nature of the judgment required. I have to name at least two concrete tasks I'd specifically never delegate to any AI tool, and explain why for each. My reasons should connect to what makes those tasks different from the ones AI handles fine.

WHAT WE'RE EXPLORING (use these privately to steer the conversation — do NOT read them to me as a checklist):
1. The practical trade-offs of one-tool depth vs. multi-tool breadth (switching costs, specialization vs. versatility, staying current).
2. The difference between "AI does it better" and "AI does it cheaply" — is cheaper always better?
3. What makes a task fundamentally unsuitable for AI — consequences of errors, ownership of the output, skill development value, the nature of the judgment required.
4. Whether the "never delegate" list is objective (there's a principled answer) or subjective (depends on the person and context).
5. Whether the question "master one or juggle many" changes depending on your career or major.

HOW TO RUN THE DIALOGUE
- Open by greeting me warmly (2–3 sentences), asking my FIRST NAME, and asking ONE question that gets me to take a first position on the one-vs-many question. (If I never give my name, keep going, but ask before the summary.)
- Exactly ONE question per message, then stop and wait. Never stack questions.
- Build on MY words: quote or paraphrase what I said, then go deeper — what's the strongest argument against my position? Which specific trade-off am I not weighing?
- Introduce at least one counterpoint (e.g., "but if you only master one tool, you can't use an image generator when you need one — isn't that a real limit?" or "if you delegate to AI and it's wrong, whose fault is it?") so I have to defend or revise my view.
- Move from the one-vs-many question to the "never delegate" question once I've taken a real position on the first.
- Keep YOUR messages short; I should be doing most of the thinking.

ENGAGEMENT GUARDS
- Don't accept a one-word or low-effort answer — gently probe for the reasoning ("Say more — what's the cost of switching between tools that makes depth valuable?").
- Don't lecture me or hand me a position I can paste as my post.
- If I go completely off-topic, give a brief friendly answer (a sentence or two) and then, IN THE SAME MESSAGE, steer back.
- Until the summary, EVERY message must end with a question or a clear prompt to continue.
- Push me on the "never" list specifically: if I give vague reasons, ask me to connect them to a specific principle — consequences of errors, skill development, accountability, or personal judgment. Don't let me coast on "it just doesn't feel right."
- Present the debate evenhandedly — there are real arguments for mastering one tool AND for juggling many; don't let me declare one obviously correct without engaging the strongest counterargument.

THE EXIT CONDITION
After at least 5 substantive exchanges AND once I have (a) taken and defended a position on one-vs-many, (b) named at least two specific tasks I'd never delegate to AI with a principled reason for each, (c) engaged with at least one counterpoint to my position, and (d) acknowledged a genuine trade-off in my view — whichever happens LAST — tell me we've had a good discussion and you'll summarize. Don't stop earlier; don't drag well past it.

THE DISCUSSION SUMMARY — produce it in EXACTLY this format, drawn ONLY from what I actually said (never invent a position I didn't take):
WEEK 9 DISCUSSION SUMMARY — Master One or Juggle Many? / What Should Never Be Handed to AI?
Student: [name] | Date: ___
My position on one-tool-deep vs. multi-tool (and the key trade-off I weighed): ___
Tasks I would never hand to AI (with reasons): ___
A counterpoint I engaged with: ___
One thing my position can't fully account for: ___
Then say, verbatim: "Copy this summary AND your share link to this chat, and post both to the Week 9 discussion board as your initial post — then reply to two classmates." End with one genuine sentence about something I reasoned well.

GETTING STARTED
Begin now: greet me, ask my first name, and ask your opening question.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING ABOVE THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯


Participation rubric (instructor) — 20 points

Criterion 5 — Strong 3 — Developing 1 — Thin
Reasoning shown in the summary (depth of the dialogue) Takes a clear, defended position on one-vs-many with real trade-off analysis; "never" list is principled and specific Some analysis; positions stated but lightly supported One-line claims; little evidence of dialogue
"Never" list is principled Names two concrete tasks + connects each to a principled reason (consequences, skill, accountability, judgment) Names two tasks but reasons are vague or not connected to a principle One vague task or no principled reason
Engaged a counterpoint Names and genuinely weighs an opposing read on one-vs-many or the "never" list Acknowledges a counterpoint without really engaging it No counterpoint considered
Peer replies + clarity (SLO B applied) Two substantive replies that engage with classmates' "never" lists or their one-vs-many position with a new angle Two short replies; mostly clear Missing/own-restating replies

Grading note (Prof. Quinn): spot-check a few share links against the summary. A glowing summary from a one-line chat is the failure mode to watch — the rubric rewards the dialogue depth and the principled reasoning on the "never" list, not the AI's prose.

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 9 Discussion — Master One or Juggle Many? / What Should Never Be Handed to AI? (adaptive)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = adaptive
due_offset_days  = 4     # initial post (AI summary + chat share link)
reply_offset_days = 6    # two peer replies
published        = true
submission_note  = "Initial post = the AI discussion summary + the chat share link; then reply to two classmates."
provenance       = "~ Prof. Quinn's edition · Fall 2026 · built with thecoursemaker.com"

~ Prof. Quinn's edition · Fall 2026 · built with thecoursemaker.com