A framework for allocating projects when multiple teams in a company could deliver what's needed.

As a company grows, different teams will build out their own content to make customers successful. Eventually, the inevitable question will get asked: Does this live in the docs or on the knowledge base?

I’ve found that most companies expect us to be spider-shaped. Slightly less wide than a lot of professions, and slightly deeper than most others

Disagreements that happen in the context of the leadership team don't exist to the wider team. Once a decision is made, we commit to that decision and put on a united front in front of our engineering teams and anyone else in the company.

In which I try to answer the age old question: "How do I know what to put on the blog and what lives in the docs?

How to present the same piece of information in multiple different ways to help meet your content goals

Content is a mainstay of many Developer Relations teams, but it can sometimes be tough to show the impact that you’re having. The best way I’ve found to justify your existence (and yes, unfortunately this is a thing in every business) is to attach yourself to the revenue generating teams. Read more to find out how