Thread

1. cube00 · 1789928452 · focus · HN ↗

   I can't say I agree with forcing your team to use your own personal "framework" of approaching a problem or else you'll get "feedback".

   > Sometimes I will give feedback to people when they are missing steps in the framework, or are poorly executing some of the steps. I expect the same feedback in return.

   I also don't like that urgency is built in as the standard process either, no wonder everyone is burnt out.

   > 6. Act with urgency to achieve the goal

   1. adamsb6 · 1789931712 · focus · HN ↗

      It’s basically OODA loop, which is itself just as descriptive of how people act and adjust than it is prescriptive.

      How else would you describe iteratively solving problems?

      1. baxtr · 1789933071 · focus · HN ↗

         Interestingly enough the problem with most of problem solving is identifying the right problem to solve.

         It may sound weird but OODA starts making sense once you’ve identified the right problem to focus on.

         In its original definition it was based on dogfights. There, your problem is clearly defined.

         1. datadrivenangel · 1789933269 · focus · HN ↗

            and the fun question of how do you find good problems is very hard to systematize!

Unofficial Hacker News client; not affiliated with Y Combinator.