What You’ll Learn
π« The Myth
“If you can speak English fluentlyβsmooth delivery, no grammatical errors, sophisticated vocabularyβyou’re a good communicator. Candidates with polished English have a major advantage in GDs and interviews. Those with regional accents, slower speech, or less-than-perfect grammar are at a significant disadvantage.”
Candidates from regional-medium backgrounds feel intimidated before they even enter the room. They see convent-educated, English-fluent peers and assume the battle is already lost. Meanwhile, fluent English speakers assume their delivery will carry them throughβand focus less on the substance of what they’re actually saying. Both groups are wrong.
π€ Why People Believe It
This myth is deeply ingrained in Indian culture. Here’s why it persists:
1. Colonial Legacy and Social Signaling
In India, English fluency has historically been a class markerβa signal of elite education and social privilege. This association runs deep. We unconsciously equate polished English with intelligence, competence, and “sophistication.” It’s a bias, not a reality, but it shapes perceptions.
2. Surface-Level Evaluation Habits
In casual settings, fluent speakers often dominate conversations. They sound impressive. In a first impression, smooth delivery creates a halo effect. Candidates observe this and conclude that fluency equals effectiveness. What they don’t see is how that impression changes when substance is examined more closely.
3. Coaching Center Reinforcement
Many coaching centers emphasize English improvementβvocabulary building, accent neutralization, grammar drills. This creates the impression that English fluency is the primary determinant of success. It’s easier to teach vocabulary than to teach structured thinking, so that’s what gets emphasized.
4. Self-Fulfilling Confidence Dynamics
Fluent English speakers often have more confidence, which helps their performance. Less fluent speakers often have less confidence, which hurts their performance. Observers attribute the outcome to fluency when it’s actually driven by confidence. The fluency is correlated, not causal.
β The Reality
Here’s what actually matters in B-school evaluationsβand what doesn’t:
Fluency vs. Communication: The Critical Distinction
- Smooth, uninterrupted speech
- Correct grammar and syntax
- Rich vocabulary
- Neutral or “polished” accent
- Fast pace of speaking
- Minimal pauses or hesitations
- Nice to have, not essential
- Can mask empty content
- Creates false confidence
- Often prioritized by wrong candidates
- Clear expression of ideas (understood easily)
- Structured thinking (logical flow)
- Substantive content (depth, not fluff)
- Appropriate conciseness (no rambling)
- Responsive listening (actually answers questions)
- Authentic engagement (genuine, not performed)
- Essential for selection
- Independent of accent or fluency
- What actually gets tested
- What separates converts from rejects
What Panels Actually Write in Feedback
- “Regional accent affected evaluation”
- “Grammar errors were problematic”
- “Not fluent enough in English”
- “Vocabulary too simple”
- “Speaking pace too slow”
- “Couldn’t articulate clear reasons for MBA”
- “Answers lacked depth and structure”
- “Didn’t respond to what was actually asked”
- “Said a lot but communicated little”
- “Surface-level thinking on complex topics”
Real Scenarios from Interview Rooms
But when asked “Why MBA?”, he gave a structured, specific answer: “In my 3 years at [manufacturing company], I’ve led a team of 12 on the shop floor. I’ve learned to manage production targets. But when I tried to propose a process improvement to senior management, I realized I lack the financial and strategic vocabulary to make business cases. Last quarter, my idea was rejectedβnot because it was wrong, but because I couldn’t present the ROI analysis convincingly. I need structured business education to bridge that gap.”
Panel member later told me: “His English wasn’t polished, but his thinking was crystal clear. We knew exactly what he wanted and why. That’s what we’re looking for.”
Same question: “Why MBA?”
“Well, I believe that an MBA is a transformative journey that will help me unlock my true potential. I’m passionate about business and want to develop a holistic perspective on organizational dynamics. I feel that the rigorous curriculum and peer learning environment will catalyze my growth as a future business leader.”
Panel: “That’s very general. Can you be more specific about what skills you want to develop?”
“I want to develop leadership skills, strategic thinking abilities, and a strong business acumen that will help me navigate the complexities of the corporate world.”
Panel (internally): Still nothing specific. Let’s try again.
Three more follow-up questions. Three more eloquent non-answers.
Candidate A (Fluent): Spoke 5 times, dominated the discussion, impressive vocabulary. But every contribution was a generalization: “Manufacturing is the backbone of any economy.” “Services alone cannot sustain long-term growth.” “We need a balanced approach.” Sounded smart, said nothing specific.
Candidate B (Regional Accent): Spoke 3 times, slower pace, occasional grammar slips. But each contribution had data: “Germany’s manufacturing is 20% of GDP and they have 4% unemployment. UK went services-heavyβtheir manufacturing is 9% now and they’re facing skills crisis.” “In my state, Odisha, one steel plant creates 2,000 direct jobs and 8,000 indirect. One IT park? Maybe 500 total.” Built on others’ points. Added evidence to arguments.
Panel Discussion After: “Candidate Aβspoke a lot, said nothing. Classic GD dominator without substance.” “Candidate Bβfewer interventions but every one moved the discussion forward. That’s what we want.”
β οΈ The Impact: What Happens When You Confuse Fluency with Communication
| Candidate Type | What Goes Wrong | What Should Happen |
|---|---|---|
| Fluent English Speakers | Assume delivery will carry them. Underinvest in content depth. Use impressive language to mask shallow thinking. Get exposed by follow-up questions. | Recognize fluency is necessary but not sufficient. Focus equally on substance. Use clear language to convey clear ideas. Back claims with evidence. |
| Regional-Background Candidates | Feel defeated before starting. Avoid speaking in GDs. Apologize for their English. Let fluent speakers dominate even when they have better points. | Recognize that content matters more than delivery. Focus on structured, substantive contributions. Speak with confidence about what they know. |
| In GD Settings | Fluent speakers dominate airtime with generalizations. Less fluent speakers stay silent despite having specific knowledge. Group produces more noise than insight. | Quality contributions valued over quantity. Specific evidence trumps eloquent generalizations. Best ideas win, regardless of delivery style. |
| In PI Settings | Fluent speakers give polished non-answers. Panels ask more follow-ups to extract substance. Less fluent speakers undersell good experiences. | Clear, specific answers valued. Panels appreciate directness over eloquence. Substance demonstrated through examples, not vocabulary. |
For fluent speakers: Your fluency can actually hurt you if it masks shallow thinking. Panels are trained to probe past impressive delivery. The more polished you sound while saying nothing, the more suspicion you generate. You’ll face harder follow-up questions, and your lack of depth will be exposed.
For less fluent speakers: Your accent won’t hurt you, but your lack of confidence might. If you believe fluency matters more than substance, you’ll stay silent when you should speak, defer when you should assert, and let weaker but more fluent candidates outperform you.
π‘ What Actually Works: Communication That Panels Reward
Regardless of your fluency level, here’s what actually drives positive evaluation:
The Substance Stack: Four Layers of Effective Communication
Practice: After preparing any answer, ask: “Can I say this in simpler words?” If you’re using jargon or sophisticated vocabulary, check if it’s necessary or just impressive-sounding.
Example: Instead of “I want to develop strategic acumen and leadership capabilities,” say “I want to learn how to build business cases that convince senior management.”
Practice: Use frameworks (PREP, STAR) to organize thoughts. It’s okay to pause and say “Let me structure this” before answering.
Example: “Three reasons I want to join this program: First, [specific reason with evidence]. Second, [another reason]. Third, [final reason]. The combination of these makes this program ideal for my goals.”
Practice: For every claim you make, ask: “What’s my evidence?” If you can’t cite a specific example, number, or experience, the claim is too general.
Example: Instead of “I have strong leadership skills,” say “I led a team of 8 to complete a project 2 weeks ahead of deadline, reducing costs by 15%.”
Practice: Before answering, mentally repeat the question to ensure you’re addressing it directly. If your prepared answer doesn’t fit, adapt on the spot.
Example: If asked “What was your biggest failure?”, don’t pivot to a disguised success. Answer the actual question with a genuine failure and what you learned.
For Regional-Background Candidates Specifically
When you need a moment to formulate a response in English, use bridging phrases: “That’s an interesting questionβlet me think about the best way to explain this.” “I want to give you a specific example here.” “Let me break this down into parts.” These phrases buy you time to think while sounding deliberate and structured. Panels interpret them as thoughtfulness, not hesitation.
π― Self-Check: Are You Confusing Fluency with Communication?
English fluency is not the same as effective communication. Panels at top B-schools are trained to look past delivery to evaluate thinking. They’d rather hear a clearly expressed, well-supported idea in imperfect English than an eloquent but empty statement in perfect English. If you’re a fluent speaker, don’t let your delivery mask shallow content. If you’re from a regional background, don’t let accent consciousness stop you from sharing substantive ideas. In either case, focus on clarity, structure, specificity, and responsiveness. That’s what actually gets evaluated.