Real emails for hard situations

Hi Marcus, I wanted to follow up on our conversation from last week and put the key points in writing. Your performance over the past quarter has not met the expectations for your role. Specifically, the client deliverables for the Horizon project were submitted late on three occasions, and the quality review on the September report required significant revision. These issues have put additional pressure on the team and have been noted by the client. I'd like to establish a 60-day performance improvement plan beginning November 1st. The plan will include bi-weekly check-ins, clearer milestones on your current projects, and additional support from your team lead. By the end of the 60 days, I expect consistent on-time delivery and quality that meets the standards we've discussed. I want to be direct: this is a serious conversation, and the outcome of this plan will inform decisions about your role going forward. Please confirm you've received this email and let me know if you'd like to talk before we formalize the plan. — Jordan

Hi Sarah, Thank you for the proposal you sent over last week. I can see the thought and effort that went into it, and I appreciate you taking the time. After reviewing it with the team, we've decided not to move forward. The scope and budget don't align with what we're planning for Q1, and we don't want to commit to a project we can't resource properly. I hope this doesn't close the door on working together — there may be a better fit down the road. I'll keep your proposal on file. Thanks again for the work you put into this. Best, Alex

Hi Claire, I want to flag something before we get further into Phase 2. Over the past two weeks, we've absorbed three scope additions: the revised dashboard UI, the export feature, and now the API integration with your CRM. None of these were in the original brief. I want to keep delivering quality work for you, but I need to be honest: the current scope is about 35% larger than what we scoped and budgeted together. If we continue without adjusting, we'll either miss the deadline or compromise the quality of the core deliverables. I'd like to have a quick call this week to either reprioritize what's in scope for this phase, or discuss a scope amendment with updated timeline and budget. I'm not trying to be difficult — I want this project to succeed. But I owe you the honesty that we can't absorb these additions without an impact. Talk soon, David

Hi Tom, I'm reaching out about Invoice #1042 for $4,800, which was due on October 15th — it's now 30 days past due. I understand things can slip through the cracks, and I'd like to give you the benefit of the doubt. If there's an issue with the invoice or the payment process, please let me know and I'll get it resolved quickly. If payment has already been sent, please disregard this note and let me know so I can check on it from my end. Otherwise, I'd appreciate payment by November 20th. You can pay via bank transfer using the details on the invoice, or reply here and I can send a payment link. Thanks for taking care of this. Best, Maria

Hi Jennifer, I want to give you advance notice of a rate adjustment that will take effect on January 1st. Starting in Q1, my standard hourly rate will increase from $150 to $175 per hour. This is the first adjustment in three years, and it reflects increased costs and the expanded scope of services I've been providing. Your current retainer agreement will remain at the existing rate through December 31st. If you'd like to lock in the current rate for additional work or extend the retainer before year-end, I'm happy to discuss that. I genuinely value this working relationship and I'm not taking this lightly. I wanted to give you enough lead time to plan accordingly. Let me know if you have any questions. Best, Kevin

Hi Robert, I owe you a direct update: the project is running approximately three weeks behind the schedule we committed to. The delay comes down to two things: a technical issue with the data migration that took longer to resolve than expected, and a resourcing gap in week three that I should have flagged earlier. I'm sorry I didn't communicate this sooner. You deserved to know as soon as the risk became clear, not after the fact. Here's where we stand: the core build is complete. What remains is the QA pass and integration testing. The new delivery date is December 14th. I'm confident in that date. If this delay affects your internal plans, please let me know and I'll do whatever I can to minimize the impact — including prioritizing specific pieces you need first. Again, I apologize. I'll keep you updated every week from here. — Priya

Hi Lisa, I need to walk you through a change to the scope we agreed on, and I want to be transparent about what happened and why. During development this week, we discovered that the real-time notification system we spec'd isn't compatible with your current infrastructure without a significant refactor. Building it as originally designed would add 4-6 weeks and isn't something we can absorb without impacting other deliverables. I've drafted two alternatives: 1. A near-real-time polling solution (updates every 60 seconds) that we can deliver on schedule. 2. The original real-time system, but delayed to Phase 3, with polling as an interim. Both options serve the core use case. I wanted to bring this to you now so we can decide together rather than I make the call unilaterally. Can we jump on a call this week? I'll send a calendar invite. Best, Nathan

Hi Caroline, Your current retainer agreement is set to expire on November 30th, so I wanted to reach out early to discuss renewal. This past year, we've delivered the rebrand, the investor deck series, and three campaign launches. I think we've built a strong working rhythm, and I'd like to continue that into the new year. For 2025, I'd like to propose a similar structure with two updates: a rate adjustment to reflect the expanded scope we've been operating at, and an extended 12-month agreement for better planning stability on both sides. I'll send a formal renewal proposal by Friday. In the meantime, does the overall direction make sense to you? Looking forward to hearing your thoughts. Best, Diana

Team, I want to share an organizational change that will take effect on December 1st. The Product and Engineering teams will be consolidated into a single Product & Technology unit. This change reflects how we've been working in practice — the two teams have been operating as one for most of the past year — and it formalizes a structure that better serves how we build. What this means in practice: - The two teams will report through a single leadership structure, led by Sam. - Roles and responsibilities will be clarified and communicated to each team member individually this week. - There will be no layoffs as part of this change. I know organizational changes create uncertainty. I want to be direct: this is about building a better working structure, not reducing headcount. I'll hold a team Q&A on Thursday at 2pm. Please bring questions. I'd rather you hear answers from me directly than fill gaps with speculation. — Michael

All, Effective February 1st, we're updating the remote work policy. The current policy allows fully remote work with no in-office requirement. The updated policy requires teams to be in the office two days per week (Tuesday and Thursday), with remote work the other three days. This applies to all employees in the metro area. Employees more than 60 miles from the office are unaffected. I want to be straightforward about why: team leads have flagged that collaboration on complex work is harder without dedicated in-person time. This is a real problem, and the data from the past year backs it up. I also recognize this affects people differently depending on commute, childcare, and personal circumstances. Managers will work individually with anyone who needs accommodation. The full updated policy is in the employee handbook. Questions can go to your manager or directly to HR. — Operations Team

Hi Jordan, I wanted to reach out privately before our next team meeting because I think what I need to say deserves a direct conversation, not a group setting. I've noticed that in the last few team discussions, when ideas get challenged, the response has sometimes come across as dismissive — particularly toward junior team members. I don't think it's intentional, and I know you care about the work. But I've had two team members mention separately that they're hesitant to speak up, which concerns me. I'm raising this because I respect you and think we do better work when the team feels safe to push back. I'd like to find a way to have this conversation that's useful rather than just critical. Can we grab coffee this week? — Sam

Hi Mark, Thank you for thinking of me for the Westfield project — I can see it's a meaningful piece of work. I have to be honest with you: I don't have the bandwidth to take this on right now and do it justice. I'm at capacity through the end of Q1, and I'd rather decline upfront than commit to a timeline I can't hold. I don't want to leave you without options. A colleague of mine, James Lee, does similar work and has capacity this quarter. I'd be happy to introduce you if that would help. If the timeline shifts or you have something coming up in Q2, I'd love to pick up the conversation then. Thanks again for reaching out. — Ryan