The Lie of a Benevolent Dictator; the Truth of a Working Democratic Meritocracy

Preview:

DESCRIPTION

Keynote at OpenStackSV's inaugural event. Essentially a call to arms to fix the missing "product leadership gap" that is clearly causing drag on the project(s).

Citation preview

SEPTEMBER 2014openstacksv.com

The Lie of The Benevolent Dictator

The Truth of a Democratic Meritocracy!Randy Bias, CEO

SEPTEMBER 2014 Page

Do we need a benevolent dictator?

2

SEPTEMBER 2014 Page

OpenStack *has* a leadership, or at least governance/management structure

3

PageSEPTEMBER 2014 4

Board

Foundation

TC

Developer Community

PTLs Ind.Plat. Gold Ind.

ED

Rel Mgr Ind. Corp.

Subcommittees• legal• finance• DefCore• etc.

User Committee• nascent• user survey

RM

elected

appointed

hired

volunteer

Strategic Business Direction Tactical Software Dev Life Cycle

SEPTEMBER 2014 Page

But is it the right kind of leadership?

5

SEPTEMBER 2014 Page

Does OpenStack have a product vision and product

strategy?

6

SEPTEMBER 2014 Page

NO!

Does OpenStack have a product vision and product

strategy?

6

SEPTEMBER 2014 Page

The Gap

7

Board TC

Strategic Business Direction Tactical Software Dev Life Cycle

Strategic Product Vision &

Direction?No one owns!!

SEPTEMBER 2014 Page

“product strategy” for open source project(s) ?

8

SEPTEMBER 2014 Page

Product strategy and vision will not “emerge” from a group

9

PageSEPTEMBER 2014 10

SEPTEMBER 2014 Page 11

SEPTEMBER 2014 Page

We are a democratic meritocracy

11

SEPTEMBER 2014 Page

We are a democratic meritocracy

We are not the Linux community

11

SEPTEMBER 2014 Page

We are a democratic meritocracy

We are not the Linux community

We don’t need a dictator, but we do need product leadership

11

SEPTEMBER 2014 Page

Some Product Leadership Requirements not a complete list, OK?

12

PageSEPTEMBER 2014

• OpenStack is NOT a Product, BUT … It Must Be Managed Like One• Long term vision + long term prioritization & planning• Corporate independence

• Work for the community: developers, operators, and end-users

• Focus on end-user needs and requirements• Working with the user committee, obviously…

• Ability to work closely with the Board and the TC• Priority setting, vision, etc.

• Architectural oversight and leadership

13

Some Product Leadership Requirements

SEPTEMBER 2014 Page

What does AWS do?

14

PageSEPTEMBER 2014

• Small architecture review board• Werner Vogels, James Hamilton, etc.

• Product management function• Team of product managers per product line

15

What does Amazon do for product leadership?

SEPTEMBER 2014 Page

What *might* we do?

16

PageSEPTEMBER 2014

• Arch Review Board (ARB)• Elected for 2-4 years• Small # of seats• Wide set of domain expertise• Remit is:• work with TC on BP/Specs• help PMs validate priority

17

What could we do? (Just a SUGGESTION)

• Product Management (PM)• Not elected• 1+ per program• Specific domain expertise• Work for the Foundation• Annual 360° feedback• Remit is:• priority setting & negotiation

PageSEPTEMBER 2014

Foundation

18

Board TC

Developer Community

PTLs Ind.Plat. Gold Ind.

ED

Rel Mgr

Ind. Corp.

Subcommittees• legal• finance• DefCore• etc.

User Committee• nascent• user survey

elected

appointed

hired

volunteer

Strategic Business Direction Tactical Software Dev Life Cycle

ARB • Shared

chair?• Elected PTL

seat?• Independents• Long term

Architects

Prod. Mgrs

SEPTEMBER 2014 Page 19

SEPTEMBER 2014 Page

Product leadership the issue; NOT dictatorship

19

SEPTEMBER 2014 Page

Product leadership the issue; NOT dictatorship

Product leadership cannot be emergent

19

SEPTEMBER 2014 Page

Product leadership the issue; NOT dictatorship

Product leadership cannot be emergent

Many paths forward; *all* require creating ownership

19

SEPTEMBER 2014 Page

Product leadership the issue; NOT dictatorship

Product leadership cannot be emergent

Many paths forward; *all* require creating ownership

Collective responsibility to fix this

19

SEPTEMBER 2014 Page

Product leadership the issue; NOT dictatorship

Product leadership cannot be emergent

Many paths forward; *all* require creating ownership

Collective responsibility to fix this

Failure to fix may result in insurmountable challenges

19

SEPTEMBER 2014 Page

Thank you

@randybias

20

Recommended