Week 13 — Discussion (Adaptive Learning) · "Can Concision Go Too Far?"

Course: English Composition (ENGL 1A) · Silver Oak University (fictional sample) · Prof. Lindgren
Objective: Objective 7 (revision & style) · SLO A (compose clear, well-organized prose)
This is Discussion 13 of 15 · Discussions group = 10% of the grade · Worth 20 points
Format: adaptive learning — instead of writing a post cold, you'll think it through in a real-time dialogue with your own AI, 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. This week's craft lesson says cut the deadwood — concision is strength. But is that always true? Can you cut too much, until you lose nuance, voice, or meaning? You'll take a position on that in a back-and-forth with an AI chatbot. The AI's job is to draw out and challenge your thinking — it will not write your opinion for you. When you've thought 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 chatbot — Gemini, Claude, or ChatGPT (free versions are fine).
2. Copy everything in the box below and paste it as one single message.
3. Have the conversation. Answer honestly and push back — 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 13 discussion board as your initial post by Wednesday, Nov 25. Then reply to two classmates by Sunday, Nov 29 — engage with their position and their example.

Integrity note. The dialogue and the analysis are yours; the posted summary must reflect your reasoning, in your own words. (This is an adaptive-learning activity — you complete it with an approved chatbot, per the course AI policy.)

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

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

You are my discussion partner for Week 13 of English Composition (ENGL 1A) at Silver Oak University. We are going to have a real back-and-forth about a question in writing style: does cutting words always improve writing, or can concision go too far? Your job is to draw out and challenge MY thinking through conversation — not to lecture me, and never to write my discussion post for me.

THE DRIVING QUESTION
This week's lesson is that concision is strength — cut the deadwood (wordiness, redundancy, empty intensifiers) and writing gets stronger. The debate: is that always true? Help me take and defend a position on whether you can cut TOO much — losing nuance, rhythm, voice, emphasis, or meaning — and where the line is between tightening and stripping.

WHAT WE'RE EXPLORING (use these privately to steer the conversation — do NOT read them to me as a checklist):
1. My starting position: does cutting words (almost) always improve a piece, or is there a real point of diminishing returns?
2. A concrete example — ideally from MY own writing or reading: a sentence or passage that got better when cut, AND (the harder one) a case where cutting would lose something worth keeping (a qualifier that mattered, a deliberate rhythm, a bit of voice or warmth, a needed example).
3. The distinction between deadwood (filler that carries no meaning — safe to cut) and substance/voice (words doing real work — risky to cut). Push me to name how I'd tell them apart.
4. Audience and genre: does the "right" amount of concision change with the situation — a text vs. a legal contract vs. a personal essay vs. a tweet? (A wedding toast and a lab report don't want the same density.)
5. My reasoned take, stated plainly enough for a friend who's never taken this class to follow — including where I think the line is.

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 state my starting position on whether concision can go too far. (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 — ask me to test my rule against a hard case (a sentence where cutting would lose something), or to define how I tell deadwood from substance.
- Introduce at least one counterpoint to whatever I argue — e.g., if I say "shorter is always better," show me a stripped sentence that lost its nuance or warmth; if I say "concision is overrated," show me a bloated passage that a 25% cut clearly improves — so I have to defend or refine my view.
- Keep YOUR messages short; I should be doing most of the thinking and talking.

ENGAGEMENT GUARDS
- Don't accept a one-word or low-effort answer and move on — gently probe for the reasoning first ("Say more — what would be lost if you cut that?").
- Don't lecture, and don't hand me my opinion or sentences I can paste as my post. If I ask you to "just write it," redirect with a question that helps me write it myself.
- If I go completely off-topic, give a brief friendly answer (a sentence or two) and then, IN THE SAME MESSAGE, steer us back to the concision question.
- Until the summary, EVERY message must end with a question or a clear prompt to continue.
- Don't just agree with me — if I assert a rule ("always cut," or "never cut voice") without testing it, ask me to try it against a counter-case.

THE EXIT CONDITION
After at least 5 substantive exchanges AND once I have (a) stated a clear position on whether concision can go too far, (b) given at least one concrete example where cutting helped and one where cutting would lose something, (c) drawn some line between deadwood and substance/voice, and (d) engaged with at least one counterpoint — 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 13 DISCUSSION SUMMARY — Can Concision Go Too Far?
Student: [name] | Date: ___
My position (does cutting always improve writing?): ___
A case where cutting HELPED: ___
A case where cutting would LOSE something worth keeping: ___
How I tell deadwood from substance/voice: ___
A counterpoint I weighed: ___
Then say, verbatim: "Copy this summary AND your share link to this chat, and post both to the Week 13 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

Grading note (Prof. Lindgren): the posted artifact is the AI-written summary + the chat share link; spot-check a few links against the summary. A glowing summary from a one-line chat is the failure mode to watch — the rubric rewards the dialogue, not the AI's prose. There is no "correct" answer here; reward the reasoning and the trade-off thinking.

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 13 Discussion — Can Concision Go Too Far? (adaptive)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = adaptive
due_offset_days  = 2     # initial post (AI summary + chat share link) — Wed Nov 25, before the holiday
reply_offset_days = 6    # two peer replies — Sun Nov 29
published        = true
submission_note  = "Initial post = the AI discussion summary + the chat share link; then reply to two classmates."
provenance       = "~ Prof. Lindgren's edition · Fall 2026 · built with thecoursemaker.com"

Traditional variant — for comparison. This sample course is configured adaptive learning, so its actual Week-13 discussion is the BYOAI-dialogue version in G-discussion-week-13.md. This file shows the same Week-13 topic built the traditional way — an instructor-posted prompt where students write their own post and reply to peers — so you can see both formats side by side. (Choosing discussion_type = traditional at course setup generates this style instead.)

Course: English Composition (ENGL 1A) · Silver Oak University (fictional sample) · Prof. Lindgren
Objective: Objective 7 (revision & style) · SLO A (compose clear, well-organized prose)
Discussion 13 of 15 · Discussions group = 10% of the grade · Worth 20 points

The Discussion

This week's craft lesson is blunt: concision is strength. Cut the deadwood — wordiness, redundancy, empty intensifiers — and your writing gets stronger. But here's the arguable question: is that always true? Can concision go too far — can you cut so much that you lose nuance, rhythm, voice, emphasis, or even meaning? Where is the line between tightening a sentence and stripping it?

Your initial post (by Wednesday, Nov 25 — about 150–200 words). Take a clear position and defend it with examples:

• State your position. Does cutting words (almost) always improve a piece of writing, or is there a real point where cutting starts to cost something? Be specific about where you land.
• Show one case where cutting HELPED — a wordy sentence (yours, or one you make up in the instructor's style) that got stronger when you trimmed it. Give the before and after, and name what you cut (filler? redundancy? an empty intensifier?).
• Show one case where cutting would LOSE something worth keeping — a qualifier that mattered, a deliberate rhythm, a bit of voice or warmth, a needed example. Explain what would be lost and why it's worth the words.
• Draw the line. How do you tell deadwood (safe to cut) from substance/voice (risky to cut)? Does the answer change with the audience and genre (a text vs. a contract vs. a personal essay)?

Replies (by Sunday, Nov 29). Reply to at least two classmates. Don't just agree — test their "rule" against a case where it would break (a place their cut would lose something, or a bloated passage their position would leave untouched), or offer a genre where the right density is different. One or two solid sentences each.

What a strong post looks like: "My position: cutting almost always helps — until it touches voice. Example where it helped: 'Due to the fact that I was very tired, I made the decision to go home' → 'Because I was tired, I went home.' Pure deadwood gone, meaning intact. But here's where I'd stop: in a personal essay, 'I was tired, bone-tired, the kind of tired that makes the stairs look like a mountain' is 'wordy' by the OWL's rules — and I'd keep every word, because the rhythm and the image ARE the meaning. My line: cut filler that carries no information; keep words that carry voice, emphasis, or feeling. A lab report and a personal essay don't want the same density."

Why this matters: revising well isn't applying "cut words" like a rule — it's judgment. You learn to cut hard where there's deadwood and to protect the words that are actually doing work. That judgment is the difference between a reviser and a word-counter.

Integrity & AI note. Write your post in your own words — that's the point of the exercise. You may use an approved chatbot (Gemini, Claude, or ChatGPT) to brainstorm or check a definition, but the post you submit must be your own thinking; if AI helped, add a one-line note saying which tool and how. (Note: this is the traditional format. In this course's actual adaptive discussion, thinking the question through with the chatbot is the activity — see G-discussion-week-13.md.)

Participation rubric — 20 points

Grading note (Prof. Lindgren): you read and grade each student's posted writing + their two replies against this rubric — the traditional flow. There is no "correct" side; reward the position-taking, the before/after examples, and the trade-off reasoning. (The adaptive version instead has students submit an AI-dialogue summary + chat link.)

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 13 Discussion — Can Concision Go Too Far? (traditional)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = traditional
due_offset_days  = 2     # initial post — Wed Nov 25, before the holiday
reply_offset_days = 6    # two peer replies — Sun Nov 29
published        = true
submission_note  = "Students write an original initial post and reply to two classmates in the Canvas discussion."
provenance       = "~ Prof. Lindgren's edition · Fall 2026 · built with thecoursemaker.com"