imperfections
The monotonous perfection
The mathematical physicist must simplify in order to get a manageable model, and although his concepts are of great beauty, they are austere in the extreme, and the more complicated crystal patterns observed by the metallurgist or geologist, being based on partly imperfect reality, often have a richer aesthetic content. Those who are concerned with structure on a super atomic scale find that there is more significance and interest in the imperfections in crystals than in the monotonous perfection of the crystal lattice itself.
The aesthetic potential of flaws
The archaeological quality of this section of exposed wall provides an example of the aesthetic potential of that which is flawed or broken.
A Painted Karatsu as Food for Thought
Recently there is a tendency to pursue distortion in art, but in the case of this jar, natural deformation has raised distortion to the level of spontaneous beauty.
The Japanese Perspective
An Essay from The Beauty of Everyday Things by Yanagi SōetsuGenerally speaking, the Western perception of art has its roots in Greece. For a long time its goal was perfection, which is particularly noticeable in Greek sculpture. This was in keeping with Western scientific thinking; there are no painters like Andrea Mantegna in the East. I am tempted to call such art ‘the art of even numbers’.
In contrast to this, what the Japanese eye sought was the beauty of imperfection, which I would call ‘the art of odd numbers’. No other country has pursued the art of imperfection as eagerly as Japan.
Is perfection boring?
An Article by Ralph AmmerWe love to see the process, not just the result. The imperfections in your work can be beautiful if they show your struggle for perfection, not a lack of care.
Product vs. Feature Teams
This article is certain to upset many people.
Empowered product teams
When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility
In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us.
However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap.
What went wrong?
If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong.
Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question.
And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question.