Managing Up from Scratch (2026)
Managing up is the skill of building a productive relationship with your manager to create better outcomes for both of you. It is not about sycophancy or manipulation. It is about understanding what your manager needs to succeed, communicating proactively, and taking ownership of your career growth rather than waiting for your manager to figure it out. Engineers who manage up well get promoted faster, receive better opportunities, and have more autonomy.
This guide covers the specific practices of managing up: understanding your manager's priorities and constraints, communicating effectively, setting expectations, handling feedback, and navigating difficult situations. The principles apply whether you love your manager or struggle with them.
Understanding Your Manager's World
Your manager has pressures you may not see. They are accountable for the team's delivery, quality, and morale. They have their own manager who sets goals and deadlines. They attend meetings you do not see and make trade-offs you do not witness. The first step in managing up is understanding your manager's priorities, constraints, and communication preferences. What does their manager measure them on? What keeps them up at night? What information do they need from you to succeed in their own role?
Ask directly in a 1:1: What are your top priorities this quarter? How can I best support you? What information would be most helpful for you to receive from me? These questions show that you are thinking about the team's success, not just your own tasks. They also give you the context you need to align your work with what matters most to your manager and the organization.
const managerDiscoveryQuestions = {
topPriorities: 'What are your top priorities this quarter?',
support: 'How can I best support you in achieving them?',
information: 'What information would be most helpful for me to share proactively?',
communication: 'Do you prefer async updates, written summaries, or quick syncs?',
growth: 'What skills should I develop to have the most impact on the team?',
stress: 'What are the biggest challenges you are facing right now?'
};Effective 1:1 Meetings
The weekly 1:1 is your most valuable recurring meeting with your manager. Yet most engineers waste it by giving a status update that could be async. A great 1:1 is strategic, not operational. Use it to discuss career growth, challenges, feedback, team dynamics, and long-term planning. Come prepared with a written agenda. Send it to your manager 24 hours in advance so they can prepare too.
The structure: first 5 minutes for quick updates and logistics, next 15 minutes for the main topic (career discussion, a challenge you are facing, feedback), last 5 minutes for open Q&A and planning for next week. Rotate the main topic each week: one week focus on career growth, next week on technical challenges, next on team dynamics. A well-run 1:1 builds trust and alignment over time.
const oneOnOneTemplate = {
before: 'Send agenda 24 hours in advance with topics',
structure: {
first5min: 'Quick updates and logistics',
middle15min: 'Main topic (career, challenge, feedback, or team)',
last5min: 'Open Q&A and next week planning'
},
topicRotation: ['Career growth', 'Technical challenges', 'Team dynamics', 'Feedback exchange', 'Long-term planning'],
after: 'Send brief summary of decisions and action items'
};
function prepareOneOnOne(weekTopic) {
return `1:1 Agenda
1. Quick updates (5 min)
2. Topic: ${weekTopic} (15 min)
3. Open discussion (5 min)
4. Action items`;
}Communicating Proactively
Proactive communication means sharing information before your manager asks for it. This includes: progress updates on key projects, potential risks or delays as soon as you spot them, decisions you made and why, and blockers you cannot resolve alone. The rule is: no surprises. If your manager hears about a problem from someone else before you, trust erodes. If they hear it from you first, trust deepens.
Write weekly async updates that summarize: what you accomplished, what you are working on next, any blockers or risks, and any decisions needing input. Keep it to 3-5 bullet points. Send it before your 1:1 so the meeting can focus on discussion rather than status. This small habit signals reliability and builds trust over time better than any single achievement.
const weeklyUpdate = {
accomplished: ['Refactored auth middleware to reduce latency by 30%', 'Reviewed 12 PRs'],
inProgress: ['Implementing rate limiter with Redis sliding window', 'Writing migration for user preferences'],
blockers: ['Need decision on cache invalidation strategy for user profiles'],
risks: ['Rate limiter rollout depends on Redis cluster readiness — tracking with infrastructure team'],
helpNeeded: 'None this week'
};
function formatWeeklyUpdate(update) {
return Object.entries(update).map(([k, v]) => `## ${k}\n${Array.isArray(v) ? v.map(i => `- ${i}`).join('\n') : v}`).join('\n\n');
}Setting and Managing Expectations
Clear expectations prevent most manager-engineer conflicts. At the start of each project, clarify: what success looks like, the timeline, the level of autonomy you have, how decisions will be made, and how progress will be measured. Write this down and get agreement. When expectations change — as they always do — communicate the impact clearly: With this new requirement, I need to descope X or extend the timeline by Y.
Saying no or pushing back is part of expectation management. When asked to take on more work than you can handle, do not just say yes and suffer. Instead say: I can take this on, but it will delay X by two weeks. Which should I prioritize? This forces a trade-off decision rather than leaving you holding an impossible workload. Engineers who manage expectations well are seen as reliable, not overloaded.
const expectationSetting = {
projectStart: ['Define success criteria', 'Agree on timeline', 'Clarify autonomy level'],
duringProject: ['Flag risks proactively', 'Communicate scope changes immediately', 'Update ETA if assumptions change'],
sayingNo: 'I can take this on, but it will delay X by two weeks. Which should I prioritize?',
pushingBack: 'I am concerned about quality if we add this without extending the timeline. Could we descope something else?'
};
function negotiateScope(newRequest, currentWork, timeline) {
return `I can add ${newRequest}, but ${currentWork} will ship ${timeline} weeks later. Is that acceptable, or should we reprioritize?`;
}Handling Feedback and Difficult Conversations
Feedback is a gift, even when it stings. When receiving critical feedback, listen without defensiveness. Ask clarifying questions: Can you give me a specific example? What would success look like instead? Thank them: I appreciate you sharing this. I will work on it. Then take time to process before responding. A defensive reaction shuts down future feedback, which is the fastest way to stagnate.
When you need to give feedback to your manager, do it constructively and privately. Use the SBI model (Situation, Behavior, Impact): In yesterday's sprint review, when you asked me to present the results without advance notice, I felt unprepared and it reduced the quality of the presentation. In the future, could you give me 24 hours notice for presentations? This framing focuses on the behavior and its impact, not on attacking the person.
const feedbackModel = {
receivingFeedback: ['Listen without interrupting', 'Ask clarifying questions', 'Thank them', 'Take time to process', 'Follow up with action plan'],
givingFeedback: {
situation: 'In yesterday's sprint review',
behavior: 'When you asked me to present without advance notice',
impact: 'I felt unprepared and the presentation quality suffered',
request: 'Could you give me 24 hours notice for future presentations?'
}
};
function sbiFeedback(situation, behavior, impact, request) {
return `${situation}, ${behavior.toLowerCase()}, ${impact.toLowerCase()}. ${request}`;
}Navigating a Difficult Manager Relationship
Not all manager relationships work. If you have a manager who is micromanaging, unavailable, or ineffective, you still need to manage up — but the strategy changes. Document your work and decisions more thoroughly. Communicate in writing to create a paper trail. Seek feedback from other senior engineers and stakeholders so you have multiple perspectives on your performance. Build relationships with skip-level managers and peers.
If the relationship is genuinely toxic or blocking your growth, start preparing to leave. Update your resume, network actively, and interview. Do not threaten to leave unless you are ready to follow through. In the meantime, focus on what you can control: your skills, your output, your relationships with peers, and your reputation. A bad manager can slow you down, but they cannot stop you from growing if you take ownership of your development.
const difficultManagerStrategies = {
micromanager: 'Send detailed updates before they ask. Build trust through transparency.',
unavailableManager: 'Book time in advance. Prepare agendas. Get decisions in writing.',
ineffectiveManager: 'Seek mentorship elsewhere. Document decisions. Protect your growth.',
toxicManager: 'Document everything. Build skip-level relationships. Plan exit strategy.',
generalPrinciple: 'You cannot change your manager. You can only change how you respond and when you leave.'
};Frequently Asked Questions
What if my manager is not responsive to my managing up efforts?
Adjust your approach to match their style. Some managers prefer written updates, others prefer quick syncs. If they remain unresponsive despite your efforts, seek feedback from other stakeholders and consider whether this manager can support your growth goals.
Does managing up work with a bad manager?
It helps, but it cannot fix a fundamentally broken relationship. With a bad manager, managing up protects you (through documentation, proactive communication) but does not change their behavior. Focus on building your skills and network for your next opportunity.
How do I manage up without seeming like I am sucking up?
Focus on outcomes, not appearances. Managing up is about making your manager more effective so the team succeeds. Share information proactively, solve problems before they escalate, and communicate honestly. Engineers who do this are valued, not distrusted.
Originally published on Ayodhyyya. Last updated June 1, 2026.