Intranet Project Initiation Meeting<br />GSS Architecture <br />06.05.10<br />2:00pm<br />Presented by <br />David Fisher/...
Agenda<br />Introductions<br />Objectives of meeting<br />Demo of Interact<br />Design – Look and Feel<br />Information Ar...
Objectives of Meeting<br />
Let’s have a look at Interact ...<br />
Intranet Look & Feel<br />Design Remit:<br /><ul><li>Professional
Good use of Whitespace</li></ul>Design Remit:<br /><ul><li>Clean and Simple
Name to be part of Design
Fun and cartoony</li></ul>Design Remit:<br /><ul><li>Not to look like NHS
Include a character “dog”</li></ul>(Hull have since amended Search button to read “Fetch”)<br />
Styling your intranet doesn’t need to be difficult<br />
Naming your Intranet<br />Two questions to consider:<br />Do you want to name the intranet?<br />If so, do you want the de...
Information Architecture<br />
Communication<br />The Model for an Ideal Intranet<br />Most communication is time sensitive – such as events and launches...
The Project Team<br />??<br />Project Manager Day to Day Contact<br />David Fisher<br />Project Director<br />Celine Galla...
Implementation Process<br />Planning<br />Implementation<br />Client<br />Appoint Intranet Team & Champions<br />Create Pr...
What you have bought - Software<br />Core (70 Licenses)<br />Modules<br />
Upcoming SlideShare
Loading in …5
×

Interact 4 0 pim gss - v4

632 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
632
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Introduce self and state how long meeting should last
  • Run through agenda
  • Run through focus of what the meeting is about
  • Main navigationHomepagesFindabilityDocument Management and QualityStaff Directory
  • Look and feel - If naming intranet, need name before design mock-up – really important to stress this!Browsers, resolution, citrix
  • Objectives / How want to use Interact (ie content) - questionnaireInformation Architecture (ie structure)
  • Find out who the key people are in the project. Go through what each person in Odyssey does and the role they play
  • Create a Launch Plan – build up enthusiasm Competitions (e.g. name your Intranet)Internal Road-shows Workshops and videos for previews before launchTreasure Hunt around the IntranetRegular pre-launch reviews with “Champions”Discuss Ideas for day of LaunchQuick feedback from launch – use the Intranet to gather responsesRegular reviews post-launch with “Champions”Phased approach to adding content/killer apps Especially for Business Software modulesCan mean internal business process changes
  • Green = boughtGrey = not bought
  • Green = boughtGrey = not bought
  • Green = boughtGrey = not bought
  • Go through project dates – they should be confirming these dates in this meetingHave they bought server? Installation relies on getting Config Form and Software License Agreement back in timeCan they get name (if applicable) and corporate branding to us for design mock-up stage?Who are your weekly calls to be with? What day/time is best?Mention Lydia will be in contact once the intranet has been installed to introduce herself – support queries go to support deskHave they resources set aside for adding content?When going live?Handout – intranet planning checklist – things client needs to think about/confirm during project lifecycle
  • Go through project dates – they should be confirming these dates in this meetingHave they bought server? Installation relies on getting Config Form and Software License Agreement back in timeCan they get name (if applicable) and corporate branding to us for design mock-up stage?Who are your weekly calls to be with? What day/time is best?Mention Lydia will be in contact once the intranet has been installed to introduce herself – support queries go to support deskHave they resources set aside for adding content?When going live?Handout – intranet planning checklist – things client needs to think about/confirm during project lifecycle
  • Interact 4 0 pim gss - v4

    1. 1. Intranet Project Initiation Meeting<br />GSS Architecture <br />06.05.10<br />2:00pm<br />Presented by <br />David Fisher/ Scott Hitchins / Celine Gallagher<br />
    2. 2. Agenda<br />Introductions<br />Objectives of meeting<br />Demo of Interact<br />Design – Look and Feel<br />Information Architecture<br />Project Team<br />Steps from Planning to Launch<br />What you have bought<br />Project Milestones & Dates<br />AOB<br />
    3. 3. Objectives of Meeting<br />
    4. 4. Let’s have a look at Interact ...<br />
    5. 5. Intranet Look & Feel<br />Design Remit:<br /><ul><li>Professional
    6. 6. Good use of Whitespace</li></ul>Design Remit:<br /><ul><li>Clean and Simple
    7. 7. Name to be part of Design
    8. 8. Fun and cartoony</li></ul>Design Remit:<br /><ul><li>Not to look like NHS
    9. 9. Include a character “dog”</li></ul>(Hull have since amended Search button to read “Fetch”)<br />
    10. 10. Styling your intranet doesn’t need to be difficult<br />
    11. 11. Naming your Intranet<br />Two questions to consider:<br />Do you want to name the intranet?<br />If so, do you want the design of the intranet to be lead by the name of it?<br />
    12. 12. Information Architecture<br />
    13. 13. Communication<br />The Model for an Ideal Intranet<br />Most communication is time sensitive – such as events and launches. However some becomes important knowledge in the company. Interact then adds this to the Intelligence Store.<br />e.g. A document on what to do if you get Swine flu<br />Communications are pushed to the users –used in conjunction with pull forms of content such as knowledge, collaboration and business processes.<br />Knowledge <br />Management<br />Documents<br />Best Practice<br />Policies<br />Reports<br />Collaboration<br />Intranet Business Processes<br />The Interact Intelligence store pushes relevant content and helps users find content using innovative features like ‘Interact Recommends’, improving knowledge sharing and best practice.<br />Collaboration often forms an important part of any knowledge in a company. The collective intelligence of the company is then harnessed. <br />e.g. A user posts a comment on a new marketing document with good ideas for a product launch.<br />Collaboration is critical to the success of an Intranet as it is mass participation – using tools such as blogs, article comments, and forums.<br />Workflow and Forms module (Expenses Form)<br />
    14. 14. The Project Team<br />??<br />Project Manager Day to Day Contact<br />David Fisher<br />Project Director<br />Celine Gallagher<br />Project ManagerDay to Day Contact<br />??<br />Technical Contact<br />Jo Sullivan<br />Training Consultant<br />??<br />Design Sign-off<br />Sanjay Shah<br />Installation Engineer<br />??<br />Main contact for our Support Team<br />Mike Hague<br />Lead Designer<br />??<br />Intranet Champions<br />
    15. 15. Implementation Process<br />Planning<br />Implementation<br />Client<br />Appoint Intranet Team & Champions<br />Create Project Plan<br />Name your Intranet<br />Plan Sitemap<br />Odyssey<br />Appoint Project Team<br />Create Project Plan<br />Create Welcome Pack<br />Arrange Project Initiation Meeting<br />Build & Promote<br />Odyssey<br />Create Design Mock-up<br />Arrange Training (Intranet Manager)<br />Installation<br />Client<br />Identify/buy server & software<br />Prepare data<br />Review & Sign-off Design<br />Launch<br />Client<br />Pre-Launch Campaign<br />Email Screenshots<br />Marketing Material<br />Odyssey<br />Intranet Training Courses<br />Odyssey<br />Regular reviews with your Account Manager<br />Client<br />Bask in the glory of your Launch!<br />Continue with your Intranet Team Reviews<br />
    16. 16. What you have bought - Software<br />Core (70 Licenses)<br />Modules<br />
    17. 17. What you have bought – Training<br />
    18. 18. What you have bought - Consultancy<br />
    19. 19. What you have bought - Support<br />
    20. 20. Project Milestones<br />Project Initiation Meeting<br />Consultancy<br />Pre-Requisites:<br />Server Configuration FormSoftware License Agreement<br />Intranet Design<br />Interact Installation<br />Intranet/Module Training <br />Add Content<br />Go Live<br />Weekly Communications<br />Warranty/Support<br />
    21. 21. Project Milestones<br />Project Initiation Meeting<br />Intranet Manager Training Course<br />Pre-Requisites:<br />Server Configuration FormSoftware License Agreement<br />Intranet Design<br />Interact Installation<br />Content Manager Training <br />Add Content<br />Go Live<br />Weekly Communication<br />Warranty/Support<br />
    22. 22. AOB<br />Any questions?<br />

    ×