Should your team post too?
You have a system producing content in your voice. Someone asks the obvious next question. Should the rest of the firm be posting too?
The answer is yes for some of them. The test is narrower than the advice you have been given.
A colleague earns a place in the firm's public voice on two conditions. They hold a point of view, and they carry experiences that enrich what you publish. Without those two things, their posting adds nothing your system does not already produce, and it costs you something.
The reach argument is true, and it is not your problem
Start with why every firm gets told to do this. People follow people.
Metricool's 2026 study of 673,658 LinkedIn posts found personal profiles running about 63% ahead of company pages on engagement. A named human outperforms the firm's account, and that gap is why advocacy software exists.
Read the case for team posting closely and it is almost always a reach argument. More profiles, more networks, more impressions.
Reach is a fine goal for a company selling software to thousands of buyers. You are not doing that. You need perhaps a dozen of the right people to believe something specific. They have to believe you are the best in the country at your one thing.
Volume does not produce that belief. A specific person saying a specific thing does.
The bar is a point of view and experiences that enrich
Here is the test I use. Could this person write something the firm's system could not write for them?
Your senior associate who has run 40 of these cases has seen patterns nobody outside the work has seen. She has watched the same mistake three times in a year. She can name it. Nobody else can.
That is a point of view, and it belongs in public.
Now the other case. A capable colleague reads your blog, summarizes it in six lines, and posts it under their own name. Nothing was added. The idea already existed, better argued, on your site.
That second post carries a cost. It fills the firm's feed with an echo. It also teaches readers that your firm's name on a post predicts nothing about the post.
What a feed full of echoes costs
Your buyer is looking you up before they call. They land on three profiles from your firm.
If those three read interchangeably, the reader learns one thing. This firm has a content policy.
Now say one of them names a mistake she watched a client make, and what it cost. The reader learns something else. There is a person in there who knows the work.
The platforms have started grading the same way. LinkedIn said in May 2026 that it would restrict distribution for content that looks generated and carries no perspective. Recycled thought leadership and automated comments were named alongside it. The tells reported include the em dash and the "it's not X, it's Y" construction.
Take the platform's rule as one more reason rather than the reason. A reader was already making that judgment, and a reader's judgment does not get appealed.
The failure that has nothing to do with content
Programs fail for a duller reason than quality, and any owner considering this should know it before starting.
Somebody has to run the thing. That person sends the reminders, keeps the queue full, and nudges the colleague who went quiet in week three.
When that person gets busy, the reminders stop. The queue goes stale. Participation fades without anyone deciding to end it. Nearly every guide on this subject describes the same collapse. Most of those guides are published by companies selling advocacy software.
There is a second cost, quieter than the first. Posting becomes an obligation. Obligation produces the flat, safe, interchangeable writing that made the feed worse in the first place.
Two colleagues who want to publish will outlast a program that ten people were assigned.
Where a colleague's voice is worth more than yours
Three cases are worth saying yes to.
The first is the specialist whose buyers are not your buyers. A partner running a practice area with its own audience reaches people who would never follow you.
The second is recruiting. Someone two years into the work describes it in a way no principal can. People considering a move read that instead of your careers page.
The third is the colleague who is already writing. Someone in your firm may already post well, on their own initiative. That answers the question before you ask it. Your job is to give them better material.
One caution for regulated fields. In law, medicine, and financial advice, a post can create exposure. Run the same review you would run on any published statement.
How to do it without building a program
Interview them. Sit down for an hour with your colleague, ask the questions somebody asked you, and record it.
That hour produces the raw material: the cases, the patterns, the arguments they have with the textbooks. The system drafts from their transcript, in their voice, and they approve what goes out.
It is the same capture that runs your own publishing, aimed at one more person. That is why owner posting and system posting do not compete when both grow from the same material.
Keep the count small. Two or three people with something to say, interviewed properly, beat a firm-wide rollout. They will still be publishing a year after the rollout has stopped.
Your firm's feed is a claim about who inside the firm is worth hearing from. That claim is stronger when it is short.
