How many of you agree that asking a question with product version/release will improve the quality of discussion & lead time to answer in SCN?
I always had this on the back of my mind for a long time that we should always try to ask question with as much information as possible in a crispy way to get quick response/answers.
There is a saying that ‘Well defined problem is half solved’.
Sometimes we keep trying to solve an issue posted and person facing the problem keeps on trying different suggestions with no success. Later on when we ask for the product version/release we find out that suggestions given are for a different version/release. In this process, we loose a lot of our valuable time.
I have faced this problem many times and I guess I am not the only one..
So when we provide product version/release information with questions, our lead time to get answer reduces and also quality of discussion improves. The other biggest benefit is that, we open up an big search opportunity.. We will be able to search all the problems/question & answers related to product version/release for e.g. EHP4/6, PPM 5.0, Solution Manager 7.1 etc.
For example, let’s say that a person has a problem in Project systems ECC6.0 EHP6. He will be able to search all the problems related to PS-EHP6 in SCN and filter his own problem if available.
My question to space editors is that why can’t we enhance our searching capability in SCN similar to SAP Classification.
How many of you agree that asking a question with product version/release will improve the quality of discussion & lead time to answer in SCN?
5)Neither agree nor disagree or No Response.
Looking forward for all your views on this from all community members..
To post this, I was eagerly searching to create a ‘Poll’ but later came to know that only Space editors can create a Poll.. 🙂
Expecting a Poll creation for this from Jason Lax xMoshe Naveh (Old Acct) with their views.
As per Jason Lax suggestion, i have posted this idea in the SAP Idea forum, if you feel this idea is good, please vote in the below link.
With Warm Regards,
Communities (Not all I have mentioned here.. whichever I was following.. may be others can mention their own communities)
strongly agree with this post
Great Blog Ravi..!!
My views, at creation of a discussion there should be an option to categorize the discussion, such as:
> General Discussion
> Configuration Issue
> Bug/ Error
> Technical etc.
And on the basis of this there should be mandatory parameters to provide the system/ package/ version used before one can post the discussion. This will drastically reduce the solution lead time. 🙂
Thanks for your feedback Hardik.
I also have the same view on your feedback.
Let's us wait for some more views from other SCN community members.
I would suggest you to post this or atleast link of this blog in most of the spaces, so that we get maximum views.
Hope to see the change 🙂
Hassan.. Thanks for your suggestions.
Will try to post in the spaces.
Thanks for the valuable suggestions.
Nice blog Ravi,
I strongly agree with you
Thanks Vivek for your feedback.
I certainly agree that mentioning the release could be helpful in some cases, but I am afraid that even more contradictory and poor information would flood SCN then. Looking at the quality of some questions makes me think that those questioners will not be able to enter the correct release/product version to their question. The OP should anyway be more interested on a (timely) solution and hence give good information by himself.
Sometimes I have the impression that we "Helpers" are more interested than the OP.
(like the scout who guides a grandma across the street for his daily good deed - but she didn't want to cross the street)
For me it is more important to make the people search for existing content before posting the 6800. discussion on OBYC or the 19700. on number ranges.
What about doing the first step yourself? Just checked your questions and the history of some who liked this blog, but have not seen anyone giving this info (only saw many questions which have not been closed 😛 )
Thanks for your feedback and the detailed views on this.
I understand that some questions does not have adequate information and we "helpers" extract those information from OP. But this is not done intentionally, either in urge to get quick answers or the problem severity makes OP to post a question quickly without reviewing it.
My view in this, system should prompt for such details 😉 and I do agree to Jason Lax view,that Product version/release should not be mandatory but should available as optional. And these kind of product version/release details can be specific to the SCN spaces(Project System, PPM, CRM, SRM etc) where mostly 70-80% of posts are related to product technical / configuration issues, bugs/errors etc.
Coming to your above point, I do completely agree that we should search before posting a question to avoid duplication of discussions.
For this, I would suggest, whenever we create a post first only the subject, tags, product version/release should be keyed-in and this information should be used to find the similar posts and then if the OP does not find the right post, then create a new one(Similar to SAP Marketplace-Product error reporting).
I agree to Jürgen L, and eco same, if person posting issue first read SAP help , search forum for relevant issues, search SAP note , majority of the post not needed. 🙂 🙂
I found Tag field more relevant to tag what ever i understand as relevant to my thread.
Making any field mandatory or putting more validations just cant help greatly searchig relevant information or contribute towards cleaning forum.
Thanks for your feedback. 🙂
I agree with the point, that tags can be used to indicate the product version/release.
My point through this blog was that product version/release should be there somewhere in the post.. so that the people who are answering can give answers relevant to product version/release.
In this case, we need to bring more awareness among the users to use tags for indicating product version/release. By this I request again Jason Lax to create a poll to bring this awareness among all SCN community members.
Something's in the works but only after managed tags are released next week.
Hi Jason Lax
As discussed earlier, can we create a poll to encourage SCN members to use tags for mentioning 'Product version/release in the posts.
As suggested before, community member suggestions are always welcome and encouraged on SCN Innovation and Enhancements on Idea Place.
I'm with Jürgen on this one, but I guess it depends on the particular space. In the last year I can remember maybe 2-3 discussions where such information would be relevant. Otherwise in SD forum, for example, vast majority of questions would apply at least from 4.6. But, say, in Basis forum I can see how the release information would be quite important.
Overall it seems that "did not search" and "question not clear" posts are much more of an issue.
I think this is a great idea. Ideally you could just tick off e.g. Release 7.31 SP8 or so.. I also think Jürgen has a valid point but those kind of questions just should be rejected in my opinion with a "frequently ask question use the serarch function"..
Thanks Martin for your feedback.
Thanks for your feedback. I agree that including any relevant information such as the product name and version--among other things--is very helpful and should be included where possible in the title, opening text of the content and tags.
In fact, I want to highlight that SCN members can tag their content, which can include product version tags. These are user generated tags (put what you want) but it's best to follow what other members have used before. Just look to the popular tags widget often found on the lower right of space overview pages, such as SAP Business Warehouse:
And again on the lower part of the page when creating or editing content:
These tags are clickable and doing so searches for other content tagged with the same (It's a pretty cool functionality, actually, and will be further enhanced very soon).
Sometimes you may also find categories in a space, but these generally aren't product version based.
One important question is what happens when a product version isn't important, relevant or that all versions apply? I guess including this information can never be mandatory.
I'm not sure what you mean by expecting Moshe and I to create a poll so we'll take it as a suggestion 😉 . Such a poll would be a good way to encourage more positive authoring behavior on SCN.
Thanks for your feedback.
It will be an good option to tag the production version/release but there are chances that some users may tag a content with bw_7.3 / business warehouse and miss out the other similar tags.
Adding to your thoughts,
1)If we can bring tags next to the content title with a note mentioning to 'Add product version/release in tags' & benefits of tagging would encourage people to tag well.
2) And usage of these tags & content title for searching similar discussions and then allowing to create will also greatly help in avoiding duplication of discussions(Similar to SAP Marketplace product error reporting).
Coming to your point,
I do agree product version/release may not be applicable to all spaces & all categories and this should be optional only. If tags are used for this then it is already an optional entry and only thing is.. people needs an awareness on this aspect and as you said for this, poll can be very useful.
In this case, the most effective way to encourage this positive behavior is to lead by example.
It wouldn't be practical to surface the tags into the title because there is no limit on the number of tags, which could make for some very long and complex titles.
I also encourage your to read the section on managed tags on the blog post I shared yesterday: SCN Platform Update
Beyond that, community member suggestions are always welcome and encouraged on SCN Innovation and Enhancements on Idea Place.
Thanks for your kind reply.
Definitely i would try myself by leading.
My view was not to include the tags in title.. instead bring it below the title, so that it will provide the benefits.. as mentioned in the above of my comment.
Anyhow i will post this idea in the link suggested by you.
As per your suggestion, to encourage people & to bring more awareness of this tagging.. can we create a poll?
I strongly agree with you. Thanks for asking this question to us!
Thanks for your feedback Hari.. 🙂
Good Day! It my great pleasure to provide you feedback.
I liked it very much.
Keep sharing and rocking!
Have a wonderful day!
Just want to add that it would be more important to know if the questioner is an enduser, a student or a consultant with experience
As per my view, that information is not important while answering a question to the "helper". This information is already there in the user profile of the questioner and anyone can see it if the user has enabled the viewing rights.
The "helpers" may judge and prioritize the issue based on the questioners status. Eg. If the questioner is a student, I may prioritize the issue as "it can wait".
Anonymity is equally important.
Well, of course it is a good idea to provide version or release information. One that was mentioned before and is kind of an ongoing theme in the discussions all over SCN, where versions of the specific software is importend to answer the questions properly.
BUT the problem here is not with the missing opportunity for users to mention the version or release number, but they just simply don't provide it in their question. What is stopping users from writing this information now? And how would that behaviour change, if you include something like a field for this, especially if it is optional? I'd say: nothing. ^^
If the thread opener thinks he's getting help faster with writing down a short statement with as little information as possible, that he is downright wrong. If the OP doesn't have time to explain the problem properly, because it's so urgent and the solution is needed ASAP and fool-proofed, too, then those people won't think about filling out the field for release number or adding tags. Some at them don't even bother to find the right space to create their query.
I don't think that more possibilities to add information are needed. There are enough given already, it's just that they aren't used by those users you want to reach with this. 😉
But that's just my two cents... ^^
Thanks for your detailed feedback.
I would agree in some way that some users are not interested about this.. but if these kind of information's are prompted, then definitely they would fill it.
Agree with this post.
Thanks for your feedback Niki..
I agree with your point of view.
It will be much easier to resolve the issue soon.
Thanks for your feedback Shoaib. 🙂
Agree with this blog
Saves time and the person who posted the query can get the exact solution what he is expecting by providing all the relevant information.
Thanks for your feedback Prashanth. 🙂
Definitely it will be saving lot of time for all.
It is also useful to expand knowledge. You can get knowledge about various issues and also get solution for resolve the issue.
Thanks for your feedback Arpit 🙂
I cast my vote once again due to account issues.
Good Blog Ravi..!!
Its rightly said: question better explained is half solved. and in today world when things changing fast and new innovations improvising the software, it may be that the feature u asked for is present in the upgraded version. At least speaking about the version eliminates one iteration and allows us to think with respective to the user.
I hope you agree.
It is a frequent post requesting that information. In some instances for more general communities, it is necessary to ask the poster what product or application they are talking about. Quite frustrating to see the wasted time. Then many of the experts just ignore the Discussion (since you have no real clue what the poster is having problems with) which ends up frustrating the OP. I have a little sympathy with the OP, but not much even though I often suggest to them how to provide more information.
are the two links I often post, sometimes individually, sometimes together to address grossly inadequate Discussions.
Sometimes it helps, but sometimes nothing changes as a result.
Cheers, Mike (Moderator, Space Editor, and curmudgeon)
SAP Technology RIG