>How much should I tell my team about what's going on above me? I think everything you reasonable can. It will allow your developers to decide how to spend th

>How much should I tell my team about what's going on above me? I think everything you reasonable can. It will allow your developers to decide how to spend their time most effectively. Ex. You tell a developer to build out a certain demo screen. Even given the same specs there is a huge difference between "this screen will be shown to the other companies CEO and could be the cornerstone of a multi-million dollar deal" and "yeah we promised to deliver this screen in the deml, but now we dont think it's important. We're pretty much only building it because we promised.". Not to mention there is going to be lots of new information that your subordinate will learn over the course of solving a problem. And if he knows everything you know he'll know what information is new and which you already knew. But if he doesn't know what you know or assume it can lead to all types of messes. "I thought you knew this was going to be a 3 week change, and would break backwards compatibility"