# How to Bring Solutions, Not Problems (the Right Way) Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/bring-solutions-not-problems/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/bring-solutions-not-problems.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer "Bring solutions, not problems" is good advice — until it isn't. What the rule really means, the levels of escalating an issue, and when to just bring the problem. ## Key facts - Title: How to Bring Solutions, Not Problems (the Right Way) - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Decision-Making, Influence - Primary keyword: bring solutions not problems - Source page: https://headwayskills.com/knowledge/working-with-your-manager/bring-solutions-not-problems/ ## What this page covers - "Bring solutions, not problems" is good advice — until it isn't. What the rule really means, the levels of escalating an issue, and when to just bring the problem. - Practical guidance for bring solutions not problems - How this topic connects to Working with Your Manager ## Detailed explanation "Bring solutions, not problems" means that when you take an issue to your manager, you do the thinking first: you arrive with the problem clearly stated, one or two options, and a recommendation — not just a complaint and an open question. Done well, it makes you [someone a manager can rely on](/knowledge/working-with-your-manager/manage-up/). Taken too literally, though, it can quietly do damage. That last part surprises people, because the phrase is repeated like gospel. The truth is more useful than the slogan: it's a skill with a few distinct dimensions, and knowing them is what separates looking proactive from actually being trusted. ## What "bring solutions, not problems" really means At its best, the principle is about ownership. Instead of handing your manager a raw problem and walking away, you show that you've engaged with it — you've understood the situation, weighed a couple of paths, and formed a view. It signals initiative and respects your manager's time, which is exactly why it builds trust. But the literal version — *never* bring a problem unless you've solved it — backfires. A widely cited 2017 *Harvard Business Review* article argued that demanding solutions creates "a culture of advocacy instead of one of inquiry," where people push the first fix they think of instead of exploring the real issue. Worse, it teaches people to stay silent. As organizational psychologist Adam Grant put it, the rule "doesn't eliminate problems — it stops people from [raising the hardest problems](/knowledge/working-with-your-manager/disagree-with-your-manager/)," because the biggest issues are usually too complex for any one person to arrive with a tidy answer. So the goal isn't to suppress problems. It's to bring them with thought attached. ## The levels of bringing a problem The most practical way to picture this is as a ladder. The same problem can be delivered at very different [levels of initiative](/knowledge/influence/show-initiative-at-work/), and moving up the ladder is what makes you more useful. ### Level 1 — just the problem "The vendor missed the deadline. What should we do?" There are times this is the right move (more on that below), but as a default it pushes all the thinking onto your manager. ### Level 2 — the problem plus your read You add analysis: "The vendor missed the deadline, and from what I can see it's a capacity issue on their side, not a one-off." You've made the problem legible, even if you don't yet have a fix. ### Level 3 — the problem plus options Now you bring choices: "Here's the situation; we could escalate with the vendor, switch to the backup supplier, or push the launch a week." You've turned a dead end into a decision. ### Level 4 — options plus a recommendation The level most managers are really asking for: "...and I'd lean toward the backup supplier, because it protects the launch date even though it costs a bit more." You've done the reasoning and committed to a view. ### Level 5 — a recommendation already in motion For problems inside your authority: "...so I've already contacted the backup supplier to hold capacity, and I'll confirm once you say go." You report rather than ask. Most day-to-day issues belong at level 3 or 4; reserve level 5 for things that are genuinely yours to decide. ## When you should just bring the problem The exception matters as much as the rule. Some problems should come to your manager *before* you have a solution: issues too big or cross-cutting for you to solve alone, anything outside your authority or budget, and anything touching safety, ethics, or legal risk. Sitting on one of those because you "don't have a solution yet" is how small problems become crises. Grant's reframing is the safe default for these: bring the problem early, as long as you're willing to be part of the solution. Raising something you can't fix isn't weakness — it's exactly what a manager needs to hear in time to act. ## How to frame a solution so it lands Even a strong recommendation fails if it's delivered badly. Lead with the problem in one sentence so your manager knows the stakes immediately. Offer no more than [two or three options](/knowledge/decision-making/decision-making-process/) — a wall of choices is just the problem in disguise. Name the trade-offs honestly, including the downside of your preferred path, because a recommendation that hides its costs reads as a sales pitch. And say what you've already done. The goal is to make saying "yes, go" the easiest thing your manager does all day. If you're not sure your judgment calls land that way yet, it's worth [checking how you come across](https://assessment.headwayskills.com/) before the next high-stakes one. ## The skills that turn this into a habit Notice what this actually requires. Bringing solutions well isn't a single trick — it draws on a few underlying, learnable skills that show up far beyond this one situation. **Working with Your Manager** is the relationship this all serves. The framework treats it as a genuine partnership: you deliver your part, you stay honest even when it's risky, and you bring solutions rather than just problems — while still feeling free to raise the issues you can't yet solve. Getting the balance right is what makes a manager trust you with more. **Decision-Making** is the engine behind a good recommendation. Generating two or three real options, weighing trade-offs with the facts you have, getting another opinion, and accepting "good enough" rather than chasing a perfect answer — that's the work that happens before you ever walk into your manager's office. **Influence** is what compounds over time. Every problem you bring well is a small deposit in your reputation: you become known as someone who takes initiative and thinks about the bigger picture, which is precisely how junior people earn a say in decisions above their title. You can probably feel that these three pull in different directions sometimes — and the free Work Skills Test maps where each of yours stands today, so you can see [which one needs attention](https://assessment.headwayskills.com/) rather than guessing. They're three of twelve such skills the framework treats as buildable, not fixed. ## What this means for you Some of this may already be how you operate — pausing to draft a couple of options before you knock on a door, flagging the risky stuff early instead of hoping it resolves itself. If so, that instinct is worth building on, because bringing solutions well is a habit you sharpen with practice, not a personality you're born with. And it carries more weight the further you go: as your responsibilities grow, more of your influence comes from how you handle problems than from your job title. The fact that you're thinking past the slogan to how it actually works already puts you ahead of most. ## See where your work skills stand You can see the shape of the skill now; the only thing left is an honest read on which parts come naturally to you and which slip when the pressure's on. The **free** Work Skills Test is a short self-assessment that shows where you stand across all twelve work skills — including the manager, decision, and influence habits that "bring solutions, not problems" really depends on — and points you to the one worth working on first. **[Take the test](https://assessment.headwayskills.com/)** *Free, and it takes about 7 minutes.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? "Bring solutions, not problems" is good advice — until it isn't. What the rule really means, the levels of escalating an issue, and when to just bring the problem. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Decision-Making, Influence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/decision-making.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/bring-solutions-not-problems/ Preferred summary: ""Bring solutions, not problems" is good advice — until it isn't. What the rule really means, the levels of escalating an issue, and when to just bring the problem." ## Change log - 2026-07-07: Content collection version published.