How to Prepare a Group Meeting Presentation: A Four-Hour Timetable and Three Things a Graduate Student AI Assistant Does
For Monday group meetings, I usually start preparing the presentation on Sunday afternoon. The reason I break the group meeting presentation process into time slots and write it down is that I once tried "just preparing casually," and the cost was getting stumped by questions at the meeting.
18:00 | Write the conclusion first, then organize the process
Before touching the data, write one sentence: what does the work I did this week show? If you can't write it, it means what you did this week doesn't line up with the problem you're trying to solve—in that case, going back to last week's to-do list is more useful than forcing together slides.
19:00 | Data and figures
Keep only the charts and tables that support that conclusion. Get the figure standards right first: put axis units, sample size, and the meaning of error bars in the captions; don't wait to be asked. When working with chemistry or materials data, use a cheminformatics agent to run analyses (toolchains such as RDKit, Datamol, PyTDC, MedChem, and TorchDrug), and keep scripts and versions together. Data reproducibility is the baseline—you need to be able to reproduce on the spot how a figure was made.
20:00 | Generate a first draft of the PPT
Use MuchSci's office assistant agent to generate an editable PPT from one sentence (the same applies to Word and Excel). Deleting and trimming from a first draft is much faster than building from a blank page. For occasions with a fixed structure, such as thesis proposal and midterm reviews, it has templates: enter the project title, research question, and preliminary ideas, and it outputs a first draft including research background, current status, methods, and technical route; missing sections are obvious at a glance.
21:00 | Say it through
Talk through a few pages to the air. While speaking, two problems will surface: which page actually has no content, and which section is in the wrong order. When you read a script, you can just slide along; when you speak, you can't fool yourself.
22:00 | Prepare three "what ifs"
Prepare one-sentence answers for "Why did you do it this way?" "Where does the error come from?" and "What's next?" if asked. These three questions are the most likely to come up at group meetings.
Half an hour after the meeting | Archive
Use AI meeting notes (listen and translate in real time, automatic segmented summaries, translation editing, and report generation) to organize the recording transcript and key points into an archivable report; put this week's translated papers and notes into your personal knowledge base (PDF, DOCX, PPTX, XLSX, TXT, and MD can all be imported; personal use by default, not shared), and send handwritten key points and whiteboard photos through the personal database layer; write the tasks your advisor assigns into next week's list.
Two boundaries to add: before recording, ask the people present—not every setting is suitable for recording; decide for yourself whether unpublished data from group meetings should be uploaded to tools—one thing I have confirmed is that uploaded papers, data, and recordings are not used for model training.
The division of labor for this graduate student AI assistant is: hand figures and first drafts to it; keep conclusions and judgment for yourself. The time it takes to prepare for a group meeting hasn't shortened much; what has changed is the number of times I get stumped by questions at the meeting.