'User' Experience

 

Introduction

Given our recent focus in specific verticals I believe it necessary to separate and classify them in to unique audiences with the goal of catering the OOBX to each audience.

Purpose

OOBX needs improving in order increase user retainment through an much improved initial exposure to our software.  Our initial efforts in this area will focus on educating users.

Intended Audience

  1. Develop
  2. Document
  3. Learn More

Additional information

Other areas of interest for OOBX outside the scope of this Functional Spec:

  1. Discovery
  2. Purchase
  3. Download/Acquisition Process
  4. Setup/Installation

References

Any bugs, forums, other pages

Status

 

Currently in the initial stages of research and brainstorming. 

  1. Monday August 10th - Met With Roy
    1. Discussed initial objectives of OOBX
    2. Identified who to talk to
    3. Set deadline - Mineopa Release
       
  2. Thursday August 13th - Met with Mark
    1. Documented Mark's thoughts regarding OOBX
    2. Presented My original functional spec to Mark
    3. Brainstormed together
       
  3. Friday August 14th - Met with Jessica
    1. Documented her previous research and development
       
  4. Monday August 17th - Met with Mark
    1. Documented Goals, Tools, Characteristics for each Admin Group (intranet, extranet, knowledge base)
       
  5. Friday September 18th, Met with Mark
    1. Discussed OOBE ver 2 with Mark

 

 

Use Cases

  1. Developer User

    1. User Goals -
    2. Tools/Features to achieve goals
    3. Things to consider -
    4. Soft sell to accompany goals -
  2. Documentation User

    1. User Goals -
    2. Tools/Features to achieve goals -
    3. Things to consider -
  3. Learn More User

    1. User Goals -
    2. Tools/Features to achieve goals -
    3. Things to consider -
    4. Soft Sell-

Functional Specification

 

This particular portion of OOBX is intended to focus specifically on the experience a user has once the software is installed and first being used.  Therefore our feature will be served as the default homepage content for new users and admin to use as a navigational and instructional resource to encourage adoption.  Sections on the homepage may include:

  1. Navigation Education: Identifying important parts of MindTouch that may have discoverability issues
    1. Templates:
    2. Recent Changes:
    3. Users:
    4. Control Panel
    5. Sales Resources - Clearly State that it is Sales they're contacting
  2. Developer Education: Identifying important tools and functions to entice user development
    1. DekiScript
    2. Community Support Links
      1. Forum
      2. Wiki
    3. API Teasers
      1. Quick Links to some API url's
      2. Link to the API documentation at dev.mt.com
    4. Extensions: Introduce and link to dev.mt.com resource
    5. Syntax Highlighter
    6. DekiScript / Paramatarized Templates
      1. 5 Demo DekiScript Templates
        1. Hello World
        2. User Properties and Permissions
        3. Native DekiScript functions
        4. Intro To Paramatarized Templates
        5. RSS and External data manipulation
      2. Button To Create A new Template
  3. Documentation Education (knowledge base):  Identifying tools and approaches to clean documentation
    1. Templates:  Explanation of how to use templates for content layout
    2. Include 5 default content layouts - with simple icons and teaser Headers and content
      1. 1 Column With A Picture Floated Right
      2. 2 Column with A Picture in first column
      3. 3 Column
      4. Right Hand SideBar with gray background
      5. Left Hand SideBar with gray background
    3. Control Panel Overview with quicklinks to Control Panel tools

 

 

Non-goals

  1. The OOBX homepage will not INITIALLY have functional tools on it, strictly education and navigation

 

Administrator Experience

 

Introduction

Given our recent focus in specific verticals I believe it necessary to separate and classify them in to unique audiences with the goal of catering the OOBX to each audience.

Purpose

OOBX needs improving in order increase user retainment through an much improved initial exposure to our software.  Our initial efforts in this area will focus on educating users.

Intended Audience

  1. Intranet
  2. Extranet
  3. Knowledge Base
  4. Other

Additional information

Other areas of interest for OOBX outside the scope of this Functional Spec:

  1. Discovery
  2. Purchase
  3. Download/Acquisition Process
  4. Setup/Installation

References

Any bugs, forums, other pages

Status

 

Currently in the initial stages of research and brainstorming. 

  1. Monday August 10th - Met With Roy
    1. Discussed initial objectives of OOBX
    2. Identified who to talk to
    3. Set deadline - Mineopa Release
       
  2. Thursday August 13th - Met with Mark
    1. Documented Mark's thoughts regarding OOBX
    2. Presented My original functional spec to Mark
    3. Brainstormed together
       
  3. Friday August 14th - Met with Jessica
    1. Documented her previous research and development
       
  4. Monday August 17th - Met with Mark
    1. Documented Goals, Tools, Characteristics for each Admin Group (intranet, extranet, knowledge base)

 

Use Cases

  1. Intranet Admin

    1. User Goals -
      1. Set up my site
      2. Show me what a good intranet looks like
      3. Set up my teams/devisions/spaces/groups
        1. with Tabs on top
      4. Invite people to my Intranet
      5. Start my blog
      6. Start my forum
    2. Tools/Features to achieve goals -
      1. Projects Templates - created by Bob
      2. Executive Dashboards
    3. Things to consider -
      1. Permissions
        1. Groups/Roles
      2. Privacy
      3. Authentication
    4. Soft sell to accompany goals -
      1. Promote plugins
  2. Extranet Admin

    1. User Goals -
      1. Customer Extranat
      2. Partner Extranet (ecosystem)
        1. Keep partners informed
        2. Share data
        3. Share files!
        4. Start a help forum
        5. Create FAQ's
        6. Share co-branded documentation
          1. Allow my partners to brand our documentation
        7. CRM info
          1. Show my partners their leads/sales/opportunities
        8. News Announcements
        9. Show latest articles from the blog.
    2. Tools/Features to achieve goals -
      1. User Profile
    3. Things to consider -
      1. Is this a Customer Extranet or Partner Extranet
      2. SAAS
      3. Permissions - Private vs. Public
  3. Knowledge Base Admin

    1. User Goals -
      1. Find a knowledge expert
      2. Find the right content
      3. Use a template to create Question/Answers
    2. Tools/Features to achieve goals -
      1. FAQ
    3. Things to consider -
      1. Storing Data
      2. HEAVY document management
      3. Expert Search
      4. MT ANSWERS - like yahoo answers
        1. Rating system
      5. User rating
    4. Soft Sell-
      1. Prof Services
  4. Other Admin
    1. User Goals -
    2. Lessons to achieve goals -
    3. Tools/Features to achieve goals -
    4. Videos to achieve goals -
    5. Templates to achieve goals -
    6. Soft sell to accompany goals -

Functional Specification

 

This particular portion of OOBX is intended to focus specifically on the experience a user has once the software is installed and first being used.  Therefore our feature will be served as the default homepage content for new users and admin to use as a navigational and instructional resource to encourage adoption.  Sections on the homepage may include:

  1. Navigation Education: Identifying important parts of MindTouch that may have discoverability issues
    1. Templates:
    2. Recent Changes:
    3. Users:
    4. Control Panel
    5. Sales Resources - Clearly State that it is Sales they're contacting
  2. Developer Education: Identifying important tools and functions to entice user development
    1. DekiScript
    2. Community Support Links
      1. Forum
      2. Wiki
    3. API Teasers
      1. Quick Links to some API url's
      2. Link to the API documentation at dev.mt.com
    4. Extensions: Introduce and link to dev.mt.com resource
    5. Syntax Highlighter
    6. DekiScript / Paramatarized Templates
      1. 5 Demo DekiScript Templates
        1. Hello World
        2. User Properties and Permissions
        3. Native DekiScript functions
        4. Intro To Paramatarized Templates
        5. RSS and External data manipulation
      2. Button To Create A new Template
  3. Documentation Education (knowledge base):  Identifying tools and approaches to clean documentation
    1. Templates:  Explanation of how to use templates for content layout
    2. Include 5 default content layouts - with simple icons and teaser Headers and content
      1. 1 Column With A Picture Floated Right
      2. 2 Column with A Picture in first column
      3. 3 Column
      4. Right Hand SideBar with gray background
      5. Left Hand SideBar with gray background
    3. Control Panel Overview with quicklinks to Control Panel tools

 

Non-goals

  1. The OOBX homepage will not INITIALLY have functional tools on it, strictly education and navigation
Tag page (Edit tags)
Viewing 2 of 2 comments: view all
@jessicaR - Don't forget about the install process. Perhaps a paginated approach Page 1 - Install requirements Page 2 - Informational questions like email address company size ... etc
Posted 20:01, 29 May 2009
It would be useful to provide some "best practices" guidelines for new users and admins. That "blank canvas" effect can be deadly for many users. The guided entry is a great idea.

An important part of this would be included library of templates for pages and page parts (as mentioned above). The template selector should probably allow an annotated "gallery" view of available templates, perhaps with small previews. Better yet, allow categorization of templates for more intuitive navigation.
Posted 01:09, 15 Aug 2009
Viewing 2 of 2 comments: view all
You must login to post a comment.