‹ BackHN Continuity

Thread

I don't want the details

466 points · 226 comments · mooreds

  1. FartyMcFarter · · focus · HN ↗
    > Then I realised that "I don't want the details" wasn't being dismissive. The executive assumed that we were competent, and was saying "I already believe you. Now let's talk about what happens next".

    Something about this feels wrong:

    - If you trust them completely, you don't need to know what happens next either. Just trust them to do the right things, your leadership isn't required.

    - If you don't trust them completely, how can you know if "what happens next" is appropriate without knowing the details?

    Isn't this just reinforcing the idea that leadership doesn't need to have their feet on the ground?

    The best leaders I've worked with were paying attention to things from the bottom-up as well as top-down.

    1. layer8 · · focus · HN ↗
      One reason is prioritization. It’s enough to know what the effects of the failure were, the likely cost of what needs to change, and what areas and processes the changes will affect, to decide if and when this should happen.

      Leadership still needs to understand these aspects on a conceptual, topical, and cost level to decide on the resource allocation (including time and schedule). They don’t need to understand the technical details, unless they are a technical leader with higher relevant technical competence than their reports.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.