The tools engineering managers actually need
You don't need twenty apps. You need one tool per job, and most engineering manager stacks are missing the one for people.
No password. Sign in with a quick email code. No credit card.
1. Delivery: your issue tracker
Jira, Linear, or GitHub Projects. Pick whatever the team already uses and resist adding a second layer on top. If you need a dashboard to understand your own tracker, the tracker setup is the problem.
2. Planning and decisions: one docs tool
Notion, Confluence, or Google Docs for design docs, RFCs, and decision logs. The only rule that matters: decisions get written down somewhere people can find them in six months.
3. Communication: chat plus a calendar you defend
Slack or Teams, and a calendar with protected focus time. The tooling here is solved. The discipline isn't.
4. People: the slot most stacks leave empty
This is where engineering managers improvise. 1:1 notes end up in a personal doc, a notebook, or nowhere. Follow-ups live in memory. Then someone resigns and, looking back, the signs were in three different 1:1s.
A people tool should be private to you, organized per person rather than per meeting, and bring context back before each 1:1.
- One page per report with notes, cadence, and open follow-ups.
- A prep before each 1:1 built from your own notes.
- Early cues across weeks: overload, disengagement, stalled growth.
Where LeaderCues fits
LeaderCues fills slot four and nothing else. It doesn't replace Jira, Notion, or Slack, and it doesn't track commits. It's the private notebook for your 1:1s that reminds you what matters before you walk in. There's a free plan, and Plus is $7 a month.
Related reading
- 1:1 meeting software for engineering managers
How LeaderCues handles recurring one-on-ones.
- Best 1-1 meeting tools
A comparison of the main options.
- People management software
For managers, not HR departments.
- 1-1 questions that get real answers
What to ask when "how's it going?" stops working.
Questions about engineering manager tools
- What tools does an engineering manager need?
- Four kinds: something to track delivery (your issue tracker), something for planning and docs, your team's chat, and a private place for people work: 1:1 notes, follow-ups, and context about each report. Most teams have the first three and improvise the fourth.
- Do engineering managers need a separate 1:1 tool?
- Not always. With three reports, a doc per person works. Past five or six, or with biweekly 1:1s, things start slipping and a dedicated tool pays off.
- Should people notes live in Jira, Notion, or Confluence?
- Usually not. Those are shared workspaces, and notes about someone's burnout or career worries shouldn't sit next to sprint pages. Keep people notes private to you.
- Is LeaderCues an engineering metrics tool?
- No. It doesn't connect to GitHub or measure output. It's for the human side: 1:1s, follow-ups, and noticing early signals like overload or a stalled career thread.
Fill the empty slot in your stack
Keep your people context in one private place and go into every 1:1 prepared.