Forum

  • If you are new to these Forums, please take a moment to register using the fields above.
Announcement Announcement Module
Collapse
No announcement yet.
Tracking others projects... Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tracking others projects...

    Hi all,

    I seem to remember reading a good tip about this on the forum a while back, however, I can't seem to find it. What I'm looking for is tips on how to track projects that have been delegated to my staff.

    I manage a group of three people, and think that it would be helpful to have some kind of list of their projects. I remember reading something on here where people used @Projects - JD (their initials), etc.

    Any tips?

  • #2
    Here you go

    http://www.davidco.com/blogs/kelly/a...ng_delega.html

    Comment


    • #3
      Thanks for the info!

      I was really hoping to get some tips surrounding tracking other's projects, not necessarily just one-off's that I delegate.

      In other words, say I delegate 10 projects to John Doe. I'd like to have some kind of inventory of all of the projects that I've delegated to him. I'm not really "waiting" for the projects to be completed (or, if I am, they'll be on my @waiting for list for months), however, I do care that they do get completed. Any suggestions?

      Comment


      • #4
        try an "agenda" list for john doe but in the memo's section.(not quite kosher, but...it allows one memo per outstanding delegate which becomes the agenda that guides meetings/conversations that occur, as they need to.

        Comment


        • #5
          How closely do you want to monitor John Doe's projects? Weekly or monthly status updates? Followup X weeks before his deadline to make sure everything is on track?

          Or, put another way, what is the Next Action you need to take with regard to each project? It seems to me the answer to that question affects the kind of recordkeeping you need to do.

          Katherine

          Comment


          • #6
            You should be reviewing your @Waiting For list at least every week, though, so if someone's work has been hanging out for a month or two, you'll know.

            Comment


            • #7
              Originally posted by Brent
              You should be reviewing your @Waiting For list at least every week, though, so if someone's work has been hanging out for a month or two, you'll know.
              Well, the thing is that a "typical" project will take months to complete. I don't oversee every NA related to that project, because it's delegated and not micro-managed. But, I'd like to have some kind of inventory that the project exists and who is driving it to completion. I probably don't need to see it weekly, however, I would probably need to see it monthly.

              I remember reading somewhere on here where somewhere suggested that you add a category such as "Projects - John Doe" or "Projects - Others" with a list of that (those) individual's projects. Is there anyone doing this currently?

              Comment


              • #8
                Again, what is *your* Next Action for the project? It will probably be something like "review Joe's status report" or "check with Joe re: ABC project status," but it might be something like "@Call QA mgr: why hasn't Joe gotten the data he needs?"

                My point being that each of your delegatee's projects is also a project for you, and can be handled in the same way as any other project.

                Katherine

                Comment


                • #9
                  Originally posted by kewms
                  Again, what is *your* Next Action for the project? It will probably be something like "review Joe's status report" or "check with Joe re: ABC project status," but it might be something like "@Call QA mgr: why hasn't Joe gotten the data he needs?"

                  My point being that each of your delegatee's projects is also a project for you, and can be handled in the same way as any other project.

                  Katherine
                  I see where you're going with this.... and what you're suggesting would definitely work.

                  Comment


                  • #10
                    Originally posted by jkgrossi
                    But, I'd like to have some kind of inventory that the project exists and who is driving it to completion.
                    And that's exactly what a Waiting For list is. Here's my Waiting For list at work, printed on one of the 4x6 cards that I carry with me:

                    Brennen for MFD part numbers
                    SoftwareCenter for CVS
                    Jimmy about Eric QA job (26 Aug)

                    It's an inventory of each project and who's driving it to completion. Review this every week, and you'll know what projects are outstanding and who's responsible for them, optionally with a date by which you want to touch base (as in the list above, where I want to talk to Jimmy on 26 Aug if he hasn't contacted me by then).

                    I probably don't need to see it weekly, however, I would probably need to see it monthly.
                    Then do it monthly.

                    Comment

                    Working...
                    X