How to Set Expectations with a New Manager

A new manager arrives with their own habits, priorities, and questions about the team. You arrive with your own assumptions about what good work looks like. Early conversations can close that gap. The goal is not to negotiate a promotion or to test the manager’s judgment. It is to agree on a few working arrangements that let both of you do your jobs without guessing. This guide walks through five questions to ask in the first weeks, and a simple way to review the arrangement later.

A practical example

Bring one piece of current work to your first conversation with a new manager. Five questions about a real deadline can settle more than a general discussion of communication styles.

  1. Priority: “If I can finish the supplier brief or the reporting cleanup this week, which should come first?”
  2. Updates: “Would a Friday note with the brief’s status and open decisions be useful, or do you need something sooner?”
  3. Authority: “Can I approve wording changes myself? Who signs off on a change to the quoted price?”
  4. Escalation: “If the supplier misses Thursday’s cutoff, should I call you then rather than wait for the Friday note?”
  5. Feedback: “Could we look at my first update together and decide what to keep or drop?”

Afterward, write back what you heard, not what you hoped to hear. A recap might read: “The brief comes first. I’ll handle wording changes and send price changes to you. I’ll call if Thursday’s cutoff slips; otherwise you’ll get a short update on Friday.” If the manager corrects a detail, you have found the misunderstanding before acting on it.

Handle disagreements early

You may find that your expectations and the manager’s do not match. Raise the difference calmly and early, before it grows into a pattern of missed updates or unmet requests. Describe what you understood, what you were prepared to do, and what would help you meet the manager’s needs. A short, respectful conversation at this stage is far easier than a difficult discussion months later.

Try the agreement on real work and set a short review date. Bring the first update to that review and ask which line helped the manager make a decision. If nobody used the rest, you have a reason to send a shorter note next time.

Ask about priorities first

Begin by asking what the manager most needs from your role over the next quarter. Their answer may differ from the priorities in your job description, and that difference is worth knowing early. Ask which projects matter most, which ones can wait, and what success would look like by the end of the period. If the manager is still forming a view, ask when they expect to have one, and offer to bring a draft list of your current work to the next conversation.

Write the answer down in a short note. Priorities often change, and a written record makes it easier to see whether the shift came from you, from the business, or from a misunderstanding.

Agree on how you will share updates

Every manager has a preferred rhythm for updates. Some want a short written note each week, while others prefer a standing meeting or a message only when something changes. Ask which format they want, how much detail is helpful, and whether they want to hear about small wins or only about risks. Agreeing on this early saves both of you from the frustration of too little information or too much.

Offer a sample update in the format you suggest. A concrete example makes the agreement easier to test, and the manager can correct it immediately if it does not fit their needs.

Clarify decisions and escalation

Ask which decisions you can make on your own, which ones need a quick check, and which ones should come to the manager before anyone else hears about them. Ask how the manager prefers to be contacted when something urgent happens, and what counts as urgent for them. A clear escalation path protects you from surprises and helps the manager trust that problems will reach them in time.

Be specific with examples. A question such as “Should I approve a vendor change under a certain amount?” is more useful than a general question about authority.

Learn how feedback will work

Early feedback is an opportunity to set the pattern for the relationship. Ask how the manager gives feedback, whether they prefer to give it in private or in a group setting, and how you can ask for it when you need it. You might say, “When you have a moment, I would like to know what is working and what I could change.” This makes it normal to request input without waiting for a formal review.

Also ask how the manager prefers to receive your concerns. Some managers want to hear about problems as soon as they appear, while others want to see a proposed solution first.

Set a review point

Agreements work best when you check them. Propose a short review after three or four weeks. Use the conversation to ask what is working, what is not, and whether any part of the arrangement needs to change. Keep the review focused on practical adjustments rather than on judging the manager’s style. If a commitment is too heavy, reduce it. If a meeting feels unnecessary, suggest replacing it with a shorter note.




How to Compare Two Job Offers Beyond Salary

One offer pays more; the other gets you home in time for a commitment you can’t move. Decide first which conditions are nonnegotiable. Then compare what the remaining differences are worth to you, and mark anything you still need the employer to confirm in writing.

A practical example

Suppose Offer A pays $66,000 and requires three office days each week. Offer B pays $62,000 and lists one office day. The $4,000 difference is real. So are the two extra trips. Before giving either offer a score, check whether its required hours fit the commitments you cannot move.

Questions behind the two example offers
Item What to compare What to confirm
Pay Guaranteed base separately from bonuses or commission. Which payments are conditional, and when are they payable?
Office time At $15 per round trip over 48 working weeks, two extra trips a week cost $1,440 a year. Are those office days fixed, and could the requirement change?
Benefits Your contribution, eligibility date, and coverage you would actually use. Can you see the written plan summary?
Development The work you would own and who would review it. What did a recent hire learn in the first six months?

Do not simply subtract $1,440 from $4,000 and call the difference take-home pay. One figure is an estimated out-of-pocket expense; the other is salary before deductions. Run the comparison with your own commute, hours, and expected take-home amounts. Keep travel time visible even if you prefer not to put a dollar value on it.

Mark each important condition as written, discussed, or unknown. If B works for you only with one office day, ask for clarification before turning down A. A scorecard can help choose between two workable offers. It should not turn an unconfirmed promise into a reason to accept one.

Identify your nonnegotiables

Begin by listing the conditions you must have. These might include a maximum commute, a need for predictable hours, a minimum salary, or a role that builds a specific skill. Keep the list short, usually three to five items. Nonnegotiables provide a clear test: if an offer fails one of them, you can set it aside without reopening the whole comparison.

Separate nonnegotiables from preferences. A preference, such as a larger title or a newer office, is worth noting, but it should not outweigh the conditions you truly need.

Compare pay in full

Write down the base salary for each offer, then add any guaranteed bonus, commission structure, or allowance that is clearly stated. Treat variable pay with caution. A bonus that depends on targets you cannot control is not the same as a fixed amount. Compare the two offers on the same basis, such as annual gross pay, so the numbers are consistent.

Check the pay schedule and any probation terms. A slightly lower salary with a clear review date may be more valuable than a higher offer with uncertain terms.

Weigh flexibility

Flexibility can take many forms: adjustable start and end times, the ability to work from home, time off for family needs, or the freedom to attend personal appointments without losing pay. Describe what a normal week would look like under each offer. If one employer requires attendance five days a week and another allows two days at home, estimate the hours saved on commuting and the effect on your routine.

Do not assume that a stated policy will always apply. Ask how the policy works in practice, especially for new employees.

Assess growth and learning

Think about what you will learn in the first year. Does the role give you responsibility, mentorship, or exposure to new tools? Consider whether the position moves your career toward the work you want to do. A role that builds useful skills can create options later, even if the starting pay is modest.

Ask who you would work with and how they develop people. A manager who gives regular feedback can shape your progress more than a single line on the offer letter.

Look at benefits as employer-specific

Benefits differ widely. Health coverage, retirement contributions, leave policies, and training budgets may look similar on paper but work differently in practice. Ask for the actual summary documents, and do not rely on a general description of what a benefit usually includes. Where a detail matters to your decision, verify it with the employer and keep a written record of the answer.

Count the costs you do not see in the offer

Include the cost of commuting, work clothing, childcare, equipment, and meals. A higher salary can shrink quickly if the job requires a long drive or expensive daily travel. Estimate these costs for each offer, and subtract them from the pay to see the more complete difference.

Confirm the open questions in writing

Before you decide, ask each employer about anything still unclear. Useful questions include how performance is reviewed, what the probation period involves, and when the role may change. Request written confirmation of important points, such as the start date, pay schedule, and any remote work arrangement. Written details protect both sides and prevent misunderstandings later.

Make the decision with a simple scorecard

Create a short table with your nonnegotiables and the other factors you care about. Score each offer on a consistent scale, then review the totals alongside your gut reaction. A scorecard does not replace judgment, but it makes trade-offs visible. If one offer wins on pay and the other wins on flexibility and growth, you can see exactly what you would be giving up.




How to Prepare for a Job Interview with Three Work Stories

Pick three moments from your work that you could explain without notes: a problem you solved, a decision you made with someone else, and something that didn’t go as planned. For each one, be ready to say what you personally did and what happened afterward. Practice choosing the right story for a question rather than memorizing three speeches.

A practical example

Three interview stories should give you three things to talk about, not three ways of saying you work hard. Sketch them on separate cards. Here is an illustrative set for someone applying for an operations role:

  1. A problem you solved. Two shifts kept ordering the same supplies. I checked the order history and added an “already ordered” field to the shared sheet. The team could see outstanding orders before placing another.
  2. A decision you shared. Dispatch wanted a firm pickup time; packing wanted room for late orders. I asked each team which cutoff it could actually meet. We agreed on one regular pickup and a separate process for exceptions.
  3. A miss you learned from. I sent a customer an estimate before confirming the delivery address. The shipping charge changed. I called to correct it and added the address to my intake questions.

Use moments from your own experience. Notice what the first example does not say: there is no invented percentage for spending reductions. If you can document savings and are free to share them, explain how you measured them. Otherwise describe the change you actually saw. Separate your contribution from the team’s and leave out identifying client details.

Match each story to likely questions

Review the job description and note the skills it emphasizes. Then decide which story best fits each skill. A story about a difficult client may suit a question about handling conflict, and a story about a process change may suit a question about improvement. Matching in advance helps you choose quickly during the interview.

Ask a practice partner to interrupt with “Why did you choose that?” or “What happened next?” If your answer depends on remembering the next sentence of a script, put the script away. Keep only the situation, your choice, and the outcome on the card.

Choose stories from real work

Use examples from your actual experience. Choose situations you were involved in, and be careful about confidential information. Do not reveal private client details, internal figures that are not public, or the business plans of a former employer. If a detail is sensitive, describe the situation in general terms. A truthful story with the specifics removed is better than an impressive story that cannot be verified.

Avoid inventing numbers. If you do not know the exact figure, say “about” or describe the change without a precise measure. An interviewer may ask follow-up questions, and a story that cannot survive them will hurt your credibility.

Pick three different types of situation

Aim for variety. One story might show a difficult problem you solved, another might show how you worked with a team, and a third might show a time you learned from a mistake or handled a change. Variety helps you answer a range of questions without repeating the same example. Make sure each story is relevant to the role you want, not only to your current job.

Describe the situation briefly

Begin each story with enough context for the listener to understand the problem. Name the situation, the people involved, and what was at stake. Keep this part short. Two or three sentences are usually enough. A long setup delays the part the interviewer wants to hear: what you did.

Choose a structure you can remember, such as situation, task, action, and result. The structure gives you a reliable path through the story, even when the interviewer interrupts with questions.

Explain your actions specifically

The action section should describe what you personally did. Use “I” where it is accurate, and avoid hiding your role behind “we.” Explain the decisions you made, the steps you took, and why you took them. Specific actions help the interviewer picture how you would perform in the new role.

If the team made a decision, explain your contribution to it. Describe what you proposed, what you changed, or what you took responsibility for.

Describe the result honestly

End with what happened. A result can be a measurable outcome, a change in process, a lesson, or a problem that was reduced. If the result was partial, say so. An honest account of a mixed outcome, with a clear explanation of what you would do differently, often impresses interviewers more than a story with no complications.

Rehearse a concise version

Practice each story aloud, aiming for about one to two minutes. The goal is not to memorize every word. It is to know the main points well enough to tell the story naturally. Time yourself, and notice where you lose focus or add unnecessary detail. Cut anything that does not help the listener understand the action or the result.

Also prepare a shorter version of each story, about thirty seconds long, for interviews that begin with a quick question. The short version should still include a clear result.




How to Write a Meeting Recap That Leads to Action

A meeting recap is useful only if people read it and know what to do afterward. A transcript records everything that was said, which is rarely what the team needs. A better recap focuses on the decisions made, the people responsible for next steps, the dates that matter, and the questions still open. This guide explains how to write a recap that supports action rather than simply documenting the conversation.

A practical example

If you missed the launch meeting, which note would help you get back to work: “Printer deadline discussed,” or this one?

Subject: Launch booklet | Tuesday proof deadline

We agreed to print the eight-page version. A longer booklet would need a second round of proofs, and we want copies for Friday’s event.

Maya: Send the eight-page proof to the printer by noon Tuesday. Lee: Check the delivery address with the venue by Monday afternoon and send it to Maya.

Still open: Can the printer deliver before the doors open? Maya will ask when she sends the proof. Until we hear back, please don’t promise copies at registration.

Notice what the note leaves out: who first proposed twelve pages, how long the debate lasted, and who changed their mind. It keeps one piece of history: why eight pages won. That’s the detail someone will need if the longer version comes up again.

When the meeting didn’t settle it

A recap can accidentally turn a suggestion into a commitment. If Lee offered to check the address, don’t write that Lee agreed to arrange delivery. If nobody took the job, say so: “Delivery still needs an owner. Maya will raise it at Monday’s check-in.” Only name Maya if she agreed to do that. A visible gap is easier to fix than a task everyone assumes someone else is doing.

Send the note while people can still correct it. Put it where the team keeps the project, share it with the people affected, and invite corrections to the decisions, names, or dates. When the printer replies, update the open item in that same place. Nobody should have to reconstruct the decision from three inboxes.

Write the recap within a day

Send the recap soon after the meeting, while the discussion is still fresh. A recap sent a week later may be accurate, but people will have moved on, and the decisions may be harder to recall. If you cannot write a full version immediately, send a brief note with the decisions and owners, then add the detail later.

Keep the length short. Most meeting recaps can be read in two or three minutes. If the discussion covered several topics, group the notes by topic so the reader can find the part that concerns them.

Summarize the decisions first

Begin with the decisions. Write each one as a complete sentence that states what was agreed. For example, “We will move the launch review to the second Tuesday of the month” is clearer than “Launch review discussed.” Decisions are the most important part of the recap because they change what people do.

If the group considered an option and rejected it, record that briefly as well. A note that says why an alternative was not chosen can prevent the same discussion from returning in the next meeting.

List owners and dates

Every action should have one owner. A task assigned to “the team” often belongs to no one. Name the person responsible, describe the action in a few words, and include a date if one was agreed. If a date was discussed but not confirmed, mark it as provisional so the reader knows it can still change.

A simple table or list works well for this section. Keep each row to four elements: the action, the owner, the date, and the status. People can scan that structure quickly, which makes it easier to follow up.

Flag unresolved items

Some questions will remain open after the meeting. Record them clearly and say who will bring the answer back. Unresolved items are not failures; they are part of the work. The problem arises when they disappear from the notes and reappear later as surprises. A short section titled “Open questions” helps the group return to them deliberately.

If an item needs a decision by a certain date, say so. A reader who sees a deadline attached to an open question is more likely to respond before it becomes urgent.

Leave out the transcript

Avoid recording every comment. A transcript-like recap makes it hard to see what matters and tempts readers to skim. Include the context needed to understand a decision, such as a constraint or a trade-off, but leave out the back-and-forth that did not change the outcome. If someone needs the full conversation, offer a recording or notes available on request.

Be careful with sensitive remarks. A recap is a shared document, so describe disagreements neutrally and avoid attributing personal opinions unless they affect a decision.

Confirm before you send

Before sending, check that each owner agrees with their assignment. A quick message to the people named can prevent confusion later. If someone says they cannot take on a task, update the recap and note the change. This step takes only a few minutes, and it turns the recap from a summary into a commitment.




How to Ask for Feedback You Can Actually Use

Feedback is most useful when it describes something you can see, hear, or change. Yet many requests for feedback are vague: “What do you think?” or “Any comments?” These questions invite general praise or a reaction that is hard to act on. A better question points to one moment, asks for an observation, and invites a small experiment. This guide uses an example unrelated to performance ratings, such as a draft email, a short presentation, or a project plan, to show how the same approach works in everyday work.

A practical example

“Does this look OK?” is a difficult favor to do well. The recipient has to guess whether you want proofreading, encouragement, or a reason to change direction. Compare these two requests about the same proposal:

“Can you review this before Friday?”

“Could you read the pricing paragraph by Thursday? Without looking at the table, tell me which revisions you think the fee includes. I’m deciding whether the table needs to move up.”

The second request tells your colleague where to look, what to report, and which decision is still open. It doesn’t tell them which answer you hope to hear. If they say “two rounds” and you meant one, you’ve learned something useful without asking anyone to rate your writing.

When the answer is vague

Suppose your colleague replies, “Seems fine.” Instead of pressing for criticism, try “If the client asks for a third draft, would you expect a new charge?” If they found the answer immediately, ask which words settled it. If they had to guess, ask where they looked first. Either reply is more useful than another verdict.

The observation and the proposed fix are different things. A reader who missed the revision limit might suggest rewriting the whole proposal. You can take the observation seriously and try a smaller edit: move the limit next to the price. Ask a fresh reader the same question before deciding you’ve fixed it.

Ask while you still have time to act. If the price is settled and the proposal goes out tomorrow, say so. Five minutes spent checking whether the terms are clear is a fairer request than inviting a colleague to rethink a decision you cannot reopen.

Pick one specific moment

Start by choosing the part of the work you want help with. Instead of sending an entire document, identify a paragraph, a slide, a decision, or a single exchange in a meeting. Specific requests give the other person something concrete to examine. For example, “Could you look at the opening paragraph of this proposal?” is easier to answer than “Could you review the proposal?”

Explain briefly what you were trying to achieve in that moment. A sentence of context helps the reader understand whether the section is doing its job.

Ask for an observation

An observation describes what happened. A verdict judges whether it was good. Ask for observations because they are easier to use. “When you read the opening, where did your attention drift?” asks for a direct reaction. “Is the opening good?” invites a simple yes or no, which tells you little about what to change.

Observations also reduce the pressure on the reader. People are often more willing to describe what they noticed than to pass judgment on your work, and the descriptions usually contain the clues you need.

Name the decision you need to make

Tell the reader what decision the feedback will help you make. Are you deciding whether to shorten the section, change the order, or keep a particular example? When the purpose is clear, the other person can focus their attention on the question that matters, and you can judge their response more quickly.

If you have already made a choice, say so. Feedback on a settled decision may be less helpful than feedback on the part you are still unsure about.

Make it easy to answer

Reduce the effort required to respond. Give a deadline that fits the reader’s schedule, specify how much time you need, and offer to discuss the result in a short call if that is easier. If you can, send the material with a clear question at the top. A reader who can answer in five minutes is more likely to give thoughtful feedback than one who must find an hour.

Listen for what is not said

Sometimes the most useful feedback is an absence: a reader skipped a section, asked a question you did not expect, or rushed through a paragraph. Notice those signals. If someone says the section is fine but seems confused when you discuss it, ask a follow-up question such as “Which part felt least clear?” That question often reveals the real issue.

Avoid defending the work while the other person is speaking. Your job during the conversation is to understand their view, not to justify each choice.

Try one change before asking again

After you receive feedback, choose one change to test. Changing everything at once makes it hard to know which edit helped. Make the change, then ask a specific follow-up question about the same moment. This creates a useful loop: request, observation, one adjustment, and a second look.

Thank the reader for their time, and tell them what you changed based on their input. People are more willing to help again when they see that their observations were taken seriously.




How to Rehearse a Presentation in 20 Minutes

Set a timer for twenty minutes and say the opening of your talk aloud. If you stumble, don’t spend the whole session polishing the first sentence. Save time for the transition you keep losing and for the last thing the audience needs to hear.

A practical example

For a ten-minute briefing, set aside twenty minutes and use a clock you can see while speaking. The aim is to find the part you need to change, not to deliver the same talk twice.

  1. Minutes 0 to 2: Find your opening. Say the first few sentences aloud. If you need a minute of background before the audience hears why they are there, try beginning with the decision or question instead.
  2. Minutes 2 to 12: Run the briefing. Stand or sit as you will on the day, advance your slides, and keep talking if you miss a word. When the ten minutes end, mark where you are. If you never reached the request, you have found a timing problem that faster talking is unlikely to solve.
  3. Minutes 12 to 17: Repair one rough spot. Cut a repeated example or practice a transition that gave you trouble. Say the sentence on each side of it aloud. “That is what the shorter booklet saves. Here is what we would leave out” makes a shift in the argument audible even to someone who cannot see the slide.
  4. Minutes 17 to 20: Land the ending. Start on the next-to-last slide and deliver the close. Name the decision or action, then stop. Note the one thing you still need to check, such as whether the chart is readable from the back of the room.

Giving a forty-minute talk? Use the ten-minute run for the hardest section and book a separate full-length rehearsal. Timing one section cannot tell you whether the whole talk fits. And if the projector or microphone is unfamiliar, arrange a room check rather than spending your only speaking practice on the equipment.

Treat the timing as a suggested routine

The twenty-minute plan below is a practical starting point, not a standard that every presentation must meet. A short briefing may need only one pass, while a longer talk may need several. Use the routine to create a habit, then adjust the steps to fit the length of your talk, the room, and the level of detail your audience expects.

If you have a fixed time limit, check your rehearsal against it. Going over the time allowed is a common problem, and a practice run is the best place to find where the extra minutes are going.

Rehearse the opening first

Begin by practicing the first two minutes. The opening should tell the audience why the topic matters and what they will gain from listening. Say it aloud, standing as you will in the room, without reading from notes. If you stumble, shorten the sentences rather than trying to recite them perfectly. A clear first minute is usually more valuable than a polished joke or a long introduction.

Record yourself if you can. Listen for whether the main point arrives early, and whether the audience has a reason to keep paying attention.

Time a full run

Once the opening feels steady, run the entire presentation from start to finish without stopping. Use a timer and do not correct yourself mid-sentence unless you lose the thread completely. Note where you ran long, where you rushed, and where a slide took more time to explain than you expected. A full run shows the rhythm of the talk, which a section-by-section practice cannot reveal.

Keep a simple record of the total time and the three longest sections. Those notes will guide the next revision more reliably than your memory of how the talk felt.

Practice the transitions

Many talks lose their audience between sections, not inside them. Practice the sentence that moves from one point to the next, and make sure it names the connection. For example, “That is the cost side. Now let’s look at what the change would save” tells listeners where the argument is heading. If a transition is hard to say, the connection between the sections may be weak, and the slides may need reordering.

Look at each slide during this step and ask whether it supports the sentence you just said. A slide that does not connect to the transition may be a candidate for removal.

Tighten the close

End with a short summary of the main message and one clear action or question. Rehearse the final thirty seconds until you know exactly how you will finish. Do not let the talk trail off with “that’s about it.” A deliberate close tells the audience that the presentation has reached its end, and it leaves them with the point you most want them to remember.

Check the environment and the equipment

During a practice session, test the same equipment you will use on the day. Confirm that the clicker, laptop, microphone, and display work, and that your slides open in the expected order. If the room has an unfamiliar layout, consider how far you will stand from the screen and whether you will need to face the audience while advancing slides. These details are small, but they can change your pace and confidence.