Service Now forums

[mattberan]

Here's why the forums aren't making any sense to me and why people aren't collaborating as much as they should here.

1) The forums headings are illogical, think about the structure of your application or environment and restructure in line with that (this is also a good knowledge practice too, so think about having INC categories pre-populate your KB cats).

You can keep your current structure too, but just add substructure Something more like this:
Forums - Implementing an application - Change
Forums - Implementing an application - Catalog
Forums - Local groups - Minnesota

where change and catalog are both sub forums. This way, when I'm looking into building a Service Catalog, I can simply browse to the forums, click on the feature/plugin/app/ITIL best practice sub forum and begin reading. Also, we're talking tech-savvy people here, so RSS is king.

2) There is no "one blog to rule them all"... or maybe there is and I can't find it. I get that I can read the aggregate of all our blogs by click "blogs" in the nav menu, but where is the "Service Now" blog. I really think adding that and allowing public comment would be your best way to drum up some community.

3) There is no documentation for browsing your site, granted, I don't there is a "need" for this per se, but at our local user meeting yesterday there was some confusion about who can post where. This isn't a standard wordpress install, so some guidance is necessary (looks like a great first post for your Service Now blog!)

4) OLE. Or at least some editing options (think wordpress again) It would be nice to bold, or italicize without the HTML markup, plus, I had to create this unordered list manually (shudder)

4) That being said, I'm going to build a quick guide and post it in my next post with my local user group as the audience so we can start taking advantage of one of the best communities for an incident management tools I've seen!

note: also, the "read more" link is not in a logical position... should follow the teaser text IMHO.