From what you've described, you're like most people -- mananaging multiple competing tasks isn't something that comes naturally to everyone. There are plenty of tricks for keeping track of them, the easiest of which is to just keep a written record of everything that needs to be done.
For large projects, where there are multiple people involved in development, you can place the items in a ticket tracking system, like bugzilla, or trac.
For tasks specifically on you, you can just keep a book. I've seen different techniques, from keeping a list on a whiteboard (benefit -- other people can glance in and see how loaded you are), or keeping a daily notebook (each morning, copy down everything that wasn't crossed out from the day before, and cross out items as they get done. benefit -- you have a daily reminder of what's outstanding).
Sometimes, you just have to learn when to say you're overloaded, and be willing to pass off issues to someone else. It's taken me many, many years to be willing to pass on responsibilies to other people, as it's kinda like admitting defeat and asking for help, and sometimes it requires more work when you have to clean up after their work or if they keep asking you questions about it, but if you work with other skilled people, it's not so bad.
Also, you mention that you make sure that everything gets done, and gets done properly, which is a good trait, but you have to be sure that you're really sure what's required, and what's just something that you want -- I have a few outstanding projects that I made a major number of modifications that would benefit users, but I went to add a few more things that were more complicated than I thought they would be, and got sidetracking, which results in no one benefiting from my earlier changes, as I didn't commit my changes at the right time, and I'd have to spend more time trying to sort things out.
If you've been doing the same basic thing for a few years, you might've outgrown your position, and it's time to move on, and find new opportunies for learning, but depending on your personality, it might be better to go to something where you have skills, but aren't an expert, so you can keep learning new things. (these days, I'm most likely to take a job based on the other people I'd work with, than anything else .. okay, and a non-crappy commute)
Try to figure out what you like doing, and what skills you need to develop to best do it. In your case, if you really like developing stuff, you might prefer to develop your organization skills, rather than trying to find a job that avoids the problem. (of course, if you don't like development, then sure, go and find something else)
You might also look into the concept 'life hacking', which is trying to streamline things, and deal better with interuptions, but I'm not sure what the best resources are for it.
In reply to Re: OT: Testing, operations and support resources
by jhourcle
in thread OT: Testing, operations and support resources
by talexb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |