I'm stoked that I was able to help you. That makes writing this article completely worthwhile. 1. Dave (designer) works in our NYC across office right across f

I'm stoked that I was able to help you. That makes writing this article completely worthwhile. 1. Dave (designer) works in our NYC across office right across from me (http://www.carbonmade.com/blog/2009/09/24/150000-portfolios-and-new-office http://www.carbonmade.com/blog/2009/09/24/150000-portfolios-...). Jason (programmer) works back in Chicago and is moving to NYC in May or sooner. What I find works best is to plan for the future, but not to necessarily bring it up with the other folks until it's time. I actually find myself saying "let's focus on the present" a lot more than I find myself sharing my thoughts for the future. Sharing those thoughts are best left for when you've completed a new version or a major segment of your product. Keep everyone focused on the task at hand and bring out your plans for the future only at the appropriate times. 2. Someone mentioned in a response to one of my posts (and I'm paraphrasing) that "a response to a support ticket takes the same time today as it does tomorrow, so you might as well answer it today." I think that's very true. You shouldn't let it derail you if you're deep in concentration, but if you see it and you can take a minute to respond, why not respond then and there? By responding it won't weigh on you for the rest of the day and affect your other work. 3. What troubles have you been having? I think the decision of having a user guide or not should be based on whether your product needs one or not. Luckily, ours is simple enough that a few FAQs do all the work for us. Let me know if you have any other questions here or via email [at] spencerfry [dot] com. I'm also open to having lunch/coffee/beer with you if you're in NYC at any time.