Aim, Fire, Scan: The 80/20 of Executing on Big Projects by Indie Hackers
Metadata
- Author: Indie Hackers
- Full Title: Aim, Fire, Scan: The 80/20 of Executing on Big Projects
- Category: #articles
- URL: https://www.indiehackers.com/post/aim-fire-scan-the-80-20-of-executing-on-big-projects-571580cd0a
Highlights added January 31, 2024 at 11:02 AM
By inputs, I really just mean time: "How many hours did I put in versus the amount of hours I was supposed to put in?" Outputs is more self-explanatory: "Did I ship my must-ship objective?" (View Highlight)
What I do is identify at least one of these flaws at the end of each iteration cycle. (View Highlight)
So I made an adjustment: within 30 minutes of waking up, I needed to get started on the manuscript and knock out at least 2 hours of work before opening the pandora's box of digital distractions. (View Highlight)
The second reason why this is good is because writing is thinking. Often, the act of writing your learnings from the iteration will lead to far greater clarity about your performance than you could gain otherwise. It's similar to the process of rubberducking. (View Highlight)