Starting, adding to and summarising a discussion
35 min · Intermediate
Need help? Ask a tutor on WhatsApp (opens in a new tab)In a GD, most candidates wait and speak once or twice. Evaluators remember the ones who open clearly, add something new and tie the talk together at the end, so these three moments are worth practising.
Ways to start: definition, fact, question, quote
An opening is the first 20 to 30 seconds of a GD, in which one candidate frames the topic for the group, usually with a definition, a fact, a question or a well-known saying.
Four safe ways to open are a definition (say what the key words mean), a fact (one true, relevant piece of information), a question (one that splits the topic into parts) and a quote or saying. Pick the opening you can say most clearly.
Example 1 · Four openings for one topic
Topic: "Work from home or office: which is better for freshers?"Definition: "By work from home we mean doing the full job remotely, and by office we mean working at the company's desk most days. For a fresher, the real question is where they learn faster."Fact: "After the pandemic, many large Indian IT companies asked employees to return to office for some days every week."Question: "Should we look at this from three sides: learning, cost and work-life balance?"Quote: "There is an old saying, 'Two heads are better than one.' For a fresher, the question is whether those heads need to be in the same room."Definition: safest; works for every topic Fact: strong if you are sure; never invent the details Question: gives the group a structure to follow (shows leadership) Quote: memorable, but only with words you are certain of
What this code does
- Each opening ends by pointing the group somewhere: learning speed, return to office, three sides, or being in the same room.
- The fact is worded at the level you can stand behind ("many large companies"), without a made-up percentage.
- The question opening is the easiest to build on, because it hands the group three headings.
A definition is the safest, because nobody can call it wrong. A fact is strong only if you are sure of it. A quote is risky if you are unsure of the words or who said it, so a well-known saying is safer than a famous name.
Adding value: a new point, an example, data
Adding value means that every turn you take moves the discussion forward with a new point, an example or data, instead of repeating what was already said.
You can add value in three ways: a new point nobody has made, an example that makes an earlier point real, or data that supports or tests a point. "I agree with Anil" alone adds nothing.
Example 2 · Repeating versus adding value
Weak: "I agree with Anil. Office is better. Yes, office is better."Strong (new point): "One angle we have not covered is the company's side: training 500 freshers is easier when they sit together."Strong (example): "Building on Anil's point, in my internship I fixed a bug in ten minutes because my mentor sat at the next desk."Strong (test): "That works for city campuses. For someone living two hours away, daily travel costs time and money, so a mix may be fairer."Weak: nothing new -> no content marks New point: a new angle -> content Example: makes Anil's point real, names him -> content + teamwork Test: checks a point against a real case -> content + depth
What this code does
- The weak turn repeats the same idea twice and gives the evaluator nothing to mark.
- Naming the person you build on ("Building on Anil's point") shows you were listening.
- Testing a point politely ("That works for..., but...") adds depth without starting a fight.
"I agree with Anil, and here is an example from my internship..." adds an example and also shows teamwork, because it builds on a person by name.
- New point: "One angle we have not discussed is cost for the company."
- Example: "In my hostel, for example, ..."
- Data: "A survey I read last month said roughly..." (only if you are sure).
- Test a point: "That works in cities, but what about small towns?"
Find the bug
Which turn adds no value?
Tap the line that fails the adding-value test.
Topic: "Work from home or office for freshers?" Which turn adds nothing new?
Round 1 of 3Bringing in quiet members
Bringing in is inviting a quiet member, by name and with an open, easy question, to share a view. It shows leadership and teamwork because you use your turn to help the group.
Ask by name, with an open and easy question such as "Esha, we have not heard from you. Do you think office work suits freshers?"
Example 3 · Bringing in a quiet member
(Eight minutes in. Esha has not spoken.)Divya: "We have heard a lot about learning in office. Esha, we have not heard from you yet. What do you think matters most for a fresher?"Esha: "I think it is getting feedback quickly. In office, a senior can look at your screen and correct you on the spot."Divya: "That is a good point, quick feedback. Let us see if that is possible online too."- Uses Esha's name, so the question is clearly for her - Asks an open, easy question, not a trick - Repeats Esha's key words, which shows the group heard her - Links her point back to the topic so the talk moves on
What this code does
- Divya scores for leadership and teamwork, and Esha gets a fair chance to be scored at all.
- An open question ("What do you think matters most?") is easier to answer than "Do you agree with Rohit?"
- Divya does not take over Esha's point; she only names it and moves the group forward.
Do not put the person on the spot with a hard or trick question, and do not do it more than once or twice in a round.
Summarising at the end in 30 seconds
A GD summary is a short, neutral wrap-up of what the group said: the topic, the main points on each side, where the group agreed and the way forward, with no new points.
A summary is not the place for your own opinion, and it adds no new points. At a normal speaking speed of about 120 to 150 words a minute, 30 seconds is roughly 60 to 75 words.
Example 4 · Does the summary fit in 30 seconds?
WORDS_PER_MINUTE = 130 # a normal, clear speaking speed
def check(label, summary): words = len(summary.split()) seconds = words * 60 / WORDS_PER_MINUTE verdict = "fits in 30 seconds" if seconds <= 30 else "too long, cut it" print(f"{label}: {words} words, about {seconds:.0f} seconds, {verdict}")
long_one = ( "So friends, we discussed work from home and office and I personally " "feel strongly that office is better because I learn better when people are " "around me, and Anil also said that, and Bhavna gave a campus-project example, " "and Chetan talked about traffic which is a real problem in Bengaluru and " "Hyderabad and every big city, and Esha said feedback is quick in office, and " "some people also said that online meetings are tiring, so overall I think " "office is better, but maybe a hybrid model can also work for some people, " "and companies should decide based on their teams and projects and also the " "location of their employees.")short_one = ( "We discussed whether freshers should work from home or from office. " "Most of us felt the office helps freshers learn faster, through quick " "feedback and mentors nearby. Others pointed out the cost and time of daily " "travel. The group agreed on a hybrid plan: office three days a week in the " "first year, with flexibility for long commutes.")check("First try", long_one)check("Rewritten", short_one)First try: 109 words, about 50 seconds, too long, cut it Rewritten: 58 words, about 27 seconds, fits in 30 seconds
What this code does
- The first try retells every turn in order and slips in a personal opinion ("I personally feel"), which a summary should not do.
- The rewrite follows the four lines: topic, points for, points against, where the group agreed.
split()with no argument splits on any run of spaces, solen(...)is the number of words; 130 words a minute is a typical clear pace.
Write a few practice summaries and count the words; it is the easiest way to learn how much fits.
- Line 1: the topic in one sentence.
- Line 2: the main points for, then against.
- Line 3: where most people agreed.
- Line 4: the way forward the group suggested.
Order of execution
Build a 30-second summary
Tap the parts of a summary in the order you would say them.
Annotated model GD transcript
An annotated transcript is a written GD with a note beside each turn that says what the turn does and which evaluation parameter it scores.
Reading an annotated GD shows the patterns above working together: an opening, additions that build, a person being brought in, and a summary. Read the model below once for the content and once only for the notes.
Example 5 · A model GD, with notes
Topic: "Should coding be taught from Class 6 in all schools?"1 Ravi: "Let us first agree on the word 'coding'. I take it to mean logical problem-solving using simple programs, not only one language. Can we look at benefits, readiness of schools and cost?"2 Sana: "On benefits: coding builds step-by-step thinking, which helps in maths too. My cousin learnt Scratch in Class 6 and now enjoys puzzles."3 Ajay: "Adding to Sana, early exposure helps students choose careers with more information."4 Meera: "I see the benefits, but readiness is a problem. Many schools lack computers or trained teachers, especially in villages."5 Ravi: "Meera's point on teachers is important. Farhan, what do you think could fix the teacher shortage?"6 Farhan: "Unplugged coding: logic games on paper that need no computer. Teachers could be trained online in a few weeks."7 Sana: "So we could start with unplugged lessons everywhere and add computer labs step by step."8 Ajay: "Summing up: we agreed coding builds logical thinking and helps career choice. The concern is schools without computers or trained teachers. The group suggests starting with unplugged lessons in Class 6 and adding labs over time."1 Ravi: definition + question opening -> leadership, content 2 Sana: new point with a real example -> content 3 Ajay: builds on Sana by name -> teamwork, small content 4 Meera: polite counter-point on readiness -> content, balance 5 Ravi: links Meera's point, brings in Farhan -> leadership, teamwork 6 Farhan: practical solution -> content 7 Sana: joins two ideas into a plan -> content, teamwork 8 Ajay: neutral 4-line summary, no new points -> leadership
What this code does
- Turn 1 uses two openings together: a definition, then a question that gives the group three headings.
- Turn 4 disagrees without attacking: "I see the benefits, but..." keeps the tone calm.
- Turn 8 follows the four-line summary pattern and adds no new opinion.
Then use the same note style when you review your own mock GDs.
Next step
Check your understanding
12 quick questions