A backlog keeps growing, a client complaint mixes three different problems, or the numbers you need will not arrive before the deadline. Business problem solving at your level means checking the facts, splitting the problem, and bringing your manager evidence and a recommendation, not a guess. The two-minute videos follow individual contributors, such as an operations specialist watching a backlog grow overnight or a sales rep checking her dashboard before blaming the market. The course is part of Individual Contributor Excellence on JoVE Coach.
Tell a one-off glitch from a problem that is growing
Find the real reason behind a performance gap before you act on it
Turn a tangled complaint into separate tasks, each with one owner
Hand over findings another team can verify and act on
Choose between similar options using criteria you can defend
Keep work moving when inputs are missing, without hiding the gaps
Judge which problems to fix yourself and which to escalate
1. Verifying facts before raising an unexpected issue
Verifying facts means confirming a problem is real before anyone acts on it. When something looks wrong, such as orders sitting past their processing target, check the records for missing information or system errors, then recheck more often to see whether the number is stable or growing. Log affected items, delays, and at-risk commitments, and escalate once the trend is confirmed.
2. Data-informed decision making instead of assumptions
Data-informed decision making means checking the numbers before you settle on a cause. A plausible story, such as a slow market, can hide a gap in your own approach. Break the data down by segment, separate internal factors from outside conditions, then act on what it shows and track the trend weekly. A standard dashboard is usually enough for data-driven decisions.
3. Breaking complex problems into owned actions
Breaking down a complex problem means splitting one tangled issue into named parts, each with one owner and one next action. A complaint about unreliable service may really be service interruptions, slow responses, and billing confusion. Route each part to the team that owns it, track each one separately, and close it only when it has a confirmed outcome. That is problem decomposition in practice.
4. Supporting root cause analysis with evidence
Root cause analysis finds why a problem keeps happening, not just how to fix one case. Your role is to support it, not lead it. Define the problem clearly, review complaints, case notes, and order records, and look for the detail that repeats, such as orders that needed address clarification before dispatch. Then document the pattern for the team that can fix recurring problems.
5. Evidence-based decision making when comparing options
Evidence-based decision making means judging options against criteria you set before comparing anything. With two vendors at similar cost, define what matters, such as delivery time, conversion rates, and return, then gather records and feedback and review risk, since a history of delays can outweigh strong numbers. Write down your reasoning and share it. A criteria-based comparison is easier to defend than instinct.
Frequently asked questions about decisions and escalation
You make the decision easier for the person who owns it. That means verified facts, organized evidence, compared options, and a clear recommendation, while your manager coordinates and approves. Bringing a recommendation, not just a problem, is also a core part of managing up.
Only when three things are true: the issue is low impact, you have a solution, and it is within your authority. If any answer is no, escalate. A mislabeled chart is yours to fix. Conflicting figures from two teams need a decision, and the solve or escalate check shows why.
Propose a transparent workaround. Check past reports for steady trends you can estimate from, then recommend delivering on time with estimates labeled, gaps marked, and a date for the full update. If a gap cannot be estimated reliably, mark it instead of guessing. That keeps work moving within work constraints.
Then say so, with the evidence. If your effort is spread sensibly and results are low across every segment, an outside cause becomes more believable. Share the breakdown with your manager, keep tracking it weekly, and let the data, not the story you started with, shape the next step.
Bring evidence and a next step. Confirm the facts first, so you never escalate a false alarm, then share what is affected, by how much, and what you recommend. Verifying first also protects your credibility. The same structure works for raising issues with any team.
Four habits, practiced on small problems first. Verify before you act, split big issues into owned parts, check the data before you choose a cause, and write down why you picked an option. Needing your manager to make every call is one of the clearest gaps in promotion readiness.