You should never... and I mean never... TELL your boss (much less a founder or CEO) what they can and can't do.
That's a great way to torpedo your career.
"You can't invest $10 million in ergonomic chairs." should be "While ergonomic chairs are a good investment, we might be better served investing $10 million in our core competencies for now, and perhaps focus later on the chairs when our revenue stream is a bit more stable."
"You can't add cool-sounding feature because it's an inherent security risk." should be, "While cool-sounding feature does, indeed, sound cool, I'm concerned about the potential liability this might expose the company to, given that implementing cool-sounding feature causes <security issue> by its very nature. I could look at implementing something that mimics the functionality of cool-sounding feature, but keeps our products secure."
And lastly, Humble Jr. QA Engineer should say, "Mr./Mrs./Miss So-And-So, if I claim that bug <Z> is fixed when its not, this might come back to reflect negatively on our company when Customer Y reports that bug."
And lastly, almost every company's founder / CEO / leader has dictatorial powers. Companies aren't governments. You live and die by the good graces of those above you, and if you can get noticed by the people at the very top, and you consistently deliver for them, you'll have a far more pleasant work life.
Or just telling people what they can and can't do and see how that one works out for you...
That's a great way to torpedo your career.
"You can't invest $10 million in ergonomic chairs." should be "While ergonomic chairs are a good investment, we might be better served investing $10 million in our core competencies for now, and perhaps focus later on the chairs when our revenue stream is a bit more stable."
"You can't add cool-sounding feature because it's an inherent security risk." should be, "While cool-sounding feature does, indeed, sound cool, I'm concerned about the potential liability this might expose the company to, given that implementing cool-sounding feature causes <security issue> by its very nature. I could look at implementing something that mimics the functionality of cool-sounding feature, but keeps our products secure."
And lastly, Humble Jr. QA Engineer should say, "Mr./Mrs./Miss So-And-So, if I claim that bug <Z> is fixed when its not, this might come back to reflect negatively on our company when Customer Y reports that bug."
And lastly, almost every company's founder / CEO / leader has dictatorial powers. Companies aren't governments. You live and die by the good graces of those above you, and if you can get noticed by the people at the very top, and you consistently deliver for them, you'll have a far more pleasant work life.
Or just telling people what they can and can't do and see how that one works out for you...