Anonymized examples of how transparent community work can be planned, reviewed and improved.
SaaS community research
A software team first mapped relevant communities, reviewed posting rules and documented recurring user questions. The final task asked for research and a useful answer outline rather than a promotional post.
- No fixed positive opinion
- No request for votes
- Commercial context documented
- Community rules checked before execution
Revision after disclosure review
A draft contribution contained useful information but did not clearly explain the contributor’s relationship to the brand. The reviewer requested revision before approval.
- Relationship disclosed near the claim
- Promotional wording reduced
- Evidence links added
- Final URL recorded
Rejected engagement campaign
A proposed campaign requested coordinated upvotes and repeated comments. It was rejected because disclosure cannot make vote manipulation acceptable.
Frequently asked questions
Are these real client names?
No. Examples are anonymized and focused on process.
Do the examples guarantee similar results?
No. Community decisions and outcomes vary.