Booth Essay Examples - Before and After 300 Characters

Booth Essay Examples - Before and After 300 Characters

Write Booth's four answers the way you would say them out loud and you will produce something close to 1,800 characters. The application allows 1,200 in total: four fields, 300 characters each. Everything difficult about these answers happens inside that gap. This page takes four drafts written at natural length and cuts each one until it fits, showing the count at every stage, the exact spans that were deleted, and the two places where compression made the answer worse. When your own four fit, the Booth short-answer rubric reads them as one set.

Four honest drafts came to 1,819 characters. The finals come to 902, leaving 298 of the allowance unspent, which is fine: the limit is a ceiling, not a target. The format itself — official prompt wording, the optional and reapplicant fields, where the image upload sits relative to the written allowance — belongs to our Chicago Booth short-answer guide, and anyone rebuilding an older long-form draft should start with what the switch to short answers changed. This page assumes you know the format and are looking at a draft 60 percent too long. For a second read on your own set, MBA essay review returns revision signals, and the MBA rubric catalog shows what other programs ask this cycle.

Every answer below is a constructed teaching example. The applicant, the employer, the grandmother, the crossword habit, and every detail inside them are invented or composited for instruction. None is a submitted or accepted application essay, none is described as successful, and none is output from a GradPilot review. They exist so the character counts have something concrete to measure.

The four prompts and the 300-character limit were checked on Booth's Full-Time MBA how-to-apply page on August 10, 2026, where the same page lists Round 1 as September 15, 2026 at 11:59 p.m. Central Time. Booth's application announcement states that the school "has replaced our essays with four short answer prompts" with a "300 character limit per response" (also checked August 10, 2026). Requirements move mid-cycle, so confirm the wording and the limit inside your own application before submitting.

Cut in this order, not in the order you notice things

Most people compress by reading from the top and deleting the first weak word they see. That is why the second draft is usually still over. Adjectives are cheap: cutting "really," "somewhat," and "very" returns six to eight characters each, and you need to find two hundred.

The large returns come from deleting whole functions — an entire sentence that was doing a job the field does not require. Below is the order that recovers the most characters soonest, with the measured length of each deleted span taken from the drafts on this page.

Two cautions. The yields are measured lengths of deleted text, not a subtraction you can perform on the drafts: the finals do not equal draft minus sum, because surviving sentences were rewritten as well as shortened, and one rewrite below deliberately gets longer. And the order matters beyond arithmetic — every deletion changes what the remaining sentences must carry, so cutting small words first leaves you protecting a sentence a later cut would have made unnecessary.

Goal one: 495 characters, then 324, then 218

What is your immediate post-MBA career goal?

Draft as written (495 characters), a constructed teaching example:

After Booth, my immediate goal is to move from consulting into a product role at a healthcare payments company, where I would work on the claims and billing tools that hospital revenue-cycle teams use every day. I have spent the last four years advising these teams on process redesign, and I have seen how much of the problem is actually software that nobody has updated since 2014. I want to be on the side of the table that builds the tool rather than the side that writes the recommendation.

Nothing in that draft is bad writing. It is a person answering the question at the length the question deserves in conversation. It is also 195 characters over.

The first pass removes the prompt restatement (36) and the descriptive clause "where I would work on the claims and billing tools that hospital revenue-cycle teams use every day" (99), which is mostly restating the phrase "healthcare payments company" in longer form.

Second pass (324 characters), still 24 over:

Product manager for hospital claims and billing software at a healthcare payments company. I have spent four years advising hospital revenue-cycle teams on process redesign, and I have seen how much of the problem is software that nobody has updated since 2014. I want to build the tool rather than write the recommendation.

Twenty-four characters is the interesting part of this exercise, because at that distance the obvious deletions are gone and you have to decide what the answer is actually for. There are three candidates: the four years of advising, the diagnosis about 2014-era software, or the closing line about which side of the table you sit on.

Deleting the closing line saves the most. It is also the only sentence explaining why the writer wants a different job, which is the closest thing this field has to a motive. Deleting the four years removes the reason a reader should believe the diagnosis. So the final does something the first two passes could not: it merges two sentences into one clause, spending ten extra characters on the merged phrase in order to retire ninety-two.

Final (218 characters), a constructed teaching example:

Product manager for hospital billing software at a healthcare payments company. I spent four years advising revenue-cycle teams on workarounds for tools nobody had updated; I want to build the tool instead of the memo.

The merged clause went from "I have spent four years advising hospital revenue-cycle teams on process redesign" (81) to "I spent four years advising revenue-cycle teams on workarounds for tools nobody had updated" (91). It is ten characters longer and it absorbs the entire diagnosis sentence, because the single word "workarounds" implies the tools were failing. That is the move worth learning: not shorter sentences, but fewer jobs per sentence and more jobs per word. The closing figure shrank the ordinary way, from 111 characters to "I want to build the tool instead of the memo" (45) — the contrast survives, the staging around it does not.

At 218 characters, 82 remain unused. Resist spending them. The answer already carries a function, a product, a buyer, and the origin of the writer's knowledge. A fifth element would be the first thing a reader forgets.

Goal two: trading a reason for a measure

What is your long-term post-MBA career goal?

Draft as written (400 characters), a constructed teaching example:

In the long term, I hope to eventually become a senior leader, ideally at the executive level, at a company that is working to fix the financial side of American healthcare, because I believe that the administrative burden on hospitals is one of the largest and most solvable sources of waste in the system, and I would like to be someone who has real influence over how that gets addressed at scale.

The opening 97 characters contain two hedges ("hope to," "ideally"), one redundancy ("eventually" inside "in the long term"), and a title ladder that climbs from "senior leader" to "executive level" without naming a responsibility. Replacing all of it with "Long term, I want to run" (24) returns 73 characters and makes the ambition larger, not smaller, because a verb beats a rank.

Second pass (217 characters), now legal:

Long term, I want to run the product organization at a company that takes billing work off clinical staff, because administrative burden is one of the largest and most solvable sources of waste in American healthcare.

This version fits, and most applicants stop here. But the 110-character clause beginning "because administrative burden is one of the largest and most solvable sources of waste" has two problems visible only once the answer sits inside the four-field set: it is a claim about an industry rather than about the applicant, and it restates territory the first answer already established. Compression is not only deletion. At this length a generic justification and a specific measurement cost about the same, so you can trade one for the other for free.

Final (203 characters), a constructed teaching example:

Long term, I want to run the product organization at a company that takes billing work off clinical staff. The number I care about is hours returned to nurses per hospital, not claims processed per hour.

The replacement sentence is 96 characters against the 110 it displaced, so the answer got shorter and more specific. It also does something the justification could not: it commits the writer to a metric that could be wrong, and it is not a sentence another applicant in the same industry would happen to write.

Read against the immediate goal, the pair now progresses — build the billing tool, then run the organization that builds it — without either field repeating the other's ground. Directional language is honest here. "I want to run" claims an intention, not an outcome, and no short answer can promise where a career lands.

The image explanation: 553 down to 285, and why this one is hardest

Upload an image and explain its significance to you.

This field is the hardest of the four to compress because two different jobs compete for the same 300 characters. The text has to identify enough of what is in the picture for the sentence to make sense, and it has to say what the picture means to you. Description is expensive and meaning is what the prompt asked for.

Draft as written (553 characters), a constructed teaching example:

The image is a photo of the whiteboard in my grandmother's kitchen in Fresno, where she ran a home daycare for eighteen years. She used it to track nap times, allergies, and which parent was picking up which child on which day, and it was color-coded in a system that only she fully understood. After she died we found it still had the last week's schedule on it. I keep the photo because it reminds me that the systems people build for themselves are usually smarter than the ones we design for them, and that is something I try to remember in my work.

Almost twice the limit. Three deletions come out immediately: "The image is a photo of the whiteboard in" (41), because the reader can see that it is an image and the first noun can simply be the object; the framing "I keep the photo because it reminds me that" ahead of the meaning; and the trailing takeaway "and that is something I try to remember in my work" (51), which asserts a habit rather than showing one.

Second pass (333 characters), still 33 over:

My grandmother's kitchen whiteboard in Fresno, where she ran a home daycare for eighteen years. It tracked nap times, allergies, and which parent was picking up which child, in a color code that only she fully understood. It taught me that the systems people build for themselves are usually smarter than the ones we design for them.

Now the remaining cuts are all inside the description. "Which parent was picking up which child" (52 in the full draft form) becomes the noun phrase "pickup parents" (14). "In a color code that only she fully understood" (46) becomes "in a color code only she used" (29), losing a small amount of characterization to buy back seventeen characters. "Usually" (7) goes, and the claim gets sharper for it.

One addition earns its cost. The second pass lost the detail about the last week's schedule still being on the board, and that detail is the only thing in the answer that carries the grandmother's absence. It comes back in compressed form.

Final (285 characters), a constructed teaching example:

My grandmother's kitchen whiteboard, still holding the last week of the home daycare she ran for eighteen years: nap times, allergies, pickup parents, in a color code only she used. It taught me that the systems people build for themselves are smarter than the ones we design for them.

Three structural notes. The colon does the work of a verb, which is the most reliable way to buy characters in a descriptive sentence. "Fresno" is gone, because a place name earns its characters only when the place matters to the meaning. And the last week of the schedule is now a subordinate phrase rather than its own sentence, so the loss registers without the answer becoming about grief.

What survives is the ratio: roughly 180 characters of description and 105 of meaning, with the meaning stated in language the described object actually supports. An explanation that spends all 300 characters inventorying the picture leaves a reader knowing what you photographed and nothing about why. The reverse failure is thinner and more common.

Over-compressed version (82 characters), a constructed teaching example:

My grandmother's whiteboard from her daycare. It shaped how I think about systems.

That is legal, it is inside the limit with 218 characters to spare, and it has thrown away everything specific. "Systems" is now an abstraction with nothing under it, and the second sentence could be attached to any object in the world. Fitting is not the goal. The 285-character version fits too.

A boundary worth naming: a text-only review can read your explanation but cannot see, judge, or verify the image you upload. Whether the picture is legible, appropriate, and consistent with the caption is something only you can check inside the application.

The fun fact: stopping at 196

Share a fun fact or something unique about yourself.

Draft as written (371 characters), a constructed teaching example:

A fun fact about me is that I have a somewhat unusual hobby: I am really into competitive crossword construction, and over the past few years I have submitted a number of puzzles to various outlets. I like it because it combines wordplay with a kind of grid engineering that most people do not realize is involved, and it has taught me a lot about patience and precision.

The prompt restatement plus the wind-up runs 77 characters before the answer begins. The final sentence, 56 characters of "patience and precision," converts a hobby into a job interview.

Final (196 characters), a constructed teaching example:

I construct crossword puzzles. The hardest part is not the clues; it is the one stubborn corner where four entries have to agree, and the fix is almost always to give up the answer you liked most.

This one stops 104 characters short of the limit, deliberately. The first sentence is thirty characters and unambiguous. The second supplies a detail only someone who has done the thing would produce — the stubborn corner, the four entries, the concession — and it describes a way of thinking without ever claiming to.

Notice what is not in it. No assertion that the hobby is unique; "unique" is unprovable, and the prompt is satisfied by an answer that is concrete and specific to you. No bridge to business. No tally of puzzles published, because a count spends characters on scale when the field rewards texture. Compressed personal answers fail more often from added significance than from missing information, and the phrasings that signal it are catalogued in our guide to MBA essay clichés and the patterns behind them.

Three cuts that cost more than they save

Compression has a floor, and you can go through it while still being technically inside the limit. Three failures account for most of it.

Cutting the agent. The first casualty of aggressive trimming is usually the person doing things. "PM, healthcare payments, RCM tools." is 35 characters and answers nothing: a reader cannot tell what you would do on a Monday, and two of its four terms are abbreviations requiring an industry to decode. Noun stacks look efficient because they are short, but if a sentence has lost its subject and its verb you have not compressed it, you have replaced it with a label.

Cutting the concrete noun and keeping the abstraction. This is the 82-character whiteboard version above. When a draft is over, the specific object feels expendable because it is long and the conclusion feels essential because it is the point. It is the wrong way round. The conclusion is the part any applicant could write; the object is the part only you have. Delete conclusions before you delete nouns.

Cutting the numbers that carry time and scale. "Eighteen years" is 14 characters and the cheapest credibility in the image answer; "four years advising revenue-cycle teams" does the same work in the first. Numbers like these replace a paragraph of implied history, so they go last — with one exception. A number measuring your own performance rather than your exposure usually needs a mechanism to be believable, and 300 characters has no room for a mechanism. Duration and scope survive compression better than outcome statistics do.

When two answers want the same 60 characters

The long-term goal above traded its justification clause not because the clause was badly written, but because the same idea was already implied one field earlier. The real budget is 1,200 characters across the set, and duplication is the only waste that stays invisible while you edit a single box.

Run one pass with all four answers in a single document and highlight every noun phrase that appears twice. In these drafts, "healthcare" and "billing" appeared in both career answers, "systems" appeared in the image explanation and nearly reappeared in the fun fact, and one version of the crossword answer ended on precision, echoing the workarounds clause in the first field.

A useful test at the end of this pass: cover the two career answers and ask whether the remaining two still tell a reader something new. Coherence across four fields does not mean a single theme. It means four facts that can all be true of the same person without any of them being a restatement.

The discipline transfers to other schools with hard limits. Columbia's MBA application asks two short answers at "50 characters maximum" each, checked on the school's application requirements page on August 10, 2026 — a field where the answer is one noun phrase, which we work through in our page on Columbia's 50-character short answers. At 300 characters Booth still gives you a sentence and a half of reasoning: enough room to be specific, not enough to be careful, which is why these drafts get cut rather than written short.

Count it where it counts

Every count on this page includes spaces and punctuation. The four finals total 902 characters across 157 words, which puts these examples at roughly 40 to 55 words per full field, depending on how long your nouns are. Treat that as a drafting estimate only. Word processors, browsers, and application forms do not always agree on what a character is once curly quotation marks, pasted dashes, or a stray line break are involved, and the counter inside your own live application is the only authority. Paste each answer into the real field and read the number there.

Leave margin. An answer sitting at exactly 300 has no room for the typo you find in October, and fixing one at that ceiling means re-solving the compression problem to buy back four characters. The finals here sit between 196 and 285 for that reason, not because shorter reads better. Draft in a plain text file rather than in an autosaving form, and start earlier than the calendar suggests: Round 1 closes September 15, 2026 at 11:59 p.m. Central Time, per Booth's official page on August 10, 2026.

What compression cannot supply

Cutting is a subtractive operation. It can only remove, which means every yield on this page was already sitting in the draft before the first deletion: a diagnosis about software nobody had updated, a whiteboard that hung in a real kitchen, one corner of a grid where four entries had to agree. Run the same six-step order over a draft with nothing underneath and you will not get a shorter answer. You will get a shorter absence — clean syntax, correct length, no person in it.

There is a way to check which one you have, and it runs backwards from everything above. Take any of your four finals and try to expand it to 500 characters without inventing a single new fact. Where the material exists, the expansion writes itself: "workarounds" unpacks into the four years and the 2014-era tools, "pickup parents" unpacks into the color code and the last week still on the board, the stubborn corner unpacks into the four entries and the answer you gave up. Where it does not, the only way back to 500 is adjectives, significance, and a takeaway sentence — which tells you the answer was never compressed. It was always that thin, and the 300-character ceiling was doing you the favor of hiding it. That is the peculiar honesty of a field this short: there is no room to explain a mechanism, so there is also no room to fake one, and a reader's whole impression rests on the one detail you chose to keep.

If you use generative tools anywhere in revision, check Booth's current application instructions for authorship and AI rules and submit only your own writing. The hazard specific to this length is that a model is fluent at exactly the thing compression cannot produce: a well-formed 300-character sentence that never had 500 characters behind it. What tends to register in that case is not an error but a gap, which is the subject of our piece on how readers respond to AI-assisted application writing — and a four-field, 1,200-character set magnifies a gap rather than covering it. Polish cannot restore a detail that was never in the draft, and at 300 characters there is nothing else on the page to look at.