Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

71%
+3 −0
Q&A How can we integrate a lightweight public ticketing system into our documentation feedback form?

How to present the question This section doesn't directly answer your questions, but address problems with such web pages that are all too common. I'm one of those that pretty much never answers ...

posted 2y ago by Olin Lathrop‭

Answer
#1: Initial revision by user avatar Olin Lathrop‭ · 2021-07-08T13:35:32Z (over 2 years ago)
<h2>How to present the question</h2>

This section doesn't directly answer your questions, but address problems with such web pages that are all too common.

I'm one of those that pretty much never answers <i>"Was this helpful?"</i>.  Most of the reason a web page was not helpful is because a search engine directed me there, but it wasn't a match.  It doesn't feel like it makes any sense to respond.

Another common reason is that I'm trying to understand <i>what</i> something is, but the site only gives me content-free marketing babble about how wonderful it is.  Providing feedback to an image-over-value company seems pointless, and by treating me like a mark at a circus instead of a potential collaborator makes me feel like they don't deserve my volunteer help.  What's in it for me?

(For a real life example of the above, go to the Adobe web site and try to actually understand what the various products do if you don't already know.)

<b>Before you ask for a favor, you need to treat people with respect.</b>

Consider asking differently.  I think <i>"How can we improve this page?"</i> sounds better than <i>"Was this helpful?"</i>.  I can't explain why, but the first sounds better somehow.

Also, reduce the barrier to entry.  <i>"Was this helpful (Y,N)?"</i> is bad because I have to click on "No" first to get anywhere.  I'm thinking <i>"What happens then?  Too much hassle.  Screw this.</i>".

If on the other hand there was <i>"How can we improve this page?"</i> followed by a box I can directly type in, then I might just vent on what I didn't like.  It's right there.  I can see what's going to happen.  All I need to do is start typing.

<h2>What to do with the responses</h2>

Have a public web forum.  This can be useful for supporting your products in general.  One section can be about web site issues.  Somewhere in there is where the <i>"How can we improve this page?"</i> responses go.

The rest of the mechanics I'm not sure about.  There are several ways to structure this.  Probably only experience will tell you what works best.

For example, should there be a thread (or some collection) for each page that has a response form?  It could be useful to see all the responses for a particular page in one place.  That allows a link to that web forum section directly below the response box.  This may make it more difficult to respond to individual suggestions, though.

Users that want to follow up would need to get onto the forum where they can  participate as usual for a forum, including providing more detail on their own and other people's responses.  Users can then opt-in to get notified about new posts in various sections or threads or whatever.