4 ms·

>> take stock of the “what” you’re asking as well as the “how.” I think a lot of errors stem from assuming that "what" and "how" are somehow distinct concepts.

>> take stock of the “what” you’re asking as well as the “how.” I think a lot of errors stem from assuming that "what" and "how" are somehow distinct concepts. In reality they are the same thing, we are just describing objectives at varying levels of abstraction. There are important inflection points along the entire gradient.

space_oddity 2y ago
Delegation doesn’t demand strict separation between "what" and "how"
- Suppafly 2y ago
  >Delegation doesn’t demand strict separation between "what" and "how" Sure, but a lot of times, figuring out the how is what takes the time, if you're figuring out the how you might as well not delegate it at all.
  - space_oddity 2y ago
    Delegation isn’t just about offloading tasks; it’s about leveraging team expertise
    - Suppafly 2y ago
      My point still stands.
whatshisface 2y ago
Perhaps a better way to phrase what the author was saying is that you need to tell your reports the things that you know more than them about (which incidentally usually is direction), but should avoid trying to prescribe things that it is their job to know more than you about (which incidentally covers most things about the codebase they see every day). "I'll run so far ahead of my team that I won't need their advice" - last spoken words of a new lead who died trying to do eight jobs faster than the people hired to do them. ;)
- osigurdson 2y ago
  Agree. However, avoid becoming an information gatekeeper. Usually higher level objectives can be explained in 30s or less.
Attummm 2y ago
Although how and what are connected, they are not the same. For example, 'I would like to become fit and healthy.' 'What' is getting fit and healthy, but 'how' has almost endless possibilities, each with their own success level and compatibility with you and your lifestyle. Just like nouns and verbs are connected, they are not the same.
- osigurdson 2y ago
  Getting fit and healthy is an objective, you now choose concrete sub objectives (such as running), more concrete objectives included buying a pair of running shoes. Like many things, inflection points along the way make all the difference. Details matter, just not all details. Similarly, a higher level objective to "getting fit and healthy" might be "achieve long life" which in itself may have a range of sub objectives and varying levels of abstraction. So yeah, all just objectives, no "the what", no "the how".
  - Attummm 2y ago
    The "what/how" distinction is fundamental. If the "what" is getting healthy and fit, that is a very high-level goal. Within your example, you choose the "how" through running It could've been walking in nature, going to the gym, or doing calisthenics. all of them different "hows". But since your example made a choice, we are now one level deeper and more concrete than before. The what/goal has in this level become to run a 5K, and the how/method is how you will train to achieve that goal. "How" and "what" can be very conceptual, especially at a high level, and just like the 5 Whys technique, it could take a few levels to become concrete. Top-down programming is often taught by separating the "how" and the "what." For example: customer = get_customer(id=id) The "what" is getting the customer. The "how" is not revealed, yet its intent is clear. Within the function get_customer we could have another 'what' for example run_query Top-down programming will often first skip the "how" and focus only on the "what" by writing the functions, methods, and classes later on. https://en.m.wikipedia.org/wiki/Bottom%E2%80%93up_and_top%E2%80%93down_design https://en.m.wikipedia.org/wiki/Bottom%E2%80%93up_and_top%E2...
    - 2y ago
goodcanadian 2y ago
What and how are most definitely not the same thing. They aren't necessarily even related: If you tell people where to go, but not how to get there, you'll be amazed at the results. George S. Patton

space_oddity 2y ago

Delegation doesn’t demand strict separation between "what" and "how"

Suppafly 2y ago
>Delegation doesn’t demand strict separation between "what" and "how" Sure, but a lot of times, figuring out the how is what takes the time, if you're figuring out the how you might as well not delegate it at all.
- space_oddity 2y ago
  Delegation isn’t just about offloading tasks; it’s about leveraging team expertise
  - Suppafly 2y ago
    My point still stands.

whatshisface 2y ago

Perhaps a better way to phrase what the author was saying is that you need to tell your reports the things that you know more than them about (which incidentally usually is direction), but should avoid trying to prescribe things that it is their job to know more than you about (which incidentally covers most things about the codebase they see every day). "I'll run so far ahead of my team that I won't need their advice" - last spoken words of a new lead who died trying to do eight jobs faster than the people hired to do them. ;)

osigurdson 2y ago
Agree. However, avoid becoming an information gatekeeper. Usually higher level objectives can be explained in 30s or less.

Attummm 2y ago

Although how and what are connected, they are not the same. For example, 'I would like to become fit and healthy.' 'What' is getting fit and healthy, but 'how' has almost endless possibilities, each with their own success level and compatibility with you and your lifestyle. Just like nouns and verbs are connected, they are not the same.

osigurdson 2y ago
Getting fit and healthy is an objective, you now choose concrete sub objectives (such as running), more concrete objectives included buying a pair of running shoes. Like many things, inflection points along the way make all the difference. Details matter, just not all details. Similarly, a higher level objective to "getting fit and healthy" might be "achieve long life" which in itself may have a range of sub objectives and varying levels of abstraction. So yeah, all just objectives, no "the what", no "the how".
- Attummm 2y ago
  The "what/how" distinction is fundamental. If the "what" is getting healthy and fit, that is a very high-level goal. Within your example, you choose the "how" through running It could've been walking in nature, going to the gym, or doing calisthenics. all of them different "hows". But since your example made a choice, we are now one level deeper and more concrete than before. The what/goal has in this level become to run a 5K, and the how/method is how you will train to achieve that goal. "How" and "what" can be very conceptual, especially at a high level, and just like the 5 Whys technique, it could take a few levels to become concrete. Top-down programming is often taught by separating the "how" and the "what." For example: customer = get_customer(id=id) The "what" is getting the customer. The "how" is not revealed, yet its intent is clear. Within the function get_customer we could have another 'what' for example run_query Top-down programming will often first skip the "how" and focus only on the "what" by writing the functions, methods, and classes later on. https://en.m.wikipedia.org/wiki/Bottom%E2%80%93up_and_top%E2%80%93down_design https://en.m.wikipedia.org/wiki/Bottom%E2%80%93up_and_top%E2...
  - 2y ago

goodcanadian 2y ago

What and how are most definitely not the same thing. They aren't necessarily even related: If you tell people where to go, but not how to get there, you'll be amazed at the results. George S. Patton