Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthoranGel
    • CommentTimeFeb 2nd 2006 edited
     permalink
    Hi.

    I have to make an audit for the intranet website of one of my client... And I am wondering about the content of the document I'll give him after the audit...
    Does anyone of you have ever done that before ? I think I'm supposed to do a small document (about 10 pages)...

    I plan to include in the doc :
    - Where are the strengths of your Intranet ?
    - Where are the weaknesses of your Intranet ?
    - Content update methods : How to make them better ?
    - Tools to update : How to use them more efficiently ?
    - Appendix : Graphics creation for an Intranet website. Content tips & tricks.

    On your opinion & experience, is it ok ?
    •  
      CommentAuthorJohnRiv
    • CommentTimeFeb 3rd 2006
     permalink
    Those look like good general categories. Be sure to touch on the usability and help documentation available. A well-designed intranet should have as small of a learning curve as possible for new users. It should also offer a support contact area where users can ask for help and also offer suggestions for new features.
    • CommentAuthoraconnor
    • CommentTimeFeb 7th 2006
     permalink
    Agreed, you've got a good start. Try to get a read on what the company's purpose for having an intranet is. For instance, is it mainly a communication vehicle to convey things to employees or a collection of tools to help employees do their work. Maybe it's a combination of both.

    If you know what the client is looking for out of thier intranet, you can better gauge the language in the report as to its strength and weaknesses.
    • CommentAuthoranGel
    • CommentTimeFeb 8th 2006
     permalink
    Ok, I've just finished my document...
    Thanks for the advices ;)

    > JohnRiv : About the help documentation, on every page of the application, there is a maito link for "Support". I think it might be enough because it's a not-that-big company (300 employees), so everybody knows at least one of the 3 webmasters... Feedback and support is not a problem since the launching of the intranet 6 months ago...

    > aconnor : The company have recently been bought by a big international group. So this company have been "forced" to create an Intranet to be included in the Group intranet... They still don't see it as a communication tool... I've oriented my report to point this (omho) very important use of an Intranet : collaborative work.

    Just for information (and because it might interest one or two skillshare users), here is my doc structure :

    1. Introduction
    2. Website ergonomics
    3. Updates on content
    4. Graphic coherence
    5. User visits
    6. Handling content & files
    7. Users interactivity
    8. General recommendations

    For each chapters, from 2 to 7, I mostly have two parts :
    - What do we have ?
    - How can we make it better and more efficient ?

    Then, in the last chapter, I recommend a few things to make the Intranet a real communication tool and hints to make visitors adopt it in this way.

    Thank you all :D
Add your comments
    Username Password
  • Format comments as (Help)