Slide 1

Slide 1 text

#WEBU17 | @bermonpainter PEOPLE, PROCESS, & PATTERNS

Slide 2

Slide 2 text

PEOPLE, PROCESS, & PATTERNS What about people makes projects hard How to overcome communication styles & engage in successful conflict Tips and tricks to effectively negotiate conversations How to successfully scope projects and reduce risk Ways patterns can be a central talking point to build consensus 1 2 3 4 5 WEB UNLEASHED

Slide 3

Slide 3 text

PEOPLE

Slide 4

Slide 4 text

WHY ARE PEOPLE IRRATIONAL?

Slide 5

Slide 5 text

“It is self-evident that people are neither fully rational nor completely selfish, and that their tastes are anything but stable.” - Daniel Kahneman

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

ACTIVE LISTENING

Slide 9

Slide 9 text

SLOW. IT. DOWN.

Slide 10

Slide 10 text

TONE

Slide 11

Slide 11 text

POSITIVE & PLAYFUL 1 SLOW & MEASURED 2 ASSERTIVE 3

Slide 12

Slide 12 text

POSITIVE & PLAYFUL 1 SLOW & MEASURED 2 ASSERTIVE 3

Slide 13

Slide 13 text

POSITIVE & PLAYFUL 1 SLOW & MEASURED 2 ASSERTIVE 3

Slide 14

Slide 14 text

MIRRORING

Slide 15

Slide 15 text

LABELING

Slide 16

Slide 16 text

PARAPHRASING

Slide 17

Slide 17 text

“The single biggest problem in communication is the allusion that is has taken place.” – George Bernard Shaw

Slide 18

Slide 18 text

RESOURCES

Slide 19

Slide 19 text

PROCESS

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

Product Backlog SPRINT Scoped User Stories Releasable Software Scoped User Stories Releasable Software Scoped User Stories Releasable Software Scoped User Stories Releasable Software Priority L H SPRINT SPRINT SPRINT TRADITIONAL AGILE PROCESS

Slide 22

Slide 22 text

t APPEALING t FUNCTIONAL t VALUABLE DESIGN DEVELOPMENT USABILITY RESEARCH & VALIDATION USEFUL BUILDING GREAT PRODUCTS A great product decreases customer frustration, increases their productivity, lessens the need for training, provides consistent and predictable interactions, and increases user satisfaction and loyalty.

Slide 23

Slide 23 text

t APPEALING t FUNCTIONAL t VALUABLE DESIGN DEVELOPMENT USABILITY RESEARCH & VALIDATION USEFUL BUILDING GREAT PRODUCTS A great product decreases customer frustration, increases their productivity, lessens the need for training, provides consistent and predictable interactions, and increases user satisfaction and loyalty.

Slide 24

Slide 24 text

t APPEALING t FUNCTIONAL t VALUABLE DESIGN DEVELOPMENT USABILITY RESEARCH & VALIDATION USEFUL BUILDING GREAT PRODUCTS A great product decreases customer frustration, increases their productivity, lessens the need for training, provides consistent and predictable interactions, and increases user satisfaction and loyalty.

Slide 25

Slide 25 text

t APPEALING t FUNCTIONAL t VALUABLE DESIGN DEVELOPMENT USABILITY RESEARCH & VALIDATION USEFUL BUILDING GREAT PRODUCTS A great product decreases customer frustration, increases their productivity, lessens the need for training, provides consistent and predictable interactions, and increases user satisfaction and loyalty.

Slide 26

Slide 26 text

LIFECYCLE OF A REQUIREMENT REQUIREMENTS

Slide 27

Slide 27 text

LIFECYCLE OF A REQUIREMENT ASSUMPTIONS

Slide 28

Slide 28 text

LIFECYCLE OF A REQUIREMENT RISK

Slide 29

Slide 29 text

LIFECYCLE OF A REQUIREMENT IDEAS

Slide 30

Slide 30 text

LIFECYCLE OF A REQUIREMENT IDEAS IDEA IDEA IDEA IDEA IDEA IDEA DELIVERY BACKLOG

Slide 31

Slide 31 text

LIFECYCLE OF A REQUIREMENT DELIVERY BACKLOG IDEA IDEA IDEA IDEA IDEA IDEA IDEA

Slide 32

Slide 32 text

LIFECYCLE OF A REQUIREMENT EA EA FRAME ASSUMPTIONS MAKE SENSE OF THE PROBLEMS BRAINSTORM SOLUTIONS DETERMINE FOCUS AREAS DISCOVERY CYCLE VALIDATION CYCLE LEARN BUILD 1 2 3 4 7 6 5 MEASURE IDEA

Slide 33

Slide 33 text

LIFECYCLE OF A REQUIREMENT FRAME ASSUMPTIONS MAKE SENSE OF THE PROBLEMS BRAINSTORM SOLUTIONS DETERMINE FOCUS AREAS DISCOVERY CYCLE VALIDATION CYCLE LEARN BUILD 1 2 3 4 7 6 5 MEASURE VALIDATED IDEAS A

Slide 34

Slide 34 text

LIFECYCLE OF A REQUIREMENT ME ON BRAINSTORM SOLUTIONS DETERMINE FOCUS AREAS DISCOVERY CYCLE VALIDATION CYCLE LEARN BUILD 1 3 4 7 6 5 MEASURE VALIDATED IDEAS DELIVERY BACKLOG

Slide 35

Slide 35 text

LIFECYCLE OF A REQUIREMENT VALIDATED IDEAS DELIVERY BACKLOG SCOPED ITERATION

Slide 36

Slide 36 text

LIFECYCLE OF A REQUIREMENT DELIVERY BACKLOG SCOPED ITERATION WORKING SOFTWARE

Slide 37

Slide 37 text

DUAL TRACK DISCOVERY / DELIVERY DISCOVERY DELIVERY DISCOVERY CYCLE VALIDATION CYCLE DISCOVERY CYCLE VALIDATION CYCLE SPRINT SPRINT DISCOVERY CYCLE VALIDATION CYCLE IDEAS IDEAS IDEAS

Slide 38

Slide 38 text

DUAL TRACK DISCOVERY / DELIVERY Discovery Backlog Priority L H FRAME ASSUMPTION MAKE SENSE OF THE PROBLEMS BRAINSTORM SOLUTIONS DETERMINE FOCUS DISCOVERY CYCLE VALIDATION CYCLE LEARN BUILD 1 2 3 4 7 6 5 MEASURE Discovery / Validation Cycle Validated Ideas

Slide 39

Slide 39 text

Discovery Backlog Priority L H Kanban Validated Ideas Ready In Progress Review Done DUAL TRACK DISCOVERY / DELIVERY

Slide 40

Slide 40 text

DUAL TRACK DISCOVERY / DELIVERY Delivery Backlog Priority L H Discovery / Validation Cycle Releasable Software SPRINT

Slide 41

Slide 41 text

t APPEALING t FUNCTIONAL t VALUABLE DESIGN DEVELOPMENT USABILITY RESEARCH & VALIDATION USEFUL CHANGING THE DEFINITION OF DONE A great product decreases customer frustration, increases their productivity, lessens the need for training, provides consistent and predictable interactions, and increases user satisfaction and loyalty.

Slide 42

Slide 42 text

RESOURCES

Slide 43

Slide 43 text

PATTERNS

Slide 44

Slide 44 text

WHAT IS A PATTERN LIBRARY? A collection of user interface design patterns that appear multiple times across a website or application. The pattern library documents each patterns and defines: 1. what they look like 2. how they behave 3. how to code them

Slide 45

Slide 45 text

WHAT IS A PATTERN LIBRARY? CORE COMPONENTS PATTERNS TEMPLATES PAGES

Slide 46

Slide 46 text

WHAT IS A PATTERN LIBRARY? CORE COMPONENTS PATTERNS TEMPLATES PAGES Aa Transport New Medium ABCDEFGHIJKLMNOPQRTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789 Grid Baseline

Slide 47

Slide 47 text

WHAT IS A PATTERN LIBRARY? CORE COMPONENTS PATTERNS TEMPLATES PAGES

Slide 48

Slide 48 text

WHAT IS A PATTERN LIBRARY? CORE COMPONENTS PATTERNS TEMPLATES PAGES

Slide 49

Slide 49 text

WHAT IS A PATTERN LIBRARY? CORE COMPONENTS PATTERNS TEMPLATES PAGES

Slide 50

Slide 50 text

WHAT IS A PATTERN LIBRARY? CORE COMPONENTS PATTERNS TEMPLATES PAGES

Slide 51

Slide 51 text

WHY ARE PATTERN LIBRARIES USEFUL? CONSISTENCY Large projects are developed by different people over a long period of time which leads to fragmentation. A pattern library provides central documentation for all patterns across multiple projects or teams and make it easy to quickly duplicate existing patterns when creating a new page. 1 REUSABILITY Large teams typically work in isolation and reinvent the wheel at a considerable cost. A pattern library, developed in collaboration between relevant teams, make sure patterns can be reused. When a new pattern is created, it is permanently available for the whole team to use on current and future projects. 2 MAINTAINABILITY Inconsistencies and reinventing the wheel decrease maintainability. In a pattern library each pattern is tested across multiple browsers and complies with existing brand standards. This reduces the number of bugs reported, and allows the teams to focus on creating new features. 3

Slide 52

Slide 52 text

WHO ARE THE DECISION MAKERS? MARKETING Typically an easier conversation. They tend to focus a lot on brand consistency and customer engagement / satisfaction. 1 IT / DEVELOPMENT They tend care about implementation details, how to reduce development costs, improve test coverage, and in some cases how to avoid writing front-end code. 2 FORWARD THINKING C-LEVEL (CMO, CTO, CIO) They may have attended a conference or latched on to some buzzwords & want to help their organization be more effective and increase time-to-market on new features. 3

Slide 53

Slide 53 text

MATURITY MODEL INCONSISTENT The team has no pattern library and may be missing core capabilities to build one. Their output is inconsistent. STATIC They may have a designer that’s produced a static document to detail branding guidelines. MANUAL A pattern library exists and has some code, but it has to be manually updated and isn’t fully integrated with their development. AUTOMATIC A pattern library exists and is fully integrated in to the development build process. GOVERENED The pattern library is built into the core of how the organization builds applications and websites.

Slide 54

Slide 54 text

SOLITARY CENTRALIZED FEDERATED MATURITY MODEL

Slide 55

Slide 55 text

PROJECTS ARE EASY. PEOPLE ARE HARD.

Slide 56

Slide 56 text

ACTIVELY LISTEN 1 CHOOSE YOUR TONE 2 MIRROR 3 LABEL 4 PARAPHRASE 5

Slide 57

Slide 57 text

RESOURCES NATHAN CURTIS https://medium.com/@nathanacurtis 1 https://www.smashingmagazine.com/design-systems-book/ 2 ALLA KHOLMATOVA

Slide 58

Slide 58 text

FIN OPEN OFFICE HOURS Friday mornings: 7am-9am officehours.io/people/bermonpainter TWITTER/SKYPE/EMAIL @bermonpainter KEEP IN TOUCH