What a capstone is, and what graders look for
A capstone is a substantial applied project that integrates the program: strategy, finance, marketing, operations, people and analytics. Formats vary. Some programs assign a real client organization, some a simulation, some an independent research or business plan project. Whatever the format, graders look for the same four things: a well-defined problem, rigorous analysis, a recommendation that follows from the evidence and professional communication.
| Format | Typical deliverable | Main risk |
|---|---|---|
| Client consulting project | Report, presentation to the client | Scope creep and unclear client expectations |
| Business plan or venture | Plan with financial model | Optimistic assumptions without evidence |
| Research project | Paper with data analysis | A topic too broad to answer |
| Strategy simulation | Decision log and reflection | Describing results instead of explaining decisions |
Scope the question in the first three weeks
Most capstone problems begin with a topic ("improve customer retention") rather than a question. Turn it into a question that can be answered with the time and data you have. A good capstone question is specific, answerable, important to someone and limited in scope.
| Topic | Weak question | Strong question |
|---|---|---|
| Retention | How can the company improve retention? | Which two changes to onboarding would most reduce first-year customer churn of the small business segment, and what would they cost? |
| Expansion | Should the firm grow? | Should the firm open a second distribution center in the Southeast within 18 months, given projected demand and a funding limit of $4 million? |
| Cost | Reduce costs | Where can the operations group cut 8 percent of cost of goods sold over two years without lowering service levels? |
Write a one-page scope statement that includes the question, the deliverables, what is in and out of scope, data sources, the decision-maker and the deadlines. Get it agreed in writing by your adviser or client. Return to it whenever a request grows beyond it.
Plan the 14 weeks
A capstone feels long until the final month. Build backward from the deadline and protect the analysis and writing phases.
| Weeks | Phase | Output |
|---|---|---|
| 1 to 2 | Scoping and kickoff | Agreed scope statement; team charter if a group project |
| 3 to 4 | Context and data collection | Industry and company review; interview schedule; data request |
| 5 to 8 | Analysis | Models, comparisons, interview synthesis, first hypotheses |
| 9 | Midpoint review | Progress report; adjust scope or question |
| 10 to 11 | Options and recommendation | Evaluated options; financial case; implementation plan |
| 12 to 13 | Writing and slides | Full draft; adviser feedback; revisions |
| 14 | Presentation and submission | Final report and defense |
Schedule the full draft at least two weeks before the due date, so there is time to respond to feedback. Capstones that start writing in the last week are usually weaker in logic than in data.
Do the analysis with a hypothesis
Start with an early hypothesis about the answer, then use analysis to test it, as consultants do. Unfocused data gathering fills pages but does not answer the question. Decide in advance what evidence would confirm or contradict each hypothesis.
- Use multiple sources Company data, interviews, industry reports and academic research; triangulate.
- Quantify the problem and the solution Size the gap and the expected benefit and cost.
- Test the numbers Run sensitivity and best/worst scenarios on key assumptions.
- Listen to the people affected Interview staff and customers; document what you learn.
- Record assumptions Keep a log so every figure in the report can be traced.
See our guide to a consulting-style report for structuring findings, and the guide to feasibility studies for investment decisions.
Recommend and plan implementation
The recommendation should answer the original question directly and be specific enough to act on. Include costs, benefits, risks, timeline and owners.
| Element | What to include |
|---|---|
| Recommendation | One clear statement, then the two or three reasons that matter most |
| Financial case | Investment, savings or revenue, payback or NPV, with sensitivity |
| Implementation plan | Phases, owners, milestones, resources, dependencies |
| Risks | Main risks, probability, impact and mitigation |
| Success measures | KPIs, baselines, targets and review dates |
Offer a staged path where possible: a pilot with decision gates reduces risk and is easier for clients to approve.
Working on this assignment now? Get a price for help with your paper.
Get an instant quoteThe kickoff meeting: questions to ask the client
The first meeting with a client or sponsor decides how the project goes. Prepare questions that clarify the decision, not just the topic.
| Area | Questions |
|---|---|
| Decision | What decision will this work inform, and who will make it? By when? |
| Success | What would a great result look like? How will you judge it? |
| History | What has been tried before, and what happened? |
| Constraints | What is fixed: budget, systems, people, regulation, timing? |
| Data and access | What data exist, who owns them and who can we interview? |
| Politics | Who supports this, who might resist and why? |
| Confidentiality | What may be used in the report and shared with the school? |
Write up the answers the same day and send them to the client for confirmation. This record protects both sides when scope questions arise.
Choosing among possible topics
If you have several candidate projects, score them honestly before committing.
| Criterion (weight) | Topic A: retention | Topic B: new market | Topic C: cost reduction |
|---|---|---|---|
| Importance to the client (30%) | 4 | 5 | 3 |
| Data availability (25%) | 5 | 2 | 4 |
| Fit with your skills and interests (20%) | 4 | 4 | 3 |
| Scope can be finished in 14 weeks (25%) | 4 | 2 | 4 |
| Weighted score | 1.20 + 1.25 + 0.80 + 1.00 = 4.25 | 1.50 + 0.50 + 0.80 + 0.50 = 3.30 | 0.90 + 1.00 + 0.60 + 1.00 = 3.50 |
Topic B is the most important but the least feasible, which is common. Choose the project that will give a defensible answer in the time you have. A smaller project done well beats a large one left unfinished.
Risks to the capstone itself
| Risk | Early sign | Response |
|---|---|---|
| Data not delivered | Requests unanswered after two weeks | Escalate to sponsor; agree a fallback dataset or proxy |
| Scope creep | New requests in each meeting | Refer to the scope statement; trade new work for old |
| Team imbalance | Uneven contribution or missed handoffs | Redistribute tasks; use the team charter |
| Interviews fall through | Fewer than half scheduled by week 4 | Offer shorter calls; use alternative sources |
| Late analysis | No findings by week 9 | Cut questions; narrow the scope with the adviser |
- Keep a decision log Every change in scope, data or method, with date and reason.
- Hold a weekly 15-minute check What is done, blocked and next.
- Send a progress note to the sponsor every two weeks Surprises should never come at the end.
Present and defend
Most capstones end with a presentation and questions. Prepare by listing the ten toughest questions a client or panel could ask: about your assumptions, data limits, risks and alternatives. Have a short answer for each, with a backup slide for the numbers. Keep the main presentation to the story: situation, question, findings, recommendation, next steps. For slide design, see our guide to the MBA presentation.
- Open with the answer Executives want the recommendation in the first two minutes.
- Know your numbers Be able to explain every figure and where it came from.
- Acknowledge limits Say what you could not verify and how it affects confidence.
- Stay inside the scope Politely park questions beyond it for future work.
If you want help with a capstone project, you can order MBA capstone project help.