The Danger of Having No WHY

Slide 1

Slide 1 text

The Danger of Having No WHY @emmajanehw E M M A J A N E W E S T B Y

Slide 2

Slide 2 text

Warning! The talk contains use of the “f” word.

Slide 3

Slide 3 text

Bold Claim I think the Backdrop fork was good for our community. Backdrop offers a clear mission statement. And it is forcing us to clarify our own product’s mission.

Slide 4

Slide 4 text

Agenda 1. How (and why) to be selfish in a FOSS project. 2. The danger of not having a clear mission statement. 3. Discussion.

Slide 5

Slide 5 text

The Hobbit An unexpected bit of research

Slide 6

Slide 6 text

Everything had its place and every place had its thing.

Slide 7

Slide 7 text

“That’s not a dishcloth! It’s a doily.”

Slide 8

Slide 8 text

Bilbo chooses adventure.

Slide 9

Slide 9 text

Humans want to connect with people who believe what they believe.

Slide 10

Slide 10 text

What How Why

Slide 11

Slide 11 text

What How Why

Slide 12

Slide 12 text

What How Why

Slide 13

Slide 13 text

What How Why Simon Sinek’s Golden Circle www.startwithwhy.com bit.ly/ss-tedtalk

Slide 14

Slide 14 text

Bilbo's WHY is “home”. “You don’t belong anywhere.”

Slide 15

Slide 15 text

To understand, transform, and remove obstacles to achieve a state of flow My WHY.

Slide 16

Slide 16 text

Discovering Your WHY Your purpose. Your cause. Your belief. Your personal mission statement.

Slide 17

Slide 17 text

What makes you smile?

Slide 18

Slide 18 text

When you lose track of time, what are you doing?

Slide 19

Slide 19 text

What are your favourite things to do?

Slide 20

Slide 20 text

Is there anything you don’t feel gifted at, but love doing anyway?

Slide 21

Slide 21 text

When people ask for your help, what do they want help with?

Slide 22

Slide 22 text

If you had to teach something, what would you teach?

Slide 23

Slide 23 text

Who would your students be?

Slide 24

Slide 24 text

When you quit, what’s typically your “last straw”?

Slide 25

Slide 25 text

Define your why.

Slide 26

Slide 26 text

This space intentionally left blank.

Slide 27

Slide 27 text

Bilbo was committed to WHY the dwarves were adventuring, not WHAT.

Slide 28

Slide 28 text

@emmajanehw 2003ish Ripped the content storage tables out of Drupal for my own CMS. drupal.org/user/1773 2005 Came back to Drupal and started building sites for clients with walkah's help. 2007 2009 My first (and only) core patch. Moshe tells me my mom’s bookstore site shouldn’t be built with Drupal; that I should use WordPress instead. “For my mother, who asked for the manual to her web site.” 2011 Taught my first Drupal 8 workshop. 2013 2014 Still haven’t upgraded mum’s site from Drupal 5.

Slide 29

Slide 29 text

I sold the promise of easy growth.

Slide 30

Slide 30 text

I sold the state of flow to designers and themers.

Slide 31

Slide 31 text

Drupal 8

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

What’s our mission statement?

Slide 34

Slide 34 text

Modernization of the infrastructure. My mission statement for Drupal 8.

Slide 35

Slide 35 text

“Our mission was to make Drupal fast, small, clean and on the bleeding-edge of technology.”

Slide 36

Slide 36 text

“At the end of the day, we can't make everybody happy and it is very important that you realize that.”

Slide 37

Slide 37 text

Dries, 2006 http://buytaert.net/backward-compatibility

Slide 38

Slide 38 text

Drupal was trying to be consistent. So what happened?

Slide 39

Slide 39 text

Slide 40

Slide 40 text

“Come for the software, stay for the community.”

Slide 41

Slide 41 text

Slide 42

Slide 42 text

(you said) “Drupal 8 Will Have Something for Everyone to Love” https://drupal.org/drupal-8.0

Slide 43

Slide 43 text

Stop doing that.

Slide 44

Slide 44 text

Put the stake back in the ground. Define, and own, the WHY.

Slide 45

Slide 45 text

Massive change doesn’t happen by magic. It happens by management.

Slide 46

Slide 46 text

Change management is the application of a structured process and set of tools for leading the people side of change to achieve a desired outcome. https://www.prosci.com/change-management/ definition/

Slide 47

Slide 47 text

A shared definition of the problem…

Slide 48

Slide 48 text

so that stakeholders understand why change is necessary.

Slide 49

Slide 49 text

A shared vision of the future…

Slide 50

Slide 50 text

so that stakeholders understand how they will benefit.

Slide 51

Slide 51 text

Backdrop didn’t share Drupal’s definition of the problem. That was stressful but in a good way.

Slide 52

Slide 52 text

Discuss.

Slide 53

Slide 53 text

“The Drupal mission is to develop a leading edge open-source content management system that implements the latest thinking and best practices in community publishing, knowledge management, and software design.” https://drupal.org/mission

Slide 54

Slide 54 text

Does drupal.org accurately describe our WHY?

Slide 55

Slide 55 text

How do we define GOOD software?

Slide 56

Slide 56 text

Who has the authority to define GOOD?

Slide 57

Slide 57 text

When it’s DONE, how will we know?

Slide 58

Slide 58 text

Whose responsibility is the vision of DONE?

Slide 59

Slide 59 text

What did you think? E V A L U A T E T H I S S E S S I O N : A U S T I N 2 0 1 4 . D R U P A L . O R G / S C H E D U L E