Set Expectations With Your Manager: Win Your First 90 Days

Introduction: the brutal truth you cannot ignore

Your manager is not a mind reader. If you do not set expectations with your manager, you will work hard, deliver the wrong things, and wonder why you are not trusted. That is how careers stall in month one.

Here is the harsh bit. Most managers are overloaded. They do not have time to reverse engineer what you meant to do. They judge on clarity, progress, and outcomes. Not effort.

The good news. Expectation setting is a skill. You can learn it quickly. Do it well and you buy trust, accelerate feedback, and avoid rework. Gallup’s research points to clear expectations as one of the strongest drivers of performance. Google’s Project Oxygen flagged the same. This is not theory. It is the difference between being managed and managing your manager.

In this playbook, I will show you how to set expectations with your manager in your first 90 days with ruthless clarity. You will get scripts, templates, and a cadence that compounds trust.

What “setting expectations” actually means

Expectation setting is aligning on how success will be judged, before the work starts. It is a working contract. Not legal. Practical.

You and your manager should align on:

• Outcomes: the results that matter within 30, 60, 90 days
• Priorities: what comes first when everything feels urgent
• Standards: the quality bar, speed, and the acceptable margin of error
• Cadence: how often you update, the format, the channel
• Decision rights: what you can decide alone, when to ask, when to escalate
• Availability: response times, working hours, and time off protocols
• Stakeholders: who cares, who approves, who needs looped in
• Definition of Done: what complete looks like, including acceptance criteria
• Risks and trade-offs: known constraints, what is flexible vs fixed
• Feedback: how you want it, how often, and how to act on it

If these are not written down, they are assumptions. Assumptions kill trust.

The 90-day expectation-setting playbook

This is a simple operating system to set expectations with your manager and keep them tight.

Week 0–1: align fast and write it down

Your goal: exit week one with a one-page Expectation Brief agreed in writing.

1. Book a 30-minute alignment meeting

   Subject: Clarifying expectations for my first 90 days

   Message: I want to ensure I deliver the right outcomes fast. Can we align on priorities, success measures, and our update cadence? I will propose a one-page brief for your review.

2. Use this agenda

   • 5 minutes: what success looks like by day 30, 60, 90
   • 5 minutes: priorities and trade-offs
   • 5 minutes: stakeholders and dependencies
   • 5 minutes: communication cadence and preferences
   • 5 minutes: decision rights, escalation paths, and risks
   • 5 minutes: agree next steps and confirm written summary

3. Ask precise questions

   • What three outcomes would make you say my first 90 days were a success?
   • If priorities collide, what is the default order?
   • What is good enough vs perfect in this role?
   • Who must review or approve my work?
   • How do you prefer updates: email, Slack, or live?
   • What is an acceptable response time from me and from you?
   • What are the non-negotiables in this team?
   • What would you not want me to do without checking first?

4. Send a written summary within 2 hours

   Subject: Expectation Brief – draft for your confirmation

   Attach your one-page Expectation Brief. Ask for edits in the document, not vague replies.

Week 2–4: deliver visibly and calibrate

Your goal: provide weekly written updates and one small win that matches the brief.

• Ship to the Definition of Done. Not your version. The agreed version.
• Send a Friday status update that shows progress, risks, and asks. Template below.
• Share decisions you made and how they align to priorities. Make your thinking visible.
• Invite correction early. It is cheaper to pivot on day 10 than day 60.

Week 5–8: scale your impact

Your goal: increase scope without ambiguity.

• Propose improvements with trade-offs written out. Never dump problems. Bring options.
• Tighten stakeholder loops. Meet the people who influence your outcomes.
• Run a midpoint review. Check the original Expectation Brief still holds. Update if needed.

Week 9–12: lock in trust

Your goal: close the loop with a clear outcomes report and next-quarter plan.

• Deliver a short write-up: outcomes achieved, lessons, next-step recommendations.
• Confirm the operating rhythm that worked. Adjust for the next 90 days.
• Ask for direct feedback. Do not fish for compliments. Ask for what to do differently.

Templates and scripts you can use

1) One-page Expectation Brief (copy and adapt)

Title: [Your Name] – First 90 Days Expectation Brief

Purpose: Align how we will define success, work, and communicate.

1. Outcomes and measures

• Day 30: [Outcome], measured by [metric or milestone]
• Day 60: [Outcome], measured by [metric or milestone]
• Day 90: [Outcome], measured by [metric or milestone]

2. Priorities and trade-offs

• Priority order: [1], [2], [3]
• If X vs Y conflict, default to [X/Y]. If unsure above [impact threshold], I will check.

3. Standards and Definition of Done

• Quality bar: [e.g. no typos, stakeholder-approved, compliant with policy]
• Definition of Done: [checklist specific to your work]

4. Stakeholders and approvals

• Reviewers: [names]
• Approvers: [names]
• Inform: [names]

5. Cadence and channels

• Weekly status: Fridays, email to [names]
• Stand-ups or check-ins: [day/time]
• Channels: [Slack/email/Docs], response expectations: Me [X hours], You [Y hours]

6. Decision rights and escalation

• I decide without check on: [areas]
• I consult on: [areas]
• I escalate to you when: [conditions]

7. Risks and constraints

• Known risks: [list]
• Constraints: [budget/time/tech]
• Mitigations: [list]

Confirmation

Agreed by: [Manager Name], [Date]

2) Manager preferences checklist

Use this in week one to avoid avoidable friction.

• Communication: concise email, detailed doc, quick chat, or live call?
• Update format: bullet points, dashboard link, or narrative?
• Meeting style: agenda upfront, decisions first, or brainstorm?
• Detail tolerance: summary first or data deep-dive?
• Work style: early draft for review or finished product?
• Availability: quiet hours, off-days, time zone limits?
• Pet peeves: last-minute surprises, missed deadlines, long emails?
• Recognition: public wins or quiet note?
• Feedback: direct in the moment or scheduled sessions?

3) Weekly status update template

Subject: Weekly update – [Project/Area] – [Week ending DD MMM]

1. Progress

• Delivered: [What shipped, mapped to the Expectation Brief]
• Impact: [Metrics, customers affected, time saved]

2. Risks and blockers

• Risk: [Describe], Impact: [High/Medium/Low], Mitigation: [Action]
• Ask: [Decision needed], Deadline: [Date]

3. Next week plan

• Top 3 priorities, linked to Day 30/60/90 outcomes

4. Decisions made

• Decision: [What], Rationale: [Why], Aligned to: [Priority]

4) Definition of Done checklist (adapt to your work)

For any deliverable, confirm:

• Purpose is stated and ties to a specific outcome
• Requirements are met and acceptance criteria are ticked
• Stakeholders reviewed and approved
• Data sources cited and links provided
• Spelling, formatting, and naming conventions correct
• Risks, assumptions, and limitations are listed
• Next step or call to action is clear
• File is stored in the agreed location with version control

5) Working Agreement snippet

This is your operating rhythm. Keep it short.

• Check-in: 15 minutes, Tuesdays, agenda shared 24 hours before
• Updates: Friday status email, 12:00, standard template
• Escalation: If blocker >24 hours, alert manager with options
• Response: Slack under 4 working hours, email under 24 hours
• Meetings: Start with decisions needed, end with owners and deadlines
• Docs: Single source of truth in [folder], no attachments unless asked

Handling tough scenarios without drama

Manager is too busy or vague

Problem: your manager gives high-level guidance and no time.

Do this:

1. Draft the Expectation Brief yourself from what you know
2. Send with options, not questions: “Option A focuses on speed, B on quality. I recommend A because [reason]. Reply with A/B or add edits.”
3. Book a 15-minute slot. Show the draft on screen. Ask for yes/no on key items.
4. Capture decisions in writing. Share the updated brief immediately.

Conflicting priorities or stakeholders

Problem: multiple people ask for different things.

Do this:

• Use a simple RACI or rights model: who decides, who advises, who is informed
• Ask the manager to set the priority order in writing
• Create a one-line rule: “When X and Y conflict, default to X.”
• Summarise in email. “Per our chat, Priority order is A, B, C. I will pause C if A slips.”

Remote or hybrid specifics

Distance multiplies ambiguity. Tighten the cadence.

• Overcommunicate outcomes and decisions in writing
• Keep calendars up to date with focus time and availability
• Use shared docs. Default to links, not attachments
• Record key decisions and tag stakeholders
• Turn cameras on during alignment meetings to read cues

When things go wrong: reset fast

You will misread something. It is fine. Silence is not.

• Flag the gap early. “I see a mismatch between what I delivered and what you expected. Here is what I think caused it. Here are three options to correct. I recommend B.”
• Ask for a reset. Update the Expectation Brief if needed
• Show the fix within 48 hours if feasible

Signals you are on track (and off track)

On track:

• Your manager uses your updates to brief others
• You get faster responses and more autonomy
• Stakeholders ask for your input early, not after the fact
• Fewer “quick chats” about missed details

Off track:

• Rework requests become frequent and vague
• Deadlines creep without clear decisions logged
• You are surprised by feedback others saw coming
• Your manager starts checking in more, not less

How to set expectations on day one without sounding pushy

Use simple, confident language.

Try this approach in your first 1:1:

“ I want to make sure I deliver exactly what you need. Can we align on three things: the outcomes that matter in my first 90 days, the priorities when things collide, and how you prefer updates? I will write it up so we both have a clear reference.”

Then follow through. Always write it up.

Master the art of asking for a decision

Managers hate long problems with no options. Become the person who frames decisions.

Use the 2x2 message:

• The decision: what you need and by when
• The options: A, B, C with one-line pros/cons
• Your recommendation: A or B, and why
• The risk of doing nothing: clear and bounded

Example:

Decision: pick the launch date by Wednesday.

Options:

• A: Launch next Tuesday. Pro: faster impact. Con: lower QA coverage.
• B: Launch in two weeks. Pro: stronger QA. Con: slower impact.
• C: Split launch. Pro: mitigate risk. Con: extra coordination.

I recommend B because the risk profile is safer for first release.

If we do nothing: we slip into the holiday week and lose momentum.

Set expectations on quality without guesswork

Quality is not subjective if you define it. Borrow your manager’s brain with a quick calibration exercise.

• Find a previous deliverable your manager liked. Ask why it was good
• Find one that missed. Ask what was off
• Turn the answers into a checklist. Include style, depth, and the must-not-miss items

Your job is not to be perfect. It is to be predictable.

Protect your time with priority rules

You will be pulled into low-value work. Partner with your manager to defend your focus.

• Agree rules like:
• If asked to do X that conflicts with an agreed priority, reply with the trade-off and ask for a call. “Happy to take X. That will move Y to next week. Is that okay?”
• If a task takes more than 2 hours beyond estimate, flag it early
• If two stakeholders disagree, escalate with both copied. Do not mediate alone

Create proof you can point to

Verbal alignment is not alignment. You need receipts.

• After every decision, send a two-line summary in the channel you agreed
• Store the Expectation Brief and decisions in a shared folder
• Reference them in your updates. “Per the brief, Priority 2 is paused for Priority 1.”

This is professional, not political. It protects you and your manager.

First-time job seeker? Read this twice

If this is your first role, expectation setting is your superpower. It compensates for lack of experience.

• Ask for examples. “Can you show me a version of this done well?”
• Share early drafts. Invite feedback before you overinvest
• Repeat back what you heard. Then write it up
• Never be embarrassed to ask, “What does good look like here?”

The pitfalls to avoid

• Vague commitments: “I will try” is not a plan
• Hidden work: if your manager cannot see it, it did not happen
• Overpromising: a missed promise costs trust for weeks
• Late escalation: do not protect your manager from reality. They need time to help
• Drifting scope: always tie tasks back to outcomes

Career accelerators: do these and you will stand out

• Pre-mortems: ask, “If this fails, what would have caused it?” Then mitigate
• Demo days: show progress live, not just reports
• One metric that matters: pick a measurable outcome and improve it weekly
• Teach-back: summarise complex topics to your manager in one page. This proves understanding

A simple cadence that compounds trust

Use this weekly structure in your first 90 days:

Monday

• Confirm priorities in writing. “Top three for this week are A, B, C.”
• Ask for missing inputs. Do not wait until Thursday.

Mid-week

• Share a quick progress note if anything moved
• Proactively flag risks and propose options

Friday

• Send the weekly status update using the template
• Share a small win with evidence. Screenshots, numbers, or stakeholder feedback

Monthly

• Book a 30-minute review. Update the Expectation Brief if priorities shifted

Managing up is not political. It is operational excellence

The best people make their manager’s job easier. That is not flattery. It is leverage.

• Give your manager artefacts they can forward without editing
• Turn chaos into clear options
• Anticipate questions and answer them in your update
• Protect their time by making your asks crisp

What to do if expectations are unfair

Sometimes the workload or timeline is unrealistic. Push back with facts and options, not emotion.

Use this structure:

• State the goal everyone wants
• Show the constraint with numbers
• Offer two or three options with trade-offs
• Ask for a decision and record it

Example:

Goal: deliver the report by Friday at the agreed quality.

Constraint: current data access is delayed by 3 days, which removes 40 percent of our analysis window.

Options:

• A: Deliver a lighter version by Friday. Con: lower depth.
• B: Deliver full depth next Wednesday. Con: later impact.
• C: Split delivery: summary Friday, full report Wednesday.

Request: approve B or C today. I recommend C to maintain momentum and quality.

How to get feedback that actually helps

Vague feedback wastes time. Ask specifically.

• “What is the one thing you would change if you were me?”
• “On a scale of 1–10, how close is this to what you expected? What would make it a 10?”
• “If this is off, where did the misread happen: scope, quality, or timing?”

Hard reset checklist if trust is wobbling

If you feel misaligned, use this 24-hour reset plan.

• Book a quick call: “I think we have a gap in expectations. Can we reset?”
• Bring a one-page gap analysis: expectation vs what happened vs fix
• Confirm the new plan in writing
• Deliver a visible win within one week

Quick implementation plan

• Today: book the alignment meeting and draft your Expectation Brief
• This week: agree your Definition of Done, cadence, and decision rights
• Friday: send your first weekly status update
• Week 2: deliver a small win tied to Priority 1
• Week 4: run a midpoint review and adjust the brief
• Week 8: expand scope with clear trade-offs
• Week 12: close the loop and set up the next 90 days

Final word

If you only remember one thing, remember this. Setting expectations with your manager is not a one-time conversation. It is a system. Write it down. Review it regularly. Update it as reality changes. Do this and your first 90 days will not be a blur. They will be a springboard.

You do not need permission to be clear. You just need to start.

Next Steps

Want to learn more? Check out these articles:

Personal SWOT for Career Planning: Map Strengths, Fix Gaps

Must-Have Soft Skills Employers Seek for 2025 Success

Mastering Professionalism: Your Guide to Workplace Success

Check out our Advanced Employability Course for all the help you need to get your dream job, fast.