heat
Winter is by far the oldest of the seasons
...and we feel warm because it is cold out-of-doors.
Retained as a quality
Thermal information is not differentiated in our memory; rather it is retained as a quality, or underlying tone, associated with the whole experience of the place. It contributes to our sense of the particular personality, or spirit, that we identify with that place. In remembering the spirit of a place, we can anticipate that if we return, we will have the same sense of comfort or relaxation as before.
Two thermal archetypes
The hearth, a refuge of dry warmth from a cold world, and the oasis, a preserve of coolness and moisture in a desert wilderness.
The notion of a thermal optimum persists
There is an underlying assumption that the best thermal environment never needs to be noticed, and that once an objectively "comfortable" thermal environment has been provided, all of our thermal needs will have been met. The use of all of our extremely sophisticated environmental control systems is directed to this one end—to produce standard comfort zone conditions.
Warmed by the afternoon sun
Textbooks on water-system engineering state that supply mains are generally installed on the north side of the street in the Northern Hemisphere and on the south side in the Southern Hemisphere, so that the sun will warm them. In both hemispheres they are supposed to be on the east side of north-south streets, on the premise that the afternoon sun is warmer than the morning sun.
Predicted Mean Vote
A DefinitionThe predicted mean vote (PMV) was developed by Povl Ole Fanger at Kansas State University and the Technical University of Denmark as an empirical fit to the human sensation of thermal comfort. It was later adopted as an ISO standard. It predicts the average vote of a large group of people on the a seven-point thermal sensation scale where:
- +3 = hot
- +2 = warm
- +1 = slightly warm
- 0 = neutral
- -1 = slightly cool
- -2 = cool
- -3 = cold
A Q&A with Figma's VP of Product
Since we launched FigJam back in April, teams having been using it to grow all kinds of ideas into great designs. We recently caught up with Figma's VP of Product, Yuhki Yamashita, to hear what it was like to build FigJam and how things have changed since then. Here, he reflects on the evolving role of design and product management, what it means to welcome “non-designers” into the process, and the future of FigJam.
Stretching the product
When we’re thinking about where to take our product next, we actually take a lot of inspiration from our customers and the Figma Community, to see how they’re stretching our product in interesting or unexpected ways. We saw this happening in the early days of the pandemic. Our users were starting to use Figma for everything from brainstorming ideas to running team warm-up activities, to even putting on social events for people to get to know each other. We saw a lot of use cases that got us thinking.
Engineering, design, and product management
The boundary between engineering, design, and product management is blurring. Some of us used to have a mental model in which roles and responsibilities dictated how things work—that designers do one thing and engineers do another, for example. Increasingly, more people are crossing team lines to problem solve together...Now, it’s not about who “owns” what—it’s more of a collective endeavor. And the roles have become more interlocked, and I think that’s fundamentally a good thing.
Embracing the mess
Design is non-linear. At Figma, we often talk about “embracing the mess,” and that really means leaning into the chaos and complexity that makes the design process what it is. Even once you have the seedling of an idea, you need to explore and iterate, then pull back and evaluate to see what’s working and what’s not. Sometimes you’ll scrap an idea after a brainstorm session, and other times you’ll get pretty far with a concept, but still need different perspectives and input to move forward.