Skip to content

Commit 6c7f02b

Browse files
committed
Shorten slightly
1 parent 0f8b860 commit 6c7f02b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/blog/newsletter-september-2025.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Perhaps you, as a documentarian, assume good intentions when people engage with
2323

2424
If someone has contributed some "good" and "bad" ideas, consider acknowledging the "good" ones and, if necessary, indicating why some were "bad". (To soften your initial reaction, don't respond immediately and consider reevaluating what you consider "bad". See `Who’s running this content? </blog/newsletter-july-2017/#who-s-running-this-content>`__.) Consider communicating the focus of the documentation and documentarians' role in the company. You may get some ideas from `Help contributors think like users </blog/newsletter-june-2025/#help-contributors-think-like-users>`__.
2525

26-
If a person pushes back or is a frequent requestor of "bad" content, you and your team may need to set boundaries. (See `Setting boundaries </blog/newsletter-april-2023/#setting-boundaries>`__, which focuses on reviewers but may be relevant to unwelcome contributors.) To avoid personal confrontations, you may have to develop a workflow that addresses problems like this. For example, you could designate a single point of contact, specific dates to respond, specific types of legitimate requests, or procedures for documentation suggestions. (`Help your contributors help your project </blog/newsletter-december-2017/#help-your-contributors-help-your-project>`__ might be useful for procedures for problematic contributors.)
26+
If a person pushes back or frequently requests "bad" content, you and your team may need to set boundaries. (See `Setting boundaries </blog/newsletter-april-2023/#setting-boundaries>`__, which focuses on reviewers but may be relevant to unwelcome contributors.) To avoid personal confrontations, you may have to develop a workflow that addresses problems like this. For example, you could designate a single point of contact, specific dates to respond, specific types of legitimate requests, or procedures for documentation suggestions. (`Help your contributors help your project </blog/newsletter-december-2017/#help-your-contributors-help-your-project>`__ might be useful for procedures for problematic contributors.)
2727

2828
Some people disregard documentarians’ expertise and consider writing to be something that "anyone can do". These people regard their suggestions as better than what you or your team can produce, undermining your team's authority and credibility. Frequent pushback can cause stress and frustration, disrupting your team’s well-being and productivity. You may need to bring in management to support your team’s decisions rather than confronting these people directly.
2929

0 commit comments

Comments
 (0)