Rereading 'Getting Things Done' by @gtdguy (David Allen)
I didn't exactly *finish* the first time - and it still helped a BUNCH.
The biggest issue for me is that The Network Operations Company does so MANY things with so few employees. Keeping track of what we're doing, who we're doing it for, who is working on it and where else we can apply what we're learning/doing/building is always a struggle. Add the struggle of most of our staff working part-time, and I end up with a lot to track.
The premise of GTD (my paraphrasing) is that if you have a system to keep track of everything that's going on - and the very next thing that needs to happen to reach each goal or outcome - then you can stop worrying about missing something and let your brain be more productive. When I shift from working with our graphics guy to getting an update from a coder to taking a tech support call to getting sign-off on a new project all in the space of 10 minutes or less, it would certainly help to have access to my whole brain. And no, that's not an ususual 10 minutes in our office - that's normal.
Well, it's the frenzied version of normal that keeps our office interesting.
If you are interested, Google 'gtd' and see just how pervasive this methodology has become. http://davidco.com
