How to tell your boss that part of your job sucks.

January 23, 2026

Before You Invest Time in This Process:

The Reality Check

Some jobs just suck. Period.

When I brought this topic up with our design team they immediately said that some jobs just plain suck and there’s not a whole lot you can do about it – you might not be the right fit for the job. They’re right. What I’m talking about here is lobbying for a change in your job that’s pretty good for the most part with a few pieces that get frustrating. A job you don’t want to quit (yet) and are willing to fight to change.

So before we dive into HOW to talk to your boss, let’s make sure you’re in a situation where this will actually work. Some workplace situations aren’t fixable, no matter how strategic you are.

You should probably just quit if:

• They punish people who suggest improvements (If speaking up gets you labeled a troublemaker, that’s toxic)
• Multiple people have tried and failed to change this (If you’re the fourth person to suggest this fix and the previous three all gave up or left, take the hint)
• It’s a symptom of deeper cultural problems (You can’t fix culture from a junior position)
• You’re fighting against core company values (Maybe you just need a company with different values)

If none of these apply to you, great! Let’s talk about how to make your case effectively starting with a…

STEP 1: Mindset Shift

Approaching your boss with a problem:
From perceived conflict to public service announcement. 

Some people view speaking to their boss about the annoying parts of their jobs as conflict. I view it as a public service announcement, a favor to the company, a person showcasing a problem solving mindset. In my opinion, your boss should thank you for bringing it to their attention. You’re not bothering – you have the mindset of an entrepreneur which in most work places should be rewarded. 

Case in Point #1: The MailChimp Disaster

Years ago MayeCreate onboarded our email marketing to MailChimp (and would have stopped days in had someone complained but alas we just ended up off boarding it years later instead ***SIGH***). I worked through the initial steps, validated it was going to meet our needs, and handed it all off to Katie. Katie worked in it for months, built out even more features over YEARS.

Then one day, Katie wasn’t there and I had to get in and do her job.

I was shocked it was terrible. It took 17 steps to do any one thing and even then I felt like a fish out of water in the user interface.

So I went to Katie: “Katie, this is terrible.”

Katie’s response? “I know. It takes forever.”

I was floored. How was I just finding out about this!?! It was wasting so much of her time and just not the right solution for our team but I had no idea until literally years later.

Case in Point #2: The Employee Who Never Complained

Stacy had a really long-time employee who was amazing at her job. She was very much a doer and she never complained about anything. She was always willing to take on another task.

At the time, they were scheduling everything on Google Calendar, and there were lots of inefficiencies in the process.

Ultimately, this employee had a family crisis. She was in the middle of it, had to be there for family, couldn’t work as many hours, and ended up leaving.

Had she complained, or told us that her job was taking forever, I know there are so many things we could have done to make it more efficient. In that instance, she was amazing at her job, and I really would have listened and loved if she would have complained! Losing her was a punch in the gut! She’s amazing!

Her leaving became a huge catalyst for change – maybe one of the biggest MayeCreate has ever had. After crying under my desk Stacy and I went to the drawing board and slowly but surely adjusted those time consuming processes to improve the efficiency of our workflow.  But it didn’t have to happen that way. If she’d spoken up, we could have made those changes while she was still there, and she might not have had to leave.

The Lesson

If these amazing women had explained to me the annoyingness and inefficiency of those situations I would have absolutely worked to correct them. Instead I paid thousands of dollars to build out a system that didn’t really work and eventually lost an amazing long term employee. Both situations suck way worse than someone telling me that PART of their job sucks.

NOTE: The thing that sucked wasn’t a person.

In both of these examples, note, we’re talking about a service we used, a part of a process, the tasks of a job, NOT a person. 

If a person is what’s making your job suck, that’s a whole other issue that is far more delicate and not what I’m advising on here. You can’t control another person or how they do their job. You can, however, control yourself and take ownership of the things that could be in your control.

STEP 2: Reflection through conversation.

Talking to Your Boss About Problems at Work: The Discovery Phase

The key to successfully approaching your boss isn’t just about what you say—it’s about the work you do beforehand. First, take a step back and get your head on straight, do some digging and reflection. Have a conversation with yourself, potentially a co-worker in the same role as you to get another perspective, and possibly a conversation with a good friend who’s removed from the situation and is good at finding solutions. (Working Genius calls these idea generating folks ideators).

Your goal in these conversations is to determine:

1. If it’s a viable problem that can be solved or just a thing you need to get over.
2. Identify potential solutions to benefit everyone involved – you want to arrive at your conversation with your boss WITH solutions. Not just a complaint.
3. Determine the best course of action to get what you want.

I do understand that you may not see solutions. 

You may not be an ideator or even have the experience to propose a solution. But most consultants don’t KNOW exactly how to solve the problems they’re facing, but they can see the roadblocks that need to be removed and how removing those roadblocks will benefit the outcomes. If that’s the case for you, you’ll frame your conversation differently, but you’ll still need to do some self evaluation to prepare to present your case.

Have a conversation with yourself.

Use these questions to really example the problem at hand.

Question #1

Is this actually a problem that needs solving?

Some things genuinely suck and need to change. Other things are just uncomfortable in the moment because you had a bad day or you’re hungry or the printer jammed for the third time this morning.

Ask yourself: Was this the tipping point? Are you just pissed off right now because this was the 10th or 11th thing that went wrong today? The first three things you can roll with. By thing seven, you’re getting annoyed. And then there’s that tipping point where you’re DONE.

That’s okay. You have a right to be frustrated. Go buy yourself a Coca-Cola or a hamburger. Take a walk around the block. Scream at the universe for a few moments if you need to. Then move on.

Because sometimes you just need to vent and reset, not reinvent a wheel that already spins and works. That piece of self-awareness is key when evaluating whether something truly needs to change, or if you’re just having a day.

Question #2

Are you new? Do you actually understand the system yet?

If you’re new, you might not understand the whole picture yet. And that’s okay – but it means you need to pump the brakes before proposing sweeping changes.

When new hires immediately start trying to adjust processes, it’s a red flag. It’s kind of like when clients hire a new marketing director who comes in and decides they have to overhaul everything. In the animal world, they’d just be peeing on their territory to show everyone they’re in charge.

But here’s the thing: the person before you probably wasn’t a total idiot.

We’ve developed and modified our processes at MayeCreate over the course of 20+ years. Do they still need improvement? Absolutely. Things change every day. And sometimes a new person has exactly the insight we need to show us where processes need to be modified.

However, new hires do better when they learn to work through the process in its entirety first – to experience WHY we do it the way we do it – before trying to change it. Because then they can see why some processes require a bit of discomfort along the way to guard against an entire dumpster fire down the road.

Voicing complaints about a process you haven’t worked through because you PERCEIVE it may be uncomfortable isn’t the same as presenting a solution to ACTUAL discomfort in a process you’ve done over and over again.

That doesn’t mean you shouldn’t ask questions. Please ask questions. Ask WHY it’s done a certain way instead of immediately saying “that sucks.” Because when you ask why, it shows you’re a thinker, that you’re learning how the company works, and that you want to do better – not just that you want to get territorial and change everything because you can.

Question #3

Is there a reason WHY it’s done that way?

This goes back to the “working through the process” question. The person before you was probably pretty smart. They did it a certain way for a reason.

Ask yourself:

• Am I upset about this, but if I changed it right now, who else would it impact?
• Why would that process be made that way?
• Is it just uncomfortable for ME, or is it uncomfortable for everyone?
• If I adjusted it, could it be a win for everyone else too?

Because it’s not just about you. Good process improvements benefit the team, not just your personal preferences. Sometimes discomfort is just part of the job. Not everything that’s uncomfortable needs to be “fixed.”

There are things we do at MayeCreate that we don’t love, but we do them anyway because they solve problems for future us or others on our team. We’ve decided these uncomfortable steps are worth it to prevent bigger disasters down the road.

The question isn’t “Is this uncomfortable?” The question is “Is this unnecessarily uncomfortable in a way that’s actually causing problems?”

That piece of self-awareness is critical. 

Are you trying to change something genuinely broken, or are you just trying to avoid something that feels hard at the moment? And if it did change, would it create far more discomfort for others on your team?

Question #4

Is it recurring or did the planets just align wrong today?

One of the MayeCreate team’s coping mechanisms is to just jump in and fix things – we’re not averse to change. But usually, one of us pulls back and asks: 

Has this happened before?
What’s the likelihood of it happening again?
How many dominoes had to fall into one another to make this collapse?

Sometimes it’s just a series of seriously unfortunate events. All the planets aligned and crap just got busted. In those cases, you don’t really need to try to fix it right now. Just wait and see if it happens again.

But sometimes going through that rabbit hole is powerful. When you look through all the things you feel like you could have done differently, you might realize you already DO those things and they’re already planned into your process. That reaffirms it was just a one-time thing.

Question #5

What can you change without permission?

Not everything requires your boss’s approval. Some things you’re empowered to just… do differently.

Ask yourself: What would happen if your boss found out you did it differently? Would they even care? What’s the worst thing that could happen? Would they fire you, or would they just ask you to do it the old way?

If it doesn’t impact anyone else and your boss has no clue how you’re doing it, what does it matter if you do it differently?

Waaaay back in the day I had a job where I had to create open house ads every week. On repeat. Talk about boring and tedious. I started adjusting the process by creating templates. Then intake forms so people submitted information the right way. I didn’t ask permission for those efficiency improvements. The boss didn’t care about the intake form. And the ads were supposed to look the same so who cared if I used a template versus designing from scratch? Nobody. So I just did it.

Question #6

Is it worth rocking the boat for?

My dad is the dean of a college. He says all the time: “I’m here to win the war.”

What that means is every decision he makes is strategic. He picks which battles he’s going to fight and which ones he’s going to let go. He wants to do the things that make the most overall impact for the school. Taking on every single little detail wouldn’t push the needle forward – it would just leave him stuck on a hill with no army.

You can choose your battles too.

Some things are worth fighting for. Some aren’t. Pick the ones that matter most.

Question #7

Are you the right person to initiate the change?

Here’s a hard truth: if you’re the office complainer, or if you’re the office clown who’s never serious about anything, it’s hard for people to take you seriously when you finally do have a legitimate concern.

Story time: As a teenager, I was a pain in the butt (just ask my mom – she’ll confirm). So when my brother and I wanted something he was always the delegated asker. 

Why? Because we knew how much more likely our parents were to say yes if he asked.

We were strategic about it. The goal was to get what we wanted. As long as we were playing by the rules, how we got there didn’t matter. I didn’t need the glory of being the one to ask. I just wanted the change to be made. So Travis asked, the change got made, and we got what we wanted. We won.

Pass the ball to the person who’s open. That’s how you win.

You don’t have to take every shot yourself. As kids our goal was to get the change we wanted. As long as we were playing by the rules, it didn’t matter how we got there. I didn’t need the glory of being the one to ask or looking smart for having the idea. I just wanted the change to be made. So Travis asked, the change got made, and we got what we wanted. We won.

Also, respect the chain of command. It would be very weird at MayeCreate if a project manager came to me wanting to change something about the account services process without talking to Stacy, their manager first. 

Question #8

If they say ‘yes’ are you willing to step up and make it happen?

This is critical. Don’t bring up a problem if you’re not willing to be part of the solution.

There are times I think “Man, this really sucks. It needs to be done differently.” But then I realize: I cannot be the driving force for this right now. I’m busy. This is an overhaul. I don’t have time to do it.

So I put it on the future wish list and move on.

And that’s okay. Sometimes it feels painful in the moment because of external factors. If you’re not willing to take on the extra work yourself to make the change happen, maybe it’s not the right time to bring it up.

You can always reevaluate later.

Question #9 (A real doozy.)

Is it really the job?

Sometimes the honest answer is: you’re just not the right fit for this job.

I used to do Stacy’s job 14-15 years ago. I hated it. When I hired Stacy and she started taking over pieces of it bit by bit, I was thrilled to not have to do it anymore and I would still hate doing Stacy’s job to this day.

But Stacy? She’d probably enjoy my job for a few days or a week, and then she’d be like “I am DONE with this crap. My brain hurts. I need my spreadsheets back.”

Just be honest with yourself. Sometimes the job  just isn’t for you.

Have a conversation with a Co-Worker.

After you’ve done that self-evaluation, the next step is often talking to a coworker who does the same job you do. 

NOTE: THIS IS NOT A BITCH SESSION. 

This isn’t you going home to complain to your spouse. This is an adult conversation rooted in problem solving and discovery. There is not any emotion in this conversation other than the desire for improvement.

When I say ADULT I’m talking about the Adult ego state. 

Ego states are “modes”, “mind-spaces” or communication patterns we slip into, based on how we learned to think, feel, and react. They’re pre-programmed based on our past experiences. The Adult ego state is level-headed and emotion free. It focuses on facts, logic, and what’s true right now instead of reacting from past experiences or emotions. 

I preach this concept on the regular to my two teenage daughters:

“If you want your sister to do something for you, treat her like an adult. Go in with an emotion-free proposition. Don’t yell at her because she left her towel on the floor again – if you want to borrow her shoes, ask about the shoes in a non-emotional way.”

Your boss’s office is not a drama-filled WWE production. It’s also not a teenage girl’s bedroom. It’s a business setting. So stay adult and stay focused.

Question #1

Is this just a “you” problem, or does everyone feel this way?

They might not have the same frustration you have. They might be doing the task a different way and you just don’t know about it.

I get frustrated about something and put it in Slack. Tyler will respond: “Oh, there’s a keyboard shortcut for that.” Or “All you have to do is click on these three things and it’ll select everything that’s the same color.”

And I’m like, “Well, aren’t I stupid.”

I just didn’t know. Tyler had more experience or came from a different background that taught him that trick.

Or maybe your co-workers are doing it the same way, and it IS frustrating for everyone. In which case, you’ve just validated that this is a real problem worth addressing.

Question #2

Do they know why it’s done that way?

This goes back to the earlier question. Together, you can examine:

• Who else is this impacting?
• Is there another way you could approach the task that might benefit both of you and others?
• Or at least not impact others negatively?

Two minds are usually better than one. Put your heads together and see if there’s a positive way forward.

Question #3

How do they think the boss will react?

This person works with the same boss you do. They might have insight you don’t about how the boss handles suggestions, what time is best to bring things up, or what approach works best.

You have to know what might happen so you can go in prepared. Just like in sales – if you can anticipate objections, you can prepare responses.

Question #4

Can they see any solutions you haven’t thought of?

Fresh perspectives help. Maybe they see a solution you didn’t consider. Maybe they can poke holes in your idea so you can refine it before taking it to the boss.

And hey, if you don’t have a coworker to bounce this off of, you can literally ask ChatGPT. I do this all the time when I write website copy. “How will contractors react if I put this information up there? Would it be too much? Am I talking down to them? Can I say it like this?”

And ChatGPT will tell me if I’m being great or condescending without realizing it.

Just remember to use your real intelligence WITH your artificial intelligence.

Have a conversation with a friend.

Sometimes you need to talk it through with someone completely removed from the situation.

• Are there alternatives they can see?  
• Do they perceive conflict with approaching your boss about this change?
• What objections do they think the boss might have?

If you need to, this is your opportunity to bitch. 

Your friend is removed and shouldn’t be running around spreading drama amongst your co-workers. HOWEVER, when it gets down to time to brainstorm solutions with your friend, put your emotions aside. You HAVE to be open minded to find a solution. If you have a hard time doing that then keep the whole conversation adult, zero emotion so you can keep your mind open. 

When my 15 year old daughter is faced with a problem she’s feeling emotional about every idea I present is wrong. I am stupid and I clearly can’t see the whole picture. DON’T make your friend feel that way. Try to see the potential in their outside view of the situation. They see something you may not, but you have to be dialed in to see it.

STEP 3: Know Your Boss

You already made sure you have the right person going to the boss to make the change happen. If that’s you, great. But here’s the deal: when you talk to your boss about problems at work, different bosses need completely different approaches.

Think of this like a sales meeting. Not a bitch session. It’s an opportunity for you to enhance your workplace and build rapport with your boss. That will only happen if you can show them what a great problem solver and communicator you are.

Your goal is to:

• AGAIN: Arrive with a solution. Or multiple solutions.
• Present them in a way your audience will best receive them.

The Data-Driven Boss

Think Captain Raymond Holt (Brooklyn Nine-Nine) or Toby Ziegler (The West Wing)

Everything needs proper documentation, structure, and evidence. Bring them statistics and they’ll listen. Bring them feelings and you’ll get a lecture about proper procedure.

At MayeCreate, when someone brings Stacy a spreadsheet showing exactly how much time a task takes and how it impacts the bottom line, she’s immediately on board. That’s her language. Come to her with “this feels inefficient” and you’ll get questions. Come with “this takes 20 minutes, 10 times a week, that’s 173 hours a year we could spend on revenue-generating activities” and you’ve got her attention.

How to approach them:

• Bring metrics, time-tracking, efficiency numbers
• Show cost/benefit in real numbers
• Have spreadsheets ready (seriously)
• Start a timer and track how long the task actually takes
• Document the frequency – daily? weekly?
• Calculate the annual impact

The Big Picture Boss

Think Leslie Knope (Parks & Recreation) or Jack Donaghy (30 Rock)

Leslie Knope wants to know how your change makes Pawnee better. Jack Donaghy cares about NBC’s strategic position. Don’t bring them 14 specific examples of daily annoyances – bring them the strategic impact.

Everything connects to the larger mission. Show them how your idea helps the team/company/vision and they’re all in. They care about strategy and positioning, not day-to-day complaints.

The Relationship-Focused Boss

Think Ted Lasso or Michael Scott (The Office)

It’s all about the team, morale, and people feeling good. Frame it as helping team dynamics and they’re listening. Michael Scott desperately wants everyone to be happy and love working there (even though he’s terrible at making that happen). Ted Lasso measures everything by how it affects the team.

The Just-Fix-It Boss

Think Ron Swanson (Parks & Recreation) or Miranda Bailey (Grey’s Anatomy)

Don’t bring them problems, bring solutions. Better yet, just fix it and tell them after. Ron Swanson literally says “I know more than you” and expects you to just handle things. Miranda Bailey wants it done yesterday and doesn’t want to hear about your process.

I’m this boss in many situations. If you can fix it without negatively impacting anyone else, I think you should just do it. Asking for too much permission actually annoys me. I’d rather you ask for forgiveness if you screw it up than ask permission for every little thing.

The Defensive Boss

Think Jan Levinson (The Office) or Logan Roy (Succession)

Volatile. Takes feedback personally. You have to walk on eggshells. Everything feels like criticism to them and they can turn on you fast. Logan Roy takes suggestions as threats to his authority.

Monica had one of these at a bar she worked at in her 20s. Any suggestion felt like a threat to his authority. It was exhausting.

If this is your boss, we’re sorry. Maybe you do need a new job after all. 🤷‍♀️

STEP 4: Time it right.

When NOT to Have This Conversation

Timing matters. A lot. Here are the situations where you should absolutely wait:

Right after you screwed something up.

This looks defensive. You’re not proposing improvements; you look like you’re making excuses for your mistakes. Wait at least a week.

During a crisis or busy season.

Don’t propose big changes when everyone’s in firefighting mode. At MayeCreate, when we know a team member will be on maternity leave first quarter, we push to make changes BEFORE the employee goes on maternity leave. We don’t entertain major process overhauls when the team is already stretched thin.

When your boss is already stressed or dealing with big issues.

Read the room. If your boss is managing a major client crisis or dealing with company-wide problems, your process improvement can wait.

Your first week on the job.

You don’t know enough yet. What feels inefficient to you might be protecting against problems you haven’t seen yet. When Stacy started at MayeCreate 15 years ago, her predecessor could keep everything in her head – which invoices were sent, which payments were received, all of it. Stacy knew she wasn’t that person. But that was a HER problem to solve with better documentation, not a company process problem. It was her first few weeks – she needed to create systems that worked for her brain, not complain that the process was wrong.

If it’s a big deal, make an appointment.

Don’t ambush your boss in the hallway or catch them right before they head into a meeting. Respect their time and the importance of what you’re proposing by scheduling dedicated time to talk through it.

Step 5: Frame it sandwich style.

Make a Sandwich

Make a constructive criticism sandwich. Tell them what’s working well, explain what’s not working, and then tell them how you propose to make it better. Good – Bad – Good.

I use this constantly – in coaching, with my kids, with my team. It works because you’re acknowledging reality (some things ARE working), being honest about the problem, and showing respect by arriving with solutions.

The positives are the bread. The constructive criticism is the filling. Don’t skip the bread.

Stay Adult, Positive, and Focused

The first person to go emotional loses the upper hand.

If you stay adult and focused, what usually happens is the other person comes back to adult with you. They might get emotional at first, but they’ll come back to the adult ego state with you if that’s where you stay.

Key principles:

Start with what WORKS (don’t lead with complaints)

Bad: “This part of my job is a disaster and it’s wasting everyone’s time.”
Good: “I really appreciate how we’ve streamlined the client intake process – that’s working great. I’ve noticed one area where we might be able to apply that same thinking…”

Frame as opportunity, not grievance

Bad: “I’m so tired of dealing with this terrible system.”
Good: “I see an opportunity to make our process even more efficient.”

Use “I’ve noticed” not “you always”

You’re not placing a personnel complaint. This is a process adjustment. When you can, use first person plural “we” – remember, you represent the TEAM. It’s not about you personally; it’s about making things better and more efficient for everyone.

Example opening: “During our project management meetings, I noticed we kept having the same conversation about X over the past few months. That got me thinking, so I spoke with the other project managers and discovered Y. I’d like to propose a few solutions that could make the process go smoother and help us reach our goals.”

See what happened there? No blame. No “you always make us do this stupid thing.” Just observations, team input, and solutions focused on goals.

Stay Professional – Don’t Deviate from Adult Ego State

Say this: “I’d like to propose a more efficient way to handle X”
Not this: “This part of my job is ridiculous”

Say this: “I’ve tracked the time this takes and found it’s consuming 20 hours per week across the team”
Not this: “This is such a waste of time and everyone hates it”

Say this: “Three team members have mentioned challenges with this process”
Not this: “Everyone complains about this constantly”

Arrive with Solutions (Or Multiple Solutions)

This is huge. Don’t just bring problems. Bring solutions. Show you’ve thought it through:

Show how it works towards company goals.

If you’re proposing something that doesn’t obviously connect to what the company is trying to achieve, your boss has to figure out if it’s worth it. Do that work for them.

Address who else it impacts.

You did this in your self-discovery. Now share it. “This would affect the design team workflow, so I talked to Tyler and Kerra about it. They’re on board and actually suggested this modification…”

Explain the “why” behind your proposal.

Not just what you want to change, but why it matters. What problem does it solve? What gets better?

Explain how you and your team are willing to facilitate the change.

You’re not dumping this on your boss’s desk as another thing for them to handle. You’re saying “here’s the problem, here’s the solution, and here’s how I’m willing to make it happen.”

If they propose another solution that doesn’t seem to meet the goals, make sure you understand the goals – they may have changed and you just don’t know it yet.

Example: “I noticed our client onboarding takes about 4 hours per project, and a lot of that time is spent gathering the same information in different formats. I talked with Brittany and Caitlin about creating a single comprehensive intake form that feeds into all our systems.

Here’s a mockup I created and tested with our last two clients – it cut the time to 90 minutes and the clients said it was way easier on their end too. This would free up about 15 hours per week that we could put toward actual client work instead of administrative tasks.

I’m happy to build this out fully and train everyone on it if you think it makes sense. The only team it would impact is account services, and they’re the ones who suggested we bring this to you.”

That’s arriving with a solution.

Step 6: Prep for what happens after.

Okay, so you had the conversation. You stayed adult, you made your sandwich, you brought solutions. Now what?

If They Say No

Stay adult. 

This is where people lose it. You put in all this work, you brought a great solution, and they said no. Don’t pout. Don’t get passive-aggressive. Don’t spend the next week sighing dramatically at your desk.

Accept it gracefully. That doesn’t mean you have to be thrilled about it, but it means you stay professional.

Clarify what kind of “no” this is.

Is it a NO NEVER? Like, this conflicts with core company values or goes against something fundamental?

Is it a NO RIGHT NOW? Maybe it’s a timing thing. Maybe the company is in the middle of other changes and can’t handle this too.

Is it a NO NOT ME? Sometimes your boss actually agrees with you but doesn’t have the bandwidth or authority to implement it. Maybe they’d love it if someone else took the lead.

Ask a question.

Ask this question (exactly like you would in a sales conversation):
“I understand. Can I ask – what would need to change for you to reconsider this?”

This might tell you it’s a timing issue (“we’d need to finish the Q1 projects first”), a resource issue (“we’d need budget approval from corporate”), or a fundamental issue (“this conflicts with how we’ve committed to serve clients”).

Recognize when to stop pushing.

You got the no. You asked for clarification. They gave you an answer. Now it’s time to move on.

Don’t be the person who keeps bringing it up in different ways hoping for a different answer. 

Do NOT throw your team under the bus to get what you want.

Here’s the scenario: You ask if you can work from home two days a week. Your boss says no, it’s against company policy. You say “But Bob works from home every Friday!”

Guess what? Your boss might already know about Bob. Your boss might know Bob’s exact situation – maybe Bob’s dealing with a family health crisis, or Bob has a medical accommodation, or Bob negotiated it as part of his hiring package. Your boss might not be at liberty to share Bob’s situation with you.

And now you’ve potentially put Bob’s arrangement at risk. How are you going to feel if Bob loses his work-from-home privilege because you mentioned it?

Keep Bob out of it. Focus on your own situation and your own merits.

That said: If you get a clear answer from your boss that you think affects Bob, go to Bob afterward with a heads up. “Hey man, I asked about X and got a pretty firm no with this reasoning. Just wanted to give you a heads up that this is on their radar.”

That’s the respectful way to handle it.

Do the things YOU can do to make it better.

Remember all that self-discovery you did? You probably uncovered quite a few little things that could be implemented without your boss’s approval.

So go do those things. Make your own life better in the ways you can control.

Sometimes the answer IS to quit – and that’s okay.

Know when that’s the right call. If this issue is making you miserable, if it goes against your core values, if you’ve tried everything and nothing changes – it might just not be the right fit.

If They Say Yes

Let’s be honest about something: Things are not going to change immediately.

It may take weeks, months, or even years to implement process changes. Especially in bigger companies with multiple stakeholders and approval processes.

Volunteer to be part of the effort to make the change happen if you can. Don’t just dump it on your boss and walk away. Show them you’re invested in seeing it through.

Get clear on implementation timeline and expectations.

Don’t leave the meeting with a vague “yeah, let’s try that.” Get specifics:

• When does this start?
• Who’s responsible for what?
• How will we know if it’s working?
• What does success look like?
• When do we evaluate and adjust if needed?

Report back on results – prove your solution worked.

This is critical. You proposed a change, they said yes, now you need to show it was worth it. Track the same metrics you brought to them initially:

• “Remember I said this was taking 20 hours per week? It’s now taking 8 hours and we’ve had zero errors.”
• “We’ve been using the new system for a month and client satisfaction scores went up 15%.”
• “Three clients specifically mentioned how much easier the new process was.”

This does two things: It proves you were right (always satisfying), and it builds trust for the next time you want to propose a change.

Give credit where due – if others helped make it better, say so.

Don’t be the person who takes credit for everyone else’s ideas. I once quit a job in part because the boss continually claimed the team’s ideas and work as his own in client meetings.

Don’t be that dude.

If Brittany suggested the modification that made it work, mention Brittany. If the design team helped troubleshoot, give them credit. You proposed the change and saw it through – that’s your win. You don’t need to steal credit for the implementation details too.

If It Gets Weird

They might get defensive. They might get emotional. Plan for that.

Stay adult. 

The first person to go emotional loses, remember?

Have a graceful exit strategy prepared.

“I’m sorry, it seems like this is a bad time for you. I feel like maybe we should discontinue this conversation and pick it up again later, if you’re okay with that.”

Then get up and leave. Calmly. Professionally.

If you have a defensive boss, practice this. Seriously:

• Write it down
• Say it out loud
• Record it in a voice memo on your phone
• Play it back
• Say it to your friend or spouse
• Make sure you sound adult and calm, not emotional or sarcastic

Because in the moment when your boss is getting emotional, it’s really easy to slip into emotion yourself. Having practiced your exit line means you can deliver it professionally even when your heart is racing.

Don’t burn bridges by pushing too hard.

Choose the hill you’re willing to die on. You’re here to win the war, not just this battle. Some things are worth really fighting for. Most things aren’t.

If this particular issue is THE thing that makes or breaks your job satisfaction, then yes, dig in. But if it’s one of seven things that annoy you, this might not be the one to stake your career on.

---

The Bottom Line

When you approach your boss with a problem strategically, you’re not bothering them—you’re showing initiative. Learning how to talk to your boss about problems at work is a career skill that separates good employees from great ones.

You have the mindset of an entrepreneur, which in most workplaces should be rewarded.

At MayeCreate, Monica and Stacy WISH their employees had told them sooner about the MailChimp disaster and the scheduling inefficiencies. They wasted time and money on problems that could have been solved years earlier if someone had just spoken up.

The good bosses will thank you for it. They’ll appreciate that you cared enough about your work and the company to think through solutions and bring them forward professionally.

And if they don’t? Well, that’s probably the information you needed anyway.