X: Where do you get your amazing people at Netflix?
A Cockcroft: I get them from you.

It is not about hiring brilliant people.
It is about Netflix building an organisation, a management structure and leadership that enabled people to do their best and create outcomes effectively
The system is important!

If you hire good people into a bad system, you break the people.

> A bad system will beat a good person every time
>-- Deming

@jezhumble #agiletd
People don't create outcomes. Teams create outcomes.
What enables teams is good management and good leadership.
@jezhumble #agiletd
Favourite story about organisational change: Nummi

worst performing plant of GM

joint-venture with Toyota: rehired the same people
=> produced highest quality cars of all GM North America

=> the problem wasn't the people, it was the management

@jezhumble #agiletd
What happened at the GM factory:
QA driven quality process

What happened at the Toyota factory:
build quality in, continuously improve the process, andon cord to stop the production line when it is broken

@jezhumble #agiletd
Building Quality In
and
Giving the people doing the work the tools and the ability to build quality in turns out to be what is important.

"Our people are too stupid"
turns out that is true, but it is not the people you are thinking of.

@jezhumble #agiletd
> What my Nummi experience taught me that was so powerful was that the way to change culture is not to first change how people think, but instead to start by changing how people behave -- what they do ...
> -- John Shook

@jezhumble #agiletd
The term Lean comes from all those people in that Nummi factory who then went write papers and books and gave talks. They invented the term Lean.

@jezhumble #agiletd
People tried to copy the Nummi plant but it did not work, because managers were still rewarded for the number of cars they produced whether they were working or not.

Same problem with Software Methodologies
a software methodology is a bunch of stuff we do in an organisation

then we copy it and do the same stuff and we think it will achieve the same results

this is misguided
taking things that worked in one complex system with a particular set of goals and copying it, does not guarantee you the same results

partly because it is a different system and
also partly because you hopefully have different goals.
you got to work out for yourself

and the failures you will encounter while working out for yourself are important!
That is how you implement Continuous Delivery.
That is how you get better at what you do.

Don't copy what other people did. It is useful inspiration, but it won't create a culture of improvement. You have to do it yourself and management have to focus on helping you do that.
I was in the belief the term Lean came from the book:

The Machine that Changed the World from Womack, Jones and Roos🤔

Or could it be the authors took the term from the Nummi workers?

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Thierry de Pauw

Thierry de Pauw Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @tdpauw

2 May
Another implication of Conway’s Law is that if we have managers deciding on teams, and deciding which services will be built, by which teams, we implicitly have managers deciding on the system architecture.
@ruthmalan on Conway’s Law

web.archive.org/web/2018102200…
Conway’s Law also kicks in if we take an initial guess at the system decomposition allocate subsystems to teams, and sally forth–the team boundaries will tend to become boundaries within the system.
Anything else will be a feat of architectural heroics; hard to accomplish, when architectural heroics have to compete with schedule heroics driven by the steady beat of integration clocks.
Read 5 tweets
2 May
Conway's Law:
We can view a system as a linear graph.
Each node is a subsystem which communicates with other subsystems along the branches.
Each subsystem may contain a structure similarly portrayed.
"Interface" refers to the inter-subsystem communication path or branch.
The linear-graph notation is useful because it provides an abstraction that has the same form for the two entities we are considering:
the design organization
and the system it designs.
Replace "system" with "committee."
Replace "subsystem" with "subcommittee."
Replace "interface" with "coordinator."
Just as with systems, we find that design groups can be viewed at several levels of complication.
Read 4 tweets
2 May
... organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations.
-- How Do Committees Invent?, Melvin Conway
(aka Conway's Law)
... we have found a criterion for the structuring of design organizations: a design effort should be organized according to the need for communication.
This criterion creates problems because the need to communicate at any time depends on the system concept in effect at that time. Because the design which occurs first is almost never the best possible, the prevailing system concept may need to change.
Read 5 tweets
2 May
The structures of large systems tend to disintegrate during development, qualitatively more so than with small systems.
Why do large systems disintegrate?
-- How Do Committees Invent?, Melvin Conway
First, It is a natural temptation of the initial designer to delegate tasks when the apparent complexity of the system approaches his limits of comprehension. ... Either he struggles to reduce the system to comprehensibility and wins, or else he loses control of it.
Second, application of the conventional wisdom of management to a large design organization causes its communication structure to disintegrate.
Read 10 tweets
2 May
... we have demonstrated that there is a very close relationship between the structure of a system and the structure of the organization which designed it.
— How Do Committees Invent?, Melvin Conway
This kind of a structure-preserving relationship between two sets of things is called a homomorphism.
— How Do Committees Invent?, Melvin Conway
... it is reasonable to assume that for any system requirement there is a family of system designs which will meet that requirement, we must also inquire whether the choice of design organization influences the process of selection of a system design from that family.
Read 7 tweets
2 May
... the very act of organizing a design team means that certain design decisions have already been made, explicitly or otherwise. ...
— How Do Committees Invent?, 6th par, Mel Conway
... Given any design team organization, there is a class of design alternatives which cannot be effectively pursued by such an organization because the necessary communication paths do not exist. ...
— How Do Committees Invent?, 6th par, Mel Conway
... Therefore, there is no such thing as a design group which is both organized and unbiased.
— How Do Committees Invent?, 6th par, Mel Conway
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(