12-02-2009, 12:54 AM
Kinda sounds like you, not he, should be the project manager here. He spouts off ideas or requests and you get back to him with a yea or a nay based on his previous spout or request.
In other words, your responses wind up like this, "sure, we can do that but not if we also do x and y you already requested because they are incompatible."
If he can't keep track of what he requests, you can. If he doesn't know what he wants, this method will decide for him for better or worse.
A simple shared spreadsheet might be all you need. Although the wiki idea is good too; might be easier for you to document conversations there.
Maybe start with the ultimate goal and you -not he- work backwards and show him how you'll get there. If/when he gets down in the weeds, where he doesn't belong, you can "flatter him" by gently reminding him that he needn't bother with the minutia; that's what you're there for. Might keep him outta your hair on the tech stuff.
In other words, your responses wind up like this, "sure, we can do that but not if we also do x and y you already requested because they are incompatible."
If he can't keep track of what he requests, you can. If he doesn't know what he wants, this method will decide for him for better or worse.
A simple shared spreadsheet might be all you need. Although the wiki idea is good too; might be easier for you to document conversations there.
Maybe start with the ultimate goal and you -not he- work backwards and show him how you'll get there. If/when he gets down in the weeds, where he doesn't belong, you can "flatter him" by gently reminding him that he needn't bother with the minutia; that's what you're there for. Might keep him outta your hair on the tech stuff.