Quotes About Outcomes

how we design our organization dictates how work is performed, and, therefore, the outcomes we achieve. Throughout

outcomes are what matter—not the process, not controls, or, for that matter, what work you complete.

Kanban boards are an ideal tool to create visibility, and visibility is a key component in properly recognizing and integrating Ops work into all the relevant value streams. When we do this well, we achieve market-oriented outcomes, regardless of how we've drawn our organization charts.

When we have long deployment lead times, heroics are required at almost every stage of the value stream. We may discover that nothing works at the end of the project when we merge all the development team's changes together, resulting in code that no longer builds correctly or passes any of our tests. Fixing each problem requires days or weeks of investigation to determine who broke the code and how it can be fixed, and still results in poor customer outcomes.

One of the most significant things they did to help change the outcomes of deployments was to have all Facebook engineers, engineering managers, and architects rotate through on-call duty for the services they built. By

Having developers share responsibility for the quality of the systems they build not only improves outcomes but also accelerates learning.

He continues, "Remember, outcomes are what matter—not the process, not controls, or, for that matter, what work you complete.

Maxine appreciates these reminders about their customers—when engineers think of "the customer" in the abstract instead of as a real person, you rarely get the right outcomes.

Our goal with a product-based funding model is to value the achievement of organizational and customer outcomes, such as revenue, customer lifetime value, or customer adoption rate, ideally with the minimum of output (e.g., amount of effort or time, lines of code). Contrast this to how projects are typically measured, such as whether it was completed within the promised budget, time, and scope.

The key thing we should care about is not the form, but the outcomes: deployments should be low-risk, push-button events we can perform on demand.

Furthermore, integrating the objectives of QA and Operations into everyone's daily work reduces firefighting, hardship, and toil, while making people more productive and increasing joy in the work we do. We not only improve outcomes, but our organization is better able to win in the marketplace.

Many psychologists assert that creating systems that cause feelings of powerlessness is one of the most damaging things we can do to fellow human beings—we deprive other people of their ability to control their own outcomes and even create a culture where people are afraid to do the right thing because of fear of punishment, failure, or jeopardizing their livelihood. This

Broadly speaking, to acheive DevOps outcomes, we need to reduce the effects of functional orientation ("optimizing for cost") and enable market orientation ("optimizing for speed") so we can have many small teams working safely and independently, quickly delivering value to the customer

Most people dont buy talent; they buy results.

Because of what you have done things will happen later which can't possibly be foreseen.

I long ago came to the conclusion that all life is six to five against.

Choices are the hinges of destiny.

Nations, like individuals, have to limit their objectives or take the consequences.

Trying to design the perfect plan is the perfect recipe for disappointment.

A battle that you win cancels any other bad action of yours. In the same way, by losing one, all the good things worked by you before become vain.

The United States can't dictate outcomes to a sovereign Iraq. But it can support, incentivize and mobilize those willing to move Iraq in the right direction.

Only thing that makes us fail in all moments, expectations.

There is asymmetry. Those who die do so very early in the game, while those who live go on living very long. Whenever there is asymmetry in outcomes, the average survival has nothing to do with the median survival.

considering that alternative outcomes could have taken place, that the world could have been different, is the core of probabilistic thinking.