Software Engineering, Project Management, and Effectiveness
In my 30 Day Improvement Sprints post, a reader asked, what tips do I have to make 30 days sprints more effective. Here's my short list
Few problems withstand sustained focus. There's a bit of captive genius in everyone that just needs to be uncorked. 30 days of focused improvement seems to be a great way to pop the cork. I'm finding improvement sprints refreshing because I now have a schedule for exploration. I can rotate through more interests. Most importantly, rather than tackle everything all at once, I just wait for my next 30 day focus. It's easier to put something aside for the moment, if I know I'll have a chance to immerse myself in it in the future. If I enjoyed something so much and I want to continue, I just do another 30 days.
Hope that helps!
Great advise, and perfect timing.
Whether I'm working on a 30 Day Improvement Sprint , or working through a complex problem, I find journaling
Why 30 Day Improvement Sprints ? I get asked this often enough that I think I should distll the keys:
Here's my short-list of techniques I use for improving efficiency on a given task: Increase the frequency
Do you have to be great at everything? If this stops you from doing things you want to try, then it's
Routines help build efficiency and effectiveness. Consistent action over time is the key to real results.
Each month I pick a focus or a theme for my improvement sprint.  I find it's easier to start and