If you want to make progress in a linguistics class, it is not enough to read the book. At some point you have to get feedback on a particular analysis. It is easy to sound right while still missing something important. Students often think of feedback as a “right” or “wrong” response, but that does not tell you much. The best feedback will show you where your account is too general, too hasty, or too fuzzy. If you want useful feedback, then you have to show your account first. In linguistics, feedback is not about giving answers. It is about making analysis clearer. Feedback on your analysis is always more helpful than feedback on your answers.
This means that the way you ask for feedback matters. Weak questions produce weak answers. “Do you understand morphology?” is too big a question. A better question would be, “I think these two words are related, but I do not know whether this suffix indicates tense or case.” That question is more focused. It is easier to give feedback on. The same principle holds for syntax questions. Instead of asking whether your tree is right, ask about a particular part of the tree. For example, you might ask, “I have two constituents that seem to be modifying this VP. Is there a difference between how they attach?” You might ask, “I have moved this phrase to the front of the sentence. Why is the result awkward?” That kind of question invites stronger feedback. The smaller the question, the easier it is to see what is missing.
Students sometimes undermine their feedback by hiding their account in technical vocabulary. A student who is struggling with an analysis will sometimes simply pile as many labels as they can onto the data and hope the labels will do the work. The result can be impressive, but it is very difficult to get useful feedback, because no one can tell which labels are actually doing the work and which are just hopeful guesses. A better strategy is to describe the phenomenon, explain its significance, and then add the technical term if it fits. For example, you might say that, “When this word comes at the end of a sentence, its final consonant seems to disappear. That is why I am guessing it is a case of final devoicing.” You might say, “When I move this constituent, the sentence seems awkward. That is why I think it is a topicalization.” That kind of presentation makes feedback easier. Feedback goes better when it is on the analysis rather than on the labels.
It is also better to include two examples rather than one. If you are doing a phonetics problem, point to two sounds that sound very similar and ask which feature is which. If you are doing a morphology problem, include two forms of the same word and ask what function the shared morpheme is playing. If you are doing a syntax problem, give one sentence that seems to work and another that does not, and ask why the analysis fails. Including a second example puts pressure on the explanation. It shows whether the account is really doing any work, and that makes the feedback stronger.
It does not take much time to get to that point. A fifteen-minute exercise can help. The first five minutes are for writing up one example as best you can, without worrying too much about getting it right. The second five minutes are for finding a second example that is as similar as possible and comparing the two. Underline the exact point where you get lost. The third five minutes are for articulating a question about that point. That simple exercise completely changes the kind of feedback you can get, because it shows exactly what you have tried and where you are getting lost. It puts you in a much stronger position to get feedback that will make a difference.
Not all feedback feels good. Sometimes it shows that a description is too general or too sloppy. Sometimes it shows that you are relying on intuition when you need careful comparison. That is okay. That is feedback working. In a linguistics class, good analysis emerges through revision, and revision can only happen when the initial analysis is good enough to be worth revising. The goal is not to have perfect notes the first time through. The goal is to have notes that are clear enough to revise. Once that becomes part of your routine, feedback starts to feel less threatening and more useful.