Build it in

Build it in

Build it in 6 hours not 6 days.

Build it in 6 hours not 6 weeks.

Build it in 6 hours not 6 months.

Build it in 6 hours not 1 year.

I messaged a friend in May 2024 to ”Build it in 6 hours not 6 months”.

I did this because I wanted to save him from making the same mistake I made everyday for 6 months.

The result was that we built MVP V1 in 3 hours 45 minutes, built V2 the next day and had his friends testing V5 or V6 before the end of the week.

Ultimately, we killed the project about 2 weeks later but the total time sunk into it was less than 100 hours combined.

Unfortunately, between then and now I have not implemented my own advice, which is disappointing. It shows a level of regression in my ability to learn and retain lessons which change my actions.

“Learning means: same condition new behaviour.
Rate of learning means: number of times exposed to the same condition before executing a new behaviour.” — Alex Hormozi

The above quote really makes me upset when I fail to implement lessons I thought I had learned because how many 6 months do I have left? Not many. But how many 6 hours do I have left? A lot!

“Impatience with actions, patience with results.” — Naval Ravikant

I like “Impatience with actions” and I see it compliments this section of my quote: “Build it in 6 hours”. However upon self reflection I seem to have poorly implemented ”patience with results.”.

  • Understand what you want.
  • Understand what needs to be done to get you that.
  • Create a plan of action, not a plan of inaction.
  • Do the actions, learn quickly and keep focusing on maxing out the quality and quantity of the inputs whilst being patient on the outputs.
  • Complete actions in “6 hours” instead of “6 months” wherever possible

Notes:

My take on quality of inputs is that it’s easy to create a 20 step plan on how you will do A then B then C then D then [INSERT MANY STEPS] so that you can finally get X. I catch myself doing this often when it really should be simpler. Instead thinking from first principles helps me and getting the plan of ACTION down to: I am going to do X so that Y and then Z..

Alex Hormozi has a pretty good take on quantity of inputs.

Quantity: Do so much volume that it would be unreasonable that you would be unsuccessful.

But the purpose of this note is to remind myself to do a task orders of magnitude faster than I initially think is needed as work expands to fit the time set for its completion.

This note was written by Odin Bryant himself, kept brief out of respect for your time, without the use of LLMs.