And while this is certainly a positive thing in many ways, it puts us in a riskier position when it comes to communicating our work.

Why? Because the only thing more dangerous to a design system’s funding case than a lack of understanding of what it is, is a false understanding of what it is. Particularly when that false understanding is often built on a collection of common myths that have elbowed their way, without nuance, into the psyche of our organisations’ leaders. Myths like:

• 10x faster
• don't need a design system team
• design system eradicate duplication effort
• bake accessibility into components and the job is done

They have to be able to talk about us without us. What this phrase means, in its simplest form, is that you have to tell a story so clear, so concise, so memorable and evocative that people can repeat it for you even after you’ve left the room.

• ground it in your values
• start with the principle
• know what makes you unique: There can’t be platitudes or generalities or vague assertions as a core part of the message
• be evocative: avoid details and pick a small subset of the most emotionally gripping parts of your story. You'll have time to go in-depth later when people are interested.
• enemies become friends: in a business or commercial context, customers can berely keep straight the difference between two competitors. What do we have in common, because those folks might not have sworn allegiance, but but they may have chosen out of convenience.
• find joyce in repetition: a disciplined, collaborative, evocative message becomes a mantra for a community
• don't obsess over exact wording: as long as it's not a "telephone game", it's a win

A free open-source chat platform

On the pitfalls of "just doing things." In contrary there are often value in not making new things.

The hardest question you'll ever ask isn’t “How do I do more?” It’s “Why am I doing any of this in the first place?”

Stakeholders are just people and “I trust this person because they often get it right” is more powerful than any theory.

The long-term goal should always be making the system better, so that it can help you get things done rather than get in the way.

1. To start fixing your system by insisting on accountability (to avoid doers degrading it)
2. the system is made of people, and the people are exhausted. A reference to constant meeting and communication.

These are people problems, which can't be solved with technological solutions. Technologies can help and be part of a solution to a real-world problem but without basing it on the needs and experience of the people who are doing the actual work, your process will fail.

Avoid https://dontasktoask.com, https://giybf.com, https://lmgtfy.com, or similar sites. They have negative impacts on the receiver.

Prefer

1. Direct & kind guidance.
2. Explain "why"
3. "Gentle Nudge towards searching ("if appropriate")
4. Quote the rule or the guideline if applicable
5. Just be nicer

1. Keep things short and remove filler content
2. Don't ask for too much.
3. Presume people are busy.
4. If a request blocks you, you're asking too late.
5. Absolutely never make it personal.
6. Be descriptive and don't presume prior knowledge.

Examples are provided after these rules.

Vela dépend effectivement de la personne appelée. Je m'y retrouves https://blog.lyokolux.space/posts/21-09-01-chaque-generation-a-son-mode-de-communication-favori

3 feeds:

• no feed: a couple of static pages about the organization. They are great as a source of truth, for timeless content and for diving deep into a topic.
• slow feed: a blog, newsletter or magazine for medium to long form content. . They tend to be medium or long form content and allow deeper thought processes. Slow feeds only try to get our attention occasionally.
• fast feed: a page with smaller more frequent content pieces, that people can refresh, come back to or even subscribe via RSS or activity pub. Fast feeds are a powerful force that tends to pull people in.

Instead of asking: I’m hungry, let’s go to McDonald’s

Why not: I’m hungry, let’s go eat: McDonald’s?

A “no, because” statement instead of a plain “no” moves the problem from a blocker into an opportunity.

Personal opinion about why Nuxt is on Github:

codeberg is great! I love it.
but I think @github is a great home for us.
for me, the most important thing is community. I'm pragmatic about a lot of other things. while a fully open source stack is ideal, I'd rather have the people (+ network effects apply to code hosting too).

by Eric Steven Raymond

From a designer that ask for help. They design their prototypes on Figma.

Un système de communication basé sur les visuels au lieu de l'alphabet que nous connaissons.

Le Lovers Communication System est une langue construite internationale visuelle. Son but est d’être un pont universel entre les différentes langues du monde, un outil de communication rapide et efficace, permettant de discuter au facilement que deux amoureux le feraient.

J’ai appris qu’un produit beau avec des erreurs fonc­tionne mieux qu’un produit moche sans erreurs. [...] l’ex­pé­rience utili­sa­teur dans la mani­pu­la­tion des inter­faces était une vraie exper­tise qui faisait toute la diffé­rence. J’ai appris que l’adé­qua­tion aux besoins métier primait encore plus sur tout ça. J’ai appris qu’un produit qui répond parfai­te­ment au besoin avec une super expé­rience utili­sa­teur ne ferait pas le poids face à un produit qui a un bon marke­ting.

Ça veut dire que la qualité tech­nique est un outil et pas une fina­lité.

Expectations should be clear. This blog post clarify them: about communication, business websites, digital or electronic products, Clothing/Furniture/Hardware, Digital Producte.