Skip to content
signalby Travis Loudin

Type to search.

    manuals /leadership / leading-tech-teams

    Leading Tech Teams

    by Travis Loudin
    Part 13 of 15field-testedplanted

    Software and IT have their own well-known laws. Each one carries a leadership lesson that non-technical leaders often miss.

    Principle Source Leadership lesson
    Brooks’s law: Adding people to a late software project makes it later. Fred Brooks, The Mythical Man-Month New people need ramp-up time from your experts. Cut scope or move the date before adding headcount to a late project.
    Conway’s law: Organizations build systems that mirror their own communication structure. Melvin Conway If two teams don’t talk, their systems won’t integrate well. Fix the communication, not just the code.
    Goodhart’s law: When a measure becomes a target, it stops being a good measure. Charles Goodhart, popular phrasing by Marilyn Strathern Ticket counts and closed tasks get gamed once they’re targets. Pair metrics with judgment and conversation.
    Hofstadter’s law: It always takes longer than you expect, even when you account for Hofstadter’s law. Douglas Hofstadter, Gödel, Escher, Bach Build buffers into commitments. Under promise, over deliver.
    The ninety-ninety rule: The first 90% of the work takes 90% of the time. The last 10% takes the other 90%. Tom Cargill, Bell Labs “Almost done” is a warning sign. Ask what’s left, not how far along it is.
    Parkinson’s law: Work expands to fill the time available. C. Northcote Parkinson Set clear, reasonable deadlines. Open-ended work drifts.
    Chesterton’s fence: Don’t remove a fence until you know why it was put up. G. K. Chesterton Understand why a legacy process or system exists before tearing it out. New leaders are especially prone to this.
    The Boy Scout rule: Leave the code cleaner than you found it. Robert C. Martin, Clean Code Encourage small, continuous improvements so technical debt never needs a heroic cleanup.
    “Make it work, make it right, make it fast.” Widely attributed to Kent Beck Sequence matters. Don’t let polish or optimization block a working first version.
    The bus factor: How many people could disappear before a project stalls. Common software usage A bus factor of one is a risk to the business and a burden on that person. Cross-train deliberately.
    Two-pizza teams: Teams small enough to feed with two pizzas. Amazon Small teams communicate faster and own more. Split before a team gets unwieldy.
    The Peter principle: People rise to their level of incompetence. Laurence J. Peter Your best engineer won’t automatically be a great manager. Offer technical growth paths and train new managers.
    Hanlon’s razor: Never attribute to malice what is adequately explained by a mistake. Robert J. Hanlon; the original says stupidity Most outages and missed handoffs are process gaps, not bad actors. Look for the gap.