Live data from Hacker News

Ask HN: How much info should founders share with early stage employees?

news.ycombinator.com

171–180 of 209 posts

Re: Ask HN: How much info should founders share with early stage employees?

#171
I can give you the opposite perspective: our CEO shares very little, and often far too late for us to be effective. It’s led to several resignations over the last year, increases stress, and encourages burnout as we all see a heavy emotional investment with little payoff. Frankly, it sucks being in a professional position with the potential (and job description) to direct operations, but to be in reality one of many assistants to a single bottleneck.

I realize that this may be a common arrangement, but I would suggest that it is not the best model for anyone involved, and would encourage you to avoid it.

Re: Ask HN: How much info should founders share with early stage employees?

#172

Earlier quoted context omitted.

There are very few startups that need to be in “stealth mode”. If anything, startups need to be more vocal to get themselves on the map and to do way way more customer development.

Are you sure, specially in easily copied technology domains? In my experience, software, business processes, and hardware are best kept close to the vest until sufficient momentum and maybe market saturation is reached. It does not matter if the item holds a copyright/patent/trade mark; they are post even re-active solutions. It's like an ambulance after a car crash. Excellent if there are good doctors in the ambulan…

If you are in the domain of easily-copied technology, you probably shouldn't be building a startup around it, because there are very few barriers to entry for someone else to do the same and eat your lunch or at least cream off some customers without ever having paid for the R&D behind whatever the anchor is.

Re: Ask HN: How much info should founders share with early stage employees?

#173
post #95

Earlier quoted context omitted.

Here's a non-conspiratorial reason: many engineers are not used to the uncertainty involved in day to day business negotiations and sales, and allow themselves to be stressed out what they see how the sausage is made. The reality is that lots of deals fall through, and that is normal . But if someone hasn't had a front row seat to that, they start wondering "are we failing?", "am I not doing a good enough job?", "is…

> many engineers are not used to the uncertainty involved in day to day business negotiations and sales 7 person startup, right? Presumably they hired people who can wear lots of hats and who can deal with uncertainty. > they start wondering "are we failing?", "am I not doing a good enough job?", "is our product a failure?" etc etc. Good. Questions lead to answers where there's transparency. I'd hope that the people…

This. Additionally this should lead to more responsible decision making when questions like “is my re-architect gone wrong going to sink the company?” are pondered at all levels. This could lead to more stress sure but if someone can’t handle it probably best to go work at big corp.

Re: Ask HN: How much info should founders share with early stage employees?

#174

Share it all. Complete transparency. Show them the cash flow. At your small size you will benefit from the additional trust and alignment this will bring. You may find yourself delighted in finding that many of your team can see and solve problems that you may have missed. You can be super secretive to combat the BigCo mentality like Apple when you have the first class problem of being a BigCo.

Slight caveat to "complete" transparency: https://youtu.be/-5SWvaKGULo?t=249

Re: Ask HN: How much info should founders share with early stage employees?

#175
You should definitely share information relevant to the employee’s decision to join and continue working at your company. It’s imperative to build trust with employees so that they know they can take your word.

The challenge for many is that it’s easy to be transparent during the good times, but much harder to be honest when things aren’t going well. You need to choose a level of transparency that you can stick with through good times and bad.

I will caution against taking HN advice unilaterally on these topics. HN comments are heavily skewed toward employees rather than founders and the advice you get will not necessarily consider the needs of founders and a company at all. Anecdotally, I have worked at a startup that tried to share everything with employees in a fully transparent manner and it backfired spectacularly. A couple of the employees used their information as leverage to work their way into high ranking roles at a competing company, taking some key customer relation knowledge with them. The roles didn’t actually work out for them at the new company. They were unqualified, the company just used them to extract their knowledge and let them go after a year. However, the damage was done. The information they took wasn’t at all necessary to be open to the employees and didn’t really benefit them behind a sense of full transparency for everyone. Don’t assume that your employees are always going to be in your court, especially as you scale past the intimate team size. It only takes one person acting in a selfish manner to try to leverage your transparency for their personal gain. Be at least somewhat careful about sharing information that doesn’t directly relate to employees making decisions about their own jobs at your company.

Re: Ask HN: How much info should founders share with early stage employees?

#176

Don’t worry about leaks. At this stage, nobody else cares about you. But what you should really worry about is risk appetite. Your employees will have different appetite for risk to you. That’s why you’re a founder and they are not. That’s neither good nor bad. It just is. Be conscious if this when you share things. Even if you can control the message, different people will respond to events differently. For example:…

> Don’t worry about leaks. At this stage, nobody else cares about you.

Actually, it’s better to pick a level of transparency that can be maintained well beyond this stage and stick with it. If a company starts out fully transparent and then walks back the transparency later, employees will become suspicious.

Much better to choose a sustainable level of transparency and demonstrate consistency over the years. Don’t play fast and loose early and then force yourself to overcorrect later.

Re: Ask HN: How much info should founders share with early stage employees?

#178
post #122

Share it all. Complete transparency. Show them the cash flow. At your small size you will benefit from the additional trust and alignment this will bring. You may find yourself delighted in finding that many of your team can see and solve problems that you may have missed. You can be super secretive to combat the BigCo mentality like Apple when you have the first class problem of being a BigCo.

While I agree on the benefits of sharing information and always being transparent, one should be mindful on how to communicate strategic and sensitive information internally, specially with regard to junior staff: - Avoid generating too much expectation, which can lead to frustration if things don't materialize, and impact team morale. - Always provide context so the team can better understand how/why events took pla…

Yeah, you really have to understand the audience.

I'd be very hesitant to share partnerships until they're done. Either because people will inappropriately mention them (a junior salesperson running his mouth on a phone call cost a former employer $5m++. no joke. a partnership deal that wasn't inked got rescinded after he told the wrong company and it got back), or more likely, get misset expectations about deals that can still fall through.

That's different than sharing rev numbers, about which I think founders should be very open. I'd share deals when they're inked, along with a lot of repetition about what can and can't be shared externally.

Re: Ask HN: How much info should founders share with early stage employees?

#179
post #130
post #75

Earlier quoted context omitted.

> On the other hand, I'd never want a "what should I do?" person as an early startup hire. This doesn't apply to tanks or healers, only dps. Playing tank as an infra person I would do my team a disservice if I didn't make myself available on a dime to unblock my team. Big picture is fine for the planning meetings but on small teams I'm usually the only one, I have a bunch of cooldowns to keep track of, and don't alwa…

Healers don't go around asking who needs healing, they see low health and prioritize. That is not asking "what should I do?", that is being proactive about the needs of the team.

Two points to that:

* Looking for people who caught aggro and getting out ahead of it is the bulk of my work. It's how I prioritize my workstream. The problem, and where the metaphor breaks down, is that I'm not omnipotent or have Grid2. If my devs don't tell me their pain points or I don't pull it out of them by asking what deliverables they would like to see out of me I would miss out lots of higher priority items than what I can see.

* The whole reason I'm on a team is because I have a specialized skillset and am but one stakeholder among many who want things from me. I will never run out of stuff to bring to planning but ultimately it's a group discussion about what I should do next. For larger companies s/me/the infra team.

Re: Ask HN: How much info should founders share with early stage employees?

#180
post #81

My experience kicks in quite a bit north of where you are, but for what it’s worth, I joined a company as employee ~150 that practiced near total transparency on everything. We went public, are now north of 8,000 employees, and it’s still nearly as transparent as when I joined - financials, product metrics, anonymized employee trends/HR data, major decisions… the list goes on but pretty much everything is done in the…

> We went public, are now north of 8,000 employees, and it’s still nearly as transparent as when I joined - financials, product metrics, anonymized employee trends/HR data, major decisions

I greatly prefer total transparency and have pushed for it when in situations that I have a say, but I'm curious how that can be achieved in a public company? Once it's public, a lot more regulations apply, many of which force reducing transparency.

Post reply on HN