How do you know whether that innovative idea is actually one worth spending time on? Here are some tools and models I have been reading about to help evaluate startup ideas.
The definition of what makes a "good team" should include some degree of willingness to read, research and suggest ideas for how things could be better.
Team change is always disruptive but can help set a positive tone for the future company culture. Thinking it through is important. Getting this wrong will cause uncertainly, rumour and confusion to grow within the organisation.
What causes cloud outages and downtime? Misconfiguration? Software bugs? Human error? A look at Amazon, Azure and Google clouds to see what causes downtime.
Does working remotely work? What examples are there of remote, distributed companies? What should core remote company principles be and what are the challenges of remote work?
Writing about experiences and sharing stories is valuable, not just for the individual to get experience writing but for everyone to benefit.
As communication is the hardest problem facing any organisation, writing well should be one of the core values for every company.
Available time does not change - you can't add more hours to the day. So why do we ignore this when planning work and progressing tasks, especially in engineering?
Deploying Slack (I dislike real-time chat in almost every situation) and having an occasional all-hands does not mean your company is good at communication. So what does it mean?
How can product managers get things done when they have little to no direct authority over the teams actually implementing the project?