First, learn to say no. You can do it politely and still say it, and it's not rude or aggressive to just say no. Second, get a task list, put all of his/her s

First, learn to say no. You can do it politely and still say it, and it's not rude or aggressive to just say no. Second, get a task list, put all of his/her suggestions on them. Use something like trac or redmine or whatever. Even better, have him/her put them in themselves. Third, after you complete whacks of work, get together and prioritize the list, then pick a chunk of it to work on next. Keep your priorities to "Need It Now", "Could Be Cool", and "Not Worth It", or similar. The idea is eventually things should just fall off the list as not worth it. Last but not least, you can reduce the amount of "no" you say by keeping to this little list. It puts their wild optimism into perspective by showing how their proposed feature fits in with all the other features currently waiting to be done and then they'll start to understand how long things take. Now, the warning, do not keep track of how long each thing takes. This will give him/her control over how long things should take, and will be seen as a contract/promise rather than a guess. This is where you use "no". You are not a factory worker. Lists of things to do are fine. Fine grain hourly tracking is for time card punchers with no education working in a 3rd world country.