|
> I'm not exactly sure what you mean by this, but it seems a bit simplistic. CEO's are also in the position to be thought leaders, public advocates, build hype, and internally, guide the company to specific results. At least the first three of those are different ways of setting culture. The last one is so loosely defined that it could mean anything. The sum of all actions of all actors within a company is its culture. If people act in an obsessive way about UX, then you have a culture of obsessive UX. The CEO has the power to shift these cultures. There are many tools, as you point out, but the biggest one is setting appropriate goals, with the proper aligning (dis)incentive structure. These are set on his subordinates, who then filter it down and specify it for their subordinates, and so on down the entire chain. > Also, I'm not sure that enforcing unit tests is exactly a "cultural" issue. How many unit tests you write is a decision that weighs current development speed against future development speed and reliability. That is of course influenced by culture, but not exactly culture itself. If you supposedly have a culture that values writing unit tests, then that should be reflected in action. The idea of tossing unit tests should be met with disdain, the same way we value not murdering people and murder is meet with disdain. It's not about tradeoffs, it's about stated cultural values (talk) versus the actual culture (walk). If there's nothing holding you to the stated cultural values, that's a management failure. |
And as far as my last factor ("internally, guide the company to specific results"), I mean that CEOs make a lot of day-to-day tactical decisions. E.g., how many engineer/sales/marketing people do we add to that team, do we need a bigger office, do we sue someone or not, do we take VC money on the offered terms or hold out for something better.
These tactical decisions are less visible, but probably make up a good deal of a CEOs day.