critique
A distinct and complementary stance
Scholars and critics
Starved for good journalism and criticism
Downsides of the internet
The McClusky Curve
The dying art of the hatchet job
An Article by Dorian LynskeyI find that the act of disagreeing with a sharp takedown sharpens my appreciation of the work in question. If I have to think a bit harder about what I like and why I like it, that’s fine by me, especially when it’s something that has been almost universally acclaimed.
...It’s not that I long for an epidemic of gleeful brutality but I will always cherish the right of critics to express their hate, hate, hate in the ultimate service of what they love, love, love.
Discourse in web design
An Essay by Jason Santa MariaA website is its own, singular thing. We know it isn’t a book, a TV show, a film, or a song, but our language is limited to talking about it in those restrictive boxes. A website is a mix of all of those things, and none of those things. It is influenced by place and time. A website changes with age. It can evolve and regress.
It was then I wondered if the problem wasn’t that web design lacked its own Emigré. What if we actually lacked a shared language to critically discuss web design? Art, architecture, and even graphic design, have critics and historians that give context to new work through the lenses of culture and important work from the past.
Design Discourse is in a State of Arrested Development
An Essay by Khoi Vinh[Designer News] is good, useful content, but most of it is written by designers themselves. Taken as a whole, it’s also a useful illustration of something vital that our industry lacks: balanced, insightful, independent writing that critically evaluates the profession.
One Designer's Response to Khoi Vinh's Complaint
An Article by Brandon DornThere is a place for discussing technique, for which forums like r/Design, Designer News, and the like are well suited. Yet expecting these platforms to provide insightful, serious critical discussion is like going to McDonald’s for an artisanal sandwich. Sure, they may advertise that, but that’s not really what you’re getting.
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.