Unit 24 · Capstone: Research, Cite, Defend

Compare two questions. First: When was the Chicago River reversed? Second: Why did Chicago decide that reversing a river was cheaper than cleaning its water, and who paid the cost downstream? The first has an answer you can look up in ten seconds: the main channel opened in 1900. The second could fill a semester. It asks about causes, choices and consequences, and thoughtful people could answer it differently. That difference is the whole test of a research question.

A workable research question has three traits. It is open: it cannot be answered yes or no, and it cannot be answered by one source. It is specific: it names a place, a time, a group or a text, so you know where to look. And it is arguable: a careful reader could reasonably reach a different conclusion, which means your paper will have to persuade rather than merely report. A question that is open but not specific, such as Why do cities change?, will drown you. A question that is specific but not arguable, such as How many people lived in Pilsen in 1920?, will bore you and your reader.

Most good questions start as bad ones and get better. Dani began with Why did the name stay? and found that the answer was too simple. She narrowed to one neighborhood, widened to two communities, and shifted from why to what it came to mean. Expect this. Write your first question down, try to answer it in one sentence, and notice what that sentence leaves out. The gap is your real question. Revise the question every time your reading shows you that you were asking the wrong thing.

One practical check before you commit: can you name two sources, right now, that would disagree about your question? If every source you can imagine would say the same thing, you have a report topic, not a research question. Disagreement is not a problem to avoid. It is the raw material of an argument. The paper you will write is your reasoned answer, set against the answers of others.

Here is the plan Dani wrote on a single page. Week 1: settle the question and list ten possible sources. Week 2: read and take notes on the four sources that seem strongest. Week 3: read six more, write a one-page summary of what the sources agree and disagree about. Week 4: outline. Weeks 5 and 6: draft the body. Week 7: draft the opening and ending, build the Works Cited list. Week 8: trade drafts with a reader, revise, proofread, submit. She taped it above her desk. That page is a research plan.

The plan works because it breaks one enormous task into pieces small enough to finish in a sitting. Nobody can write a research paper. People can find a source, read a chapter, write a paragraph. A plan also protects the part of the process that students most often skip: revision. When drafting slides into the last week, revision gets an hour at midnight. When the plan gives revision a full week, the paper gets a real second draft. Put the deadlines for the final stages on the calendar first, then work backward.

Your plan should list sub-questions as well as dates. Dani’s big question about what the name of Pilsen came to mean broke into smaller ones: Who first used the name, and when? When did Mexican families begin arriving, and why there? Did anyone try to rename the neighborhood? How do current residents talk about the name? Each sub-question points toward a different kind of source. The first wants an encyclopedia and old maps. The last wants interviews and recent journalism. Listing them shows you what to search for.

Plans change, and that is fine. If a source you counted on turns out to be unavailable, or a sub-question turns out to be unanswerable, adjust the plan and keep going. What you should not change is the total time. A plan that keeps getting extended is not a plan. Keep a short research log: the date, what you looked at, what you found, what you will try next. Ten minutes of logging saves hours of retracing your steps when you need to cite a source you half remember.

Two articles about the same neighborhood. The first is a blog post with no author’s name, no date and no list of where its facts came from. The second appeared in a university journal, names two historians as authors, was read and approved by other historians before it was printed, and ends with three pages of notes showing every source. The second is a scholarly source. The first might be right, but you have no way to check, and a research paper is built on things a reader can check.

The checking process is called peer review: before a journal prints an article, other experts in the field read it and can send it back for correction. Peer review does not guarantee truth, but it catches many errors and forces the writer to show evidence. Scholarly books from university presses go through a similar review. Newspapers of record, government reports and reference works such as the Encyclopedia of Chicago are not peer reviewed in the same way, but they have editors and standards, and they are appropriate for many questions. A personal website usually has neither.

Most scholarly articles do not turn up in an ordinary web search, or they turn up behind a paywall. They live in databases: searchable collections that libraries pay for. Google Scholar indexes many of them for free and often links to a readable copy. JSTOR holds decades of journal articles in history, literature and the social sciences. Public library systems, including the Chicago Public Library, give cardholders free access to research databases from home. Ask a librarian which databases fit your subject. Librarians are trained researchers, and helping you search is their job.

Searching a database is different from searching the web. Use fewer words and more precise ones. Dani’s first search, Pilsen history, returned thousands of results. Her better search, Pilsen Chicago Czech Mexican, returned dozens. Adding a date range narrowed it further. Read the abstract, the short summary at the top of an article, before you download anything. Then check the article’s own list of sources: an article’s bibliography is a map to a dozen more sources, already vetted by an expert.

The first paragraph of the journal article ran two hundred words, used the phrase spatial assimilation twice, and cited six other scholars in parentheses. Dani read it three times and understood nothing. This is normal. Scholarly writing is written for other scholars, who already know the vocabulary and the earlier arguments. You are joining a conversation partway through. The fix is not to read harder. It is to read differently.

Read in passes. On the first pass, do not read the article at all; read around it. Read the abstract, the headings, the first sentence of each paragraph and the conclusion. Ask one question: what is this writer claiming? Write the answer in one sentence of your own. This is skimming with a purpose. On the second pass, find the two or three sections that touch your sub-questions and read those slowly, with a pencil. Skip the rest for now. On the third pass, if the article matters, read the whole thing, now that you know where it is going.

When a sentence will not open, take it apart. Find the main verb, then the subject. Put the parentheses and the long noun phrases aside for a moment. Spatial assimilation, in a sentence about immigrants, turns out to mean moving from an ethnic neighborhood into a mixed one as families earn more. Look up terms in the article’s own definitions first, since scholars often define their key words in the opening pages. Keep a running glossary of the field’s vocabulary in your log, in your own plain words.

Take notes that separate what the source says from what you think about it. A simple method: one column for the writer’s claim and evidence, with page numbers, and a second column for your reaction, your questions and the connections to your other sources. Write the page number every single time. A paraphrase without a page number is a citation you will spend an hour reconstructing later. And write the note in your own words the first time, unless you are copying an exact quotation inside quotation marks. That habit will protect your integrity when you draft.

A weak research paper marches through its sources one at a time: first what Author A said, then what Author B said, then C. That is a book report stacked twelve high. A strong paper is organized by ideas, and under each idea it brings in whichever sources speak to it, letting them agree, disagree and correct one another. Turning a pile of sources into that kind of conversation is synthesis.

The tool for synthesis is a grid. Down the side, list your sub-questions or themes. Across the top, list your sources. In each box, write in a few words what that source says about that theme, with a page number. Dani’s grid had a row called reasons for moving to Pilsen. The university press book said highway and campus construction pushed families out of the Near West Side in the 1960s. The oral history said her interviewee followed a cousin who had found work nearby. The newspaper said cheap rent. The three do not contradict each other, but each alone would have been incomplete. The row, read across, became a paragraph.

Watch especially for the boxes where sources conflict. One of Dani’s sources described the change in Pilsen as a smooth handoff between communities; another described tension over church buildings and school language. Conflict between sources is not a problem to hide. It is a place where you must decide, using evidence, which account is better supported, or explain how both could be partly right. Your judgment in those places is the original contribution of your paper. Anyone can summarize twelve sources. Only you can weigh them.

When the grid is full, read it row by row and write one sentence per row stating what the sources together show. Those sentences are the first draft of your outline. Then read the column of your own reactions and ask what claim they add up to. Dani’s claim became this: the name Pilsen survived not because anyone chose it but because each community found reasons to keep it, and those reasons were different. Every row of the grid fed that sentence. That is what a thesis built by synthesis looks like.

A twelve-page paper is not a five-paragraph essay stretched thin. It is a building with rooms. Each room, usually a section with its own heading, takes up one sub-question and answers it. The reader should be able to enter any room and know what it is for. When Dani outlined, she wrote her thesis at the top of the page and then listed five sections: the Czech naming, the arrival of Mexican families, the years of overlap, the disputes, and what the name means now. Each section was a room, and each got a one-sentence job description.

Order the rooms by logic, not by the order you found things. Common orders: chronological, when your argument follows a change over time; problem and solution, when you show a difficulty and then the response; general to specific, when you establish a broad claim and then test it in cases; and weakest to strongest, when you want the reader’s last impression to be your best evidence. Dani used chronology for the first three sections because her thesis was about a change over time, then shifted to argument for the last two.

Hold the building together with signposting: sentences that tell the reader where they are and where they are going. The end of each section should look forward: Having shown that the name was already contested in the 1960s, the next section asks what the disputes were about. The start of each section should connect back: These disputes matter for the thesis because they show both communities claiming the name. This may feel clumsy while you write. Readers of long papers are grateful for it.

Two more rules for long arguments. First, address the strongest objection to your thesis somewhere in the body, not in a throwaway line at the end. A reader who has been thinking but what about the other view? for ten pages stops trusting you. Second, keep a running check: after each section, reread the thesis and ask whether that section moved the argument forward. If a section is interesting but does not serve the thesis, cut it or move it to a footnote. Length is not a virtue. Every page must earn its place.

Here is one book cited two ways. In MLA style: Arredondo, Gabriela F. Mexican Chicago: Race, Identity, and Nation, 1916-39. U of Illinois P, 2008. In APA style: Arredondo, G. F. (2008). Mexican Chicago: Race, identity, and nation, 1916-39. University of Illinois Press. Same book, same information, two arrangements. MLA, from the Modern Language Association, is used in English and other humanities courses. APA, from the American Psychological Association, is used in psychology, education, nursing and most social sciences. Your teacher or professor will tell you which one a course expects.

The difference shows most clearly in the in-text citation, the short note in parentheses inside your paragraph. MLA gives author and page: (Arredondo 42). APA gives author and year, plus a page number for a quotation: (Arredondo, 2008, p. 42). The reason is a difference in what each field cares about. Literature scholars want to find the exact page. Social scientists want to know how recent the study is. If you name the author in your sentence, leave the name out of the parentheses: Arredondo argues that the community was already forming by 1920 (42) in MLA, or Arredondo (2008) argues in APA.

The list at the end has a different name in each system. In MLA it is Works Cited; in APA it is References. Both are arranged alphabetically by the author’s last name, and both use a hanging indent, in which the first line of each entry sits at the margin and the following lines are indented. Titles of books and journals are italicized in both. MLA puts article titles in quotation marks and capitalizes the main words of a title; APA capitalizes only the first word of a title and any proper nouns, and uses no quotation marks around article titles.

A journal article, MLA: Last, First. "Title of Article." Journal Name, vol. 12, no. 3, 2020, pp. 45-67. APA: Last, F. (2020). Title of article. Journal Name, 12(3), 45-67. Do not memorize these patterns; look them up every time in a current handbook or a university writing center’s guide, since both systems are revised every few years. What you must memorize is the principle: every source in your text appears in the list, every source in the list appears in your text, and a reader with your list could find every source. Formatting is a courtesy to that reader.

Three ways to bring a source into your paper. The source, a sentence from a model article written for this lesson: "The parish did not switch languages so much as add one, holding Czech and Spanish Masses in the same building for nearly two decades." A quotation uses those exact words in quotation marks. A paraphrase restates the idea in your own words and structure: the church added Spanish services alongside Czech ones rather than replacing them, and the two ran side by side for almost twenty years. A summary boils a longer passage or a whole source down to its point: the parish served both communities for years. All three end with a citation.

Choose by asking what the reader needs. Quote when the wording itself is evidence: a striking phrase, a precise definition, a claim you are about to disagree with and want to state fairly. Paraphrase when the idea matters but the wording does not, which is most of the time; paraphrase keeps your paper in your own voice. Summarize when you need a source’s overall position in a sentence so you can move on. A paper that is mostly quotations reads like a scrapbook. Aim for far more paraphrase and summary than quotation, and never quote a sentence you could have said more clearly yourself.

A quotation should never stand alone as a sentence. Frame it. Before it, a signal phrase names the source and hints at how to take it: As the parish history notes, or One historian argues. After it, a sentence of your own says what the quotation shows and why it matters here. Introduce, quote, explain. Change the quoted words only with visible marks: square brackets for a word you add or alter, an ellipsis of three spaced periods for words you leave out. Never change a quotation so that it says something the source did not mean.

Long quotations get special handling. In MLA, prose longer than four lines of your paper becomes a block quotation: start on a new line, indent the whole passage half an inch, and drop the quotation marks. In APA, the block rule starts at forty words. Use blocks rarely; a long quotation shifts work from you to your reader. A real paraphrase, finally, changes both the words and the sentence structure. Swapping a few words while keeping the source’s order is patchwriting, and it counts as plagiarism even with a citation. If you cannot restate an idea without the source’s wording, you have not yet understood it. Reread until you can.

Dani stared at a blank first page for two evenings, trying to write an opening paragraph for a paper she had not written yet. On the third evening she skipped it. She opened her outline, chose the section she understood best, the arrival of Mexican families, and wrote that. Four pages came in two hours. The rule she discovered is one that experienced writers know: the introduction is written last, because you cannot introduce an argument you have not made yet.

Draft in stages, one section per sitting. Before each sitting, reread that section’s line in the outline and the matching row of your synthesis grid. Then write straight through without stopping to fix sentences, check citations or hunt for the perfect word. Mark gaps with a bracketed note, such as [find the date] or [cite Novak here], and keep moving. A draft’s job is to exist. Polishing sentences in a section you may later cut is wasted labor. Stopping to search for a citation breaks the thread of thought, and the thread is the hard part.

Write each body paragraph as a small argument. The first sentence states a claim that serves the section’s job. The middle brings in evidence from one or more sources, framed and cited. The last sentence or two explains what the evidence shows and connects it to the thesis. Readers of long papers skim first sentences; if your first sentences alone tell the story of the argument, the paper is well built. If your first sentences are all There is another source that says, the paragraphs are stacked, not argued.

When the body exists, write the ending, then the opening. The conclusion does not repeat the thesis; it says what the thesis now means, given everything shown, and what remains unanswered. The introduction then does three things in under a page: it opens with the specific scene or question that started you, it states what others have said, and it states your thesis. Dani’s final introduction began with the street sign on Eighteenth Street and the question her teacher asked. It was the last page she wrote and the first her reader saw.

Dani gave her draft to Marcus, who knew nothing about Pilsen. He read it with a pencil and put a question mark in the margin every time he lost the thread. There were eleven question marks. Three were in one paragraph where she had used the word displacement four times without ever saying what it meant. One was at the top of section four, which began with a quotation and never said why. None of the eleven were places Dani had noticed. She had read the draft six times. She could not see it, because she already knew what it was supposed to say.

That is why revision needs a reader. Revision is not proofreading; it is re-seeing the argument as a whole. A reader who does not know your subject is often better than one who does, because the expert fills the gaps in your logic without noticing. Give your reader three questions, not a general request for feedback: Where did you get lost? Where did you stop believing me? What do you think my thesis is? If the reader’s answer to the third question is not your thesis, the paper has a problem no proofreading will fix.

Revise from large to small. First the argument: does every section serve the thesis, and is the strongest objection answered? Then the structure: are sections in the best order, and is the signposting clear? Then the paragraphs: does each begin with a claim and end with an explanation? Only then the sentences, and last of all the punctuation and citations. Working in this order keeps you from polishing a paragraph on Tuesday and cutting it on Thursday. Expect to cut. Dani’s draft was fourteen pages; her final was eleven and said more.

One tool that catches what readers miss: the reverse outline. After the draft exists, write one line for each paragraph stating what it does. Read the list. Paragraphs that do two things need splitting. Two paragraphs that do the same thing need merging. A paragraph whose line you cannot write needs to go. The reverse outline shows you the building you actually built, as opposed to the one you planned, and the two are never the same.

Two sentences from two student drafts. First: Families followed cousins and coworkers into the neighborhood, building networks that made the move feel less like a leap. Second: Families followed cousins and coworkers into the neighborhood, building networks that made the move feel less like a leap (Novak 121). The words are identical, and they are Novak’s. The second sentence has a citation and is still plagiarism, because it presents Novak’s wording as the student’s own. Plagiarism is using someone’s words or ideas without making clear that they are theirs. A citation credits the idea. Only quotation marks credit the words.

Plagiarism is rarely a plan. It is usually a shortcut taken at midnight, or a note copied weeks ago without quotation marks and then mistaken for one’s own. The defenses are habits you have already learned in this chapter: notes in your own words, with copied phrases marked; page numbers on everything; and a citation for every idea that came from somewhere else, whether quoted, paraphrased or summarized. You do not need to cite common knowledge, meaning facts that any general reference would give and that no one could claim as theirs, such as the year Chicago was incorporated. If you are unsure whether something is common knowledge, cite it. No reader has ever complained about an extra citation.

Integrity also covers what you do with sources, not only how you mark them. Do not quote a sentence out of its context so that it seems to say the opposite. Do not cite a source you have not read because it appeared in someone else’s bibliography; read it, or cite the source where you found it. Do not invent a page number or a quotation you cannot locate. And do not reuse a paper you wrote for another class without permission; that is self-plagiarism, and most schools treat it as a violation. The principle behind all of these is the same: a reader must be able to trust that what you present is what you found.

Writing tools that generate text raise the same question in a new form. If a program produces sentences and you submit them as your own, the words are not yours, and the reader has been misled about who did the thinking. Schools and colleges set their own rules about such tools, and those rules vary and change. Ask what your course allows and follow it exactly. The deeper point holds whatever the rules say: the purpose of a research paper is to make you into someone who can find, weigh and defend evidence. A paper that skips the work skips the point.

A reader who loses the thread of your paper can flip back a page. A listener who loses the thread of your talk is gone, and there is no page to flip. That single difference changes everything about how a talk is built. A twelve-page paper might make five claims with twenty pieces of evidence. A twelve-minute talk on the same paper should make one claim with three pieces of evidence, chosen because they are the strongest and the easiest to picture. Turning a paper into a talk is not compression. It is selection.

Give the ear a map. Say early what you will argue and how many parts the argument has: I will show three things. First, that the name was contested from the start. Second, that both communities found reasons to keep it. Third, that those reasons were different. Then, as you reach each part, say so: that was the first point, and here is the second. This is signposting for the ear, and it is more necessary than it is on the page. Listeners who know where they are can relax and follow; listeners who do not spend their attention trying to guess.

Open with something specific: a scene, an object, a question, a number. Dani began with a street sign. A talk that opens with Today I am going to talk about my research paper has already lost the room. Close the way you opened, by returning to the specific thing and showing what it means now that the argument is made. The middle carries the evidence, one piece at a time, each introduced, shown and explained, exactly as a quotation is framed in a paper. Between pieces, pause. Silence that feels long to you feels like thinking time to the audience.

Repeat more than feels natural. In a paper, saying the thesis three times reads as padding. In a talk, saying it at the start, at the turn into each point and at the end is the minimum, because a listener who missed it once has no other way to get it. Use the same words each time so it lands as the same idea. The talk’s through-line, the one sentence a listener should be able to repeat afterward, must be short enough to remember and said often enough to stick.

Picture two slides. The first holds six bullet points, each a full sentence, in small type; the speaker turns toward it and reads. The second holds a photograph of a church sign in two languages, and the speaker, facing the audience, says what it shows. The first slide competes with the speaker: the audience reads faster than anyone can talk, finishes, and waits, bored. The second slide helps the speaker: it shows a thing that words alone would take a paragraph to describe. That is the test for every slide. Does it show something speech cannot?

A good slide carries one thing. One map, with the one route you are about to describe marked on it. One number, large, with a short label: 2 languages, 20 years. One quotation of a sentence or two, in type big enough to read from the back row, with the source under it. One chart with one line. If you want the audience to look at two things, make two slides. The one-idea rule keeps the audience’s eyes and the speaker’s voice on the same point at the same moment.

Evidence on a screen must be cited just as it is on a page. Put the source in small type on the slide: the author, the title, the year, and for a quotation the page. A photograph needs a credit; a chart needs to say where the numbers came from. Audiences trust speakers who cite, and challengers, as Dani learned, will ask exactly where a claim came from. A slide that already answers is a defense you built in advance. Put a reference slide at the end with every source, so you can show it if asked.

When you show a quotation, do not read it aloud. Let the audience read it while you stay silent for a few seconds, then say what it shows. Reading a slide aloud tells the audience that you do not trust them to read, and it wastes the talk’s scarcest resource, your voice. Face the room, not the screen; if you need to see the slide, use the laptop. A speaker’s notes belong on a card or the presenter view, never on the slide. Finally, plan for the screen to fail. A talk that cannot survive a dead projector was never a talk; it was a slideshow with a narrator.

Dani’s first rehearsal ran nineteen minutes for a twelve-minute slot. That is typical. Nearly every first draft of a talk runs long, because everything in the paper seems necessary and speaking takes longer than reading. The only way to know is to say it out loud, standing up, with a timer running, from the first word to the last. Reading the notes silently and estimating does not work; people speak at roughly 120 to 150 words a minute, slower when nervous and pausing for slides, and silent reading is far faster than that.

Cut until the rehearsal comes in under time with slack, about a minute in twelve. Cut whole points before you trim sentences; a talk with three complete points beats a talk with five rushed ones. Cut anything the audience can get from the paper if they want it. Then rehearse again. Dani’s runs went nineteen, sixteen, fourteen, thirteen, twelve and a half, then three runs near eleven and a half. By the last runs she was no longer reading her card; she was talking, and the card was a safety net. That is what rehearsal is for: not memorizing words, but knowing the path so well that you can look at the room while you walk it.

Plan for time to go wrong anyway. Mark one point in your notes as the cut point: if you reach it with less than a third of your time left, skip to the conclusion. A talk that runs over its time tells the audience that the speaker’s time matters more than theirs, and it usually means the ending, the most important minute, gets rushed or lost. Ending a minute early with a clear conclusion looks like control. Ending two minutes late with an apology looks like the opposite, even when the content was good.

The last rehearsal should be in front of a person, with the real slides, using the real clicker or keyboard, in the real room if you can get into it. Ask the listener to raise a hand every time they lose the thread or cannot see something on a slide. Record yourself once, and watch it, even though you will hate it. You will see the filler words, the hands in the pockets, the turn toward the screen. Fix two things, not ten. Then stop rehearsing the night before; a talk that has been run nine times does not improve with a tenth at midnight.

Jordan’s question about money did not surprise Dani, because she had written it down two days earlier. Before the talk she had made a list titled What will they ask? It had nine questions on it. Three came from the objection section of her own paper. Two came from evidence she had cut for time. Two came from what a skeptic would say about her sources: an oral history is one person’s memory; a newspaper feature is not a study. One was the question she most feared, and one was the question she hoped someone would ask. Jordan’s was number two.

Predicting questions is not a trick; it is the same skill as addressing the objection in a paper. Reread your paper as your harshest fair reader. Where is the evidence thinnest? Which source would an expert doubt? What did you claim that goes a step past what the evidence shows? What obvious alternative explanation did you set aside, and why? Where did you cut something for time that a listener will notice is missing? Each answer is a likely question. Write it down as the listener would say it, and write a three-sentence answer beneath it. This is your question bank.

Some questions you can answer in advance by building the answer into the talk. If you know your oral history source is vulnerable, say so yourself, briefly: this is one woman’s memory, and I use it for what she felt, not for dates. A speaker who names the weakness first has taken it away from the questioner. Others are better left for the questions, because answering them well in front of the room shows the depth of your work; keep a backup slide for those, ready to show after the reference slide.

Prepare for the question you cannot answer, too, because it will come. The honest response has three parts: say that you do not know, say what you would need to find out, and, if you can, say how it would or would not affect your thesis. That is not a failure. It is what expertise sounds like. The presenter who bluffs an answer and is caught loses everything said before; the presenter who says I did not look at that, and here is what it would take, keeps the room’s trust and usually gets a nod.

Two answers to Jordan’s question. First: Yes, you are right, I probably should have included that. Second: You are right that developers used the name, and my sixth source shows it happening in the 1990s. But that does not explain the earlier decades, when no one was profiting and the name still held. So I think money is part of the later story, not the whole story. The first answer folds: it gives up a thesis that a semester of evidence supports because a question sounded confident. The second concedes exactly what is true and keeps exactly what the evidence keeps. That is the shape of a good answer.

Start by restating the question in your own words, briefly. This does three things: it shows the room you listened, it gives you five seconds to think, and it lets the questioner correct you if you misheard. Then concede what deserves conceding, specifically. A vague you make a good point sounds like a dodge; a specific you are right that the 1990s look different sounds like a scholar. Then say what you hold and why, pointing to evidence: my sixth source, the dates in the map, the parish records. End by saying where the line is: part, not whole; later, not earlier; likely, not certain.

Two failures sit on either side of that shape. Folding is one: agreeing with everything, apologizing, abandoning the claim. It feels polite and it is actually a kind of disrespect, because it tells the questioner that the argument was never serious. Stonewalling is the other: refusing to concede anything, repeating the thesis louder, treating the question as an attack. It feels strong and reads as fragile. The room can tell the difference between a speaker defending evidence and a speaker defending pride.

Tone carries as much as content. Thank the questioner once, sincerely, not after every question. Keep your voice at talk volume, not argument volume. Look at the questioner while restating, then at the whole room while answering, because the answer is for everyone. If the question is hostile, answer the content and ignore the tone; the room will notice who stayed calm. And if a question changes your mind, say so on the spot. I had not thought of it that way, and I think that weakens my third point, is a sentence that costs nothing and earns a great deal.

After the talks, the class sat in a circle to discuss a question that cut across all of them: when a neighborhood changes, who gets to say what its history is? Two kinds of discussion could follow. In the first, each student says a prepared opinion, the next student says an unrelated one, and the teacher moves it along. In the second, the third speaker begins with Jordan said profit and Dani said community, and I think the parish records show a third thing, and by the end of the hour the group holds a view none of them walked in with. The second is what collaborative discussion means.

The core move is building: connecting what you say to what was just said. Agree and extend: Dani’s point about the church applies to the schools too, because. Disagree and explain: I read that source differently, since. Ask for more: Jordan, when you say profit, do you mean rents or the name on new buildings? Each of these names a previous speaker and shows what you took from them. A comment that could have been made before the discussion started, with no reference to anything anyone said, is not discussion; it is a speech.

Disagreement is the point, not the problem. A group that agrees quickly has usually just stopped thinking. But disagree with precision. Say which claim you doubt, which evidence makes you doubt it, and what would change your mind. I disagree with everything Jordan said is useless; I think the profit motive is real but starts too late to explain the 1970s is something the group can test. Keep the disagreement on the claim, never on the person. In a good discussion nobody wins, because the goal is not victory but a better answer.

Someone has to tend the discussion, and it should not always be the teacher. Notice who has not spoken and make room: Marcus, you wrote about the murals; does this match what you found? Notice when the group has drifted and bring it back to the question. Notice when two people are saying the same thing in different words and say so. Near the end, someone should try to state what the group now thinks, including where it still splits. The ability to do that, to summarize a live argument fairly, is rare and valued everywhere, from seminar rooms to job sites.

Marcus watched Dani’s talk with a page split into three columns: claim, evidence, reasoning. Under claim he wrote her thesis as soon as she said it. Under evidence he listed the map, the parish quotation and the interview as each appeared. Under reasoning he wrote the sentence that connected each piece to the claim, or a question mark when he could not find one. At the end he had a picture of the argument, not just a memory of the talk. That is evaluative listening: listening as a judge of the argument, not as a fan or a critic of the performer.

The three columns catch the three ways a talk can fail. A claim can be missing or so vague that nothing could count against it. Evidence can be missing, thin, or the wrong kind for the claim: one interview offered as proof of what a whole community thought. Reasoning, the link from evidence to claim, is the one listeners most often skip and speakers most often leave out; a speaker shows a striking image and moves on, and the audience supplies a link that was never argued. Write the question mark. Ask about it.

Separate the argument from the delivery. A confident speaker with a weak argument is more dangerous to your judgment than a nervous speaker with a strong one, because confidence feels like evidence and is not. Notice when you are being persuaded by the voice, the slides or the story rather than the reasoning, and check the columns. Notice, too, the opposite bias: a speaker who stumbles may have the best evidence in the room. Judge the page, not the performance. You will be asked to do exactly this for the rest of your life, by advertisements, by candidates, by people who want your money.

Listening well also means noticing what is not said. What alternative explanation did the speaker not mention? Which obvious source was absent? Where did the speaker’s confidence rise just as the evidence thinned? Those are your questions, and a question built from careful listening is a gift to the speaker: it points at the place the work can improve. Dani’s best question came from Jordan, who had listened for the one thing her talk left out. That is what a colleague does.

Three comments on Dani’s talk. First: Great job, really interesting! Second: It was kind of confusing in the middle. Third: Your map slide worked; I could see the move without you explaining it. But when you showed the parish quotation, you went straight to the next point, and I did not know what you wanted me to take from it. One sentence after the quote would fix that. Only the third is feedback. The first is applause. The second is a feeling with no location. The third names a place, describes what happened for the listener, and suggests a change small enough to make.

Specific feedback has an address. Say where: the second slide, the transition into your last point, the answer to the first question. Say what you experienced there as a listener, not what the speaker did wrong: I lost the thread, I could not read the type, I was not sure whether that was your view or the source’s. Reporting your own experience is both kinder and more accurate, because it is the one thing you know for certain. Then, if you can, suggest a fix, and make it the smallest fix that would work.

Choose. A speaker who receives twelve notes will fix none of them. Pick the one or two changes that would most improve the next version, and lead with those. Prioritizing is where the skill is: a wrong date on slide four matters less than a missing link between the evidence and the thesis, and the missing link matters less than a thesis nobody could state afterward. Say what to keep, too, and say why. Praise with a reason is information: the map slide worked because it showed the route without words. Praise without a reason is noise.

Receiving feedback is its own skill. Write it down without arguing; you can decide later what to use. Ask for the address if the note has none: where in the talk did it get confusing? Thank the person, especially for the hard note, because a hard note is a sign that someone took the work seriously. Then sort: which notes name the same problem, which ones would change the argument, and which are about taste. Fix the problems that several people named first. A single listener’s confusion might be that listener; three listeners’ confusion is the talk.

Dani opened a paragraph she had written in ninth grade, an argument about school uniforms. It had a thesis, sort of: Uniforms are bad for many reasons. It had evidence, sort of: a friend’s opinion and a website with no author. It had reasoning nowhere. She laughed, and then she did the useful thing: she wrote down exactly what her twelfth-grade paper did that the ninth-grade paragraph did not. A thesis someone could disagree with. Twelve sources she could defend. A paragraph where she weighed two accounts that conflicted. An answer to the strongest objection. That list is reflection, and it is worth more than the grade.

Reflection is not the same as feeling proud or feeling bad. It is a comparison with evidence, done to yourself. Put an early piece of work next to a late one and list the differences as specifically as you would in a research paper. Then ask how each change happened: which assignment, which piece of feedback, which habit. Dani traced her handling of conflicting sources to a synthesis grid a teacher made her fill out, which she had resented at the time. Knowing where a skill came from tells you how to get the next one.

Be honest about what has not changed. Dani still wrote introductions last and dreaded them, still overused the word significant, still ran long. A reflection that lists only strengths is a speech, not a reflection. The most useful sentence in one is often I still cannot, followed by the specific thing, followed by what I will try next. That sentence turns a weakness into a plan. It is also, not by accident, the same move as the honest answer to a question you cannot answer: here is what I do not know, and here is what it would take.

Keep the evidence. A folder with one piece of writing from each year, and a page of notes on what changed between them, is a portfolio, and it will be more useful to you than any transcript. It shows you, in your own words, that you can learn hard things, on the days when that is hard to believe. It also gives you something concrete to say when a college application or an interviewer asks how you have grown, a question nearly everyone answers with vague words and almost no one answers with a specific before and after.

A first-year college assignment: read three articles that disagree, and write eight pages saying which is right and why. A first job: the manager asks you to find out why a process is failing, and to present what you found to people who will ask questions. A community meeting: someone claims a number, and you want to know where it came from. None of these says research paper. All of them are one. The habits you built in this unit are not school habits. They are the habits of anyone who has to find out what is true and say so in front of others.

Carry the question first. In college, the students who struggle most are often those who wait to be told what to think; the students who thrive have learned to ask an open, specific, arguable question and go looking. At work, the person who asks what would we need to know to decide this is the person who gets asked into the room where decisions are made. Carry the source habit: who wrote this, when, with what evidence, and who checked it. It will protect you from more than bad grades. Carry attribution: giving credit for ideas and words, which in a workplace is the difference between a colleague people trust and one they do not.

Carry the reader. Nothing you write will be as clear to others as it is to you, and the only cure is a reader before the deadline. Carry the calendar: long work is done in stages, and revision needs its own week. And carry the answer to the hard question: restate, concede what is true, hold what the evidence holds, mark the line. You will use that shape in seminars, in job interviews, in meetings, in arguments that matter to you. It is the sound of someone who has done the work and is not afraid of being asked about it.

Finally, carry the reading. You have spent years learning to read texts that resist: a sentence that will not open, a poem that means two things, a scholarly article written for someone else. That skill is not finished, and it never will be, but it is yours. Every hard document in your future, a lease, a contract, a study, a ballot measure, a policy at work, is a text that fights back, and you know how to read in passes, take it apart, look things up and come back. This unit ends here. The habit does not.