iconography
An icon is a symbol equally incomprehensible in all human languages
An icon is a symbol equally incomprehensible in all human languages. There's a reason why humans invented phonetic languages.
A universal correspondence
In 1923 Kandinsky proposed a universal correspondence between the three elementary shapes and the three primary colors: the dynamic triangle is inherently yellow, the static square is intrinsically red, and the serene circle is naturally blue.
The series ▲■● represents Kandinsky’s attempt to prove a universal correlation between color and geometry; it has become one of the most famous icons of the Bauhaus. Kandinsky conceived of these colors and shapes as a series of oppositions: yellow and blue represent the extremes of hot/cold, light/dark, and active/passive, while red is the intermediary between them. The triangle, square, and circle are graphic equivalents of the same polarities.
BeOS Icons
Rethinking Twitter Verification
An Article by Terence EdenThe main problem, I think, is that no one knows what "Verified" means.
If I were in charge (which I'm not) there would be various types of ticks.
🤖 is a bot
🆔 proved their legal identity
🏭 is run by a brand
⚖ is run by a government department
👮 Official law enforcement
😎 CelebrityAnd so on.
What happened when I stopped using Emojis
An Article by Clo S.In March 2021, I went through a fun self-imposed experiment: no emoji for 2 weeks. Not on social media, not in private messages, not even as Slack or Discord reactions. No emoticon either: the goal was to communicate without illustrations, only with words. I did a semi-rigorous (a.k.a. half-assed) diary study, taking notes on my feelings and behaviour.
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.