<Insert Picture Here>

UE Approach towards AUBI Design PatternsAdesh Singh28 May 2008

Agenda

• Dimensions of User Experience Process• Pattern Identification• Authoring & Review• Validation• Release and Communication• Effort & Timeline• BI Pattern areas• Patterns Website• Next steps

Dimensions of User Experience Processes

• Scenarios • Pattern sets• Individual patterns

• Create template• Create draft• Review• Iterate

• Apply patterns• Gather feedback• Update patterns

• Publish • Gather feedback• Update patterns

IDENTIFY AUTHOR VALIDATE RELEASE

• App. scenarios • Applicable Patterns• New patterns

requirement

• Create task flows• Concept designs• Apply patterns• Wireframes

• Internal reviews• User feedback• Identify gaps• Update patterns

• Design solutions • Prototypes• Design specs.

IDENTIFY CONCEPTUALIZE VALIDATE RECOMMEND

Tier 1 App Creation

Pattern Creation

• Site visits • User Interviews• Customer

advisory boards

• Identify issues• Key requirements• Pain points• Suggestions

• Key usability Issues• Primary focus areas• Needs & wants

• Usability Testing• Customer feedback

sessions

STUDY ANALYZE REPORT VALIDATE

User Research

User research outcomes will feed into patterns

Patterns will be leveragedin AUBI Apps

Pattern Identification

• Extract tasks from scenarios (based on use cases)• Create generic task flows• Create pattern sets

• Map tasks to FusionGPS• Identify gaps in AU context

• Map pattern sets to task flow• Identify individual patterns for each set

• Review pattern list and structure with stakeholders• Identify key patterns for authoring in phase 1

Authoring & Review

• Initial tasks• Create a pattern template

• Identify external reviewers from UX

• Create issue tracking template (wiki)

• Authoring• Create pattern draft in Word

• Create illustration/visuals

• Review• Review internally (UX)

• Review with Dev and Strategy (tech feasibility? Use case coverage?)

• Create and track issue list

• Iterate and notify review team

• Conduct audit if needed

Validation

• Validation – Tier 1 projects• Apply patterns to Business Consoles

• Identify use case and generate task flows• Identify applicable patterns• Generate wireframes based on patterns

• Gather feedback on wireframes through user testing• Identify and create/update patterns if needed

Release and Communication

• Publish Patterns website• Include recorded introduction training• Communicate to stakeholders

• Office hours for usage support – Tier 2 and 3 projects• Feedback to product teams• Track issues on wiki• Create/update patterns if required• Route feature requests to tools team

• Communicate release/updates to stakeholders

Effort & Timeline ?

ActivityEffort(Hrs)

Start Finish Notes

Identify pattern areas 12 - May

Structure patterns 8 14 - May 16 - May

Review internally & iterate 4 16 - May 19 - May

Detailed list of patterns 12 28 - May 1 - Jun

Identify individual pattern content structure 3 3 - Jun 4 - Jun

Review internally & iterate 6 5 - Jun 8 - Jun

Setup review team/panel and issue tracking sheet 3 8 - Jun 8 - Jun

Author pattern content - drop 1 ~ 9 - 10 key patterns

Research (ongoing) 15 12 - Jun

Content creation (text + visuals) 60

Review internally & iterate 20

Review externally and iterate 20

Publish to AUBI pattern website 10 30 - Jul 25 hrs per pattern

Author pattern content – drop 2 Aug - 1 Sep - 30

Review externally and iterate

<Insert Picture Here>

BI Pattern Areas

Key User Tasks

• Login to the AUBI Business Console

• High level overview of key info (KPI, Alerts etc.) – The forest view

• Measure and monitor key metrics, scorecard etc.

• Correlate and compare information

• View details of a specific metric or KPI – The tree view

• Collect key nuggets and identify primary areas of attention

• Take necessary actions on these areas including data transaction, notification etc.

• Share & collaborate with other potential consumers of the information

• Setup and configure console

• Manage overload

AUBI Design Pattern Areas for Business Consoles

Patterns > Navigation > Decision Table

Analytic Table KPI List Tree Table Pivot Table

1. User Type Casual Casual Experienced Experienced, Frequent User

2. Do quantities of two different dimensions need to be grouped in hierarchies?

No No No Yes

3. Do the quantities need to be grouped in hierarchies?

No No Yes Yes

4. Are objects sortable within group?

Yes Yes Yes Yes

Patterns website - TBD

Next steps

• Get feedback from Strategy on the pattern areas• Identify top 10 patterns to develop during phase 1• Create a sample pattern draft by early June and share

with Strategy