quality
It passes by the river
SAFe is oriented around volume, not value
To bring out its noblest qualities
We classify too much and enjoy too little
All the way to the last bolt
v0.crap
What excellence is
The aspiration for quality
Eating your own dog food
More profitable and a better buy
Maybe I should sharpen soon
You'll know it's there
Jobs's father had once taught him that a drive for perfection meant caring about the craftsmanship even of the parts unseen. Jobs applied that to the layout of the circuit board inside the Apple II. He rejected the initial design because the lines were not straight enough.
In an interview a few years later, after the Macintosh came out, Jobs again reiterated that lesson from his father: "When you're a carpenter making a beautiful chest of drawers, you're not going to use a piece of plywood on the back, even though it faces the wall and nobody will ever see it. You'll know it's there, so you're going to use a beautiful piece of wood on the back. For you to sleep well at night, the aesthetic, the quality, has to be carried all the way through."
Measured by the number of its features
A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality.
There is no kogin that can be called poor
Ensuring Excellence
An Article by Marty Cagan…in so many of the best product companies there is an additional dimension that goes beyond individual empowered product teams, and even goes beyond achieving business results.
It has to do with ensuring a level of what I’ll refer to here as “excellence” although that is clearly a very ambiguous term.
Over the years, this concept has been referred to by many different names, always necessarily vague, but all striving to convey the same thing: “desirability,” “aha moments,” “wow factor,” “magic experiences,” or “customer delight,” to list just a few.
The concept is that an effective product that achieves results is critical, but sometimes we want to go even beyond that, to provide something special.
Maybe it’s because we believe this is needed to achieve the necessary value. Maybe it’s because the company has built its brand on inspiring customers.
Often this dimension shows up most clearly in product design, where functional, usable but uninspiring designs can often achieve our business results, but great design can propel us into this realm of the inspiring.
Avant-Garde and Kitsch
An Essay by Clement GreenbergCapitalism in decline finds that whatever of quality it is still capable of producing becomes almost invariably a threat to its own existence.
Weinberg's Law
A Quote by Gerald WeinbergIf builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.
The value-destroying effect of arbitrary date pressure on code
An Article by Gandalf HudlowThe mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.
Minimum Awesome Product
An Article by Carlos BeneytoUsers are accustomed to a minimum of quality, and they expect that of all new products.
If our product does not [meet basic expectations of quality], people will automatically believe that it is a bad product and they will not take it seriously. It is not what they expect.
Hence my suggestion that the MVP has died and the MAP: Minimum Awesome Product was born.
What happens to user experience in a minimum viable product?
An Article by Ryan Singer"Feature complexity is like surface area and quality of execution is like height. I want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I'm committing to a baseline of effort on the user experience."
There’s a distinction to make: The set of features you choose to build is one thing. The level you choose to execute at is another. You can decide whether or not to include a feature like ‘reset password’. But if you decide to do it, you should live up to a basic standard of execution on the experience side.
Features can be different sizes with more or less complexity, but quality of experience should be constant across all features. That constant quality of experience is what gives your customers trust. It demonstrates to them that whatever you build, you build well.
Why YKK zippers are the brown M&Ms of product design
An Article by Josh CentersA ‘pro tip’ for evaluating the quality of a piece of gear is to look at the small details, such as zippers and stitching. Cheap-minded manufacturers will skimp on those details because most people just don’t notice, and even a cheap component will often last past a basic warranty period, so it’s an easy way to increase profits without losing sales or returns.
If a designer does bother to invest in quality components, that’s a tried-and-true sign that the overall product is better than the competition.
The McNamara fallacy
A DefinitionThe McNamara fallacy, named for Robert McNamara, the US Secretary of Defense from 1961 to 1968, involves making a decision based solely on quantitative observations (or metrics) and ignoring all others. The reason given is often that these other observations cannot be proven.
The fallacy refers to McNamara's belief as to what led the United States to defeat in the Vietnam War—specifically, his quantification of success in the war (e.g., in terms of enemy body count), ignoring other variables.
Artifice, blindness, and suicide
A QuoteThe first step is to measure whatever can be easily measured. This is OK as far as it goes. The second step is to disregard that which can't be easily measured or to give it an arbitrary quantitative value. This is artificial and misleading. The third step is to presume that what can't be measured easily really isn't important. This is blindness. The fourth step is to say that what can't be easily measured really doesn't exist. This is suicide.
Figma's Engineering Values: Craftsmanship
An ArticleCraftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users.
What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless.
The psychology of a discount
An Article by John MaedaFound on a wall.
The bitterness of poor quality remains long after the sweetness of low price is forgotten.
Managing Oneself
Only from strength
Most people think they know what they are good at. They are usually wrong. More often, people know what they are not good at—and even then more people are wrong than right. And yet, a person can perform only from strength. One cannot build performance on weaknesses, let alone on something one cannot do at all.
Feedback analysis
The only way to discover your strengths is through feedback analysis. Whenever you make a key decision or take a key action, write down what you expect will happen. Nine or 12 months later, compare the actual results with your expectations.
Taking pride in ignorance
First and foremost, concentrate on your strengths. Put yourself where your strengths can produce results.
Second, work on improving your strengths.
Third, discover where your intellectual arrogance is causing disabling ignorance and overcome it...First-rate engineers, for instance, tend to take pride in not knowing anything about people. Human resources professionals, by contrast, often pride themselves on their ignorance of elementary accounting or of quantitative methods altogether. But taking pride in such ignorance is self-defeating. Go to work on acquiring the skills and knowledge you need to fully realize your strengths.
But bulldozers move mountains
A planner may find that his beautiful plans fail because he does not follow through on them. Like so many brilliant people, he believes that ideas move mountains. But bulldozers move mountains; ideas show where the bulldozers should go to work.
Waste as little effort as possible on low competence
One should waste as little effort as possible on improving areas of low competence. It takes far more energy and work to improve from incompetence to mediocrity than it takes to improve from first-rate performance to excellence.
How do I perform?
For knowledge workers, How do I perform? may be an even more important question than What are my strengths?.
A few common personality traits usually determine how a person performs:
- Am I a reader or a listener?
- How do I learn? Writing? Taking notes? Doing? Talking?
- Do I work well with people, or am I a loner? And if I do work well with people, in what relationship?
- Do I produce results as a decision maker or as an adviser?
- Do I perform well under stress, or do I need a highly structured and predictable environment?
- Do I work best in a big organization or a small one?
To improve the way you perform
Do not try to change yourself—you are unlikely to succeed. But work hard to improve the way you perform. And try not to take on work you cannot perform or will only perform poorly.
The mirror test
In the early years of this century, the most highly respected diplomat of all the great powers was the german ambassador in London. He was clearly destined for great things...yet in 1906 he abruptly resigned rather than preside over a dinner given by the diplomatic corps for Edward VII. The king was a notorious womanizer and made it clear what kind of dinner he wanted. The ambassador is reported to have said, "I refuse to see a pimp in the mirror in the morning when I shave."
This is the mirror test. Ethics requires that you ask yourself, What kind of person do I want to see in the mirror in the morning?
Your organization's values
Organizations, like people, have values. To be effective in an organization, a person's values must be compatible with the organization's values. They do not need to be the same, but they must be close enough to coexist. Otherwise, the person will not only be frustrated but also will not produce results.
Values vs. strengths
There is sometimes a conflict between a person's values and his or her strengths. What one does well – even very well and successfully – may not fit with one's value system. In that case, the work may not appear to be worth devoting one's lift to (or even a substantial portion thereof).
Values are and should be the ultimate test.
Successful careers are not planned
Successful careers are not planned. They develop when people are prepared for opportunities because they know their strengths, their method of work, and their values. Knowing where one belongs can transform an ordinary person – hardworking and competent but otherwise mediocre – into an outstanding performer.
The best-laid plans
It is rarely possible – or even particularly fruitful – to look too far ahead. A plan can usually cover no more than 18 months and still be reasonably clear and specific. So the question is most cases should be, Where and how can I achieve results that will make a difference within the next year and a half?
The second half of your life
Today, most work is knowledge work, and knowledge workers are not "finished" after 40 years on the job, they are merely bored.
There are three ways to develop a second career. The first is to actually start one. The second is to develop a parallel career. Finally, there are the social entrepreneurs.
There is one prerequisite for managing the second half of your life: You must begin long before you enter it. If one does not begin to volunteer before one is 40 or so, one will not volunteer once past 60.