How to manage up, expectations, status that matters, and 1 on 1 agendas for engineering managers and tech leads. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. Use this guide to move from generic advice to week by week manager habits on engineering teams.
What is how to manage up?
What is how to manage up is a manager practice that turns how to manage up into predictable team behavior, not a poster on the wall.
Engineering managers win when how to manage up is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, managing up and manager alignment intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how to manage up easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how to manage up shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
Why does how to manage up matter for engineering managers?
Why does how to manage up matter for engineering managers is a manager practice that turns how to manage up into predictable team behavior, not a poster on the wall.
Engineering managers win when how to manage up is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, managing up and manager alignment intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how to manage up easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how to manage up shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
What does research say about how to manage up?
What does research say about how to manage up is a manager practice that turns how to manage up into predictable team behavior, not a poster on the wall.
Engineering managers win when how to manage up is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, managing up and manager alignment intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how to manage up easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how to manage up shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do you implement how to manage up on a software team?
How do you implement how to manage up on a software team is a manager practice that turns how to manage up into predictable team behavior, not a poster on the wall.
Engineering managers win when how to manage up is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, managing up and manager alignment intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how to manage up easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how to manage up shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
What are common mistakes with how to manage up?
What are common mistakes with how to manage up is a manager practice that turns how to manage up into predictable team behavior, not a poster on the wall.
Engineering managers win when how to manage up is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, managing up and manager alignment intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how to manage up easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how to manage up shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do you connect how to manage up to better 1 on 1s?
How do you connect how to manage up to better 1 on 1s is a manager practice that turns how to manage up into predictable team behavior, not a poster on the wall.
Engineering managers win when how to manage up is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, managing up and manager alignment intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make how to manage up easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When how to manage up shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do how to manage up practices compare?
| Approach | Strength | Risk |
|---|---|---|
| Ad hoc conversations | Fast to start | Inconsistent across reports; hard to scale |
| Shared written profiles | Reduces guessing; helps hybrid teams | Stale if never revisited in 1 on 1s |
| Pulse and 1 on 1 loop | Connects listening to action | Fails if leaders skip follow through |
Implementation steps
- Clarify why how to manage up matters to your team this quarter.
- Co create norms with reports; do not publish mandates without input.
- Pilot for two weeks; gather friction in 1 on 1s.
- Publish what changed because people spoke up.
- Revisit after org or role changes.
Frequently asked questions
What is the first step to improve how to manage up?
Start with a visible experiment on one team: define success, run for two cycles, and review in 1 on 1s. According to iSilta's 2026 survey of 146 organizations, median formal manager training in the first 12 months is only 14 hours.
How often should managers revisit how to manage up?
Revisit at least quarterly or after reorgs. Treat it as operating rhythm, not a one off initiative.
Does how to manage up apply to remote teams?
Yes, often more. Remote work amplifies ambiguity; explicit practices reduce silent friction.
Where should documentation live?
Prefer shared team context tools and 1 on 1 notes over buried slide decks. Close loops where people already work.
How does this relate to pulse listening?
Pair practices with short pulses and name actions in team forums. Listening without follow through erodes trust faster than not asking.
Related: leadership philosophy why want to lead, why do you want to lead interview answer, fork in the road ic vs engineering management.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.