Earlier quoted context omitted.
> OODA loop? Observe, Overreact, Deny, Apologise? [Edit]. Just kidding. OODA is foundational.
I'm Out Of DA loop, can anyone explain...
Aim, fire, scan: the 80/20 of executing on big projects
41–46 of 46 posts
Re: Aim, fire, scan: the 80/20 of executing on big projects
#42Am in between house rentals at the moment and the general concept of “commitment agreements” is one that’s been on my mind. Particularly the desire to pay 6 or X months up front for a place - maybe it exists in the commercial space but haven’t seen it for general residential agreements.
Some cool points made in this article thanks for sharing. It’s a bit broad and formulaic to be directly actionable in my opinion but that can be seen as good/bad depending on the reader
Re: Aim, fire, scan: the 80/20 of executing on big projects
#43These goal escrow sites, like stickK, beeminder are not my thing but glad they help people. Here are some other hacks: 1. Set your standards ( https://www.youtube.com/watch?v=aUck-umj2WI , yes it is him, but it is good.) 2. If plausible, release something shit / half done. You will feel embarrassed and want to fix it up. 3. Just get started. Do a minute. Soon you will be in work mode, and forcing yourself to no to do…
> 4. Try to do fun stuff if possible. Going to the gym is not fun, but it feels good after. But if you have a side project, make it a fun one, something you really are in to. I'm not entirely with you about gyms in particular. Weights might just not be your thing as an individual, but "going to the gym is not fun" is often about the logistical problems of timing around gyms (peak hours, January rushes especially) and…
[deleted]
Re: Aim, fire, scan: the 80/20 of executing on big projects
#44Earlier quoted context omitted.
> OODA loop? Observe, Overreact, Deny, Apologise? [Edit]. Just kidding. OODA is foundational.
I'm Out Of DA loop, can anyone explain...
See sibling comment for a good definition. OODA is the repetitive loop of observing, understanding, planning and executing. The military talk about getting inside the enemy's OODA loop, by which they mean having a faster decision-making cycle.
But back in the network-enabled-capability day, they also used to talk about self-synchronising units operating on the cusp of tactical anarchy, but then Afghanistan happened and they had a collective sense-of-humour failure regarding these future operational concepts.
Re: Aim, fire, scan: the 80/20 of executing on big projects
#45Strongly agree. I think a point not explicit in OP's article is having low quality initial Plans in order to move forward.
Logically, we want a Plan to move towards our Goal. As Engineers we often suffer from Analysis Paralysis: lots of paths to the goal with no clear winner. We also slow down from Impostor Syndrome: surely a smarter/more talented person knows the one true Plan forward to the goal.
> I make a plan, then do the plan, then learn from my efforts by reviewing my progress. I do this every day of the year, going on half a decade now. [At many time scales: three hour cycles going up to three-month cycles.]
I believe OP would agree that the Plan should be low quality, at least at the beginning. This encourages forward movement, and learning, vs just planning in circles and without using real-world data.
Source: writing a book on Feedback Loops
Re: Aim, fire, scan: the 80/20 of executing on big projects
#46Strongly agree. I think a point not explicit in OP's article is having low quality initial Plans in order to move forward. Logically, we want a Plan to move towards our Goal. As Engineers we often suffer from Analysis Paralysis: lots of paths to the goal with no clear winner. We also slow down from Impostor Syndrome: surely a smarter/more talented person knows the one true Plan forward to the goal. > I make a plan, t…
> I believe OP would agree that the Plan should be low quality, at least at the beginning.
OP emphatically agrees. Overplanning is arrogance in a world with so many unknown unknowns.