A team does not need more templates
Templates help structure thinking, but they rarely make employees want to publish. The useful layer is personalization: what would this person say, with their examples and their tone?
Shared assets without copied posts
Give contributors an accurate brief and a personalized draft, then let each person add a real example and their own point of view before publishing. The shared message provides direction; it should not become identical copy across employee profiles.
Start with one weekly ritual
A simple pilot can use one weekly brief, voluntary contributions, personalized drafts, and a lightweight participation review. Use the product signals available to the team, and record any activity that cannot be verified from the connected workflow separately.