{"canonical_url":"https://engineer.company/glossary/technical-leadership/","content_markdown":"# Technical leadership\n\n## What it is\n\nTechnical leadership is the work of helping a team make, explain and follow through on\ntechnical decisions. It includes making the goal clear, giving people room to use their\njudgment and creating a way to learn from what happens after a decision. It can be part of a\nmanager's job, a staff engineer's work or the responsibility of someone leading a single\nchange. The test is whether the team can make a better decision and carry it through with\nclear ownership.\n\nA decision about architecture has several owners in different senses. The person making the\ndecision needs a mandate and a deadline. The people implementing it can see costs that are\ninvisible on a diagram. Whoever will operate the result has to be able to diagnose and recover\nit. A product owner or sponsor can say which user outcomes matter and which constraints are\nfixed. Technical leadership gives all these facts a place in the decision and makes clear who\ncloses it. Asking for input creates an opportunity to identify a risk. It does not give every\nparticipant a veto.\n\nThe joint ACM and IEEE Computer Society software engineering code gives this authority a\nconcrete purpose. Principle 5 makes engineering managers and leaders responsible for promoting\nan ethical approach to managing development and maintenance. Its clauses cover procedures for\nquality and risk reduction, realistic estimates and fair consideration of concerns. Principle\n7 asks engineers to help colleagues develop, review their work objectively and hear their\nopinions and complaints. These responsibilities fit together. Giving someone ownership\nincludes giving them the information, support and chance to speak up that they need to\nexercise it.\n\n## Why it matters\n\nSoftware work often brings incompatible constraints into the same room. A team can spend a\nweek reducing the risk of a change and still miss a delivery deadline. It can meet that\ndeadline and give support a manual procedure it has no capacity to perform. Choosing among\nthose costs is part of the work. The leader makes the effect on each party visible while there\nis time to change the plan. An early discussion about how to reverse a release can change the\norder of the implementation and avoid days of rework.\n\nDelegation gives people closer to the problem a chance to make choices with better\ninformation. It also develops the next person who can lead work independently. A useful\ndelegation defines the result, names the boundaries and agrees when to check in. A person who\nowns a migration might choose the order of the tables and the size of the batches. A decision\nthat changes the promised outage or makes a rollback impossible could require another\napproval. These boundaries let the person proceed with confidence and let other teams see\nwhich decisions affect them.\n\nFeedback closes the loop. During review, useful feedback names the observed behavior, who it\naffects and what a better outcome would look like. After the change, feedback compares the\nresult with the original intent. A faster import may reduce overnight processing and still\nincrease daytime contention. Reviewing both results helps the team keep what worked and\nreconsider what it originally assumed. A decision record earns its place when a new colleague\ncan read it and tell which evidence would justify revisiting the choice.\n\n## What it looks like in practice\n\nImagine a booking team whose support staff sometimes have to correct duplicate confirmations.\nA meeting starts with proposals to replace the queue, add a lock or change the order of\nwrites. The technical lead asks for one incident reconstructed from an order identifier, the\nintended behavior and a way to demonstrate that behavior. The group agrees on a rule the\nbusiness can recognize. Resending the same booking request must return the existing\nconfirmation, and a retry must never reserve a second place.\n\nThe engineer who knows the booking path proposes where to enforce that rule. A second engineer\nwrites concurrent test requests and checks the result from both the customer and operations\nsides. Support tests the message it would use when a booking is retried. The lead makes the\nreview deadline and owner explicit, and confirms with operations how the change can be paused\nif errors rise. The engineers choose the implementation. The team has a clear point at which\nto raise a change to the customer contract, with commercial and operational colleagues present\nfor that decision.\n\nA useful decision record might fit on half a page. It identifies duplicate bookings as the\nproblem, records why the team chose an approach, lists the behavior demonstrated by tests and\nstates what operators will monitor. It names who will judge the first week of results and what\nsignal warrants another look. It also records a rejected alternative with the reason. If\nretries become much more frequent than expected, the next team can revisit the design without\nguessing why it was first chosen.\n\nEngineer’s case on\n[setting a platform's founding technical decisions](/portfolio/set-the-platforms-founding-technical-decisions/)\nis a concrete example of architectural choices documented as part of the work. Its case on\n[directing full-stack GIS map development](/portfolio/directed-full-stack-gis-map-development/)\ngives another context, where technical direction extends across layers of a map product. The\n[Technical Leadership \u0026 Consulting service](/services/technical-leadership/) describes the\nsort of engagement in which technical direction and assessment are part of the work. The\nbooking scenario here is an illustration of the decision process.\n\n## Where it goes wrong\n\n**The lead becomes the approval queue.** The same person must approve familiar changes, minor\nimplementation details and work with genuinely expensive consequences. Waiting encourages\npeople to combine unrelated choices into a single approval. Agree in advance on which\ndecisions are local, which need a specialist and which have consequences broad enough for\nexplicit approval. Review how long each kind of decision is waiting before adding another\nstep.\n\n**An assignment comes without authority.** A developer is asked to own a result while another\nperson keeps choosing the means in private. Clarify who decides, where someone may challenge\nthe decision and what information needs to be brought to an escalation. If the constraints\nleave one permissible option, be direct about that before asking the engineer to take the\nwork.\n\n**Feedback becomes a verdict on the person.** Comments such as “you always overcomplicate\nthis” give the author little to do. Identify one decision and show the consequence. “Two jobs\ncan now update the same booking, so can we show what happens on a retry?” is specific enough\nfor someone to reproduce. In review, immediate corrective feedback can sit alongside a\nseparate coaching conversation about a broader pattern.\n\n**The decision has no return date.** Teams remember who approved a design and forget which\nevidence would overturn it. Put a date on the first review or name an event that will trigger\nit. At that point, look at outcomes, unresolved risks and the effect on the people who use or\noperate the system. Keep the line of authority clear so someone can act on what the team\nlearns.\n\n## Further reading\n\n- [Software Engineering Code of Ethics and Professional Practice](https://www.computer.org/education/code-of-ethics)\n  — the joint ACM and IEEE Computer Society code, especially its principles on management and\n  colleagues.\n- [Kubernetes community membership](https://github.com/kubernetes/community/blob/main/community-membership.md)\n  — an open project's definitions of reviewer, approver and related responsibilities.\n- [Google's standard of code review](https://google.github.io/eng-practices/review/reviewer/standard.html)\n  — review judgments, mentoring and improving the health of the code over time.\n\n\u003chttps://engineer.company/glossary/technical-leadership/\u003e\n","date_modified":"2026-11-19T06:00:51Z","description":"How engineering leaders set direction, delegate technical decisions, give feedback and stay accountable for the results.","formats":{"gemtext":"https://engineer.company/glossary/technical-leadership/index.gmi","gopher":"https://engineer.company/glossary/technical-leadership/gophermap","html":"https://engineer.company/glossary/technical-leadership/","json":"https://engineer.company/glossary/technical-leadership/index.json","markdown":"https://engineer.company/glossary/technical-leadership/index.md","pdf":"https://engineer.company/glossary/technical-leadership/index.pdf"},"kind":"page","language":"en","title":"What is technical leadership?","url":"https://engineer.company/glossary/technical-leadership/","version":1}