My talk at Surge 2013. Video is at http://www.youtube.com/watch?v=bGkVM1B5NuI Caution: Should not be consumed by stack-ranking six-sigma black belts with fragile constitutions.
Interesting in learning more about OKRs? We've provided a simple primer that will teach you about this effective goal-setting framework. Learn about the basic, benefits, history, grading, implementation of OKRs.
This is the first SlideShare adaption of Timothy E. Johansson's 100 Growth Hacks in 100 Days. The growth hacks that's included in the slide are 1 to 10. Timothy is the front-end developer at UserApp (www.userapp.io).
Interesting in learning more about OKRs? We've provided a simple primer that will teach you about this effective goal-setting framework. Learn about the basic, benefits, history, grading, implementation of OKRs.
This is the first SlideShare adaption of Timothy E. Johansson's 100 Growth Hacks in 100 Days. The growth hacks that's included in the slide are 1 to 10. Timothy is the front-end developer at UserApp (www.userapp.io).
We often optimize our software for performance, but what also optimizing our development teams for happiness? Take a look at how the tools you choose for your development team can impact developer happiness, and learn how to keep your teams happier and more productive.
*The graph on slide 3 is fabricated data, because studies also show that people are more likely to believe statements accompanied by scientific data.*
Getting Things Done (GTD) is a geek-friendly task (and life) management methodology by David Allen. This slide was used in my presentation at Barcamp Bangkok 4 (2010)
Comment accompagner la croissance des produits ?
Comment dérisquer simultanément la techno et le marché ?
Comment gérer un portefeuille de nouveaux produits ou services ?
Comment assurer l'industrialisation des produits par des équipes internes ?
Chez OCTO, nous avons expérimenté les process et les outils existants et nous les avons améliorés.
Nous avons réuni dans un kit tous les canevas que nous utilisons dans nos ateliers pour faire atterrir la création de nouveaux business dans les grands groupes.
On vous le partage avec plaisir
Fruit de plusieurs années de coaching OKR, nous vous proposons ce support pour définir, structurer et communiquer votre programme OKR au sein de votre organisation. Il vous aide à penser à tous les aspects de la mise en place des OKRs avant le déploiement.
Nous l’utilisons dans notre coaching comme support pour définir le programme OKR avec la direction; ainsi que comme support de communication pour le lancement du programme OKR auprès des équipes; enfin comme manuel de référence pour toute l’organisation.
Presentation of the OKRs AT THE CENTER book launch meetup 6th May 2020 together with Jeff Gothelf from Sense & Respond Press
More on: https://okrs-at-the-center.com/
How OKRs can drive ongoing change in your organization!
Changing the way you work with goals through concepts like OKRs has the potential to create important impulses for new ways of working in the whole organization. And yet many companies working with OKRs, fall short of their expectation.
In this interactive session, authors Natalija Hellesoe and Sonja Mewes will share
- how they themselves fell into the trap of high expectations
- which aha moments led to taking a different approach to work with OKRs
- and how proactive OKR System design and other ideas can help to successfully use OKRs
Objective and Key Result from *Measure What Matter* by John DoerrTaufik M. Aditama
*Measure What Matter* by John Doerr is a very amazing book to learn about OKR - an alternate to KPI methods, where i personally think are a more wonderful approach to create a more cohesive environment inside organizations. This slide include a small snippets of what exist in the book.
For every COO, CEO, or many other C-Level in small medium large business, or non-profit organizations, I recommend you to purchase this book through Amazon, or many other wonderful book purchasing platform existed.
OKRs - Practical tips for getting started from practical experience with doze...Tima Bouqdour
OKRs can and will transform your organisation when implemented properly, but many people are confused on how to get started and what pitfalls to avoid.
This presentation will give you an easy-to-understand introduction of things to consider, and our top tips, from experience gained implementing OKRs for thousands of people.
How leadership of employees via Objectives and Key Results (OKR) speeds up th...die.agilen GmbH
The major players in the industry - such as Google, LinkedIn, Zalando, Red Bull, Oracle & Co. - demonstrate it. In modern enterprises, a modern and contemporary framework is used for personnel management - OKR (Objectives & Key Results). Are goal management and "New Work" opposites? OKR combines
both! We explain the method and the framework in detail and show why it is so successful in times of digital transformation - even or especially at EDEKA.
DevOps is an increasingly useful tool for achieving business objectives, enabling your teams to work together to improve the efficiency and quality of software delivery. However, despite its growing popularity, there is still a lack of clarity over what DevOps actually means, how organizations should do it and what's the best way to get started.
DevOps 101 takes a brief look at the history of DevOps, why it started, what problems it is intended to solve and how you can start implementing it.
The slides were delivered by James Betteley, Head of Education at the DevOpsGuys in a one-hour webinar. The full recording is available here - https://youtu.be/4gC3WpbetKs?t=2s
James has spent the last few years neck-deep in the world of DevOps transformation, helping a wide range of organizations optimize the way they collaborate to deliver better software, faster. James was joined by Elizabeth Ayer, Portfolio Manager, from Redgate Software. Elizabeth looks after a range of Redgate products that help teams extend their DevOps practices to SQL Server databases.
For more information visit www.devopsguys.com and www.red-gate.com
This short deck introduces the key concepts of Objective and Key Results (OKR). OKR is a goal driven management process that thousands of top companies use to engage staff and deliver exceptional performance
“Things which matter most must never be at the mercy of things which matter least.”
― Johann Wolfgang von Goethe
This presentation gives some powerful time management tips that helps with prioritization. Importance of time management cannot be emphasized enough especially in the business world. Good time management skills enhances both personal and professional lives.
We often optimize our software for performance, but what also optimizing our development teams for happiness? Take a look at how the tools you choose for your development team can impact developer happiness, and learn how to keep your teams happier and more productive.
*The graph on slide 3 is fabricated data, because studies also show that people are more likely to believe statements accompanied by scientific data.*
Getting Things Done (GTD) is a geek-friendly task (and life) management methodology by David Allen. This slide was used in my presentation at Barcamp Bangkok 4 (2010)
Comment accompagner la croissance des produits ?
Comment dérisquer simultanément la techno et le marché ?
Comment gérer un portefeuille de nouveaux produits ou services ?
Comment assurer l'industrialisation des produits par des équipes internes ?
Chez OCTO, nous avons expérimenté les process et les outils existants et nous les avons améliorés.
Nous avons réuni dans un kit tous les canevas que nous utilisons dans nos ateliers pour faire atterrir la création de nouveaux business dans les grands groupes.
On vous le partage avec plaisir
Fruit de plusieurs années de coaching OKR, nous vous proposons ce support pour définir, structurer et communiquer votre programme OKR au sein de votre organisation. Il vous aide à penser à tous les aspects de la mise en place des OKRs avant le déploiement.
Nous l’utilisons dans notre coaching comme support pour définir le programme OKR avec la direction; ainsi que comme support de communication pour le lancement du programme OKR auprès des équipes; enfin comme manuel de référence pour toute l’organisation.
Presentation of the OKRs AT THE CENTER book launch meetup 6th May 2020 together with Jeff Gothelf from Sense & Respond Press
More on: https://okrs-at-the-center.com/
How OKRs can drive ongoing change in your organization!
Changing the way you work with goals through concepts like OKRs has the potential to create important impulses for new ways of working in the whole organization. And yet many companies working with OKRs, fall short of their expectation.
In this interactive session, authors Natalija Hellesoe and Sonja Mewes will share
- how they themselves fell into the trap of high expectations
- which aha moments led to taking a different approach to work with OKRs
- and how proactive OKR System design and other ideas can help to successfully use OKRs
Objective and Key Result from *Measure What Matter* by John DoerrTaufik M. Aditama
*Measure What Matter* by John Doerr is a very amazing book to learn about OKR - an alternate to KPI methods, where i personally think are a more wonderful approach to create a more cohesive environment inside organizations. This slide include a small snippets of what exist in the book.
For every COO, CEO, or many other C-Level in small medium large business, or non-profit organizations, I recommend you to purchase this book through Amazon, or many other wonderful book purchasing platform existed.
OKRs - Practical tips for getting started from practical experience with doze...Tima Bouqdour
OKRs can and will transform your organisation when implemented properly, but many people are confused on how to get started and what pitfalls to avoid.
This presentation will give you an easy-to-understand introduction of things to consider, and our top tips, from experience gained implementing OKRs for thousands of people.
How leadership of employees via Objectives and Key Results (OKR) speeds up th...die.agilen GmbH
The major players in the industry - such as Google, LinkedIn, Zalando, Red Bull, Oracle & Co. - demonstrate it. In modern enterprises, a modern and contemporary framework is used for personnel management - OKR (Objectives & Key Results). Are goal management and "New Work" opposites? OKR combines
both! We explain the method and the framework in detail and show why it is so successful in times of digital transformation - even or especially at EDEKA.
DevOps is an increasingly useful tool for achieving business objectives, enabling your teams to work together to improve the efficiency and quality of software delivery. However, despite its growing popularity, there is still a lack of clarity over what DevOps actually means, how organizations should do it and what's the best way to get started.
DevOps 101 takes a brief look at the history of DevOps, why it started, what problems it is intended to solve and how you can start implementing it.
The slides were delivered by James Betteley, Head of Education at the DevOpsGuys in a one-hour webinar. The full recording is available here - https://youtu.be/4gC3WpbetKs?t=2s
James has spent the last few years neck-deep in the world of DevOps transformation, helping a wide range of organizations optimize the way they collaborate to deliver better software, faster. James was joined by Elizabeth Ayer, Portfolio Manager, from Redgate Software. Elizabeth looks after a range of Redgate products that help teams extend their DevOps practices to SQL Server databases.
For more information visit www.devopsguys.com and www.red-gate.com
This short deck introduces the key concepts of Objective and Key Results (OKR). OKR is a goal driven management process that thousands of top companies use to engage staff and deliver exceptional performance
“Things which matter most must never be at the mercy of things which matter least.”
― Johann Wolfgang von Goethe
This presentation gives some powerful time management tips that helps with prioritization. Importance of time management cannot be emphasized enough especially in the business world. Good time management skills enhances both personal and professional lives.
Talk originally given at FISL 2012 in Porto Alegre, Brazil. Video was on YouTube but regrettably taken down. Fortunately, I gave a slightly updated (and frankly, tighter and better produced) version of this at the Liferay Symposium in the fall of 2012: https://www.youtube.com/watch?v=Pm8P4oCIY3g
Node.js is ready for the enterprise. This presentation covers the business state of Node and how larger, macro-trends are adding momentum to the adoption of Node.js in the enterprise.
Engineering leadership content on creating an aligned vision, building relationships, creating compelling reputations & achieving outstanding results.
Hitachi Data Systems - Best place to win!
My (very brief!) presentation at Interzone.io on March 11, 2015. A more in depth exploration of these ideas can be found at http://www.slideshare.net/bcantrill/docker-and-the-future-of-containers-in-production video: https://www.joyent.com/developers/videos/docker-and-the-future-of-containers-in-production
How to Run a Post-Mortem (With Humans, Not Robots), Velocity 2013Dan Milstein
Slides (with annotations) from a talk on post-mortems at Velocity CA, 2013.
This is an expanded version of my earlier slides, from the Lean Startup Conf.
Making your website accessible for users with disabilities isn’t flashy, but it’s necessary. Websites built for universal access benefit all users, not just users with a disability. They’re also more SEO friendly, and are generally built to be more user friendly. From generating increased revenue, to providing better access to services, the benefits of developing accessible websites are real and measurable.
The State of Georgia recently completed an Accessible Platform initiative, reviewing the templates and themes for our enterprise Drupal platform for accessibility gaps, and launching rolling improvements to the platform over several months to meet WCAG 2.0 (Level AA) compliance levels.
Accessibility doesn’t have to be an additional step in the web development process. Out of this initiative came a number of lessons learned on how code can be written to be accessible from the beginning, to mitigate the need for such cleanup efforts in the future. Building websites with accessibility in mind from the start saves time and money in the long haul. By following best practices for front end development, accessibility can be a seamless, invisible step in the build process.
Slides used at the lecture titled Leadership Styles Your Team Needs, as presented at the IGDA Leadership Forum in November 2010, by Joshua Howard.
Contact Joshua Howard at joshua@bonegames.com, and visit his blog on Leadership and Management at http://thereisnothem.wordpress.com.
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019Codemotion
What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?
What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?
Building a successful DevOps solution requires a holistic view of your development ecosystem plus solid technology that can support your organization today and in the future. Learn how to start defining your own successful DevOps solution and how to position Helix to be at the center of it all.
Scale at Reddit: Triple Your Team Size Without Losing ControlAtlassian
As of 2017, Reddit has 300 million monthly visitors, ranking #4 most visited website in US and #8 in the world. As you can guess, this kind of tremendous traffic takes some serious engineering efforts that have had to scale with the site's growing popularity. Join Nicholas Caldwell, VP of Engineering at Reddit as he discusses his engineering team's approach to agile development as they scaled from 40 to 120 engineers. He will walk you through their use of tools like Jira and Tableau, discuss meeting rhythms, and cover the must-have cultural elements of a successful team that work at every point of scale.
From Technical Debt to Technical HealthDeclan Whelan
Everyone agrees that technical debt is a burden on software innovation that we would rather avoid, and certainly clean up whenever possible. However, in most organizations, people don't prevent technical debt nearly as much as they should, and they don't ever get the time to clean it up. Why, then, if there are clear incentives to deal with technical debt, is it a rampant problem?
In this session, we will focus on how to deal with technical debt on several levels, including the individual developer, the team, the software value stream, and the larger organization. While technical debt may manifest itself in a developer's IDE, the problem starts long before the developer decides to copy and paste some code, or creates an overly-complex and under-documented class. The pressures on teams and individuals to take on more debt than they should come from many sources. Therefore, the solutions to the technical debt problem must extend beyond the team.
Perspectives on salesforce architecture Forcelandia talk 2017Steven Herod
My Forcelandia talk for 2017 on principles of Architecture, although specific to Salesforce. You can find the recording on Youtube: https://www.youtube.com/watch?v=ND-dX-__I1Y&t=7s
Tech Leads: What is it, do I want it and how to get thereYuval Kesten
What it means to be a Tech Lead and what it doesn’t. Why should someone aspire to become a Tech Lead and why not. What can you do in order to become a Tech Lead.
Similar to Leadership Without Management: Scaling Organizations by Scaling Engineers (20)
Talk given at the OCP Open System Firmware engineering workshop on 5/17/22. Talk was recorded; video at https://www.youtube.com/watch?v=eNI0wFgBNmY#t=7044s
Hardware/software Co-design: The Coming Golden Agebcantrill
Talk I gave as a keynote at RailsConf 2021. There is no Rails in the talk, though; this is all about the revolutions in open source firmware and hardware that are changing the way we build systems. Video to come!
Tockilator: Deducing Tock execution flows from Ibex Verilator tracesbcantrill
Talk given on March 20, 2020 at Oxidize 1K, a virtual conference that went from first idea to 300+ person conference in a week during the COVID-19 pandemic.
Platform values, Rust, and the implications for system softwarebcantrill
Talk given at Scale By The Bay 2018. Video is at https://www.youtube.com/watch?v=2wZ1pCpJUIM. If you are interested in this talk, you might also be interested in my talk on Platform as a Reflection of Values from Node Summit 2017: https://www.slideshare.net/bcantrill/platform-as-reflection-of-values-joyent-nodejs-and-beyond
My Papers We Love talk in San Francisco on October 12, 2017 on "ARC: A self-tuning, low overhead replacement cache." Video at https://www.youtube.com/watch?v=F8sZRBdmqc0
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
3. Scaling an engineering organization
• Adding an engineer to an organization has known drag:
• Life-related problems (illness, life events, etc.) will
grow linearly with people
• Communication- and organization-related problems
will grow non-linearly with people
• The drag is embodied in Brooks’s Law: Adding people to
a late software project only makes it later
• Most thinking around scaling an organization seems to
focus on reducing this drag — or coping with it
• But exclusively thinking along these lines only makes
sense if all software engineers are essentially equal!
4. Software engineers are not equal
• Software engineers are not equal; the best software
engineers are (at least) an order of magnitude more
productive than merely average engineers
• Steve McConnell (author of Code Complete) has
thoroughly researched this and calls it the “10X effect”
— but even this likely understates the multiplier
• While top software engineers are an order of magnitude
more productive, they do not induce any more
organizational drag that average engineers
• Software engineering organizations scale an order
of magnitude more effectively if they focus on
growing with only top performers
5. Exclusively top engineers?
• Can one build an engineering organization that consists
only of top engineers?
• May sound like an obvious aspiration, but many
organizations are not structured to do this: they either
don’t attract top engineers — or repel them outright
• What motivates superlative engineers?
• What demotivates them?
• How does one structure and operate an organization
that consists only of top engineers?
• And how does one find superlative engineers?
6. Motivators
• Above all else, engineers wish to make useful things
• The biggest single motivator for superlative engineers is
therefore mission — the “why” of an endeavor
• The other primary motivators are team and technical
problem — engineers are drawn to inspiring peers and
hard problems
• Assuming that engineers are compensated fairly,
compensation is nearly always less important than
mission, team and problem
• Compensation is important, but focusing exclusively on
compensation while neglecting the primary motivators
will attract only those with the wrong motivations!
7. Demotivators
• If the mission, team and problem are compelling (and
compensation is fair) top engineers will put up with an
astonishing amount of organizational nonsense...
• ...but there are demotivators that can become corrosive
with respect to mission, team and problem
• Many of these are structural — they can be avoided if
one is aware of them
• Ironically, engineering organizations seeking to “scale”
are at the greatest risk for creating the structures that
most profoundly demotivate software engineers!
8. Demotivator: Formalized annual review
• Feedback is essential, but formalized annual review is
the wrong kind of feedback and at the wrong cadence
• For top performers, this only serves to fixate on the
unchangeable aspects of personality (e.g. too shy/not
shy enough) instead of one’s technical achievements
• And because formalized review carries a heavy burden,
it often creates self-evaluation make-work for engineers,
serving not only to demotivate but also to waste time
• Not a radical opinion; annual performance review is one
of Deming’s Seven Deadly Diseases of Management!
9. Demotivator: Hierarchical titles
• With the rise of the “dual ladder” that allowed engineers
to advance without going into management, hierarchical
titles were invented to denote engineering rank
• e.g., “Member of technical staff” vs. “Staff engineer” vs.
“Senior staff engineer”
• But hierarchical titles create the N+1 Butt-head Problem:
people will naturally find the biggest butt-head at the
next higher rank, and be bummed out about them
• Title promotions of others are reviled (“why not me?”);
promotions of oneself are overdue (“about time!”)
• Hierarchical titles are not uplifting — they’re corrosive
10. Demotivator: Ranking
• Forces an absolute ordering of engineer performance,
with the “top” (~20%) rewarded, the “middle” (~70%)
ignored and the “bottom” (~10%) terminated
• Also known as “top grading” (Amazon), “stack
ranking” (Microsoft), “rank-and-yank” (GE), “ranking-
and-rating” (Intel) and — most gallingly — “individual
dignity entitlement” (Motorola)
• A team, organization or company tautologically cannot
have more than a set percentage of top performers!
• Self-fulfilling prophesy: if one has more than the set
percentage of top performers, the lower-ranked top
performers will do you the favor of leaving!
11. Demotivator: Ranking, cont.
• Ranking always starts harmlessly as an attempt to
“quantify” and “standardize” performance to be able to
allow a large organization to “level” compensation
• But quotas quickly arise as a part of organizational
jockeying: an organization won’t be permitted to have
exclusively top performers by its rivals
• Ranking creates the worst possible perverse incentives:
avoid working with talented engineers and be sure you
have some deadwood to throw into the lower ranks!
• Ranking is organizational cancer
12. Demotivator: Purple Robes Club
• It may become tempting to establish a select group of
engineers — often with adjectives like “distinguished” or
“principal” or nouns like “architect” or “fellow”
• This has all of the problems of ranking — but it’s even
worse if this group is actually technically empowered
• Having a select group hand down technical decisions is
tremendously demotivating to younger talent
• Standing “architectural review boards” are a variant of
this!
13. Demotivator: Non-technical management
• Non-technical management can’t resist channeling
Frederick Winslow Taylor: the fixation becomes on time-
management above all else...
• ...but those who have not developed software cannot
possibly appreciate the degree of unknown unknowns in
novel software development
• Non-technical management can never understand the
tradeoff that the unknowns imply: of functionality, quality
and schedule, one may generally pick only two!
• Non-technical management is a recipe for date-driven
death marches, where “everyone” knows the schedule is
unobtainable
14. Demotivator: Ex-technical management
• The most dangerous management is that which is
formerly technical
• They often retain the confidence of an engineer, but lose
the humility that is forced upon an engineer who must
get a complicated system to actually work
• This can happen remarkably quickly — there is a natural
bias to forget the horrors of software development
• While it must be done carefully, it is essential that those
in formalized leadership positions to continue to directly
contribute technically — if only to maintain empathy!
15. Demotivator: Inability to focus
• Especially when one has a team with many superlative
engineers, all of the world’s problems become tempting
• It can be difficult to maintain focus; tempting to say “yes”
to many different problems or opportunities
• But focus is not what you do — it’s what you don’t do (if
you haven’t yet, see Steve Jobs’ WWDC 1997 Keynote)
• Focus cannot be mere rhetoric; at both the individual
and organizational levels, must have the ability to say
“no” (or “later”)
16. Demotivator: Autocracy
• Recall that superlative engineers are motivated primarily
by mission — the “why” is essential
• Appeals to authority will fail; “because I said so” (and its
many variants) doesn’t actually work
• Present engineers with problems, not solutions — even
if those problems are organizational or economic
• When starting with the problem, a consensus-based
decision is nearly always possible among right-thinking
engineers...
17. Demotivator: Shilly-shallying
• … but decision making can become too consensus
based — there might not be consensus on some issues
• Right-thinking engineers fail to achieve consensus for
one of two reasons:
• The issue is small and boils down to personal style:
a decision either needs to be made, or different
styles need to be accommodated
• There is insufficient data on either side of an issue:
need to either gather more data, or pick a path that
forecloses the least number of options
• The one thing not to do: endless meetings!
18. Software engineering leadership
• The best software engineers — at every level of
experience and across personality types — are also
natural leaders
• Software engineering is an act of divining structure from
chaos to chart a path through the unknown: every line of
code is a business decision
• Recognizing that software engineers are natural leaders
changes the way we organize them
• One need not have middle management; a flat structure
with open communication and flexible teams allows
software engineers’ natural leadership to develop
19. Finding superlative engineers
• Three ways to find superlative engineers:
• The engineers that have worked with you or your
team in the past and are known to be good
• Talented, promising university graduates
• Individuals in the community who join or work on the
open source projects that your team leads
• None of these is deterministic; you should work on all
three fronts all the time
• Open source is your farm system; use it!
20. Further reading
• The Soul of a New Machine by Tracy Kidder
• The Rickover Effect: How One Man Made a Difference
by Theodore Rockwell
• Flight: My Life in Mission Control by Chris Kraft
• Skunk Works: A Personal Memoir of My Years of
Lockheed by Ben Rich
• Empires of Light: Edison, Tesla, Westinghouse, and the
Race to Electrify the World by Jill Jonnes