Important point for me. I used to think too much about WHAT I was doing instead of just doing it. I rolled every decision back and forth for too long instead of just getting started.
Wrong, because that way you're doing the fourth step before the third.
Look:
Envision
Plan
Execute
Improve
Those are my typical iteration steps. First, I think about where I want to be in 12 weeks (yes, I do a kind of quarterly), then I plan the weeks and days to get there, then I execute and improve afterwards to then re-plan with the insights gained.
The key here is to get into action quickly and afterwards improve the decision that led to the action.
It's also better to act first and then evaluate the decision because you only then have the "data" on which you can base your evaluation of the decision. You've taken a path, acted, achieved a result, and now you can evaluate this outcome to derive the next steps.
Sounds logical, yet I know many (including my former self), who do it the exact opposite way.
Nikolai Fischer is the founder of Kommune3 (since 2007) and a leading expert in Drupal development and tech entrepreneurship. With 17+ years of experience, he has led hundreds of projects and achieved #1 on Hacker News. As host of the "Kommit mich" podcast and founder of skillution, he combines technical expertise with entrepreneurial thinking. His articles about Supabase, modern web development, and systematic problem-solving have influenced thousands of developers worldwide.
Ihre Anmeldung konnte nicht gespeichert werden. Bitte versuchen Sie es erneut.
Comments