A somewhat similar situation...
danyoung wrote:Using TR, I was able to present my projects to my boss in a more organized fashion. I walked him through my entire workload, so that we could prioritize my projects and delegate. He could hardly deprioritize anything - almost all of my projects were mission-critical. There were only a few areas that I could delegate outside my team. So instead he decided to give me more resources.
With TR it became obvious to me
that I was in deep trouble with the amount of tasks and the given schedule. However, my current project schedule is very tight, my job requires technical knowledge that is very hard to come by (licensing, NDA:s, bureaucracy etc) and the learning curve is quite steep, so there is really no way to delegate to anyone
As requirements and requests arrive, it's now easy to talk them over with my boss and prioritize them.
danyoung wrote:TR made the difference between me complaining that I was overloaded (which was ineffective) and being able to SHOW my boss exactly how many projects I was carrying so we could make smart decisions and do something about it (which was very effective!).
Here's where I'm still struggling. I'm using the delta version of 2.0 and reports are still being worked on. Unless I can get my team/boss to actually open up my TR file, I can only improvise a short list of tasks.
However, what has happened, is that I've learned to say "no" to internal requests more often. A single glance at the actions screen is usually enough to make a go/postpone/no-go decision with my colleagues, even without the explicit approval of my boss.