Momentum Bonus

Notes on reproducible hyper productivity. Written 3 months ago.

Breaking large insurmountable tasks into smaller manageable subtasks enables hyper-productivity. I found that completing a high volume of small tasks results in a larger area under the productivity curve due to a ‘momentum bonus’ when compared to completing fewer monolith tasks.

Let’s prove it mathematically.

Definitions. Momentum is a mass in motion p=mvp=mv. Let’s define velocity to be productivity and mass to be the magnitude of the task being completed.

Momentum is conserved so if two objects AA and BB collide, elastically, mava+mbvb=mava+mbvbm_av_a + m_bv_b = m_av_a' + m_bv_b' where vv' represents their posterior velocities, respectively. In the inelastic case mava+mbvb=(ma+mb)vm_av_a + m_bv_b = (m_a+m_b)v kinetic energy is not conserved and lost to the environment. The analogy in the context of productivity is switching from task AA to task BB after either AA has been completed or not. The reason I model context switching as a collision is because it can be classified as elastic or inelastic. Kind of neat.

For a quick refresher:

  • Elastic collisions have both momentum and kinetic energy conserved e.g. throwing billiard balls against the edge of a pool table and it comes back just as fast
  • Inelastic collisions only have momentum conserved e.g. you trying to push your friend off a cliff (their kinetic energy is converted mostly to friction on the ground)

The coefficient of restitution is designed to quantify collision elasticity

e=vbvavavb.e = \dfrac{v'_b - v_a'}{v_a - v_b}.

The value of ee means that

  • e=0e= 0 is perfectly inelastic
  • 0<e<10< e < 1 is real-world inelastic
  • e=1e = 1 is perfectly elastic
  • e>1e > 1 occurs in special cases where the collision results in an explosion
  • e=e = \infin when there is a perfect explosion of a rigid system

Back to productivity.

Case 1: You fully completely task AA and move onto BB (elastic)

Since mava+mbvb=mava+mbvbm_av_a + m_bv_b = m_av_a' + m_bv_b' you’re posterior velocities remain unchanged i.e. you haven’t hit the wall yet. At this point you’ll have the maximum momentum prior to starting task BB. God speed.

Case 2: You don’t fully complete task AA and move onto BB (inelastic)

This case falls under the condition where 0e<10\le e < 1 which means your posterior velocity will decrease from loses to the environment hence mava+mbvb=(ma+mb)vm_av_a + m_bv_b = (m_a+m_b)v. By definition we know that vva,vbv \le v_a, v_b. We can re-arrange to get

v=mava+mbvbma+mb.v = \dfrac{m_av_a + m_bv_b}{m_a+m_b}.

If we decrease either mam_a or mbm_b whilst increasing vav_a or vbv_b then the final velocity vv increases. The real-world analogy is have maximum productivity on the smallest task possible results in a larger final velocity for your next collision i.e. task CC. Unfortunately we don’t live in a world where vv\rightarrow \infin. Productivity always feels like it tapers at a physical maximum. There’s many different methods to increasing vav_a and vbv_b, namely:

  • Great sleep
  • Physical exercise
  • Standing desk
  • Frequent breaks
  • Deep focus/flow state triggered from deep curiosity

Once you’ve applied everything from this list (and your own personal hacks not included in there) the only thing left to do is to start shaving down mam_a and mbm_b to non-zero values.

We always strive to have our days structured as a sequence of case 1 victories, but reality is way more brutal. I find myself frequently in case 2 territory, but now with a theoretical framework—a new attack angle.