Every stage of the MBA journey comes with structure. The GMAT® has a test date and a score report. Applications have deadlines. Recruiting has a timeline you can map from info sessions to offers, and we laid out that structure in our piece on recruiting timelines.
Then you sign the offer, and the structure gets a lot less explicit. Your company may hand you onboarding materials, goals, and a manager, but a syllabus for learning the role doesn't come with any of them.
That gap shows up quickly. After two years of structured milestones, you may find yourself looking for the next test to study for. A more useful move is to treat the first 90 days as what they probably are: the first time in a long while that you have to write the plan yourself.
You've probably done that before.
Ninety days is a convention in a lot of workplaces more than it is a deadline. Some companies fold a formal review in around that mark, others don't, and the number matters less than what the early months are for: learning.
Write the Plan Yourself
Your GMAT® prep gives you a model for this. The test date and the target score set the shape, but the plan itself, which topics in which order, which sections on which days, came from decisions you made. You probably revised that plan more than once, because the first version was built on assumptions that the first practice test corrected.
A new role works the same way. The job description sets the shape, and the plan for everything else is yours to write. For the first two weeks, that plan is mostly input rather than output. Learn how the team runs: how decisions get made, who gets consulted before things move, and which meetings matter. Take notes during this phase the way you took notes in prep, because those details are what you're there to learn.
One starting habit: at the end of each day, write down the three to five things you heard about but couldn't explain yet. That list tells you what to learn next, and writing it down while the day is fresh keeps small unknowns from piling up.
Keep a Learning Log, Not Just a Notebook
If you kept an error log during prep, you already know the logic. The value usually wasn't in recording the mistakes by itself. It came from reviewing them on a schedule until you could see a pattern, then pointing study time at the pattern instead of at whatever felt urgent.
A new role gives you the same kind of material without marking any answers wrong. Write down the workplace details that go unexplained, from an acronym nobody defines to a process that depends on two people remembering undocumented steps, including questions that seemed too basic to ask. Then review the list at the end of each week the way you reviewed a redo list, and pick one item to chase down.
Two things tend to happen when the tracking never starts. Basic questions go unasked so long that asking them later becomes a bigger moment than it needed to be. And the same confusion shows up three separate times before anyone connects it to a gap.
The review rhythm matters more than the format. A note on your phone or a doc works. A list you never reread doesn't function as a review system.
Aim at Learning First, Performance Second
Somewhere in month two, the questions start arriving: how is the new hire doing, can they handle a project yet, and are they ready for more. Some of that pressure comes from the company and some of it you carry in yourself, and it tends to show up before the learning is done.
The GMAT® had a version of this. People around you could see the score, so it was tempting to watch the number instead of working the process: specific topics, timed sets, review. The score improved when the process did.
At work, define the 90-day target as understanding rather than as a metric. What should you be able to explain by day 90 that you can't explain today? Which decisions should you understand well enough to see coming? Those targets are specific enough to study for, and they prepare you for the performance people will be watching.
When someone spends the first 90 days chasing a visible win instead, the quick project can look good once, and the context it skipped still isn't there when the second project arrives. Learning first moves slower, and it transfers to every project that follows.
Understand Before You Propose
Use the habit prep built most on the GMAT®: figure out what's being asked before you start solving. On the exam, skipping that step can cost you a wrong answer on one question. In a new job, it can cost credibility, and credibility is slower to rebuild than a score.
New hires arrive with big ideas, and that's part of what companies pay the degree for. You may notice work the previous person in the role didn't finish, and suggesting a fix in week two can look like initiative. Sometimes it is. Often, the process in front of you reflects earlier decisions the job description doesn't explain, and the apparent fix was already tried, or it was blocked by something you haven't been shown yet.
So ask how things got this way before you suggest how to change them. When you do bring a proposal, you'll be in a position to name what you already ruled out and why, and that context gives a proposal a better chance of being taken seriously.
Ask for Feedback Before It's Offered
Some companies schedule a formal check-in around the 90-day mark. Waiting for it gives you one review per quarter, which is a slow cadence for someone learning this much this fast.
Prep taught you to prefer evidence over impressions. A practice test gave you information that your general sense of readiness couldn't. Feedback at work works the same way, except it usually has to be requested, because managers are busy, and silence usually just means busy.
So set up the loop yourself. Every two or three weeks, ask your manager one specific question: what would you have done differently on that project, what should the next project stretch toward, and where do I still seem uncertain. A specific question is easier to answer than "how am I doing?", and the answer is more likely to be something you can act on.
Then do what you did with practice tests: change one thing, and let the following weeks show whether it helped. We laid out a review method for practice tests in How to Review GMAT® Practice Tests: A Three-Layer System, and the same approach transfers to a work check-in with small adjustments.
What Doesn't Work
Treating the first 90 days as a performance to give. A month-two hire usually isn't expected to match a five-year veteran, and saying what you don't know yet gives your manager a chance to fill in the context.
Optimizing a process before you understand why it looks the way it does.
Learning in private. Projects, questions, and conversations are among the most useful inputs the learning log can get, and staying quiet through them leaves the plan short on material.
Frequently Asked Questions
How long does it take to get productive in a new job?
It varies by role, industry, and how different the domain is from your pre-MBA work. Roles with a lot of context to absorb can take months before the work starts to feel automatic, and that pace is common rather than a sign something is wrong. Asking your manager what a reasonable timeline looks like for full ownership of the role usually gets you a clearer answer than guessing.
What should I focus on in my first week?
How the team works rather than what you can produce: how decisions get made, who owns what, and where the documentation lives. Then start the daily list of things you heard about but couldn't explain yet.
Should new MBA grads share ideas early?
Share questions early, and share proposals once you understand the context. Questions show engagement, and asking them early usually costs less than correcting a misunderstanding later. Proposals carry more weight when you can explain what you ruled out first and why the current setup exists.
How do I know if my first 90 days are going well?
Signals to watch for: your manager starts handing you more ambiguous work over time, your questions shift from what things are to why they're that way, and colleagues begin bringing you context without being asked. When in doubt, ask your manager directly.
Do employers expect new MBA hires to make an impact right away?
Expectations vary a lot by company and role. Many employers build a learning period into the first year of a new role, especially for career switchers. A reliable way to find out which kind you're in is to ask what the first-quarter expectations are.
Want to Learn Even More?
Related reading:
- How to Turn Your MBA Internship Into a Full-Time Offer
- Salary Negotiation Frameworks for Post-MBA Roles
- When to Leave Your First Post-MBA Job
- GMAT® Error Log: How to Track and Review Mistakes
And if you want to hear more about how the habits from GMAT® prep carry into business school and careers, our podcast is on Spotify, Apple Podcasts, and YouTube.