Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

See here

View file
nameCDEV-Website Redesign Checklist-100125-213451.pdf

...

  1. System Demos/Documentation Review- not needed. User documentation is minimal.

  2. Data, Systems, Stack, & Integrations Audit: Tech Stack Diagram

    1. A holistic document that describes the connections, integrations, current tech stack

    2. Mike will create a diagram for geoinfo based on the system map started by Jake here: https://nmbgmr.atlassian.net/wiki/spaces/DataServic/whiteboard/1993375760

    3. This diagram describes the specific tech stack and specifications

  3. Current State Ecosystem Map

    1. Potentially a user groups map.

      Jira Legacy
      serverSystem Jira
      serverId80b48cb9-91b6-32ac-9347-1cacf7c78dd1
      keyNG-34

    2. The features and functionality that current system offers

  4. Additional Visual Models (ie: Anatomy of a Water Right)

    1. As identified by 2 and 3 if specific concepts or components need visual models

    2. The current publications work flow for both data and reports- what are the similarities and differences

    3. The work flow for e-commerce

    4. Current Bureau org chart? What are the different groups and programs within the NMBGMR?

  5. Content Audit & Assessment- This should be performed by the publications group

    1. Select the top ten most popular pages and do a content audit on those.

    2. What is the grade level language of the pages?

    3. What is the age of content?

    4. Is communication effective?

    5. Are topics or themes that are common?

  6. User Interviews

    1. Need to select group of stakeholders who would be good for initial user interviews.

    2. Survey for users that is available on geoinfo to get external users

    3. Identify external user feedback group to engage?

  7. Pain Points & Feature Requests

    1. Identify from user interviews/feedback

  8. Current Workflow Documentation

    1. See no. 4.

  9. Current State Sitemap & Taxonomy Audit

    1. Site Map: Website architecture. What are all the topics and pages covered by the site.

    2. Taxonomy Audit: Lets keep this high level or else it could be a big time sink. Focus on the program names or page titles. Want to identify where terms are inconsistent. We could also ask Pubs to help with this as a subset of the content audit.

  10. Brand Audit

    1. Lets have pubs do this.

    2. Current logo and visual style, core values and mission

  11. Competitive / Comparative Analysis

    1. Look at other groups and organizations with websites that we want to aspire to: Put list here: Website Examples For Comparative Analysis

    2. Confluence page with screenshots of home pages, things that are both good and bad

  12. SEO & Analytics Audit

    Set up google analytics for website

    Jira Legacy
    serverSystem Jira
    serverId80b48cb9-91b6-32ac-9347-1cacf7c78dd1
    keyNG-38

    1. Use Matomo for this

      1. where are users located?

      2. What percentage is at NMBGMR/NMT vs external?

      3. what are they using laptop or mobile?

      4. What are the most popular pages for internal/external users


Future Visioning (What Could we Do?)
Jira Legacy
serverSystem Jira
serverId80b48cb9-91b6-32ac-9347-1cacf7c78dd1
keyNG-39

  1. Stakeholder Interviews

  2. Stakeholder Alignment (Performance Continuums / Strategic Workshop

  3. Personas & Scenarios / Permissions Levels

    1. We understand internal personas but don’t have such a good handle on the public personas

  4. Future Workflows

    1. Improved publications workflow

    2. Improved ecommerce workflow

    3. Improved data sharing-Better linking between maps and data, better linking between projects and data, mechanism to download any data on website.

    4. Events workflow

    5. Improved contact/request workflow

  5. Service Blueprinting

    1. E.g. GIS server for maps, CKAN for open data etc.

  6. Data, Systems, Stack, & Integrations Roadmap

  7. Product Strategy

    1. What is our product? What are our goals? Who is it for?

  8. Requirements (Epic Level)

  9. Notional Product Roadmap

  10. Brand Strategy

    1. How do we communicate who we are?


Structure (What Should We Do?)

...