Guide for direct reports
How to Bring Up Problems in a 1:1
You’ve got something on your mind, a blocker that keeps eating your week, a process that doesn’t work, a coworker who’s hard to work with, a workload that’s starting to wear you down, or maybe something your own manager is doing. The check-in is the right place to raise it. The hard part isn’t finding the words, it’s saying them in a way that gets you help instead of putting your manager on the defensive.
Most problems don’t backfire because they were raised. They backfire because of how they were raised: as a vague complaint, an accusation, or a venting session with no ask attached. The good news is the difference comes down to a few moves. Get clear on what you want, lead with the impact, bring an idea, stay specific, and land on a next step. The rest of this page walks through each one.
Decide what you want before you open your mouth
The most common reason a problem lands badly is that the person raising it hasn’t decided what they want out of it. There are three goals here, and they call for three different conversations. Knowing which one you’re in keeps you from frustrating both yourself and your manager.
Three things you might want:
- To vent and be heard.You don’t need it fixed, you need someone to know it’s hard. Say that.
- To solve it. You want a decision, a resource, or a change. Come ready with the specifics.
- To think it through.You don’t know the answer yet and you want help reasoning about it.
Saying which one up front is a small move that saves the whole conversation. A manager who thinks you want a fix will jump straight to solutions while you only wanted to be heard, and you’ll both walk away annoyed. One sentence heads it off.
Five steps to raise a problem well
- 1
Get clear on what you want
Before you say anything, decide what you're after. Sometimes you need to vent and be heard. Sometimes you need a decision or a resource. Sometimes you want help thinking it through. Those are different conversations, and naming the one you want up front saves both of you a lot of guessing. A line like "I mostly need to talk this through, I'm not asking you to fix it" tells your manager how to listen.
- 2
Lead with the issue and its impact, not the blame
Open with what's happening and what it's costing, not with who's at fault. "The handoff from design keeps landing late, so I'm losing a day or two each sprint" lands differently than "design never gets me anything on time." The first is a problem you can solve together. The second puts your manager in the spot of defending someone, and the real issue gets lost.
- 3
Bring a possible solution, or ask for help deciding
You don't need a perfect fix, but showing up with one idea changes the tone of the whole conversation. It tells your manager you've thought about it and you want to move things forward. And if you don't know the answer, that's fine too: say so plainly and ask for help. "Here's what I've considered, and I'm stuck between two options" is a solid place to start.
- 4
Stay specific and factual
Vague problems get vague responses. Bring an example or two, a date, a number, the specific thing that happened. "Twice last week I waited on an approval for more than a day" is something your manager can act on. "Things are always slow around here" isn't. Specifics also keep the conversation from sliding into a debate about whether the problem is real.
- 5
Agree on a next step before you leave
A problem you raise and then never mention again tends to stay a problem. Before the check-in ends, land on something concrete: who's doing what, by when, or when the two of you will revisit it. Even "let me try X for two weeks and we'll check back" counts. That next step is what turns a good conversation into a real change, and it gives you a natural reason to follow up.
The same problem, said two ways
The wording does most of the work. Here’s the difference between a version that puts your manager on the back foot and one that invites them to help.
| The situation | Try this instead |
|---|---|
| A blocker | "I'm stuck waiting on approvals, and it cost me two days last week. Could we agree on a faster path?" |
| A process issue | "The current handoff keeps landing late. Here's one idea, can we try it for a sprint?" |
| A coworker | "Working with Sam has been tense lately and it's slowing the project. Can I get your read on it?" |
| Workload / burnout | "I'm running close to empty and I don't think it's sustainable. Can we look at what to drop?" |
| Something your manager is doing | "When work changes get assigned without a heads-up, I lose track of priorities. Could we sync first?" |
Notice the pattern: each one names the issue, states the cost, and ends with an opening for your manager to step in. If you want a deeper script for the hard ones, read our guide to difficult 1:1 conversations. For the workload one especially, MeetFika gives you a quieter way in — the one-minute read on workload and stress before each check-in flags that you’re running close to empty before you have to say it out loud — and the follow-up you agree on carries forward so the fix doesn’t quietly evaporate.
When the problem is sensitive (or about your manager)
Raising something about your manager, a coworker conflict, or burnout takes more care, but the same rules hold. Keep it about behavior and impact rather than character, and give your manager a concrete way to respond. “You never give me direction” is hard to hear and harder to act on. “I’d work better with clearer priorities at the start of the week, could we try a quick Monday sync?” is feedback anyone can use.
For sensitive topics, an honest opener helps lower the temperature. Try “I want to bring something up, and I’m sharing it because I want this to work, not to complain.” That one line tells your manager you’re on the same side, which makes them far more likely to listen instead of defend. If you’re not sure what else to surface alongside it, our list of questions to ask your manager in a 1:1 is a good place to start. Raising a problem about your own work also pairs naturally with asking for feedback in a 1:1, since both come down to getting the support you need to do better work.
A note on timing
The check-in is usually the best place to raise a real problem, because it’s private, recurring, and already meant for exactly this. For most issues, add it to the shared agenda a day ahead so your manager isn’t caught flat-footed and has time to think. A heads-up almost always gets you a better conversation than an ambush.
A few things are exceptions. If something is urgent or safety-related, don’t wait for the next check-in. And if you’re raising it while you’re still hot about it, give yourself a beat first, because the version you’d send in anger is rarely the version that gets you what you want. Raising it well is partly about saying the right thing and partly about saying it at the right moment.
Raising problems FAQ
How do I raise a problem without sounding negative?
Frame it around impact and a path forward rather than complaint. Describe what's happening, what it costs, and one idea for fixing it. When you bring a problem plus a proposed next step, your manager doesn't hear "this person is being difficult." They hear "this person is trying to make things better." Tone matters too: curious and steady beats frustrated and final.
What if the problem is my manager?
Keep it specific and about behavior, not character. Instead of "you micromanage me," try "when you review my work before I've finished a draft, I lose momentum, could we agree on a checkpoint instead?" Lead with the effect on your work and offer a concrete alternative. Most managers want this kind of feedback; they rarely get it in a way they can act on. If it feels too risky to say out loud, see our guide on difficult 1:1 conversations below.
What if I bring it up and nothing changes?
Give it one honest follow-up first. Reference the earlier conversation, restate the impact, and ask directly what's blocking the change. If you raised something, agreed on a next step, and it still goes nowhere after a second try, that tells you something useful about the relationship. Keep a record of what you raised and when, and consider whether a skip-level or HR conversation is warranted for anything serious.
Should I put the problem on the agenda first?
For most issues, yes. Adding it to the shared agenda ahead of time gives your manager a chance to think before they react, and it signals the topic matters. A short line is enough, like "want to talk through a blocker on the launch." Save the unannounced raise for something sensitive or time-critical, where a heads-up would do more harm than good.
Bringing up a problem isn’t a confrontation, it’s part of the job, and a good manager would rather hear it from you than find out later. Get clear on what you want, lead with the impact instead of the blame, come with an idea or an honest ask, keep it specific, and leave with a next step you can both point to. Do that and most problems stop feeling risky to raise. Pick the one that’s been on your mind and put it on the agenda for your next check-in.
Where MeetFika fits
It’s easier to raise a problem when there’s a place to put it. MeetFika gives you and your manager a shared agenda you both write into, so you can add a topic ahead of time, keep your follow-ups visible, and check back on whether anything changed.
Free to start, and your first check-in takes about two minutes to set up.