18
Being a generalist and being great at what you do IS IT POSSIBLE? / GOOD AND BAD

Being a generalist and being great at what you do

Embed Size (px)

Citation preview

Page 1: Being a generalist and being great at what you do

Being a generalist and being great at what you doIS IT POSSIBLE? / GOOD AND BAD

Page 2: Being a generalist and being great at what you do

Where do I come from?

Page 3: Being a generalist and being great at what you do

To DevOps or not to DevOps?This is the question!

Page 4: Being a generalist and being great at what you do

3 levels of Operational response

Page 5: Being a generalist and being great at what you do

EMT

Page 6: Being a generalist and being great at what you do

EmergencyRoomDoctor

Page 7: Being a generalist and being great at what you do

SpecialistSurgeon

Page 8: Being a generalist and being great at what you do

Is it a progression or a differentiation?

* Are you winning or are you loosing when you’re specializing?

* Do you want to know 1 thing only and be clueless all around?

* Don’t you need to know a lot of things anyway?

Page 9: Being a generalist and being great at what you do

Organizational thoughts on specialistsBENEFITS

* Can quickly figure out the problem

* Provides best (?) advise and solution (?)

* Knows his stuff

CONCERNS

* Hard to find and hire

* What does he do between the tasks?

* Point of contention – hard to plan, need to wait to allocate

* Expensive (mostly)

Page 10: Being a generalist and being great at what you do

It’s a range/gradient of valid possibilities

Knows Everything:* Dev* Ops* Business* Sales* Marketing* …..

Kills in ONE Things ONLY:* Ex: networking packets

Most of us common folksare somewhere here ….

Page 11: Being a generalist and being great at what you do

Team composition options (depends on business needs)VERTICAL SILO TEAMS

Team composition:◦ Specialists (only)

Pros:◦ In-depth specialization◦ Easy to assemble◦ Scales vertically (bigger team)

Cons:◦ Narrow specialization◦ Hand-overs◦ Long waiting queues

FEATURE (WIDE SKILL) TEAMS

Team composition:◦ Generalists augmented (on demand) by specialists

Pros:◦ Flexible◦ Autonomous (solves the tasks end-to-end)◦ Can be reassigned in a moment to most urgent tasks◦ Scales horizontally (more autonomous teams)

Cons:◦ Non-traditional◦ Hard to hire and assemble◦ Hard to incentivize people grows (Spotify uses tribes)

Page 12: Being a generalist and being great at what you do

Needs of companies evolve over time

Page 13: Being a generalist and being great at what you do

Who is this mysterious DevOps person?

Page 14: Being a generalist and being great at what you do

DevOps Skills signature of a person/team

Quality of knowledge

DeveloperMindset

Operational/SustainingMindset

Page 15: Being a generalist and being great at what you do

ROI of the gradient spread

Compensation

Availability of talent(bell curve of normal

distribution)

Hot-spots of high ROISpecializing Generalist

Generalizing Specialist

Page 16: Being a generalist and being great at what you do

Danger zones of the talent spread

You’re so generic that you can be easily replaced by a cheaper guy

Your head will explode ... You’re alone and have

to be the best in the field to be relevant

Page 17: Being a generalist and being great at what you do

We need everyone! Choose your path!

Page 18: Being a generalist and being great at what you do

Thank you! Questions?

@igor_moochnick

[email protected]

http://r44e.wordpress.com/