innovate uxi community_3b

UXI COMMUNITYINNOVATION

1

CREATINGA CULTURE OF UXPresented by: Brad Briscoe


2


3

User Experience Design is like a

3 Ring Circus


4

User Experience Considerations

A/B TESTING

WIREFRAMESFLOW DIAGRAMS

PERSONAS

HEURISTIC EVALUATIONS

SITE MAPS

CONTEXTUAL INQUIRY

CARD SORTING

AFFINITY DIAGRAMMING

SCENARIOS

PERSONAS

PROTOTYPING

STORYBOARDS

USER INTERVIEWS

STORYBOARDS

CONCEPT MAP


5

THE THREE CORE UX ATTRIBUTES

In the last six weeks, have you spent more than two hours watching someone use our application designs or a competitors design?

Can everyone on the team describe the experience of using a design five years from now?

In the last six weeks, have you rewarded a team member for creating a major design success or failure?

VISION FEEDBACK CULTURE

For Great User Experience Design


6

WHY ARE WE

HERE TODAY?


7

Development Communities fragmented, grass root efforts

Domain Owners

UXI DeveloperCommunity

BPMSCommunity(pending)

SOA Community

SOA Technical Design

Reviews

ArchitectureReview Board

ArchitectureSteering

Committee

Monthly Architecture Call

Solution Architect

Round Table

Architecture

Arch

itect

ure

Stan

dard

s Bo

ards

Current State Engagement


8

Future State Engagement

Formalize Development

Communities, bring development back to

steady state

ArchitectureReview Board

ArchitectureSteering

Committee

Monthly Architecture

Call

Solution Architect

Round Table

Architecture

Arch

itect

ure

Stan

dard

s Boa

rds

UXI Sub Community

Forum

Services Sub Community

Forum

Process Orchestration

Sub CommunityForum

Development

Deve

lopm

ent

Com

mun

ity F

orum

Bi-directional communication with broader Architecture community

(Future) Sub Community

Forum


9

ObservationsInformal fragmented development communities stood up through grass roots efforts, missing knowledge sharing across communities

• Lack of commitment of participants

SOA Community forum not focusing on code & design reviews, which could improve cross team knowledge sharing

• If needed, domain owners/managers can create separate forum

SOA has separate meetings for formal technical design & code reviews

• Can design reviews be an open forum to further knowledge sharing?

Meeting attendees presence expected on many different communities, spread too thin to participate in all meetings

Training is not enough, nor a priority – need vibrant, active development community sharing experiences where developers can mature their development acumen

• Needed for all architecture patterns


10

Today’s GoalDiscuss future vision for Development Community Forums, collect your feedback, and gain consensus on next steps

Topics for discussion Current State EngagementFuture State EngagementDevelopment Community MembershipDevelopment Sub Community MembershipImplementation ConsiderationsProposed Next Steps

CREATE, COLLABORATE, CONTRIBUTE


11

CREATE, COLLABORATE, CONTRIBUTE

2 Updated and Relevant Links

3 Unique Design and Infographic

4Tools such as Feedback Requests, Updated Presentations and more

1 Collaborative Page Features

The New Content Driven Account Management IT SharePoint Page


12

COLLABORATIVE UX PAGE

2 Updated tools, Documentation and usable Widgets

3 Presentations

4 Project Lists, Surveys and useful features

1 Collaborative Content and Links

5

Owners of this page: Rick Dale, Britt Johnson, Brad Briscoe, Aaron Case, Omar Khan and George Cruz

We look forward to your feedback


13

WFA Development Sub Community Forums

Formalize current Development Communities into a Development Sub Community per architecture pattern

• UXI Sub Community Forum• Services Sub Community Forum• Process Orchestration Sub Community Forum (does not currently exist)• (Future) Sub Community Forum

Assign a dedicated (fulltime) Application Delivery team member as chairperson for each Development Sub Community

• Assign WFA Frameworks and Architecture team member to each Development Sub Community

Development Sub Community Forums membership and support

• DIO support for Application Delivery contributions• Application Delivery participants should be SMEs in v12 pattern

development• Participants rotate in/out of forum• Intent of knowledge sharing across development organization

(train the trainer)


14

WFA Development Community ForumEstablish an overarching WFA Development Community Forum • Open communication channels/collaboration across Development Sub

Community Forums • Knowledge sharing of significant content to broader

architecture/development community via Monthly Architecture Call• Recommend enhancements/new approaches to Architecture Steering

Committee (ASC)

Staffed by members and chairpersons from each Development Sub Community Forum with WFA Frameworks and Architecture participation

Chaired by scheduled rotation of Sub Committee Chairpersons

How would we set this in motion


15

Development Community Forum - Membership

Charter• Provide input to WFA Frameworks

– set priorities on work efforts• Conduct WFA Framework

code/design and QA reviews• Establish development Wiki,

sourced by sub community team members, to facilitate technical discussions and provide answers to technical questions/issues

• Open/respectful dialog, accepting diverse positions

Broad inputs ensure all participants/perspectives have a voice

Chairperson

(Application Delivery)

UXI Community

Services Community

Process Orchestrati

on Community

(Future Community

)Data

Management

WFA Framework

s

Architecture


16

Development Sub Community Forums - Membership

Charter• Discuss technical issues – innovate new

approaches, providing guidance and consistency of implementation

• Open/respectful dialog, accepting diverse positions

• Conduct code & design peer reviews; results/remediation accountability with peer group

• Mature development discipline; contribute to Framework components; recommend new tooling

• Escalate issues/promote significant events up to Development Community Forum

Using as illustration, Services Sub Community at deeper dive

Services

Chairperson

(Application Delivery)

Application Delivery

Team Member


Team Member


Team Member

Data Manageme

nt (as appropriat

e)WFA

Frameworks

Architecture


17

Implementation ConsiderationsKey needs that must be met to ensure successApplication Delivery commitment in ownership and contribution to maturation of new v12 pattern development practices

• Full-time Chairperson per Development Sub Community • 20% allocation of Application Delivery SME team members enabling

contribution to Development Community forums/efforts

• Architecture commitment to support Application Delivery/Development Community input to development practices

Formalize Sub Community Chairpersons – Possible Options UXI Sub Community

• John Haley

Services Sub Community• Rick Caponigro

Process Orchestration Sub Community• Patrick Fagan


18

Gain Consensus of Development Communities/Sub Communities

Develop Communication Plan

• DIO Weekly Meeting

• Application Development: Transformational Leadership Team

• Architecture Steering Committee

• Architecture Monthly Call

Form Development Communities/Sub Communities Membership

Define implementation timeline

Proposed Next Steps


19

QUESTION & ANSWER SESSION

FEEL FREE TO ASK NOW, OR EMAIL US AFTER THE PRESENTATION


20

THANK YOUPlease let us know how we can support you!The UXI Forum Community Support Team:Rick Dale, Britt Johnson, Brad Briscoe, Aaron Case, John Haley, Omar Khan and George Cruz


21

UX DEMAND

innovate uxi community_3b

Technology