enterprise ux patterns: good, bad and ugly

Download Enterprise UX patterns: Good, bad and ugly

Post on 21-Apr-2017

215 views

Category:

Design

0 download

Embed Size (px)

TRANSCRIPT

  • 1

    InteractionResearch in Practice.16Studies UX Pros should know

    Kath StraubUsability.org

    1

    Enterprise UX patterns:Good, bad and ugly

    Kath Straub, PhD

  • 2

    AbstractDocumented, enterprise design standards supporting homogenous customer experiences across different systems and touch points are often considered a holy grail of UX design. In many ways they are. But they can also lead to unintended consequences for both the design team and subsequent designs. We draw on experiences from a large federal agency to describe the impact, some positive and some less so, that mature but evolving design standards can have on designers, design and the development processes.

    Attendees will be exposedfor the first timeto the agencys extensive and extensively tested design patterns, and will benefit from a frank discussion of the new challenges that evolving enterprise standards introduce.

  • 3

    Designpatterns

    TheEasterbunny

    &theOsinfirstplace

    Promises, promises

  • BenefitConsistency across systems and devices.

    4

  • BenefitPatterns reduce everyones effort.

    5

  • Benefit Supports the paramedic model of UX

    6

  • BenefitIntegrate testing across projects.

    7

  • The User Experience Framework

    8

    AgencyWebPatterns

  • If you could change 1 thing about the way youve developed or managed your web standards, what would you change?

    9

  • Key insight Developers are users, too.

    10

  • 11

    Wearehere.

    ChallengePatterns are necessarily deployed incomplete.

  • ChallengeRole of developers morphs

    12

  • 13

    ChallengePattern developers have to make choices.

  • 14

    Challenge Pattern developers do not want to be CSRs.

  • 15

    ChallengePattern developers have to make choices.

  • ChallengePatterns are documented as atoms not molecules.

    16

  • 17

    ChallengePattern documentation testing needs to be multi-layer.

    Find Apply Modify

  • ChallengeOvertime patterns and code become one.

    18

    Patterns

    Code

    Axure Prototyping Tools

  • ChallengeDesigners with advanced tools stop sketching (!)

    19

  • Benefit? Challenge? A little of both?The role of designer changes, too.

    20

  • ChallengeDesigners start think in patterns first, not needs

    21

  • ChallengeDesigners now come in two flavors

    22

    Compliance

  • ChallengeRetrofitting legacy systems to patterns

    23

  • 24

    Wearehere.

    Whats next?

    Web Components

  • Methods

    25

    Questions?What do you think?

  • kath@usability.orghttps://www.linkedin.com/in/kathstraub/@kathstraub

    26

    About the speaker

    Kath Straub, PhDPrincipal

    Contact

  • 27

    Usability.org helpsorganizationsaroundtheworldimprovecustomerengagementandevolvetheircustomerresearch/designcapabilities.Weprovide

    Customerresearch Interactionandcommunicationdesign Evaluation Training/mentoring Organizationalchangestrategy Staffaugmentation

    Haveaquestion?Pleaseask!info@usability.org