Engineering Team Management

A working system for leading engineers: one-to-ones that matter, feedback given early, clear delegation, protected focus time, honest planning and delivery that stays on track.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Engineering Team Management, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

⚙️ Software Engineering

Engineering Team Management

Leading a team of engineers through one-to-ones, feedback, delegation, planning and protecting focus time while keeping delivery on track.

  1. First thirty days listening tour
  2. Team charter with mission and boundaries
  3. Profile page for each engineer
  4. Weekly one-to-one schedule and format
  5. Team working agreements
  6. Manager calendar with maker and manager blocks
  7. Stakeholder map and expectations
  8. Delivery health baseline for the team
  9. Role expectations conversation with each engineer
  10. Running one-to-ones that build trust
  11. Weekly team meeting with a shared agenda
  12. Friday update to leadership
  13. Focus time protection for the team
  14. Running feedback log for every report
  15. Monthly team retrospective
  16. Ownership map for team areas
  17. Quarterly team planning cycle
  18. Quarterly team health check
  19. Manager's Friday review
  20. Recognition and wins log
  21. Giving specific behavioural feedback
  22. Preparing for difficult conversations
  23. Coaching engineers with questions
  24. Delegating with clear levels of authority
  25. Managing up to your own manager
  26. Negotiating scope and dates with product
  27. Engineering management reading programme
  28. Team meeting audit and cut
  29. Splitting a team that has outgrown itself
  30. Deciding how much the manager codes
  31. Limiting work in progress across the team
  32. Fair share of interesting and glue work
  33. Async-first communication norms
  34. Stay conversations to reduce regretted leavers
  35. Performance review season preparation
  36. Team offsite planning and delivery
  37. Handling a resignation and handover
  38. Announcing a reorganisation to the team
  39. Supporting the team through a launch crunch
  40. Annual headcount and budget request
  41. Moving from peer to manager of former teammates
  42. Tech lead role without direct reports
  43. Leading a team across time zones
  44. Getting more from your own one-to-ones
  45. Inheriting a struggling team
  46. Cover plan for the manager's extended leave
  47. Supporting an engineer who is underperforming
  48. Skip-level meetings for managers of managers
  49. Spotting and reducing burnout on the team
  50. Resolving conflict between two engineers

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

First thirty days listening tour

A new manager who changes things in week two usually fixes the wrong problem and spends credibility doing it. Thirty days of structured conversations with every engineer, your own manager, the product partner and two or three neighbouring teams gives you a written picture of what is working, what hurts and what people expect from you. It also tells the team that you listen before you act.

First tasks

  • Write the five questions you will ask every engineer
  • Book a forty-five minute conversation with each person on the team
  • Book separate conversations with your manager and the product lead
  • Group your notes into themes and remove anything that identifies a person
  • Present the themes and three priorities at the next team meeting

Team charter with mission and boundaries

Teams that cannot say in two sentences what they own and what they do not end up absorbing every request that lands near them. A short charter naming the mission, the systems and decisions the team owns, the customers it serves and the things it explicitly does not do gives you something to point at when work arrives from the side. Write it with the team so they defend it too.

First tasks

  • Draft a rough mission in two sentences to react to, not to approve
  • Run a one-hour session where the team edits the mission and owned systems
  • Ask two neighbouring teams to check the ownership list for gaps and overlaps
  • Publish the charter and link it from the team channel description

Profile page for each engineer

Managers with six to ten reports forget who wanted to learn Kubernetes, whose partner is due in March and who prefers feedback in writing. A short private profile per person, holding their goals, strengths, working preferences and the context they have chosen to share, turns one-to-ones from small talk into continuity. Keep it factual and something you would be comfortable for them to read.

First tasks

  • Create one profile page for each direct report
  • Copy each person's stated goals from your listening tour notes
  • Ask each engineer how they prefer to receive feedback and record the answer
  • Add a link to the profile from your one-to-one notes for that person

Make it yours.

Install Engineering Team Management, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.