Expertise ergonomique

1
eMethodology
Federal Government
2
Table of Content
Introduction Chapter 1 - Project context Chapter
2 - The Workflow Chapter 3 - The Content
3
Introduction
Who are we? What do we do? Examples Todays
training
4
Who are we?

• Federale Overheidsdienst Kanselarij van de Eerste
  Minister Externe CommunicatieDienst Internet
• Service Public Fédéral Chancellerie du Premier
  Ministre Communication ExterneService Internet

5
FOD Kanselarij van de Eerste Minister Externe
Communicatie, Internet
MINISTER-RAAD
ONLINE(internet)
OFFLINE(campagnes)
Redactie Productie
Public Relations Int. Perscentrum (IPC)
6
Internet - taken 1/4

• Strategische kennis verwerven en behouden m.b.t.
  Internet-technologie, trends en tendensen en
  advies geven aan directie m.b.t. strategische
  keuzes en richtlijnen voor het garanderen van
  homogeniteit in de overheidscommunicatie

7
Internet - taken 2/4

• Onderhouden van FODKEM-informatie op het Internet

8
Internet - taken 3/4

• Coördineren van de departementsoverkoepelende
  initiatieven

9
Internet - taken 4/4

• Ondersteunen van andere FODs en PODs,
  kwaliteitscontrole en bewaking op het
  bevoegdheidsterrein van Externe Communicatie

10
Examples

• Ergonomics objectives evaluation (eye tracking,
  user testing, )
• Project support
• Design Harmonisation (Header, Footer)
• Webmaster tools (Search, Metrix, Hosting)
• Webmaster Training
• Webguide.fgov.be

11
e-Methodology

• As part of its task to support the different
  FODs and PODs with their online projects the
  External Communication department has developed a
  project methodology guideline called
  e-Methodology.

12
Chapter 1 Project context

• Why?
• Who?
• How?
• What?

13
Why?

• Similar issues with all projects
• Main issues Timing, Budget, Customer
  satisfaction,

14
Who?

• External Communication Department
• Webmasters, Communication Responsibles from
  different FODs and PODs
• External Consultants (NetWay, Lancre-Woods)
• gt Combining industry knowledge with specific
  experiences of government users

15
How?

• Interviews with different project collaborators
• Workshop with webmasters and com. managers
• Parallel group exercises
• Comparison of results
• Discussion
• Document with overview and guidelines pdf,
  online
• Training for different groups

16
What?

• Working from the point of view of the end user
• Checklist, Framework for online projects
• Pick and choose what is relevant to your project
• Working document will evolve based on your
  feedback

17
Chapter 2 the Workflow

• Prepare
• Analyse
• Build
• Deploy

18
Workflow presentation
1. Prepare
2. Analyse
3. Build
4. Deploy
19
1. Prepare

• This phase is basically about receiving the
  proper inputs needed for your project.
• It also defines your projects scope and its
  global objectives
• It reviews the current situation, outlining what
  why it should be improved.
• It will define your projects global timeframe,
  budgets, stakeholders, etc...

20
2. Analyse (1/2)

• The objective of this phase is to describe
  exactly what the new website will contain and how
  it will be presented. This description will serve
  as a convergence point for all the stakeholders,
  ensuring everybody has the same understanding of
  the projects future implementation.

21
2. Analyse (2/2)

• Because it is still mainly theoretical
  descriptive, and not yet implemented, changes in
  this phase are still possible and not too
  expensive.
• As such, it represents at least 75 of the
  success of your projects implementation, because
  it should detect and lift all major issues to a
  successful online experience, and because it is
  the basis on which the system will be built by
  the developers.
• All stakeholders will use it, as a confirmation
  that their ideas have been successfully
  materialised, or as a starting point for their
  work

22
3. Build

• This phase is about actually making what has been
  decided before. The fewer questions have been
  left aside, the quicker this phase will go,
  providing of course that all explanations are
  clear and complete.
• It mainly has to do with building the technical
  system and integrating the design and content
  with it. Thorough testing must be foreseen to
  ensure technical bugs, design and spelling
  mistakes are taken out before the public release.

23
4. Deploy

• The project is completed, and ready to go live.
  This phase will be about communicating around the
  project to make sure people know it, and also
  maintaining updating it to ensure the freshness
  of the informations.
• Finally, this is also the time to evaluate the
  project according to the criterias set before
  (KPIs), as well as final user testing and user
  feedback.

24
Chapter 3 the Content

• Prepare
• Analyse
• Build
• Deploy

25
3.1 Prepare

• Overview
• Strategy
• Vision
• Audit

26
Overview
27
1. Strategy

• The purpose of the business strategy review
  process is to identify which elements of existing
  business strategy plan could be achieved or
  assisted by the Internet.
• In addition, the review should identify
  objectives that can only be achieved using the
  Internet and therefore must be written into the
  current business strategy plan or Communications
  and Marketing plan.

28
2. Vision

• The vision describes the vision of your project -
  derived from the strategic review its global
  objectives, global timeframe budget (if already
  defined), ... In other words, it is the internet
  implementation of what has been identified in the
  strategic review.
• The objective of the Vision plan is to create a
  complete set of objectives which will define
  success for the website

29
3. KPI System specifcation

• The KPI system will report all the measurement
  and statistics gathered on the website. It is
  with this data that the KPIs defined in the
  vision phase will be filled out.
• It is important to define at this early stage
  precisely which data should be gathered, to
  ensure these will be available upon the projects
  launch.

30
4. Audit

• The situational audit is used to discover and
  define the size of the gap between the current
  website performance and the desired objectives of
  the new website.
• This analysis infers an estimate of the level of
  effort each activity is likely to require (time
  budget)
• User testings should be organised here to ensure
  an objective review of the situation is made.

31
3.2 Analyse

• Overview
• Content Structure
• User scenarios
• Technical possibilities
• Content Maintenance
• Ergolayouts
• Design research

32
Overview
33
1. Content Structure

• This phase is not only about the content and
  structuring it, but mostly about doing so in a
  user-friendly manner, as opposed to a
  company-centric one. Indeed, here the foundations
  of the project are laid, this is the theoretical
  layer and it is very important to include the
  end-users already at this stage.
• Thus, after all the stakeholders have given their
  opinion and an alpha structure is ready, user
  testing usability expertise should take place
  to check the projects logic against the users
  one.

34
2. User scenarios

• Detail the online journey of each type of
  visitor (according to the target audience defined
  earlier) through the use of ergolayouts. These
  scenarios will enable all stakeholders to see,
  rather than imagine, what the online experience
  will be for all visitors.

35
3. Technical possibilities

• Technically, everything is possible. Everything.
  But the cost, the infrastructure, the people
  and...the time may influence your decision.
• So it is important to present your new web site
  structure to the technical team and discuss the
  various options available for each functionality.
• Also, the IT teams experience may be very
  valuable to design the best possible features.

36
4. Content Maintenance

• Describing how the content of the future internet
  project will be managed will help taylor an
  online tool to the needs of the administrators.
  If the website is updated centrally, a simple
  tool will suffice, possibly accompanied by a
  training. The more complex the way the website
  will be updated (for example by external persons,
  by resellers, etc...), the more complex the
  update system will become.

37
5. Ergolayouts (1/2)

• Ergolayouts are a black white visual
  representation of the website. They mainly
  describe the general organisation of the page and
  the position of its different elements. This is
  important because too often, a beautiful
  website is mistaken for a good website.
  Ergolayouts enable to bypass most of the
  subjective aspects of designs. Because they do
  not include pictures or colors, they enable
  stakeholders to focus on the functional aspects
  of these elements, as well as their relative
  importance.
• They are the first chance all stakeholders get to
  visually see the future online site. As such,
  they enable them to interact much further than
  when taking only the structure into consideration.

38
5. Ergolayouts (2/2)

• The primary ergolayouts typically organise the
  sites common elements (such as the logo, the
  navigation, the corporate identity, the banners,
  etc...). This is often done via the homepage and
  one level below, possibly 2..

39
6. Design style research

• This step enables the designers to create
  propositions (often only the homepage and max. 1
  content page) with very few directives, solely
  based upon the site structure and a list of
  requirements (must contain a banner, etc...).
  They can research colors, image styles, even
  navigation style if this is allowed.
• This is mostly used for sites or companies where
  new styles must be evaluated, or with complex
  requirements. It enables the designers to fully
  express their creativity, not limited by
  functional or practical aspects, nor by
  ergolayouts.

40
3.3 Build

• Overview
• Design
• Content
• Technical dev. Statistics
• Integration

41
Overview
42
1. Design

• The design development concerns converting all
  the mockups into web compatible format, then
  integrate them into working html templates
• It must be done in close collaboration with the
  web developers, to ensure full compatibility
  easy integration

43
2. Content

• This phase is often overlooked, yet it is one of
  the main reasons why websites remain under
  construction or why projects do not respect
  deadlines.
• The amount of work is often overlooked, not only
  for writing the content, but gathering the images
  and finally putting it all in the content
  management tool.
• This phase can actually begin much earlier, but
  it must come to completion here because it must
  be integrated in the newly created site.

44
3. Technical dev. Statistics

• The technical development can be quite complex,
  but has been left here as one single step because
  it would otherwise require technical skills to
  understand it.
• Not only must the public web site be developed,
  but also the administration interface, which will
  contain for example the statistical tools, the
  content maintenance tools....etc

45
4. Integration

• The integration is a step during which the
  technical developments, the graphical interfaces
  the content informations are brought together
  to form the final website.

46
5. Debugging

• All projects need to be reviewed and tested in
  all functionalities and content prior to their
  public launch. Indeed, no development is totally
  exempt of errors (nor is a text exempt of
  mistyping at its first attempt), but this should
  not be found by the customer.

47
6. Training

• This training mainly has to do with the
  administration website, and the content
  management system. Depending on the complexity of
  these systems, trainings may be necessary for the
  people that will have to use them.

48
3.4 Deploy

• Overview
• Communicating
• Maintenance
• Evaluation (Stats Metrics)

49
Overview
50
1. Communicating

• Communicating your new project is vital for its
  success. This phase can be very complex in
  itself, because you may want to communicate
  directly towards your audience (for example for
  an intranet in a small group), but you may also
  want to reach your visitors via indirect means
  press conference, advertising, interviews,
  mailings, etc...
• It will of course be very important to do this
  upon project launch, but must also accompany the
  site maintenance scheme.

51
2. Maintenance

• Your projects completion isnt its public
  launch, it also comprises the periodic updates
  needed throughout the life of the site/ project.
  This maintenance phase is the actual
  implementation of what has been decided and
  described in the Content maintenance analysis
  phase.
• It is very important to ensure the visitors come
  back on your site (visitors stickiness). This
  is how you can build a traffic to become more
  and more important.

52
3. Evaluation (stats metrics)

• Now is the time to evaluate your project against
  the defined target
• User testings enable to objectively measure the
  results accomplished