Sharing the current state of things is good. It will be stressful (for everyone) at times but at 7 people, they're invested personally and professionally. Shar

Sharing the current state of things is good. It will be stressful (for everyone) at times but at 7 people, they're invested personally and professionally. Sharing things that are in-progress is harder. I'd recommend attaching timelines and probabilities. Basically saying "this should happen in the next X days" and "we're trying this idea, it may not work but we'll know in roughly Y days." There are two huge upsides to a small, tight team: a) there are LOTS of decisions made every day in every area. If people know what else is going on, they should be able to make better decisions. aka "This doesn't make sense to do for one customer.. but if there are 4 others in the pipeline, it's way more compelling." b) people with varying strengths and areas of focus will not have your blindspots and perspectives and will see/understand things that you don't. Lean into that and you'll get a better solution. Background: I was employee ~25 at Twilio, launched Okta's API security product, and am currently employee ~20 at ngrok.