What I Wish I Knew Before My First Committee Meeting

I walked into my first committee meeting like it was a dissertation defense with worse odds. I'd rehearsed answers to questions nobody asked, panicked about gaps in my literature review that turned out to matter far less than I thought, and spent a full week losing sleep over a meeting that, in the end, was fine. Better than fine, actually. Here's what I'd tell myself if I could go back — including the part where I assumed everyone in that room had some higher level of judgment than I did, simply because of the letters after their names. They didn't. They were just further along the same uncertain path I was on.

It's a Checkpoint, Not a Verdict

Your first committee meeting exists to make sure you're on a reasonable track, not to determine your worth as a scholar. Committees see early-stage, messy, incomplete work constantly — that's the entire point of meeting early, before you've sunk years into a direction nobody's weighed in on. Committee members know this. Somehow, incoming students almost never do.

The Two Weeks Before: What to Actually Do

• Send materials at least a week ahead, not the night before. A rushed timeline signals disorganization more than the content itself does.
• Write a one-page summary up front: what you've done, what's working, what you're stuck on. Committees read dozens of these across their advising load — a clear summary respects their time and gets you better feedback.
• Prepare two or three specific questions for them, not just answers for yourself. The best use of a committee meeting isn't defending your choices — it's extracting expertise you don't have access to elsewhere.

Send Materials Early, and Send Them Framed Honestly

Don't send your committee a polished narrative that hides the parts you're unsure about. Send an honest snapshot: here's what I've done, here's what's working, here's what I'm stuck on. Committees are far more useful to you when you let them see the real state of things, and framing everything as more finished than it is just delays the moment they find the actual gaps — usually in the meeting itself, in front of you, which is worse.

Silence After a Question Is Not a Crisis

You will get a question you don't have a great answer to. That's normal, and it's not a sign the meeting is going badly. "That's a great point, I hadn't considered that — let me think through it and follow up" is a completely acceptable answer, and committee members respect it far more than a rushed, overconfident non-answer.

FAQ

How far in advance should I send materials before a committee meeting? At least a week, ideally more. A rushed, last-minute packet signals disorganization and gives committee members less time to give you thoughtful feedback.

Is it okay to say "I don't know" in a committee meeting? Yes, and it's often the stronger answer. A calm "let me think through that and follow up" reads as more competent than an overconfident guess that falls apart under a follow-up question.

What's the purpose of an early committee meeting if the work isn't finished yet? It's specifically designed for unfinished, in-progress work — the goal is course correction while it's still cheap to make changes, not evaluation of a final product.

The Meeting You're Actually Having

Your committee isn't the enemy in this. In the best case, they're the small group of people whose collective expertise you get to draw on for the next several years, for free, because it's literally their job. Walk in treating it that way — as a resource, not a trial, and as a room full of people who are exactly as fallible and human as you are — and the whole relationship gets easier starting with meeting one.