
The AI question every MBA applicant is quietly asking





Ellin Lolis is the founder and president of Ellin Lolis Consulting, where she has spent over a decade helping MBA applicants gain admission to top business schools through a proven admissions methodology. An award-winning writer and certified career coach, she combines expertise in MBA admissions with long-term career strategy to help clients achieve their goals.
Table of contents
- Ethical guardrails for AI use
- Smart prompting techniques for essays
- Critique-only editing philosophy
- Spotting and avoiding AI-sounding writing
- Admissions committee dynamics and humanity
- Where AI delivers the best value
- Ethical AI boundaries: why guardrails, not prohibitions, define success in high-stakes writing
Spend time in any admissions forum or MBA subreddit today, and you'll notice the conversation has shifted. Alongside the usual worries about GMAT scores and recommendation letters, one question keeps coming up: How much should applicants rely on AI when writing their essays? For working professionals juggling client deadlines and application deadlines at the same time, this isn't an abstract debate. It's a real, practical dilemma.
The tension makes sense. Admissions committees want authentic voice and genuine self-reflection, but they rarely acknowledge how little time their applicants actually have. Someone working 60-hour weeks doesn't have the luxury of unlimited drafts and quiet reflection that good essay writing usually requires.
So here's the real question worth thinking through: can AI genuinely help with essay development by speeding up brainstorming, tightening structure, and sharpening prose without watering down the authenticity that admissions readers are trained to spot? Or does any AI involvement automatically dilute the personal story that makes an application memorable?
What follows is a way to think through that question carefully, distinguishing between AI as a crutch and AI as a legitimate tool for busy, ambitious candidates.
Ethical guardrails for AI use
As AI tools become part of everyday work, one question matters more than any other: how do we ensure these tools deliver real value rather than just telling us what we want to hear? A useful way to check this is what we might call the "consultant test," a simple standard that asks whether an AI's response would meet the bar a skilled human consultant sets for their clients.
A good consultant doesn't just nod along with a client's assumptions. Instead, they push back on weak reasoning, point out risks the client may have missed, and sometimes deliver news the client doesn't want to hear, because that's what actually serves the client's interests. This matters because AI language models tend, by design, toward what's called sycophancy: agreeing with users, softening criticism, and validating shaky ideas to seem more helpful. Both Anthropic and OpenAI have acknowledged this tendency, noting that the training process (specifically, reinforcement learning from human feedback, or RLHF) can accidentally reward agreeableness over accuracy, since people tend to prefer responses that confirm what they already think.
The practical takeaway is that you can't assume an AI will automatically give you the rigor you'd expect from a paid advisor. You have to ask for it directly. Instructing the AI to critique rather than affirm, using phrases like "identify the weakest part of this argument" or "tell me what a skeptical expert would object to," shifts the interaction away from default agreeableness and toward something more useful.
Picture a business strategist using AI to stress-test a market-entry plan. A sycophantic response would praise the logic and suggest a few stylistic tweaks. A consultant-grade response, by contrast, would question the underlying assumptions, such as market size, competitor reaction, and regulatory risk, and clearly flag where the plan looks weak, even if that means contradicting the user's confidence.
This isn't just about better output. When people rely on AI for due diligence, medical decisions, or policy analysis, uncritical validation can do real harm: reinforcing bias, hiding risk, or enabling poor decisions dressed up as confident analysis.
The consultant test works as both a check and a fix. It asks you to evaluate whether an AI interaction meets a professional standard of honesty, and it gives you the power to demand that standard outright. As AI becomes more capable and more embedded in important decisions, treating it as a passive agreement machine, rather than actively steering it toward rigorous, honest feedback, is a mistake we can't afford to keep making.
Smart prompting techniques for essays
The quality of AI feedback on your essay depends directly on the quality of your prompt. Vague requests, like "review my essay" or "make this better," get you vague answers: surface-level grammar fixes and generic encouragement. More deliberate prompting can turn an AI from a passive editor into something closer to a real critical reader.
One effective technique is role-based simulation. Instead of asking the AI to simply critique your essay, ask it to take on a specific point of view: "Act as a member of a competitive college admissions committee who has read 200 essays this week. Evaluate this essay's opening paragraph for whether it would hold your attention past the first three sentences." This does more than add flavor; it activates a different set of evaluation criteria. Admissions committees value distinctiveness and authentic voice over technical polish, while a generic writing-tutor persona might instead default to correctness and conventional structure. Giving the AI a specific role keeps its feedback focused on what actually matters for your document.
A second technique addresses a common weak spot: AI tends to answer immediately, even without the necessary context. Ask it to pause first: "Before you respond, ask me three questions that would help you give more targeted feedback." This matters because essay quality depends heavily on context, including the program's expectations, your other application materials, and the story you're telling across the whole application. Without that context, an AI can give feedback that's technically sound but strategically off. Questions like "What tone are other applicants in this pool likely to use?" or "What specific quality are you trying to show that your transcript doesn't already prove?" push you to name goals you may not have fully articulated. The feedback that follows will then align with those goals rather than generic writing standards.
Both techniques share the same logic: they compensate for the AI's lack of situational awareness by having you build the evaluation framework yourself. If you treat prompting as a one-time instruction rather than an ongoing, context-building conversation, you'll consistently get shallower feedback. The real work of good prompting happens before you ask for feedback, not after you're disappointed by it.
Critique-only editing philosophy
It's tempting to ask an AI to rewrite a passage outright, but that instinct usually backfires. When an AI generates a "corrected" version, it swaps in its own voice, rhythm, and style preferences, erasing the very qualities that made the writing yours. This isn't a small stylistic quibble; it's a misunderstanding of what editing is supposed to do. Good editing sharpens your intent. It doesn't replace your intent with a statistically average version of "good writing" pulled from training data.
Think about what happens in practice. An AI asked to "fix this paragraph" will usually default to safe, predictable phrasing: smoothing out quirks, evening out sentence length, reaching for familiar transitions. If your writing relies on fragments, unusual pacing, or deliberate repetition, that voice gets sanded away. What remains reads more "correctly" in a generic sense but loses the specificity that made it worth reading in the first place. That's why critique-only feedback, pointing out what isn't working and why, preserves your voice while still giving you something useful to work with.
The percentage-based cutting approach shows this principle at work. Ask an AI to "cut this by 20%" instead of "cut 200 words," and you get a fundamentally different kind of edit. Word-count targets invite mechanical trimming: delete a sentence here, a clause there, until the number hits, often without regard for what those cuts do to the flow or emphasis of your argument. Percentage-based instructions, on the other hand, force a more holistic read, identifying redundant passages, over-explained points, or digressions that dilute your central point, then cutting proportionally throughout. The result is tighter, more coherent writing, not just shorter writing.
The practical move here is to ask for a diagnosis, not a prescription. Ask which sections feel repetitive, where the argument loses steam, or which paragraphs could be trimmed by a certain percentage, then do the rewriting yourself. This keeps you as the final decision-maker on voice while still benefiting from an outside read. Treat AI as a sharp reader offering structured notes, not a ghostwriter. That distinction protects both your craft and your ownership of it.
Spotting and avoiding AI-sounding writing
AI-generated text has recognizable patterns, and learning to spot them is now a practical skill for anyone who wants their writing to sound genuinely human. These patterns aren't mysterious; they stem from how these models are trained to satisfy a broad audience while minimizing risk.
The most common giveaways include a fondness for groups of three ("clear, concise, and compelling"), hedging phrases ("it's important to note," "in many cases"), and abstract nouns rather than concrete details. AI writing often leans on summary statements that could apply to almost anything, such as "this highlights the complexity of the issue" or "ultimately, it depends on various factors." These sentences are grammatically fine but empty. They gesture toward insight without ever landing on one.
A related problem is what you might call the "portrait without ever seeing the face" issue: writing that describes a person, event, or idea in exhaustive, accurate detail while never mentioning the one or two specific features that would let a reader actually recognize it. A biographical sketch might say someone was "known for their dedication and innovative thinking" without ever naming the specific habit, phrase, or decision people actually remember about them. The writing is thorough but strangely unrecognizable: accurate overall, hollow in the details.
In practice, this means you should treat specificity as a diagnostic tool. If a sentence could be dropped into an essay about a completely different person, company, or event without changing a word, that's a sign of AI-pattern writing, or at least lazy human writing imitating it. The fix isn't fancier language; it's substitution. Replace the generic claim with a verifiable detail, a direct quote, a number, or a specific observation that only fits this exact situation.
One last useful check: read the passage aloud and ask whether a specific, identifiable person would actually say it in conversation, or whether it sounds like it could have come from anyone, or no one. This test catches something grammar checkers miss: the uncanny smoothness of writing optimized to sound plausible rather than to be true.
For writers and editors, the lesson is that authenticity now takes active checking, not just careful writing. Distinctiveness isn't a nice extra; it's evidence of real thought, and its absence is getting easier to spot.
Admissions committee dynamics and humanity
We often picture admissions committees as single, unified judges handing down one clear verdict. That picture is mostly wrong. In practice, most selective schools use committees made up of people with genuinely different priorities, backgrounds, and reading habits, and that friction usually works in an applicant's favor, not against them.
Picture a typical committee: an admissions officer who champions first-generation students might advocate for an applicant whose essay demonstrates resilience in the face of financial hardship, while a colleague focused on academic rigor hesitates over modest test scores. A third reader, maybe a former teacher, might weigh classroom engagement or curiosity more heavily than either factor. This isn't a flaw in the process; it's a safeguard against the narrow, formulaic evaluation applicants often fear. Institutional research from several liberal arts colleges shows that files reviewed by multiple readers with different priorities produce greater variance in initial scores than files reviewed by a single evaluator, and that committees treat that variance as a reason to discuss the file further rather than reject it.
Here's the practical implication: an applicant who presents a single, polished "brand" built entirely around what they think admissions officers want to hear may actually reduce their chances of finding an advocate in the room. A polished but generic application gives no single committee member a distinctive reason to fight for it. An application with real, sometimes idiosyncratic detail, such as an unusual intellectual obsession, an honestly awkward account of failure, or a genuine (not performative) value, gives at least one reader something concrete to champion.
This is why authenticity holds up better than formula, even though it resists a template. Admissions officers read thousands of essays built around the same patterns: the mission-trip epiphany, the sports-injury metaphor, the wise grandparent. These essays aren't dishonest, but they're interchangeable, and interchangeable essays don't win advocates in a divided committee. A specific, textured account of how you actually think, even if it's a little unpolished, creates the kind of impression that turns into an argument in the committee room.
So here's the advice: strategic authenticity beats strategic conformity. Instead of trying to guess a single "right" way to present yourself, write in a way that would genuinely appeal to at least one specific, plausible reader, understanding that not everyone will respond the same way. In a process shaped by human disagreement rather than algorithmic consistency, genuine specificity is still your strongest asset.
Where AI delivers the best value
Conversations about AI among business professionals and MBA candidates extend beyond admissions, and future business leaders must be tapped into these discussions. Many of these revolve around how to approach AI in the workplace, which tasks make sense to automate, and what deserves more time and human-led effort. There are real use cases for AI implementation across workplaces, while other tasks benefit from the predictability and speed of newly developed tools.
The case for using AI in creative and communication work becomes clearest when you look at where it consistently delivers real results, and where it doesn't. The pattern from both research and real-world use is pretty clear: AI is great at low-stakes, high-volume tasks, and shaky ground for core creative work.
Look at the numbers. A 2023 McKinsey study estimated that generative AI could automate a large share of the time employees spend on tasks such as drafting routine emails, summarizing documents, and writing first-pass product descriptions. These tasks share three traits: they're repetitive, low-stakes individually, and easy to measure success on. When a marketing team needs 200 variations of ad copy for testing, or a support team needs draft responses to common questions, AI's speed and consistency translate directly into time and cost saved.
The math changes for creative work that carries real reputational or strategic weight, such as a company's brand story, a novel's distinct voice, or messaging meant to stand out in a crowded market. Here, the "value" of AI gets harder to measure because the cost of mediocrity isn't symmetrical. A slightly generic customer service reply is forgettable; a slightly generic brand campaign can actually hurt your market position. Research from Wharton on AI-assisted creative work found that while AI raised the average quality of output from novice writers, it also flattened the results, reducing the variance that often signals a genuine creative breakthrough.
This gives us a practical way to decide when to use AI: let volume and stakes guide the decision. High-volume, low-stakes work, such as meeting notes, routine correspondence, and data-driven content variations, is where AI's speed pays off without much quality risk. Low-volume, high-stakes work, such as flagship campaigns, signature content, and strategic messaging, benefits more from AI as a support tool for research, rough drafts, or getting past the blank page, rather than as the primary creative engine.
The takeaway for organizations isn't to use less AI; it's to use it more deliberately. Teams that map their content by volume and stakes, rather than applying AI evenly across the board, tend to gain efficiency without watering down the work that requires real human judgment, cultural fluency, and originality. The smartest AI strategies aren't about maximizing use; they're about knowing exactly where automation makes sense and where it doesn't.
Ethical AI boundaries: why guardrails, not prohibitions, define success in high-stakes writing
Everything above points to one central idea: AI's real value in high-stakes writing, such as admissions essays or important business communications, lies not in generating content but in disciplined critique. The recurring emphasis on structure (percentage-based edits, critique-only requests, authenticity checks) reflects something the industry is catching onto: unchecked AI assistance quietly erodes the qualities readers actually care about, namely voice, vulnerability, and lived specificity. As polish becomes easy to manufacture, what sets writing apart increasingly comes down to human texture that AI can imitate but never truly originate.
For anyone applying this in practice, the takeaway is simple: use AI for high-volume, low-stakes work, such as brainstorming, structural feedback, and generating questions, while keeping final control over your narrative firmly in your own hands. This aligns with emerging standards in professional writing and academic integrity, where being transparent about how you used a tool matters just as much as the tool itself.
Ultimately, the tension between speed and authenticity won't be solved by better prompts alone. It calls for ongoing reflection: as AI gets better at mimicking human nuance, will our idea of "authentic" change with it, or will genuine voice only become more valuable?

