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.




How to Build a Presentation Around One Clear Message

Many presentations fail because they try to say too much. Each slide may be accurate, yet the audience leaves without a clear idea of what mattered. A strong presentation starts with one message that the audience should remember tomorrow. Everything else supports that message, and anything that does not can be cut. This guide explains how to build a presentation around one clear takeaway before you worry about slide design or rehearsal.

A practical example

Topic: The print budget. Message: Approve the shorter booklet today so the printer can deliver it before the event. Both describe the same presentation. Only one tells you what belongs on the slides.

Build the talk backward from the decision

Imagine your audience is the event committee. They know why the booklet matters; what they need to know is whether eight pages will do the job. Open by showing the proposed booklet beside the longer version. Point to what stays: the schedule, map, and contact information. Show what goes: three speaker profiles that are already online. Then show the printer’s deadline. The audience now has a trade-off to consider, not a stack of background slides to decode.

A different audience needs a different talk. The designer implementing the decision needs to see which pages come out and who signs off. The committee voting on it needs the cost, timing, and consequence of saying no. Use information you can substantiate: a current quote from the printer beats an estimate presented as fact.

What earns a slide?

Try removing the slide and saying the argument aloud. If a listener can still follow it and make the decision, keep the slide for questions or leave it out. If the decision depends on a condition, keep that condition visible. “Eight pages will arrive by Friday if we approve the proof on Tuesday” is a more useful claim than “Eight pages will arrive by Friday.”

Write the closing sentence before you design the title slide. In this case it might be: “Can we approve the eight-page version today and give Maya authority to sign the proof?” If that isn’t the decision the audience can make, change the talk while it’s still an outline.

Name the audience

Begin by describing who will be listening and what they already know. A group of new customers needs different examples from a group of managers who are deciding on a budget. Write down the audience’s main concern, the decision they face, and the level of detail they expect.

Keep the description concrete. “Small business owners who handle their own bookkeeping” gives you a clearer target than “business people,” and it helps you choose examples that feel relevant.

Write one takeaway

Write the takeaway as one sentence the audience could repeat to a colleague. It should state what they should believe or do after the talk. For example, “A monthly cash review catches shortfalls early” is a takeaway. “Cash flow is important” is a topic, not a message.

Test the sentence by asking whether a skeptical listener could disagree with it. If the message is so broad that no one could disagree, it may not be specific enough to guide the presentation.

Build a simple structure

Once you have the takeaway, outline the presentation in four parts: the problem the audience recognizes, the reason the takeaway matters, the evidence or example that supports it, and the action they can take next. This structure keeps the talk moving toward the message rather than wandering through background details.

Give the opening enough context to earn attention, but do not spend the first few minutes on general history. Move to the problem quickly, because the audience will judge the talk by how soon it becomes relevant to them.

Use an original example

Support the takeaway with an example that you can explain in your own words. Describe a specific situation, the decision that was made, and what happened afterward. If the example involves another person’s work, credit it and avoid reproducing long passages or images without permission. A concrete story is usually more memorable than a list of abstract claims.

Choose one main example rather than several weak ones. A second example can help if it shows a different condition under which the message still applies, but too many examples can hide the point.

Cut the slides that do not support it

Review each slide and ask one question: does this help the audience believe or act on the takeaway? If the answer is no, remove it, move it to an appendix, or save it for a question. This step is often the hardest because the material may be interesting. Interesting is not the same as necessary.

Look for repeated points as well. Two slides that make the same argument in different words usually need to become one.

Check the message before you design the slides

Read the outline aloud and check whether each section moves toward the takeaway. Replace vague headings with statements that carry meaning, such as “Monthly review finds problems earlier” rather than “Our process.” The slides can then follow the structure and reinforce the message.

Only after this check should you design the visuals. Simple charts, large text, and one idea per slide make the message easier to follow. Rehearsal techniques and delivery details can come later, once the content is clear.




How to Recommend a Book or Worksheet Without the Hard Sell

A good recommendation helps a reader take the next step. It names a resource that fits a real task, explains what the resource adds, and leaves the decision to the reader. A hard sell does the opposite: it hurries the reader, overstates the benefit, and hides the cost. This guide shows how to recommend a book, worksheet, template, or tool in a way that keeps the article useful on its own.

A practical example

“Write down each bill, its due date, and the balance available that day.” That is advice the reader can use in a notebook. A paid worksheet is worth mentioning only if you can explain what it adds. Here is how that could sound when the author earns a commission:

“If you want the running balance calculated for you, this worksheet includes a formula for it. You’ll need spreadsheet software that can open the file. I earn a commission if you buy through this link. If you only have a few bills to track, the notebook method above may be all you need.”

The recommendation earns its place by answering a specific question: is the formula worth paying for? Before making that claim about a real worksheet, open the current version, enter a bill, and check the total. For a book, name the chapter or exercise that helped with the task. If you have read only a sample, do not imply you reviewed the whole book.

What the reader needs to know about the recommendation

In the U.S., the FTC endorsement guides on material connections call for clear, conspicuous disclosure of a connection that could affect the endorsement’s credibility and that the audience would not reasonably expect. A commission is one example; a free review copy or a relationship with the seller may also matter. State the actual connection near the recommendation, in language readers can understand before they choose the link.

Check the destination when the edition, format, or price changes. If the exercise that made the book worth recommending disappears from the new edition, change the recommendation, not just the link.

Start with the reader’s task

Recommend a resource only after the article has already helped the reader with the main problem. The article should be complete without the recommendation. A reader who has a specific task, such as tracking expenses or preparing for a conversation, is more likely to find a resource helpful than a reader who has only been asked to buy something.

Describe the task in the reader’s words. For example, “If you want a simple way to record recurring bills, a monthly worksheet can help” is more useful than a vague statement that the reader should improve their finances.

Explain what the resource adds

Say what the resource does that the article does not. Perhaps it provides blank forms, a longer walkthrough, or a structure for practice. Be specific about the content, and avoid claims about results the resource cannot guarantee. A worksheet can help a reader organize information, but it does not replace professional advice when a decision has legal or financial consequences.

If the resource covers a limited topic, say so. Honesty about scope builds trust, and it helps readers decide quickly whether the resource is worth their time.

Offer one optional link

Include one clear link, labeled so the reader knows where it goes and what it contains. Mark it as optional. A single well-placed recommendation is easier to evaluate than several links competing for attention. If you have more than one useful resource, choose the one that matches the article’s main task and mention the others only if they are truly necessary.

Place the recommendation near the point where the reader would need it, usually after the main explanation. A link at the top of an article can feel like an interruption.

Disclose relationships clearly

If you earn a commission, received the resource free, or have a personal or business relationship with its creator, disclose that relationship near the recommendation. Use plain language, such as “I receive a commission if you buy this book,” rather than a vague note at the bottom of the page. Disclosure rules depend on your location and the type of relationship, so check the current guidance that applies to you.

Even without a financial relationship, say when you recommend a resource you have not used yourself. Readers can weigh the advice better when they know what you have tested.

Avoid pressure and false urgency

Avoid phrases that suggest the reader will fail without the resource, or that a limited-time offer will disappear. Such language may increase clicks but reduces trust. Let the article make the case, and let the resource stand on its own usefulness. If a discount exists, state the terms clearly and do not imply scarcity that is not real.

Check that the resource is current. A book with an outdated method or a worksheet with old rules can mislead readers even when the recommendation was sincere.

Review the recommendation after it runs

Look at how readers respond over time. Do they click the link, return to the article, or ask questions that suggest the resource was not what they expected? If readers feel misled, revise the description or replace the recommendation. A resource that fits the article well will usually need little pressure to be useful.

A respectful recommendation is brief, specific, and optional. It respects the reader’s intelligence and leaves the next step to them, which is usually the approach that serves readers and your credibility best.