Click here to share your feedback
Social Business User Experience blog
Cara Viktorov 270000HS28 firstname.lastname@example.org Tags:  feedback help documentation usability 1,309 Visits
Do you look for quick reference topics in Help that describe how to do common tasks? Have you found them useful or not? Let us know what you think. Take a minute to complete our short survey by Friday, February 15, 2013.
Click here to share your feedback
Working in documentation can be a frustrating experience sometimes, for reasons you wouldn't really expect. I used to think that it would be hard to accept criticisms about our work. I envisioned customers coming in and pointing out all the flaws in work, and us having to scramble to address them.
It turns out that the reality is just a little bit different. You see, I sit here most days wanting solid feedback that I can act on. Where do the docs need work? What parts are confusing, and why? How are people looking for the info they need? If you answer those questions, I can do a better job of providing information that will actually help you.
But more often than not, what I really get from users is sweeping statements like, "The docs are horrible" or "You need to make section X better." Honestly, most times I'd love to make section X better, but I'm frequently left wondering what's actually wrong with section X in the first place. How did it fail you? Where are the problems? In your mind, what could be better?
So there's the dilemma. We want feedback, we welcome feedback, and we even go out of our way to seek feedback. But oftentimes that feedback doesn't really help us, because to take any kind of meaningful action we need the feedback to be specific. The best feedback points out specific issues, tells us where you got confused, or points us to something you think is better so that we can compare.
Not sure how to give us this kind of feedback? Take a look at the end of this post for some helpful hints, but my suggestion is to start with the product wikis. You can comment on specific articles to tell us what works and what doesn't, and you can even edit them yourself if you're so inclined. We'll roll those edits right into the product doc if they make sense to us.
So let me wrap this up with a simple plea: Help us help you. Please, make your feedback specific.
(Apologies to Jerry Maguire.)
Three ways to give us feedback:
Amy Travis 1100006T7G email@example.com Tags:  communities ux engage features feedback 1,021 Visits
In the latest SmartCloud Engage release, you can now create three types of communities:
Currently, if you want someone from outside of your organization to join your community, it must be a restricted community. In other words, if your organization is "Company A", and you want to have a community that also includes people from "Company B", you can only do this if your community is Restricted.
I'd love to get some feedback on this from our SmartCloud Engage users! What types of communities do you create most often, and why? And would you want to invite people from other organizations into Moderated or Open communities?
Looking forward to hearing from you.
- Amy Travis (SmartCloud Design Lead)
Wiki users, we want to know how you rate your overall wiki user experience on the current wiki design. Visit any of the IBM WebSphere or Lotus product wikis and click the How was your visit? survey link located in the top right yellow section on any wiki Home page, or access the survey directly here. It only takes a couple of minutes to complete the survey. We look forward to hearing from you!
Do you use the activity stream in IBM Connections to stay up to date with the people and content you follow? If so, how valuable is the activity stream to you and your productivity? Tell us about your experience with activity streams in your work environment by taking a five minute survey.
Link to survey: https://www.ibm.com/survey/oid/wsb.dll/s/ag4e7
The survey will be open until March 13, 2013.
Thanks for your feedback!