ОБ ЭТОМ ВАМ НЕ РАССКАЖУТ / От какого менеджера надо бежать

Executive Summary

The video offers a practical way to assess whether a manager’s behavior is undermining work—and how to respond before frustration turns into an impulsive resignation. Its central advice is to look for repeated patterns, not one-off mistakes, and to check whether the manager changes after receiving clear feedback. Assess observable behavior and its impact rather than trying to judge the manager’s personality or technical knowledge.

Diagnostic Frameworks and Playbooks

Assess whether the work is sustainable and meaningful

Review recent work—such as the last two sprints or quarter—and assess each task on:

• Autonomy: Can you influence what, how, when, or with whom the work is done?
• Development: Does it build professional skills, or is it the same routine work repeatedly?
• Meaning: Can you see how it benefits the team, company, or customers?

A lack of balance across these dimensions is a warning sign. Routine work is unavoidable, but managers should explain its purpose and, where possible, give employees a say in how it is done or share it fairly across the team.

Check the quality and frequency of feedback

Ask yourself: Do I know how satisfied my manager is with my work?

Consider whether you receive timely, specific positive feedback—not just criticism. The speakers suggest that being unable to recall any praise over the past month may point to a feedback problem, though it does not by itself prove the manager is incompetent.

Useful corrective feedback should explain the context, what action caused the problem, what the impact was, and how to improve. “Redo this; it’s rubbish” does not meet that standard.

Feedback should be regular rather than saved up for a six-month review. Give it soon after the event, while the details are clear.

Use regular one-to-ones

The guest describes setting up a meeting with a direct manager every 2–3 weeks. Both sides can discuss whether responsibilities are clear, what is going well, and what should change. Revisit issues over time rather than expecting one conversation to fix everything.

Clarify performance, promotion, and compensation criteria

Ask:

• What does good performance look like in my role?
• What specifically is required for the next career step?
• Is performance judged by results or by visible activity?
• Are comparable contributions rewarded fairly?

Replace vague advice such as “be more proactive” or “take more responsibility” with observable actions, examples, and a timeframe. Record agreements in writing and check progress after a few weeks rather than waiting months.

Diagnose workload chaos and meeting overload

Ask whether you:

• Have uninterrupted focus time for core work;
• Are expected to respond within minutes at all times;
• Frequently abandon planned work to put out fires;
• Are contacted outside working hours; or
• Spend a large share of the week on low-value or bureaucratic activity.

For each meeting, ask: Did I contribute to a decision or useful discussion? If the meeting was mainly informational, will that information affect my work? Track recurring and ad hoc meetings; a single unproductive meeting is not proof of a systemic problem.

Give feedback using a fact-based structure

1. Raise the issue promptly.
2. Describe the specific situation and the manager’s observable action or words.
3. Explain the impact on work or results.
4. Ask how to handle similar situations in future and agree on a next step.

For example, instead of saying “our meetings are useless,” identify the meeting, note that it had no clear objective or recorded decision, and explain what work was delayed. Bring concrete examples; general complaints are easy to dismiss. Keep the discussion focused on behavior and outcomes, not presumed motives.

Escalate in stages, with judgment

1. Give the manager specific feedback and allow time for change.
2. If the issue persists, stop compensating for every broken process yourself. Continually rescuing a dysfunctional system can conceal the problem and prevent the manager from seeing its consequences.
3. If appropriate, raise a systemic issue with the manager’s manager, usually after first discussing it with your direct manager. Repeatedly escalating minor issues can damage your credibility, and escalation can be risky in organizations that punish challenges to hierarchy.
4. Consider an internal transfer or a job search if the pattern continues, work becomes increasingly difficult, and there is no credible path to improvement. The speakers advise securing an offer before resigning where possible.

Management and Organizational Lessons

• Managers should explain why routine work matters, distribute unpleasant tasks fairly, and give employees appropriate autonomy.
• Clear responsibilities and frequent alignment can prevent the gap between a manager’s expectations and an employee’s understanding from becoming a major conflict.
• Micromanagement can worsen the chaos it is intended to control: constant priority changes and additional oversight disrupt focus and create more fires.
• Meeting time has a real organizational cost. The speakers use an illustrative example in which a meeting with several participants could cost the employer about $1,000; the point is to account for participants’ time, not to present a universal benchmark.
• Some organizations use forced performance distributions—for example, a stated 10% high- and low-performer allocation. The discussion presents this as a process constraint managers may face in some companies, not a universal Big Tech practice.

Examples and Actionable Recommendations

• A vague “be more proactive” promotion requirement can mean very different things to different people. Ask for concrete examples, define what success looks like, document the agreement, and check in after 2–3 weeks.
• For a meeting-related concern, prepare facts such as the date, duration, number of attendees, purpose, and outcome. Then discuss how to make future meetings more effective rather than attacking the manager.
• The speakers describe a new employee receiving harsh code-review feedback but later viewing the mentor positively. Their point is that people may interpret bluntness differently; one person’s tolerance of a style does not establish that the feedback was clear, constructive, or effective.
• If a manager repeatedly rejects feedback or nothing changes, do not assume that waiting will solve the problem. Choose deliberately among further escalation, internal transfer, reduced discretionary effort, or an external job search.

Metrics and Timeframes Mentioned

• One-to-ones: Every 2–3 weeks as a suggested cadence.
• Work review: Inspect the last two sprints or a recent quarter for task autonomy, development, and meaning.
• Positive feedback check: Consider whether you can recall praise from the past month.
• Career-criteria follow-up: Check whether agreed behaviors are being applied after a few weeks; the speakers caution against waiting six months to discover that expectations differed.
• Meeting-cost example: Approximately $1,000 for an illustrative meeting with several attendees; not a general KPI or audited figure.
• Performance distribution example: 10% at the top and bottom in some forced-ranking processes, as described in the discussion.

Presenters and Sources

• Anton Nazarov — host of Антон Назаров I Осознанная Меркантильность.
• Alexander — management consultant and trainer, and former COO; surname not provided in the subtitles.
• The speakers also refer to audience-submitted workplace cases, a Gallup engagement survey, Goldsmith’s article Leadership Is a Contact Sport, and ideas attributed to Kegan.