The powerful compounding effect of selective quantity over quality.
The algorithmic model in this post more than doubled my productivity, and it might do the same for you. It demonstrates the compounding effects from the different aspects of rushing. Everyone knows rushing leads to more productivity, but actually analyzing those aspects and their results in an algorithmic model can be very helpful. How well you balance your priorities determines your level of success/failure. Regardless of what your goals are, this algorithmic model should help rebalance those priorities.
I created this model to analyze those aspects and their results using Omnilow algorithmic language. Here is the Main Description for Omnilow. Omnilow is fairly intuitive and this algorithmic model is fairly simple, but I would still recommend reading that post or at least its Omnilow Rules section before diving into this model.
As shown in this model, rushing even slightly more might result in being many times more productive. To fully understand it, you will probably need to read it at least twice (because naturally some algorithms have variables that aren't defined until a later algorithm).
I would suggest reading this algorithmic model as the file below with Notepad++. A big reason I suggest Notepad++ is because Notepad++ can effectively highlight/indicate parentheticals. That functionality is extremely helpful for reading these Omnilow algorithms. I would recommend having "Word wrap" turned on in Notepad++.
I, Samuel Sauer, created and wrote this post and that file and all the significant concepts in them. I made this algorithmic model so other people could learn from it and to showcase how useful Omnilow algorithmic language can be for solving real-world "Complex Problems". As discussed in the Main About Page, please don't hesitate to get in touch if you or your organization could use my assistance (which could involve making an algorithmic model like this one to provide ideation).
Appendix
I think this algorithmic model would be many times longer (or would be harder to understand) if that model was written in a more mainstream algorithmic language, especially the "(Not Undefined Rule)" variable that is in that model. I'm not sure that variable would even be possible in traditional mathematics, and it is quite necessary to have be able to properly use "(Base Demonstration #1)".
If you're an algorithmic hotshot and would prefer to read it without any helpful functionality, you can do so below. I would recommend only downloading the file above and not referring to the below copy.
Copy Of That .txt File’s Contents
Base Demonstration #1
(
((Base Demonstration #1)=((Optional Tasks)(Base Daily Task Amount)((multiple)((Person)(in)(Base Demonstration #1)))(Working Time)(Start Time)(Not Undefined Rule)))
{Everything in this parent-most parenthetical are only about describing/defining (Base Demonstration #1).}
{(Base Demonstration #1) demonstrates huge compounding benefits from rushing more. By how much a person rushes, I only mean how much faster that person generally does task(s) and how much less that person pursues less important task(s).}
((Optional Tasks)=((Optional Tasks Number)(of)(Task)))
((Person #1)=((Person)(in)(Base Demonstration #1)))
((Person #1)=(((Hour Completion Rate)(Daily Task Rate)(Daily Tasks))(of)(Person #1)))
(((Daily Tasks)(of)(Person #1))=(((Base Daily Task Amount)*((Daily Task Rate)(of)(Person #1)))(of)(Task)))
{(Optional Tasks) are a set of low priority tasks that each person is suppose to do. A person's Daily Tasks is how many higher priority tasks he/she gets per day. The (Base Daily Task Amount) is how many Daily Tasks a perfectly normal person would get per day.}
((((Hour Completion Rate)(of)(Person #1))=(((number of)(Task))(of)((Task)(in which)((Person #1)(completes)((during)((1(Hour))(in)(((Working Time)(for)(Person #1))(in)(Specific Day #1)))))))=(((number of)(Task))(of)((Task)(in which)((Person #1)(completes)((during)((1(Hour))(in)(((Working Time)(for)(Person #1))(in)(Specific Day #2))))))))(as if person #1 isn't rapid))
(((Amount Of Workable Hours)=(((number of)(Hour))(of)(((Working Time)(for)(Person #1))(for)(Specific Day #1)))=(((number of)(Hour))(of)(((Working Time)(for)(Person #1))(for)(Specific Day #2))))(as if person #1 isn't rapid))
{The Amount Of Workable Hours is how many hours (each person has to work on the Optional Tasks and/or his/her Daily Tasks) per day.}
(((Working Time)(for)(Person #1))=((Time)(during which)((Person #1)(works on)((Optional Tasks)((and)(or)(or))((Daily Tasks)(of)(Person #1))))))
(((Days Until Completion)(for)(Person #1))>0)
((Not Undefined Rule)=(((if)(((((Hour Completion Rate)(of)(Person #1))*(Amount Of Workable Hours))-((number of)((Daily Tasks)(of)(Person #1))))=0))(then)(((Days Until Completion)(for)(Person #1))=∞)))
{For simplicity, Base Demonstration #1 assumes that a person in Base Demonstration #1 will at least accomplish his/her Daily Tasks per day.
If a person in Base Demonstration #1 accomplishes no more than his/her Daily Tasks per day, then he/she never works on any of the Optional Tasks but doesn't get behind on his/her Daily Tasks. That's represented by the "(Not Undefined Rule)" variable. It's called that because normally dividing by zero is undefined.}
((as if person #1 isn't rapid)=((as if)(((Days Until Completion)(for)(Person #1))≥2)))
((Specific Day #1)=(((Day)(in)(Time Before Person #1 Finishes))(as if person #1 isn't rapid)))
((Specific Day #2)=(((Day)(in)(Time Before Person #1 Finishes))(as if person #1 isn't rapid)))
((Start Time)=((Time)(in which)(((each)((Part)(of)(Base Demonstration #1)))(starts)(exists))))
(((Person #1)(completes)((Daily Tasks)(of)(Person #1)))(before)((Person #1)(works on)(Optional Tasks)))
((Time Before Person #1 Finishes)=(((Time)(after)(Start Time))(until)((Person #1)(completes)(Optional Tasks))))
(((Days Until Completion)(for)(Person #1))=(((number of)(Day))(of)(Time Before Person #1 Finishes)))
(((Days Until Completion)(for)(Person #1))=((Optional Tasks Number)/((((Hour Completion Rate)(of)(Person #1))*(Amount Of Workable Hours))-((number of)((Daily Tasks)(of)(Person #1)))))=(((Optional Tasks Number)+(((number of)((Daily Tasks)(of)(Person #1)))*((Days Until Completion)(for)(Person #1))))/(((Hour Completion Rate)(of)(Person #1))*(Amount Of Workable Hours))))
)Specific Demonstration #1
(
((Specific Demonstration #1)=(((some)(specific))(Base Demonstration #1)))
{Everything in this parent-most parenthetical is only about (Specific Demonstration #1).}
((Optional Tasks Number)=800,000)
((Base Daily Task Amount)=80)
((Amount Of Workable Hours)=8)
{There are 800,000 Optional Tasks. The Base Daily Task Amount is 80. The Amount Of Workable Hours is 8.}
((Person A)=((Person)(in)(Specific Demonstration #1)))
(((Days Until Completion)(for)(Person A))=(800,000/((((Hour Completion Rate)(of)(Person A))*8)-(80*((Daily Task Rate)(of)(Person A))))))
(((Days Until Completion)(for)(Person A))(=(in standard mathematical graphing format))Z=(800,000/(X*8-80*Y)))
)Examples
(
{This parent-most parenthetical has examples of (Specific Demonstration #1).}
(
((Days Until Completion)(for)(Person A))((might)=)
(∞=(800,000/(10*8-80*1)))
(1,000,000=(800,000/(10.1*8-80*1)))
(100,000=(800,000/(11*8-80*1)))
(10,000=(800,000/(20*8-80*1)))
(1000=(800,000/(110*8-80*1)))
(100=(800,000/(1010*8-80*1)))
(∞=(800,000/(100*8-80*10)))
(1,000,000=(800,000/(100*8-80*9.99)))
(100,000=(800,000/(100*8-80*9.9)))
(10,000=(800,000/(100*8-80*9)))
(2000=(800,000/(100*8-80*5)))
(1111.11=(800,000/(100*8-80*1)))
(1000=(800,000/(100*8-80*0)))
(∞=(800,000/(50*8-80*5)))
(1,000,000=(800,000/(40.1*8-80*4)))
(100,000=(800,000/(36*8-80*3.5)))
(10,000=(800,000/(40*8-80*3)))
(1000=(800,000/(125*8-80*2.5)))
(100=(800,000/(1020*8-80*2)))
)
{The possible equalities above are based on "Z=(800,000/(X*8-80*Y))" which is described in the parent-most parenthetical above this parent-most parenthetical. So, the things to take note of when reading each of those possible equalities are the numbers acting as the Z, X, and Y.
The small changes to the X and/or Y resulting in major changes to the Z demonstrate the huge compounding benefits from rushing more. As shown in those changes, rushing even slightly more might result in being many times more productive.}
{After understanding what's in this file, I would probably recommend making your own examples of (Specific Demonstration #1) (or of (Base Demonstration #1) if you really want to dig in).}
)Share:
Copy This Post’s URL:
SS5.org/2025/01/16/Rush
Leave a comment.