Engineering management at its best is a set of weekly habits. The job has no week without 1:1s, no week without retrospectives, no week without strategic alignment. The managers who do it well have built a set of small, recurring practices that compound into team outcomes. The managers who don't have these habits get pulled into reactive work and lose touch with the things that determine whether the team actually performs.
The fifteen habits below are the ones we see in the best engineering managers. Not all of them every week — some are biweekly or monthly — but the rhythm is consistent. Managers who maintain these habits run teams that visibly perform better over time. Managers who don't have these habits often have teams that look fine until they don't.
1. Read every direct report's shift-end records or equivalent
The manager who reads what their engineers declare each week knows what's actually happening. Without this discipline, the manager's mental model of the team is constructed from 1:1 conversations and meetings, which is always incomplete. Reading the records takes thirty to sixty minutes weekly and produces the situational awareness everything else depends on.
2. Hold every 1:1 on schedule
1:1s are the highest-leverage hour in management. Skipping them sends a signal that the engineer is less important than whatever else demanded the time. Great managers protect 1:1s ruthlessly and reschedule rather than cancel when conflicts arise. The cumulative effect on the relationship — and on the engineer's trust that they have a real channel to their manager — is substantial.
3. Identify one risk to flag upward
Every week, identify one risk in the team that leadership above the manager should know about — a project at risk, a retention concern, an emerging issue. Surface it before it becomes a crisis. Managers who only escalate problems when they're already on fire are seen as reactive; managers who provide early signal are trusted with more.
4. Remove at least one blocker
Every week, identify a specific blocker on the team and remove it. Get the decision unstuck, get the resource approved, get the cross-team commitment confirmed. The manager's most visible value comes from removing blockers; the weekly habit forces it to happen rather than being deferred to "when I have time."
5. Document one decision
Pick one decision the team made this week and write it down in a way the team can reference. Not all decisions need formal documentation, but the discipline of writing at least one per week keeps the institutional memory accumulating and reinforces the norm that decisions are written down.
Put a context layer under your distributed team.
StandIn gives engineers a 60-second wrap at the end of every shift. The next shift wakes up knowing exactly what to pick up — no standup required.
Request early access6. Connect with one engineer outside your direct reports
Skip-level conversations, informal coffees with adjacent engineers, brief check-ins with cross-functional partners. These connections build the broader network that lets the manager understand the company beyond their team. Without them, the manager becomes parochial and their team becomes isolated.
7. Acknowledge work explicitly
Find specific work to acknowledge — to the engineer, to the team, sometimes publicly. "I noticed the way you handled X" or "Y delivered on this difficult timeline because of how A and B coordinated" — specific, attributed, timely. Generic "good job team" praise has zero value; specific acknowledgment compounds.
8. Test one team norm
Notice one thing the team does habitually and ask whether it still serves the team. The standup, the retro, the planning ritual, the way handoffs work. Some of these will be working fine; some will have decayed and persist out of inertia. Pick one each week and examine it honestly.
9. Review the work pipeline
Look at what's in flight, what's queued, and what's blocked. Not to micromanage — to understand whether the team's actual work matches the strategic priorities, whether anything important is missing, whether anything unimportant is consuming time. Five to fifteen minutes weekly catches drift early.
10. Have one strategic conversation
Talk with another leader (peer manager, your manager, a senior IC) about something beyond the operational week — team strategy, hiring direction, architectural future, organizational design. Managers who only have operational conversations become operational managers; those who have strategic conversations become strategic ones.
11. Update your own work record
Write down what you yourself did this week — for your records, your manager, and your own reflection. Engineering managers often skip this discipline, then struggle when annual reviews require them to articulate their work. A brief weekly record makes the longer reviews much easier and improves the manager's own self-awareness.
12. Review one outstanding commitment
Pull up the list of things you said you'd follow up on. Pick one and either complete it or explicitly punt it. Managers who let commitments accumulate become unreliable; managers who clear them weekly are trusted.
13. Spend time on something you don't enjoy
Performance documentation, compensation analysis, hard feedback conversations — the work managers tend to defer. Every week, pick one of these and do it. The deferred work is usually the highest-leverage work; the leverage comes from the difficulty.
14. Take time off your calendar
Block at least one hour for thinking work that isn't meetings or operational tasks. Calendar saturation is one of the most reliable predictors of management failure. Protect the unstructured time aggressively.
15. Reflect briefly on the week
At week's end, take fifteen minutes to think about what worked, what didn't, and what you'd do differently. This is the lightest discipline on the list and the most predictive of management improvement over time. Managers who never reflect repeat the same mistakes for years; managers who reflect weekly improve continuously.
The cumulative practice
None of these habits is exotic. None requires special training. None takes long individually. The fifteen together require about a half-day of weekly time, woven through the other work — which the manager has to do anyway. The compound effect over a year is the difference between managers whose teams perform reliably and managers whose teams are erratic.
The hardest part isn't doing any individual habit; it's maintaining the rhythm when the week is chaotic. Great managers protect the habits exactly because the chaotic weeks are when they matter most. Skipping the 1:1 because the week was busy is exactly when the engineer most needed the 1:1. The discipline is the leverage.
Frequently asked questions
Which habit should new managers start with?
Reading shift-end records or whatever declared-state mechanism the team has. This single habit produces the situational awareness that everything else depends on, and it's the one most commonly skipped by managers who haven't built it as a habit.
How do you maintain these habits when the week is overloaded?
Default to the habits even when the urgent work is loudest. The urgent work usually fills the time you don't protect; the habits create the time you need to do strategic work. Managers who feel like they don't have time for the habits are the managers who most need them.
How does this scale to managers with eight or more direct reports?
Some habits scale (reading records, reviewing pipeline). Others (1:1s, individual acknowledgment) become harder. The honest answer is that eight is approaching the upper bound of effective direct report span for engineering managers. Beyond that, the habits compete with each other and quality drops. The structural fix is to add another manager rather than to stretch one further.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.