Category: Blog

Your blog category

  • Alien: Earth’s Synopsis Already Has a Callback to James Cameron’s Aliens

    Alien: Earth’s Synopsis Already Has a Callback to James Cameron’s Aliens

    Anyone who has ever seen an Alien movie earlier will recall the majority of the first Alien: Earth teaser quite well. We watch a facehugger scramble through a ship with internal designs not dissimilar to [ …] due to the sounds of the warning klaxon that was so effective in the trailer for the 1978 original.

    The article Alien: Earth’s Synopsis Now Has a Callback to James Cameron’s Aliens appeared first on Den of Geek.

    In the new truck for Sinners, Ryan Coogler‘s first venture into the scary type, a worldly words warns,” There are traditions of individuals where the product of making music]is ] so true, it can create spirits from the past and the future. This product can lead to fame and fortune, but it also has the power to “pierce the mask between life and death.”

    For metaphysics and danger are essential for a story set in the South for anyone who is well-versed in the history of American songs. However, the demons are a new technology on the part of writer-director Coogler’s drama, which follows Michael B. Jordan in the dual functions of twin brothers trying to make ends meet in 1930s period Mississippi. Even so, as Coogler sees it, a monster fabric obviously translates to the rhythm and blues as well as how those noises were demonized hundreds of years ago when Jim Crow was the country’s supreme rules.

    ” The movie deals with American music, blues music,” Coogler asserts at a press conference that Den of Geek attended prior to Sinners ‘ trailer release. The director goes on to say that he is immediately stealing from the mythology surrounding well-known music players Tommy Johnson and Robert Johnson, who were rumored to have sold their souls to the Devil in Mississippi for the product of artistic skills despite having no connection to either of them. ( In actuality, Robert might have been so accused because he was one of the biggest names who dared to turn his back from playing church” spirituals” in favor of the profits of” secular”, godless music. )

    Says Coogler,” When you think about the vampire as it exists, it’s got an association or a counterpart in almost every culture. But it is the supernatural creature most associated with seduction, that’s most associated with choice. And that quality is especially present when blues music was also known as the Devil’s music. There’s a contrast between a secular lifestyle and]Christian morality]. The film is in conversation with all of those things, but the duality is always at its core.

    The seduction is clearly visible in the scenes we have seen of the movie. A smiling white faces ( including a devilish-looking JackO’Connell ) were revealed in a teaser over the weekend as they begged to be entered the brothers Elijah and Elias ( Jordan, both ). This obviously suggests the old vampire adage of being cautious of who you invite in. A similarly disturbing scene that was only broadcast to the press shows the negatives of exactly that: one of Elijah’s friends asks for an invitation after going off with those white devils.

    cnx. cmd. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    The film marks a chance for Coogler, who is on his fifth collaboration in as many films with Jordan, to dive into his influences and inspirations. The director claims that” the genre is for the popular consumers of film, but it’s also a genre that comes up when people ask about great pieces of art.” Horror itself has long been an interest for him. And I believe it is because the first tale told amid a fire was probably a horror story, which feels antiquated.

    And the horror campfire tales of, say, Robert Rodriguez and Quentin Tarantino’s From Dusk Till Dawn seem self-evident on Sinners. Even so, the director points out he is inspired just as much by Rodriguez’s The Faculty, as well as plenty of Coen Brothers with Inside Llewyn Davis and O Brother, Where Art Thou? specifically mentioned ( fitting given that the latter also features a devil at a crossroads and a hell of a guitar player ).

    The biggest influences, however, are intriguingly less cinematic than they are spiritually linked: one is among the more darkly amusing episodes of The Twilight Zone,” The Last Rites of Jeff Myrtlebank”, a yarn about a Southern man in 1920s Missouri returning from the dead after his own funeral, the other is a 1975 Stephen King novel also about vampires, Salem’s Lot.

    ” Salem’s Lot is about the town”, Coogler says,” and this movie is about this community”.

    Still, Coogler emphasizes the mixture of blues, vampirism, and Mississippi is hitting on a lot more than fictional reference points. In fact, it might very well be the most personal work in Coogler’s oeuvre.

    My maternal grandfather was from Mississippi, according to Coogler, and my uncle James, who passed away while I was finishing up Creed, was also from Mississippi. And my Uncle James and I both had wonderful relationships. And that relationship with my uncle was the beginning of it. He would constantly be listening to blues music. He would only discuss Mississippi while he was savoring the music. And he significantly impacted my life.

    It’s all intended to transport modern viewers to a bygone era and place by using a well-known form of entertainment like horror, with the vampires and the blood, and with glorious IMAX photography ( a genre first for the type of movies using 65mm IMAX cameras ).

    ” The film for me personally was a reclamation of a time period and a place that my family does n&#8217, t talk about much”, Coogler acknowledges, “because it &#8217, s a lot of feelings associated with our history. We go there, showing these people in their full … humanity.’” full of music and life.

    Sinners debuts on April 18th.

    The post Sinners: Ryan Coogler Is Tying Vampires to the Blues and ‘ Devil’s Music’ appeared first on Den of Geek.

  • Sinners: Ryan Coogler Is Tying Vampires to the Blues and ‘Devil’s Music’

    Sinners: Ryan Coogler Is Tying Vampires to the Blues and ‘Devil’s Music’

    In the new truck for Sinners, Ryan Coogler’s first venture into the scary type, a worldly words warns,” There are traditions of individuals where the product of making music]is ] so true, it can create spirits from the past and the future. This gift can bring fame and fortune, but it can also pierce the]… ]

    The article Sinners: Ryan Coogler Is Tying Demons to the Blue and ‘ Devil’s Audio’ appeared initially on Den of Geek.

    In the new trailer for Sinners, Ryan Coogler‘s first foray into the horror genre, a worldly voice warns”, There are legends of people where the gift of making music]is ] so true, it can conjure spirits from the past and the future. Although this product can win people over to fame and fortune, it can also help to break the smudge between life and death.

    For metaphysics and menace are a part and parcel of a story set in the South for anyone who is well-versed in the history of American music. However, the demons are a new technology on the part of writer-director Coogler’s drama, which follows Michael B. Jordan in the dual functions of twin brothers trying to make ends meet in 1930s period Mississippi. Even so, as Coogler sees it, a monster fabric obviously translates to something like the rhythm and blues, as well as how those noises were demonized hundreds of years ago when Jim Crow was the country’s supreme rules.

    The movie deals with blues music and American song, according to Coogler during a press conference that Den of Geek attended prior to Sinners ‘ video release. The director continues to draw inspiration from the mythology surrounding well-known music players Tommy Johnson and Robert Johnson, who were rumored to have sold their hearts to the Devil in Mississippi for the product of artistic skills despite having no connection to one another. ( In actuality, Robert might have been so accused because he was one of the biggest names who dared to turn his back from playing church” spirituals “in favor of the profits of” secular, “godless music. )

    Says Coogler”, When you think about the monster as it exists, it’s got an organization or a rival in almost every culture. But it is the divine thing most associated with romance, that’s most associated with decision. And that element is especially manifest when blues song was also known as the Devil’s music. There’s a comparison between a liberal attitude and]Christian morality]. The video has a lot of discussion with all of those items, but the paradox is always at the center.

    The film’s glaring flashes reveal a lot of that romance. As they begged to be entered a blues juke joint run by the brothers Elijah and Elias ( Jordan, both ), smiling white faces ( including a devilish-looking JackO’Connell ) were revealed in a teaser over the weekend. This naturally suggests the old monster adage,” Be wary of who you request in.” A similarly disturbing scene that was only broadcast to the media shows the negatives of precisely that: one of Elijah’s friends asks for an offer after going off with those bright devils.

    cnx. powershell. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    The video marks a chance for Coogler, who is on his second collaboration in as many movies with Jordan, to tumble into his influences and inspirations. The director said,” I think the genre is for the popular consumers of film, but it’s also a genre that comes up when people ask about great pieces of art,” and that Horror itself has long intrigued him. And I believe it because it feels very ancient, and that the first tale told amid a fire was probably a horror tale.

    And the horror campfire tales of, say, Robert Rodriguez and Quentin Tarantino’s From Dusk Till Dawn seem self-evident on Sinners. Even so, the director points out he is inspired just as much by Rodriguez’s The Faculty, as well as plenty of Coen Brothers with Inside Llewyn Davis and O Brother, Where Art Thou? specifically mentioned ( fitting given that the latter also features a devil at a crossroads and a hell of a guitar player ).

    The biggest influences, however, are intriguingly less cinematic than they are spiritually linked: one is among the more darkly amusing episodes of The Twilight Zone“, The Last Rites of Jeff Myrtlebank,” a yarn about a Southern man in 1920s Missouri returning from the dead after his own funeral, the other is a 1975 Stephen King novel also about vampires, Salem’s Lot.

    ” Salem’s Lot is about the town,” Coogler says”, and this movie is about this community.”

    Still, Coogler emphasizes the mixture of blues, vampirism, and Mississippi is hitting on a lot more than fictional reference points. In fact, it might very well be the most personal work in Coogler’s oeuvre.

    My maternal grandfather passed away before I was born, but I lived in the house he built after he moved to California. My uncle James also passed away while I was finishing up Creed. And I had the honor of having a very close relationship with my Uncle James. And that relationship with my uncle gave birth to the relationship. He would constantly be playing blues music. He would only discuss Mississippi while he was listening to that song. And he had a significant influence on my life.

    It’s all intended to transport modern viewers to a bygone era and place by using a well-known form of entertainment like horror, with the vampires and the blood, and with glorious IMAX photography ( a genre first for the type of movies using 65mm IMAX cameras ).

    ” The film for me personally was a reclamation of a time period and a place that my family does n&#8217, t talk about much,” Coogler acknowledges”, because it &#8217, s a lot of feelings associated with our history. We go there, showing these people in their full … humanity.’ ” Full of life and full of music.

    Sinners debuts on April 18th.

    The article Sinners: Ryan Coogler Is Tying Demons to the Blue and ‘ Devil’s Audio’ appeared initially on Den of Geek.

  • The Rings of Power Season 2 Viewership Data Isn’t Great News for the Show’s Five-Season Plan

    The Rings of Power Season 2 Viewership Data Isn’t Great News for the Show’s Five-Season Plan

    When it was released earlier this month, a fresh 2024 year-end statement from streaming analysis provider Luminate raised more than a few questions. The less-than-stellar data regarding major franchise streaming series that was released last year is one of its many revelations (via Deadline ). In terms of [ …] [ …], according to the report, all Marvel and Star Wars series performed poorly last year.

    The second post from Den of Geek: The Rings of Power Season 2 Popularity Data Isn’t Fantastic News for the Show’s Five-Season Plan appeared first.

    In the new truck for Sinners, Ryan Coogler‘s first venture into the scary type, a worldly words warns,” There are traditions of individuals where the product of making music]is ] so true, it can create spirits from the past and the future. Although this product is win people over to fame and fortune, it can also help to “pierce the veil between life and death.”

    For metaphysics and danger are essential for a story set in the South for anyone who is well-versed in the history of American songs. However, the demons are a new technology on the part of writer-director Coogler’s drama, which follows Michael B. Jordan in the dual functions of twin brothers trying to make ends meet in 1930s period Mississippi. Even so, as Coogler sees it, a monster fabric naturally lends itself to the rhythm and blues, as well as how those noises were demonized hundreds of years ago when Jim Crow was the law of the land.

    During a press conference that Den of Geek attended prior to the release of Sinners ‘ trailer, Coogler claims,” The movie deals with American music, blues music.” The director continues to draw inspiration from the mythology surrounding the well-known blues musicians Tommy Johnson and Robert Johnson, who were rumored to had sold their lives to the Devil in Mississippi for the product of artistic skills despite having no connection to either of them. ( In actuality, Robert might have been so accused because he was one of the biggest names who dared to turn his back from playing church” spirituals” in favor of the profits of” secular”, godless music. )

    Says Coogler,” When you think about the monster as it exists, it’s got an organization or a equivalent in almost every culture. But it is the divine thing most associated with romance, that’s most associated with decision. And that element is especially manifest when blues song was also known as the Devil’s music. There’s a distinction between a liberal life and]Christian morality]. The video is in conversation with all of those items, but the paradox is always at the center of it.

    The courtship is clearly visible in the scenes we have seen of the movie. A teaser over the weekend showed smiling white faces ( including a devil-looking JackO’Connell ) as they begged to be entered a blues juke joint operated by the brothers Elijah and Elias ( Jordan, both ). This naturally suggests the old monster adage,” Be wary of who you request in.” In addition, a disturbing scene that was only shown to the media recently exposes the negative aspects of exactly that when one of Elijah’s buddies comes back and also requests an offer after going off with those white devils.

    cnx. command. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    The video marks a chance for Coogler, who is on his second collaboration in as many movies with Jordan, to tumble into his forces and ideas. The director claims that the genre is” for the common users of film, but it’s also a type that comes up when people ask about excellent pieces of art.” And I believe it because it feels very antiquated; in fact, the first tale told amid a fire was probably a horror tale.

    And the horror campfire tales of, say, Robert Rodriguez and Quentin Tarantino’s From Dusk Till Dawn seem self-evident on Sinners. Even so, the director points out he is inspired just as much by Rodriguez’s The Faculty, as well as plenty of Coen Brothers with Inside Llewyn Davis and O Brother, Where Art Thou? specifically mentioned ( fitting given that the latter also features a crossroads devil and a hell of a guitar player ).

    The biggest influences, however, are intriguingly less cinematic than they are spiritually linked: one is among the more darkly amusing episodes of The Twilight Zone,” The Last Rites of Jeff Myrtlebank”, a yarn about a Southern man in 1920s Missouri returning from the dead after his own funeral, the other is a 1975 Stephen King novel also about vampires, Salem’s Lot.

    ” Salem’s Lot is about the town”, Coogler says,” and this movie is about this community”.

    Still, Coogler emphasizes the mixture of blues, vampirism, and Mississippi is hitting on a lot more than fictional reference points. In fact, it might very well be the most personal work in Coogler’s oeuvre.

    My maternal grandfather was from Mississippi, according to Coogler, and my uncle James, who passed away while I was finishing up Creed, was also from Mississippi. And I had the honor of having a very close relationship with my uncle James. And that relationship with my uncle was the start of it. He would constantly listen to blues music. He would only discuss Mississippi while he was savoring the music. And he significantly altered my life.

    It’s all intended to transport modern viewers into a bygone era and place by using a well-known form of entertainment like horror, with the vampires and the blood, and using glorious IMAX photography ( a genre first for the type of movies using 65mm IMAX cameras ).

    ” The film for me personally was a reclamation of a time period and a place that my family does n&#8217, t talk about much”, Coogler acknowledges, “because it &#8217, s a lot of feelings associated with our history. We go there, showing these people in their full … humanity.’” full of music and life.

    On April 18, Sinners will debut.

    The post Sinners: Ryan Coogler Is Tying Vampires to the Blues and ‘ Devil’s Music’ appeared first on Den of Geek.

  • Quentin Tarantino Is Right: Studios and Streamers Have Cheapened Movies

    Quentin Tarantino Is Right: Studios and Streamers Have Cheapened Movies

    We’ve been aware for a while that Quentin Tarantino has imposed a 10-movie cap on himself, claiming that he will leave after directing whatever may follow. However, Tarantino put a fresh spin on his oft-discussed concept while speaking with Elvis Mitchell, a writer and critic, at the Sundance Film Festival. He’s not working ]… ]

    The first article on Den of Geek was Quentin Tarantino Is Best: Studios and Streamers Have Cheapened Movies.

    In the new truck for Sinners, Ryan Coogler‘s first venture into the scary type, a worldly words warns,” There are traditions of individuals where the product of making music]is ] so true, it can create spirits from the past and the future. This product can lead to fame and fortune, but it also has the power to “pierce the mask between life and death.”

    For metaphysics and danger are essential for a story set in the South for anyone who is well-versed in the history of American songs. However, the demons are a new technology on the part of writer-director Coogler’s drama, which follows Michael B. Jordan in the dual functions of twin brothers trying to make ends meet in 1930s period Mississippi. Even so, as Coogler sees it, a monster thread naturally lends itself to the rhythm and blues, as well as how those noises were demonized hundreds of years ago when Jim Crow was the law of the land.

    During a press conference that Den of Geek attended prior to the release of Sinners ‘ trailer, Coogler claims,” The movie deals with American music, blues music.” The director continues to draw inspiration from the mythology surrounding well-known music players Tommy Johnson and Robert Johnson, who were rumored to have sold their hearts to the Devil in Mississippi for the product of artistic skills despite having no connection to one another. ( In actuality, Robert might have been so accused because he was one of the biggest names who dared to turn his back from playing church” spirituals” in favor of the profits of” secular”, godless music. )

    Says Coogler,” When you think about the monster as it exists, it’s got an organization or a rival in almost every culture. But it is the divine thing most associated with romance, that’s most associated with decision. And that quality is especially manifest when blues song was also known as the Devil’s music. There’s a comparison between a liberal attitude and]Christian morality]. The paradox is always at the center of the movie, which is why it is in conversation with all of those things.

    The romance is clearly visible in the scenes we have seen of the movie. As they begged to be entered a blues juke joint run by the brothers Elijah and Elias ( Jordan, both ), smiling white faces ( including a devilish-looking JackO’Connell ) were revealed in a teaser over the weekend. This naturally suggests the old monster adage,” Be wary of who you request in.” In addition, a disturbing scene that was only shown to the media recently exposes the negative aspects of exactly that when one of Elijah’s buddies comes back and also requests an offer after going off with those white devils.

    cnx. powershell. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    The video marks a chance for Coogler, who is on his second engagement in as many movies with Jordan, to tumble into his influences and inspirations. The director claims that” I think the genre is for the popular consumers of film, but it’s also a genre that comes up when people ask about great pieces of art.” Horror itself has long interested him. And I believe it because it feels very ancient; after all, the first tale told close to a fire was probably a horror tale.

    And the horror campfire tales of, say, Robert Rodriguez and Quentin Tarantino’s From Dusk Till Dawn seem self-evident on Sinners. Even so, the director points out he is inspired just as much by Rodriguez’s The Faculty, as well as plenty of Coen Brothers with Inside Llewyn Davis and O Brother, Where Art Thou? specifically mentioned ( fitting given that the latter also features a devil at a crossroads and a hell of a guitar player ).

    The biggest influences, however, are intriguingly less cinematic than they are spiritually linked: one is among the more darkly amusing episodes of The Twilight Zone,” The Last Rites of Jeff Myrtlebank”, a yarn about a Southern man in 1920s Missouri returning from the dead after his own funeral, the other is a 1975 Stephen King novel also about vampires, Salem’s Lot.

    ” Salem’s Lot is about the town”, Coogler says,” and this movie is about this community”.

    Still, Coogler emphasizes the mixture of blues, vampirism, and Mississippi is hitting on a lot more than fictional reference points. In fact, it might very well be the most personal work in Coogler’s oeuvre.

    My maternal grandfather was from Mississippi, according to Coogler, and my uncle James, who passed away while I was finishing up Creed, was also from Mississippi. And I had the honor of having a very close relationship with my Uncle James. And that relationship with my uncle was the start of it. He would constantly listen to blues music. He would only discuss Mississippi while he was savoring the music. And he significantly impacted my life.

    It’s all intended to transport modern viewers into a bygone era and place by using a well-known form of entertainment like horror, with the vampires and the blood, and using glorious IMAX photography ( a genre first for the type of movies using 65mm IMAX cameras ).

    ” The film for me personally was a reclamation of a time period and a place that my family does n&#8217, t talk about much”, Coogler acknowledges, “because it &#8217, s a lot of feelings associated with our history. We go there, showing these people in their full … humanity.’” full of music and life.

    On April 18, Sinners will debut.

    The post Sinners: Ryan Coogler Is Tying Vampires to the Blues and ‘ Devil’s Music’ appeared first on Den of Geek.

  • Obi-Wan Kenobi Almost Featured the Long-Awaited Return of a Star Wars Prequel Character

    Obi-Wan Kenobi Almost Featured the Long-Awaited Return of a Star Wars Prequel Character

    There are no shortage of stories about Natalie Portman’s potential gain to Star Wars. Fans seem to be more interested in seeing Portman duet her position as Padmé Amidala in […] then that Hayden Christensen and Ewan McGregor have returned as their Prequel time figures Anakin Skywalker and Obi-Wan Kenobi, both.

    Den of Geek first published a blog Obi-Wan Kenobi Nearly Featured the Long-Awaited Transfer of a Star Wars Prequel Character.

    In the new truck for Sinners, Ryan Coogler‘s first venture into the scary type, a worldly words warns,” There are traditions of individuals where the product of making music]is ] so true, it can create spirits from the past and the future. Although this product can win people over to fame and fortune, it can also help to “pierce the veil between life and death.”

    For spirituality and danger are essential to a story set in the South, according to anyone with a background in British music. However, the demons are a new technology on the part of writer-director Coogler’s drama, which follows Michael B. Jordan in the dual functions of twin brothers trying to make ends meet in 1930s period Mississippi. Even so, as Coogler sees it, a vampire yarn naturally translates to something like the rhythm and blues, as well as how those sounds were demonized hundreds of years ago when Jim Crow was the country’s supreme law.

    During a press conference that Den of Geek attended prior to the release of Sinners ‘ trailer, Coogler claims,” The film deals with American music, blues music.” The filmmaker continues to draw inspiration from the legends surrounding well-known blues musicians Tommy Johnson and Robert Johnson, who were rumored to have sold their souls to the Devil in Mississippi for the gift of musical talent despite having no connection to one another. ( In actuality, Robert might have been so accused because he was one of the biggest names who dared to turn his back from playing church” spirituals” in favor of the profits of” secular”, godless music. )

    Says Coogler,” When you think about the vampire as it exists, it’s got an association or a counterpart in almost every culture. But it is the supernatural creature most associated with seduction, that’s most associated with choice. And that quality is especially present when blues music was also known as the Devil’s music. There’s a contrast between a secular lifestyle and]Christian morality]. The film is in conversation with all of those things, but the duality is always at its core.

    The seduction is clearly visible in the scenes we have seen of the movie. A teaser over the weekend showed smiling white faces ( including a devil-looking JackO’Connell ) as they begged to be entered a blues juke joint operated by the brothers Elijah and Elias ( Jordan, both ). This obviously suggests the old vampire adage of being cautious of who you invite in. In addition, a disturbing scene that was only shown to the press recently exposes the negative aspects of exactly that when one of Elijah’s friends comes back and also requests an invitation after going off with those white devils.

    cnx. cmd. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    The film marks a chance for Coogler, who is on his fifth collaboration in as many films with Jordan, to dive into his influences and inspirations. The director claims that” I think the genre is for the popular consumers of film, but it’s also a genre that comes up when people ask about great pieces of art.” Horror itself has long interested him. And I believe it because it feels very ancient; after all, the first tale told close to a fire was probably a horror tale.

    And the horror campfire tales of, say, Robert Rodriguez and Quentin Tarantino’s From Dusk Till Dawn seem self-evident on Sinners. Even so, the director points out he is inspired just as much by Rodriguez’s The Faculty, as well as plenty of Coen Brothers with Inside Llewyn Davis and O Brother, Where Art Thou? specifically mentioned ( fitting given that the latter also features a devil at a crossroads and a hell of a guitar player ).

    The biggest influences, however, are intriguingly less cinematic than they are spiritually linked: one is among the more darkly amusing episodes of The Twilight Zone,” The Last Rites of Jeff Myrtlebank”, a yarn about a Southern man in 1920s Missouri returning from the dead after his own funeral, the other is a 1975 Stephen King novel also about vampires, Salem’s Lot.

    ” Salem’s Lot is about the town”, Coogler says,” and this movie is about this community”.

    Still, Coogler emphasizes the mixture of blues, vampirism, and Mississippi is hitting on a lot more than fictional reference points. In fact, it might very well be the most personal work in Coogler’s oeuvre.

    My maternal grandfather was from Mississippi, according to Coogler, and my uncle James, who passed away while I was finishing up Creed, was also from Mississippi. And my Uncle James and I both had wonderful relationships. And that relationship with my uncle was the beginning of it. He would constantly be listening to blues music. He would only discuss Mississippi while he was savoring the music. And he significantly impacted my life.

    It’s all intended to transport modern viewers into a bygone era and place by using a well-known form of entertainment like horror, with the vampires and the blood, and using glorious IMAX photography ( a genre first for the type of movies using 65mm IMAX cameras ).

    ” The film for me personally was a reclamation of a time period and a place that my family does n&#8217, t talk about much”, Coogler acknowledges, “because it &#8217, s a lot of feelings associated with our history. We go there, showing these people in their full … humanity.’” full of music and life.

    On April 18, Sinners will debut.

    The post Sinners: Ryan Coogler Is Tying Vampires to the Blues and ‘ Devil’s Music’ appeared first on Den of Geek.

  • Beware the Cut ‘n’ Paste Persona

    Beware the Cut ‘n’ Paste Persona

    This Person Does Not Exist is a website that uses a machine learning algorithm to create individual eyes. It takes actual photos and recombines them into false people faces. We just squirted past a LinkedIn post that claimed this site might be helpful “if you are developing a image and looking for a photo.”

    We concur that computer-generated eyes had make excellent personas, but not for the purpose you might think. Ironically, the website highlights the core issue of this very common design method: the person ( a ) does not exist. Personas are deliberately created, just like in the photos. Data is combined with natural environment to create a singular, unrealized preview.

    But strangely enough, manufacturers use personalities to encourage their style for the real world.

    A step up, identities

    Most manufacturers have at least once in their careers created, used, or encountered identities. In their content” Personas- A Plain Introduction”, the Interaction Design Foundation defines profile as “fictional characters, which you create based upon your study in order to reflect the unique user types that might use your service, product, site, or brand”. Personas typically consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a particular service/product, emotions, and motivations ( for example, see Creative Companion’s Persona Core Poster ). According to design firm Designit, the goal of personas is to “make the research relateable, ]and ] easy to communicate, digest, reference, and apply to product and service development.”

    The decontextualization of identities

    Personalities are well-known because they make “dry” research information more realistic and people. However, this approach places a cap on the study’s ability to analyze the data in a way that excludes the subjects from their particular contexts. As a result, personalities don’t describe important factors that make you know their decision-making method or allow you to connect to users ‘ thoughts and behavior, they lack stories. You are aware of the persona’s actions, but you lack the knowledge to know why. You end up with user images that are in reality less man.

    This “decontextualization” we see in identities happens in four way, which we’ll discuss below.

    People are assumed to be stable, according to individuals.

    Here’s a painfully obvious truth: people are not a fixed set of characteristics, despite the fact that many businesses still try to recruit and retain their employees and customers using outdated personality tests ( referring to you, Myers-Briggs ). You act, think, and feel different according to the situations you experience. You may behave helpful to some people and harshly to others because you come across as different from everyone. And you constantly refute the selections you’ve made.

    Modern psychology agree that while persons usually behave according to certain styles, it’s actually a combination of history and culture that determines how people act and take decisions. The type of person you are in each particular moment depends on the context, the impact of other people, your mood, and the whole history that led to the situation.

    Personas do not account for this variation in their attempt to reduce reality; instead, they present a consumer as a set of features. Like character testing, personas seize people away from real life. Even worse, individuals are labeled as” that kind of guy” with no means to practice their innate flexibility and are reduced to a brand. This behavior discredits variety, perpetuates stereotypes, and doesn’t reveal reality.

    Personas rely on people, not the environment

    You’re designing for a perspective, not an individual, in the real world. There are economic, political, and social factors to consider when a man lives in a home, a community, or an ecosystem. A pattern is not meant for a single customer. Instead, you create a product that is intended to be used by a certain number of people. But, personas don’t explicitly explain how a person feels about the environment, rather than show the user.

    Do you often make the same decision over and over again? Possibly you’ve made a commitment to veganism but still want to get some meat when your friends visit. Your decisions, including your behavior, opinions, and statements, are not only completely accurate but greatly contextual because they depend on a range of circumstances and variables. The image that “represents” you wouldn’t take into account this interdependence, because it doesn’t explain the grounds of your choices. It doesn’t give a rationale for your behavior. People practice the well-known attribution error, which states that they too often attribute others ‘ behavior to their personalities and not to the circumstances.

    As mentioned by the Interaction Design Foundation, identities are often placed in a situation that’s a” specific environment with a problem they want to or have to solve “—does that mean environment actually is considered? Unfortunately, what frequently occurs is that you choose a fictional character to handle a particular circumstance based on the fiction. How could you possibly understand how someone you want to represent behave in new circumstances if you hadn’t even fully investigated and understood the current context of the people you want to represent?

    Personas are meaningless averages

    A persona is depicted as a specific person but is not a real person, as stated in Shlomo Goltz’s introduction article on Smashing Magazine; rather, it is made up of observations from numerous people. The famous example of the USA Air Force designing planes based on the average of 140 of their pilots ‘ physical dimensions and not a single pilot actually fit within that average seat is a well-known criticism of this aspect of personas.

    The same limitation applies to mental aspects of people. Have you ever heard a famous person say something was taken out of context? I didn’t mean it that way when they used my words. The celebrity’s statement was reported literally, but the reporter failed to explain the context around the statement and didn’t describe the non-verbal expressions. The intended purpose was lost as a result. You do the same when you create personas: you collect someone’s statement ( or goal, or need, or emotion ), whose meaning can only be understood if you give its own particular context, and then report it as an isolated finding.

    But personas go a step further, extracting a decontextualized finding and joining it with another decontextualized finding from somebody else. The resultant set of findings frequently does not make sense because it is unclear or even contradictory because it lacks the underlying causes for and how that finding came about. It lacks any significance. And the persona doesn’t give you the full background of the person ( s ) to uncover this meaning: you would need to dive into the raw data for each single persona item to find it. What then is the persona’s usefulness?

    The validity of personas is deceiving.

    To a certain extent, designers realize that a persona is a lifeless average. Designers create “relatable” personas to make them appear like real people in order to overcome this. Nothing better captures the absurdity of this than a phrase from the Interaction Design Foundation:” Add a few fictional personal details to make the persona a realistic character.” In other words, you add non-realism in an attempt to create more realism. You purposefully understate the fact that” John Doe” is an abstract representation of research findings, but wouldn’t it be much more responsible to emphasize that John is only an abstraction? Let’s say something is artificial.

    It’s the finishing touch of a persona’s decontextualization: after having assumed that people’s personalities are fixed, dismissed the importance of their environment, and hidden meaning by joining isolated, non-generalizable findings, designers invent new context to create ( their own ) meaning. They introduce a number of biases in doing so, as with everything they produce. As Designit suggests, as designers, we can” contextualize]the persona” based on our experience and reality. We create connections that are familiar to us“. With each new detail added, this practice deviates from people’s actual reality, reinforces stereotypes, and doesn’t reflect real-world diversity.

    To conduct effective design research, we must report the actual situation and make it relatable for our audience, so that everyone can use their own empathy and develop their own interpretation and emotional response.

    Dynamic Selves: The alternative to personas

    What should we do instead if we shouldn’t use personas?

    Designit suggests using mindsets rather than personas. Each Mindset is a” spectrum of attitudes and emotional responses that different people have within the same context or life experience”. It challenges designers to avoid becoming fixated on just one person’s way of life. Unfortunately, despite being a step in the right direction, this proposal doesn’t consider that people are a part of a system that controls their behavior, personality, and, yes, mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. What determines a certain Mindset, is the question still unanswered.

    Margaret P., the author of the article” Kill Your Personas,” who has argued for the use of persona spectrums that include a range of user abilities, offers an alternative. For example, a visual impairment could be permanent ( blindness ), temporary ( recovery from eye surgery ), or situational (screen glare ). Because they are based on the idea that the context is the pattern, not the personality ,ersona spectrums are very useful for more inclusive and context-based design. However, their only drawback is that they have a very functional perspective on users that misses the relatability of a real person taken from within a spectrum.

    In developing an alternative to personas, we aim to transform the standard design process to be context-based. Contexts are generalizable and have patterns that we can recognize, just like we tried to do this with people before. How do we find these patterns, then? How do we ensure truly context-based design?

    Understand real people in a variety of settings

    Nothing about reality can be more relatable and inspiring. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. We refer to this method as Dynamic Selves.

    Let’s take a look at how the approach looks based on an illustration of how one of us used it in a recent study that examined Italians ‘ habits around energy consumption. We drafted a design research plan aimed at investigating people’s attitudes toward energy consumption and sustainable behavior, with a focus on smart thermostats.

    1. Select the appropriate sample.

    When we argue against personas, we’re often challenged with quotes such as” Where are you going to find a single person that encapsulates all the information from one of these advanced personas]? ]” You don’t need to, which is the simple answer. Your insights need not be extensive and meaningful, as you don’t need to know much about everyone.

    In qualitative research, validity does not derive from quantity but from accurate sampling. You pick the people who best fit the “population” you’re designing for. If this sample is chosen wisely and you have a deep understanding of the sampled people, you can infer how the rest of the population thinks and acts. There’s no need to study seven Susans and five Yuriys, one of each will do.

    In the same way, you don’t need to comprehend Susan in fifteen different ways. You have understood Susan’s plan of action once you have seen her in a few different settings. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations.

    It becomes clear why each person should be portrayed as an individual because each already represents an abstraction of a larger group of people in similar circumstances because each person is representative of a portion of the total population you’re researching. You don’t want to see abstractions of abstractions! These selected people need to be understood and shown in their full expression, remaining in their microcosmos—and if you want to identify patterns you can focus on identifying patterns in contexts.

    However, the question persists: how do you choose a representative sample? First, you must consider the target market for the product or service you are designing. It might be helpful to examine the company’s objectives and strategy, the current customer base, and/or a potential future target audience.

    In our example project, we were designing an application for those who own a smart thermostat. Everyone could have a smart thermostat in their home in the future. However, only early adopters currently own one. To build a significant sample, we needed to understand the reason why these early adopters became such. We then recruited by enticing customers to explain their needs and sources of purchase. There were those who had chosen to purchase it, those who had been influenced by others, and those who had discovered it in their homes. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants.

    2. Conduct your research

    After having chosen and recruited your sample, conduct your research using ethnographic methodologies. Your qualitative data will be enriched with examples and anecdotes thanks to this. Given COVID-19 restrictions, we turned an internal ethnographic research project into home-based remote family interviews that were followed by diary research in our example project.

    To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. Each interviewee would provide a story that would later become much more interesting and precise with the additions made by their spouses, partners, kids, or occasionally even pets. We also paid attention to the behaviors that came from having relationships with other important people ( such as coworkers or distant relatives ), as well as the relationships that came from those relationships. This wide research focus allowed us to shape a vivid mental image of dynamic situations with multiple actors.

    It’s crucial that the research’s scope remain broad enough to cover all potential actors. Therefore, it typically works best to define broad research areas with broad questions. Interviews are best set up in a semi-structured way, where follow-up questions will dive into topics mentioned spontaneously by the interviewee. This “plan to be surprised” will allow for the most enlightening findings. One of our participants responded to our question about how his family controlled the house temperature by saying,” My wife has not installed the thermostat’s app; she uses WhatsApp instead. If she wants to turn on the heater and she is not home, she will text me. I serve as her thermostat.

    3. Analysis: Create the Dynamic Selves

    You begin to represent each individual as a series of dynamic selves during the research analysis, each” Self” representing a particular context. A quote serves as the foundation of each Dynamic Self, which is supported by a photo and a few relevant demographics that serve as examples of the larger picture. The research findings themselves will show which demographics are relevant to show. In our case, the important demographics were family type, number and type of houses owned, economic status, and technological maturity because our research focused on families and their way of life to understand their needs for thermal regulation. We also included the individual’s name and age, but they’re optional; they’ll help the stakeholders transition from personas and allow them to connect multiple actions and contexts to the same person.

    To capture exact quotes, interviews need to be video-recorded and notes need to be taken verbatim as much as possible. This is crucial to the completeness of each participant’s various selves. Photos of the setting and anonymized actors are necessary to create realistic Selves in the case of real-life ethnographic research. Ideally, these photos should come directly from field research, but an evocative and representative image will work, too, as long as it’s realistic and depicts meaningful actions that you associate with your participants. One of our interviewees, for instance, shared a story of how he used to spend weekends with his family in his mountain home. We depicted him hiking with his young daughter as a result.

    At the end of the research analysis, we displayed all of the Selves ‘” cards” on a single canvas, categorized by activities. Each card featured a situation, which was indicated by a quote and a distinctive image. Each participant had a different deck full of self-assessments.

    4. Identify potential design challenges

    You will notice patterns beginning to appear once you have taken all of the main quotes from the interview transcripts and diaries and written them down as self-cards. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design.

    There was a particularly intriguing insight around the concept of humidity in our example project. We became aware of the importance of monitoring humidity for health and how a climate that is too dry or wet can cause respiratory problems or worsen already existing ones. This highlighted a big opportunity for our client to educate users on this concept and become a health advisor.

    Benefits of Dynamic Selves

    People are surrounded by changing environments, peculiar situations that people face, and the actions that follow when using the Dynamic Selves approach for research. In our thermostat project, we have come to know one of the participants, Davide, as a boyfriend, dog-lover, and tech enthusiast.

    Davide is a person we might have once consigned to the persona of a “tech enthusiast.” However, there are also those who are wealthy or poor, who are tech enthusiasts and have families or are single. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames.

    You can then generalize how Davide would act in a different situation once you have understood him in more detail and have fully grasped the underlying causes of his behavior for each circumstance. You can infer what he would think and do in the circumstances ( or scenarios ) you design for using your understanding of him.

    The Dynamic Selves approach aims to dismiss the conflicted dual purpose of personas—to summarize and empathize at the same time—by separating your research summary from the people you’re seeking to empathize with. This is crucial because scale affects how we feel empathy for people and how difficult it is to do so with other people. We have the deepest compassion for people with whom we can relate.

    If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more developing plot devices to “realize” the character, and no more need for additional bias. Simply put, this is how they are in real life. In fact, in our experience, personas quickly become nothing more than a name in our priority guides and prototype screens, as we all know that these characters don’t really exist.

    Another important benefit of Dynamic Selves is that it raises the stakes of your work: someone you and the team know and have met will experience the consequences if you violate your design. It might prompt you to perform daily design checks and may prevent you from taking shortcuts.

    And finally, real people in their specific contexts are a better basis for anecdotal storytelling and therefore are more effective in persuasion. Real research documentation is necessary to obtain this result. It reinforces your design arguments by adding more weight and urgency:” When I met Alessandra, the conditions of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. I’m worried that her life will become more complicated if we choose to use this functionality.

    Conclusion

    In their article on Mindsets, Designit mentioned that “design thinking tools offer a shortcut to deal with reality’s complexities, but this process of simplification can occasionally flatten out people’s lives into a few general characteristics.” Unfortunately, personas have been culprits in a crime of oversimplification. They fail to account for the complexity of the decision-making processes of our users and don’t take into account the contexts that humans are immersed in.

    Design needs to be simplified, but not to be a generalization. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Use those as metaphors for the person in all of their contexts. People and insights both come with a context, but they cannot be removed because it would detract from the context’s meaning.

    It’s high time for design to move away from fiction, and embrace reality—in its messy, surprising, and unquantifiable beauty—as our guide and inspiration.

  • Asynchronous Design Critique: Giving Feedback

    Asynchronous Design Critique: Giving Feedback

    Feedback, in whichever form it takes, and whatever it may be called, is one of the most effective soft skills that we have at our disposal to collaboratively get our designs to a better place while growing our own skills and perspectives.

    Feedback is also one of the most underestimated tools, and often by assuming that we’re already good at it, we settle, forgetting that it’s a skill that can be trained, grown, and improved. Poor feedback can create confusion in projects, bring down morale, and affect trust and team collaboration over the long term. Quality feedback can be a transformative force. 

    Practicing our skills is surely a good way to improve, but the learning gets even faster when it’s paired with a good foundation that channels and focuses the practice. What are some foundational aspects of giving good feedback? And how can feedback be adjusted for remote and distributed work environments? 

    On the web, we can identify a long tradition of asynchronous feedback: from the early days of open source, code was shared and discussed on mailing lists. Today, developers engage on pull requests, designers comment in their favorite design tools, project managers and scrum masters exchange ideas on tickets, and so on.

    Design critique is often the name used for a type of feedback that’s provided to make our work better, collaboratively. So it shares a lot of the principles with feedback in general, but it also has some differences.

    The content

    The foundation of every good critique is the feedback’s content, so that’s where we need to start. There are many models that you can use to shape your content. The one that I personally like best—because it’s clear and actionable—is this one from Lara Hogan.

    While this equation is generally used to give feedback to people, it also fits really well in a design critique because it ultimately answers some of the core questions that we work on: What? Where? Why? How? Imagine that you’re giving some feedback about some design work that spans multiple screens, like an onboarding flow: there are some pages shown, a flow blueprint, and an outline of the decisions made. You spot something that could be improved. If you keep the three elements of the equation in mind, you’ll have a mental model that can help you be more precise and effective.

    Here is a comment that could be given as a part of some feedback, and it might look reasonable at a first glance: it seems to superficially fulfill the elements in the equation. But does it?

    Not sure about the buttons’ styles and hierarchy—it feels off. Can you change them?

    Observation for design feedback doesn’t just mean pointing out which part of the interface your feedback refers to, but it also refers to offering a perspective that’s as specific as possible. Are you providing the user’s perspective? Your expert perspective? A business perspective? The project manager’s perspective? A first-time user’s perspective?

    When I see these two buttons, I expect one to go forward and one to go back.

    Impact is about the why. Just pointing out a UI element might sometimes be enough if the issue may be obvious, but more often than not, you should add an explanation of what you’re pointing out.

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow.

    The question approach is meant to provide open guidance by eliciting the critical thinking in the designer receiving the feedback. Notably, in Lara’s equation she provides a second approach: request, which instead provides guidance toward a specific solution. While that’s a viable option for feedback in general, for design critiques, in my experience, defaulting to the question approach usually reaches the best solutions because designers are generally more comfortable in being given an open space to explore.

    The difference between the two can be exemplified with, for the question approach:

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Would it make sense to unify them?

    Or, for the request approach:

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same pair of forward and back buttons.

    At this point in some situations, it might be useful to integrate with an extra why: why you consider the given suggestion to be better.

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.

    Choosing the question approach or the request approach can also at times be a matter of personal preference. A while ago, I was putting a lot of effort into improving my feedback: I did rounds of anonymous feedback, and I reviewed feedback with other people. After a few rounds of this work and a year later, I got a positive response: my feedback came across as effective and grounded. Until I changed teams. To my shock, my next round of feedback from one specific person wasn’t that great. The reason is that I had previously tried not to be prescriptive in my advice—because the people who I was previously working with preferred the open-ended question format over the request style of suggestions. But now in this other team, there was one person who instead preferred specific guidance. So I adapted my feedback for them to include requests.

    One comment that I heard come up a few times is that this kind of feedback is quite long, and it doesn’t seem very efficient. No… but also yes. Let’s explore both sides.

    No, this style of feedback is actually efficient because the length here is a byproduct of clarity, and spending time giving this kind of feedback can provide exactly enough information for a good fix. Also if we zoom out, it can reduce future back-and-forth conversations and misunderstandings, improving the overall efficiency and effectiveness of collaboration beyond the single comment. Imagine that in the example above the feedback were instead just, “Let’s make sure that all screens have the same two forward and back buttons.” The designer receiving this feedback wouldn’t have much to go by, so they might just apply the change. In later iterations, the interface might change or they might introduce new features—and maybe that change might not make sense anymore. Without the why, the designer might imagine that the change is about consistency… but what if it wasn’t? So there could now be an underlying concern that changing the buttons would be perceived as a regression.

    Yes, this style of feedback is not always efficient because the points in some comments don’t always need to be exhaustive, sometimes because certain changes may be obvious (“The font used doesn’t follow our guidelines”) and sometimes because the team may have a lot of internal knowledge such that some of the whys may be implied.

    So the equation above isn’t meant to suggest a strict template for feedback but a mnemonic to reflect and improve the practice. Even after years of active work on my critiques, I still from time to time go back to this formula and reflect on whether what I just wrote is effective.

    The tone

    Well-grounded content is the foundation of feedback, but that’s not really enough. The soft skills of the person who’s providing the critique can multiply the likelihood that the feedback will be well received and understood. Tone alone can make the difference between content that’s rejected or welcomed, and it’s been demonstrated that only positive feedback creates sustained change in people.

    Since our goal is to be understood and to have a positive working environment, tone is essential to work on. Over the years, I’ve tried to summarize the required soft skills in a formula that mirrors the one for content: the receptivity equation.

    Respectful feedback comes across as grounded, solid, and constructive. It’s the kind of feedback that, whether it’s positive or negative, is perceived as useful and fair.

    Timing refers to when the feedback happens. To-the-point feedback doesn’t have much hope of being well received if it’s given at the wrong time. Questioning the entire high-level information architecture of a new feature when it’s about to ship might still be relevant if that questioning highlights a major blocker that nobody saw, but it’s way more likely that those concerns will have to wait for a later rework. So in general, attune your feedback to the stage of the project. Early iteration? Late iteration? Polishing work in progress? These all have different needs. The right timing will make it more likely that your feedback will be well received.

    Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as radical candor. That means checking before we write to see whether what we have in mind will truly help the person and make the project better overall. This might be a hard reflection at times because maybe we don’t want to admit that we don’t really appreciate that person. Hopefully that’s not the case, but that can happen, and that’s okay. Acknowledging and owning that can help you make up for that: how would I write if I really cared about them? How can I avoid being passive aggressive? How can I be more constructive?

    Form is relevant especially in a diverse and cross-cultural work environments because having great content, perfect timing, and the right attitude might not come across if the way that we write creates misunderstandings. There might be many reasons for this: sometimes certain words might trigger specific reactions; sometimes nonnative speakers might not understand all the nuances of some sentences; sometimes our brains might just be different and we might perceive the world differently—neurodiversity must be taken into consideration. Whatever the reason, it’s important to review not just what we write but how.

    A few years back, I was asking for some feedback on how I give feedback. I received some good advice but also a comment that surprised me. They pointed out that when I wrote “Oh, […],” I made them feel stupid. That wasn’t my intent! I felt really bad, and I just realized that I provided feedback to them for months, and every time I might have made them feel stupid. I was horrified… but also thankful. I made a quick fix: I added “oh” in my list of replaced words (your choice between: macOS’s text replacement, aText, TextExpander, or others) so that when I typed “oh,” it was instantly deleted. 

    Something to highlight because it’s quite frequent—especially in teams that have a strong group spirit—is that people tend to beat around the bush. It’s important to remember here that a positive attitude doesn’t mean going light on the feedback—it just means that even when you provide hard, difficult, or challenging feedback, you do so in a way that’s respectful and constructive. The nicest thing that you can do for someone is to help them grow.

    We have a great advantage in giving feedback in written form: it can be reviewed by another person who isn’t directly involved, which can help to reduce or remove any bias that might be there. I found that the best, most insightful moments for me have happened when I’ve shared a comment and I’ve asked someone who I highly trusted, “How does this sound?,” “How can I do it better,” and even “How would you have written it?”—and I’ve learned a lot by seeing the two versions side by side.

    The format

    Asynchronous feedback also has a major inherent advantage: we can take more time to refine what we’ve written to make sure that it fulfills two main goals: the clarity of communication and the actionability of the suggestions.

    Let’s imagine that someone shared a design iteration for a project. You are reviewing it and leaving a comment. There are many ways to do this, and of course context matters, but let’s try to think about some elements that may be useful to consider.

    In terms of clarity, start by grounding the critique that you’re about to give by providing context. Specifically, this means describing where you’re coming from: do you have a deep knowledge of the project, or is this the first time that you’re seeing it? Are you coming from a high-level perspective, or are you figuring out the details? Are there regressions? Which user’s perspective are you taking when providing your feedback? Is the design iteration at a point where it would be okay to ship this, or are there major things that need to be addressed first?

    Providing context is helpful even if you’re sharing feedback within a team that already has some information on the project. And context is absolutely essential when giving cross-team feedback. If I were to review a design that might be indirectly related to my work, and if I had no knowledge about how the project arrived at that point, I would say so, highlighting my take as external.

    We often focus on the negatives, trying to outline all the things that could be done better. That’s of course important, but it’s just as important—if not more—to focus on the positives, especially if you saw progress from the previous iteration. This might seem superfluous, but it’s important to keep in mind that design is a discipline where there are hundreds of possible solutions for every problem. So pointing out that the design solution that was chosen is good and explaining why it’s good has two major benefits: it confirms that the approach taken was solid, and it helps to ground your negative feedback. In the longer term, sharing positive feedback can help prevent regressions on things that are going well because those things will have been highlighted as important. As a bonus, positive feedback can also help reduce impostor syndrome.

    There’s one powerful approach that combines both context and a focus on the positives: frame how the design is better than the status quo (compared to a previous iteration, competitors, or benchmarks) and why, and then on that foundation, you can add what could be improved. This is powerful because there’s a big difference between a critique that’s for a design that’s already in good shape and a critique that’s for a design that isn’t quite there yet.

    Another way that you can improve your feedback is to depersonalize the feedback: the comments should always be about the work, never about the person who made it. It’s “This button isn’t well aligned” versus “You haven’t aligned this button well.” This is very easy to change in your writing by reviewing it just before sending.

    In terms of actionability, one of the best approaches to help the designer who’s reading through your feedback is to split it into bullet points or paragraphs, which are easier to review and analyze one by one. For longer pieces of feedback, you might also consider splitting it into sections or even across multiple comments. Of course, adding screenshots or signifying markers of the specific part of the interface you’re referring to can also be especially useful.

    One approach that I’ve personally used effectively in some contexts is to enhance the bullet points with four markers using emojis. So a red square 🟥 means that it’s something that I consider blocking; a yellow diamond 🔶 is something that I can be convinced otherwise, but it seems to me that it should be changed; and a green circle 🟢 is a detailed, positive confirmation. I also use a blue spiral 🌀 for either something that I’m not sure about, an exploration, an open alternative, or just a note. But I’d use this approach only on teams where I’ve already established a good level of trust because if it happens that I have to deliver a lot of red squares, the impact could be quite demoralizing, and I’d reframe how I’d communicate that a bit.

    Let’s see how this would work by reusing the example that we used earlier as the first bullet point in this list:

    • 🔶 Navigation—When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.
    • 🟢 Overall—I think the page is solid, and this is good enough to be our release candidate for a version 1.0.
    • 🟢 Metrics—Good improvement in the buttons on the metrics area; the improved contrast and new focus style make them more accessible.
    •  🟥  Button Style—Using the green accent in this context creates the impression that it’s a positive action because green is usually perceived as a confirmation color. Do we need to explore a different color?
    • 🔶Tiles—Given the number of items on the page, and the overall page hierarchy, it seems to me that the tiles shouldn’t be using the Subtitle 1 style but the Subtitle 2 style. This will keep the visual hierarchy more consistent.
    • 🌀 Background—Using a light texture works well, but I wonder whether it adds too much noise in this kind of page. What is the thinking in using that?

    What about giving feedback directly in Figma or another design tool that allows in-place feedback? In general, I find these difficult to use because they hide discussions and they’re harder to track, but in the right context, they can be very effective. Just make sure that each of the comments is separate so that it’s easier to match each discussion to a single task, similar to the idea of splitting mentioned above.

    One final note: say the obvious. Sometimes we might feel that something is obviously good or obviously wrong, and so we don’t say it. Or sometimes we might have a doubt that we don’t express because the question might sound stupid. Say it—that’s okay. You might have to reword it a little bit to make the reader feel more comfortable, but don’t hold it back. Good feedback is transparent, even when it may be obvious.

    There’s another advantage of asynchronous feedback: written feedback automatically tracks decisions. Especially in large projects, “Why did we do this?” could be a question that pops up from time to time, and there’s nothing better than open, transparent discussions that can be reviewed at any time. For this reason, I recommend using software that saves these discussions, without hiding them once they are resolved. 

    Content, tone, and format. Each one of these subjects provides a useful model, but working to improve eight areas—observation, impact, question, timing, attitude, form, clarity, and actionability—is a lot of work to put in all at once. One effective approach is to take them one by one: first identify the area that you lack the most (either from your perspective or from feedback from others) and start there. Then the second, then the third, and so on. At first you’ll have to put in extra time for every piece of feedback that you give, but after a while, it’ll become second nature, and your impact on the work will multiply.

    Thanks to Brie Anne Demkiw and Mike Shelton for reviewing the first draft of this article.

  • That’s Not My Burnout

    That’s Not My Burnout

    Are you like me, reading about people fading away as they burn out, and feeling unable to relate? Do you feel like your feelings are invisible to the world because you’re experiencing burnout differently? When burnout starts to push down on us, our core comes through more. Beautiful, peaceful souls get quieter and fade into that distant and distracted burnout we’ve all read about. But some of us, those with fires always burning on the edges of our core, get hotter. In my heart I am fire. When I face burnout I double down, triple down, burning hotter and hotter to try to best the challenge. I don’t fade—I am engulfed in a zealous burnout

    So what on earth is a zealous burnout?

    Imagine a woman determined to do it all. She has two amazing children whom she, along with her husband who is also working remotely, is homeschooling during a pandemic. She has a demanding client load at work—all of whom she loves. She gets up early to get some movement in (or often catch up on work), does dinner prep as the kids are eating breakfast, and gets to work while positioning herself near “fourth grade” to listen in as she juggles clients, tasks, and budgets. Sound like a lot? Even with a supportive team both at home and at work, it is. 

    Sounds like this woman has too much on her plate and needs self-care. But no, she doesn’t have time for that. In fact, she starts to feel like she’s dropping balls. Not accomplishing enough. There’s not enough of her to be here and there; she is trying to divide her mind in two all the time, all day, every day. She starts to doubt herself. And as those feelings creep in more and more, her internal narrative becomes more and more critical.

    Suddenly she KNOWS what she needs to do! She should DO MORE. 

    This is a hard and dangerous cycle. Know why? Because once she doesn’t finish that new goal, that narrative will get worse. Suddenly she’s failing. She isn’t doing enough. SHE is not enough. She might fail, she might fail her family…so she’ll find more she should do. She doesn’t sleep as much, move as much, all in the efforts to do more. Caught in this cycle of trying to prove herself to herself, never reaching any goal. Never feeling “enough.” 

    So, yeah, that’s what zealous burnout looks like for me. It doesn’t happen overnight in some grand gesture but instead slowly builds over weeks and months. My burning out process looks like speeding up, not a person losing focus. I speed up and up and up…and then I just stop.

    I am the one who could

    It’s funny the things that shape us. Through the lens of childhood, I viewed the fears, struggles, and sacrifices of someone who had to make it all work without having enough. I was lucky that my mother was so resourceful and my father supportive; I never went without and even got an extra here or there. 

    Growing up, I did not feel shame when my mother paid with food stamps; in fact, I’d have likely taken on any debate on the topic, verbally eviscerating anyone who dared to criticize the disabled woman trying to make sure all our needs were met with so little. As a child, I watched the way the fear of not making those ends meet impacted people I love. As the non-disabled person in my home, I would take on many of the physical tasks because I was “the one who could” make our lives a little easier. I learned early to associate fears or uncertainty with putting more of myself into it—I am the one who can. I learned early that when something frightens me, I can double down and work harder to make it better. I can own the challenge. When people have seen this in me as an adult, I’ve been told I seem fearless, but make no mistake, I’m not. If I seem fearless, it’s because this behavior was forged from other people’s fears. 

    And here I am, more than 30 years later still feeling the urge to mindlessly push myself forward when faced with overwhelming tasks ahead of me, assuming that I am the one who can and therefore should. I find myself driven to prove that I can make things happen if I work longer hours, take on more responsibility, and do more

    I do not see people who struggle financially as failures, because I have seen how strong that tide can be—it pulls you along the way. I truly get that I have been privileged to be able to avoid many of the challenges that were present in my youth. That said, I am still “the one who can” who feels she should, so if I were faced with not having enough to make ends meet for my own family, I would see myself as having failed. Though I am supported and educated, most of this is due to good fortune. I will, however, allow myself the arrogance of saying I have been careful with my choices to have encouraged that luck. My identity stems from the idea that I am “the one who can” so therefore feel obligated to do the most. I can choose to stop, and with some quite literal cold water splashed in my face, I’ve made the choice to before. But that choosing to stop is not my go-to; I move forward, driven by a fear that is so a part of me that I barely notice it’s there until I’m feeling utterly worn away.

    So why all the history? You see, burnout is a fickle thing. I have heard and read a lot about burnout over the years. Burnout is real. Especially now, with COVID, many of us are balancing more than we ever have before—all at once! It’s hard, and the procrastinating, the avoidance, the shutting down impacts so many amazing professionals. There are important articles that relate to what I imagine must be the majority of people out there, but not me. That’s not what my burnout looks like.

    The dangerous invisibility of zealous burnout

    A lot of work environments see the extra hours, extra effort, and overall focused commitment as an asset (and sometimes that’s all it is). They see someone trying to rise to challenges, not someone stuck in their fear. Many well-meaning organizations have safeguards in place to protect their teams from burnout. But in cases like this, those alarms are not always tripped, and then when the inevitable stop comes, some members of the organization feel surprised and disappointed. And sometimes maybe even betrayed. 

    Parents—more so mothers, statistically speaking—are praised as being so on top of it all when they can work, be involved in the after-school activities, practice self-care in the form of diet and exercise, and still meet friends for coffee or wine. During COVID many of us have binged countless streaming episodes showing how it’s so hard for the female protagonist, but she is strong and funny and can do it. It’s a “very special episode” when she breaks down, cries in the bathroom, woefully admits she needs help, and just stops for a bit. Truth is, countless people are hiding their tears or are doom-scrolling to escape. We know that the media is a lie to amuse us, but often the perception that it’s what we should strive for has penetrated much of society.

    Women and burnout

    I love men. And though I don’t love every man (heads up, I don’t love every woman or nonbinary person either), I think there is a beautiful spectrum of individuals who represent that particular binary gender. 

    That said, women are still more often at risk of burnout than their male counterparts, especially in these COVID stressed times. Mothers in the workplace feel the pressure to do all the “mom” things while giving 110%. Mothers not in the workplace feel they need to do more to “justify” their lack of traditional employment. Women who are not mothers often feel the need to do even more because they don’t have that extra pressure at home. It’s vicious and systemic and so a part of our culture that we’re often not even aware of the enormity of the pressures we put on ourselves and each other. 

    And there are prices beyond happiness too. Harvard Health Publishing released a study a decade ago that “uncovered strong links between women’s job stress and cardiovascular disease.” The CDC noted, “Heart disease is the leading cause of death for women in the United States, killing 299,578 women in 2017—or about 1 in every 5 female deaths.” 

    This relationship between work stress and health, from what I have read, is more dangerous for women than it is for their non-female counterparts.

    But what if your burnout isn’t like that either?

    That might not be you either. After all, each of us is so different and how we respond to stressors is too. It’s part of what makes us human. Don’t stress what burnout looks like, just learn to recognize it in yourself. Here are a few questions I sometimes ask friends if I am concerned about them.

    Are you happy? This simple question should be the first thing you ask yourself. Chances are, even if you’re burning out doing all the things you love, as you approach burnout you’ll just stop taking as much joy from it all.

    Do you feel empowered to say no? I have observed in myself and others that when someone is burning out, they no longer feel they can say no to things. Even those who don’t “speed up” feel pressure to say yes to not disappoint the people around them.

    What are three things you’ve done for yourself? Another observance is that we all tend to stop doing things for ourselves. Anything from skipping showers and eating poorly to avoiding talking to friends. These can be red flags. 

    Are you making excuses? Many of us try to disregard feelings of burnout. Over and over I have heard, “It’s just crunch time,” “As soon as I do this one thing, it will all be better,” and “Well I should be able to handle this, so I’ll figure it out.” And it might really be crunch time, a single goal, and/or a skill set you need to learn. That happens—life happens. BUT if this doesn’t stop, be honest with yourself. If you’ve worked more 50-hour weeks since January than not, maybe it’s not crunch time—maybe it’s a bad situation that you’re burning out from.

    Do you have a plan to stop feeling this way? If something is truly temporary and you do need to just push through, then it has an exit route with a
    defined end.

    Take the time to listen to yourself as you would a friend. Be honest, allow yourself to be uncomfortable, and break the thought cycles that prevent you from healing. 

    So now what?

    What I just described is a different path to burnout, but it’s still burnout. There are well-established approaches to working through burnout:

    • Get enough sleep.
    • Eat healthy.
    • Work out.
    • Get outside.
    • Take a break.
    • Overall, practice self-care.

    Those are hard for me because they feel like more tasks. If I’m in the burnout cycle, doing any of the above for me feels like a waste. The narrative is that if I’m already failing, why would I take care of myself when I’m dropping all those other balls? People need me, right? 

    If you’re deep in the cycle, your inner voice might be pretty awful by now. If you need to, tell yourself you need to take care of the person your people depend on. If your roles are pushing you toward burnout, use them to help make healing easier by justifying the time spent working on you. 

    To help remind myself of the airline attendant message about putting the mask on yourself first, I have come up with a few things that I do when I start feeling myself going into a zealous burnout.

    Cook an elaborate meal for someone! 

    OK, I am a “food-focused” individual so cooking for someone is always my go-to. There are countless tales in my home of someone walking into the kitchen and turning right around and walking out when they noticed I was “chopping angrily.” But it’s more than that, and you should give it a try. Seriously. It’s the perfect go-to if you don’t feel worthy of taking time for yourself—do it for someone else. Most of us work in a digital world, so cooking can fill all of your senses and force you to be in the moment with all the ways you perceive the world. It can break you out of your head and help you gain a better perspective. In my house, I’ve been known to pick a place on the map and cook food that comes from wherever that is (thank you, Pinterest). I love cooking Indian food, as the smells are warm, the bread needs just enough kneading to keep my hands busy, and the process takes real attention for me because it’s not what I was brought up making. And in the end, we all win!

    Vent like a foul-mouthed fool

    Be careful with this one! 

    I have been making an effort to practice more gratitude over the past few years, and I recognize the true benefits of that. That said, sometimes you just gotta let it all out—even the ugly. Hell, I’m a big fan of not sugarcoating our lives, and that sometimes means that to get past the big pile of poop, you’re gonna wanna complain about it a bit. 

    When that is what’s needed, turn to a trusted friend and allow yourself some pure verbal diarrhea, saying all the things that are bothering you. You need to trust this friend not to judge, to see your pain, and, most importantly, to tell you to remove your cranium from your own rectal cavity. Seriously, it’s about getting a reality check here! One of the things I admire the most about my husband (though often after the fact) is his ability to break things down to their simplest. “We’re spending our lives together, of course you’re going to disappoint me from time to time, so get over it” has been his way of speaking his dedication, love, and acceptance of me—and I could not be more grateful. It also, of course, has meant that I needed to remove my head from that rectal cavity. So, again, usually those moments are appreciated in hindsight.

    Pick up a book! 

    There are many books out there that aren’t so much self-help as they are people just like you sharing their stories and how they’ve come to find greater balance. Maybe you’ll find something that speaks to you. Titles that have stood out to me include:

    • Thrive by Arianna Huffington
    • Tools of Titans by Tim Ferriss
    • Girl, Stop Apologizing by Rachel Hollis
    • Dare to Lead by Brené Brown

    Or, another tactic I love to employ is to read or listen to a book that has NOTHING to do with my work-life balance. I’ve read the following books and found they helped balance me out because my mind was pondering their interesting topics instead of running in circles:

    • The Drunken Botanist by Amy Stewart
    • Superlife by Darin Olien
    • A Brief History of Everyone Who Ever Lived by Adam Rutherford
    • Gaia’s Garden by Toby Hemenway 

    If you’re not into reading, pick up a topic on YouTube or choose a podcast to subscribe to. I’ve watched countless permaculture and gardening topics in addition to how to raise chickens and ducks. For the record, I do not have a particularly large food garden, nor do I own livestock of any kind…yet. I just find the topic interesting, and it has nothing to do with any aspect of my life that needs anything from me.

    Forgive yourself 

    You are never going to be perfect—hell, it would be boring if you were. It’s OK to be broken and flawed. It’s human to be tired and sad and worried. It’s OK to not do it all. It’s scary to be imperfect, but you cannot be brave if nothing were scary.

    This last one is the most important: allow yourself permission to NOT do it all. You never promised to be everything to everyone at all times. We are more powerful than the fears that drive us. 

    This is hard. It is hard for me. It’s what’s driven me to write this—that it’s OK to stop. It’s OK that your unhealthy habit that might even benefit those around you needs to end. You can still be successful in life.

    I recently read that we are all writing our eulogy in how we live. Knowing that your professional accomplishments won’t be mentioned in that speech, what will yours say? What do you want it to say? 

    Look, I get that none of these ideas will “fix it,” and that’s not their purpose. None of us are in control of our surroundings, only how we respond to them. These suggestions are to help stop the spiral effect so that you are empowered to address the underlying issues and choose your response. They are things that work for me most of the time. Maybe they’ll work for you.

    Does this sound familiar? 

    If this sounds familiar, it’s not just you. Don’t let your negative self-talk tell you that you “even burn out wrong.” It’s not wrong. Even if rooted in fear like my own drivers, I believe that this need to do more comes from a place of love, determination, motivation, and other wonderful attributes that make you the amazing person you are. We’re going to be OK, ya know. The lives that unfold before us might never look like that story in our head—that idea of “perfect” or “done” we’re looking for, but that’s OK. Really, when we stop and look around, usually the only eyes that judge us are in the mirror. 

    Do you remember that Winnie the Pooh sketch that had Pooh eat so much at Rabbit’s house that his buttocks couldn’t fit through the door? Well, I already associate a lot with Rabbit, so it came as no surprise when he abruptly declared that this was unacceptable. But do you recall what happened next? He put a shelf across poor Pooh’s ankles and decorations on his back, and made the best of the big butt in his kitchen. 

    At the end of the day we are resourceful and know that we are able to push ourselves if we need to—even when we are tired to our core or have a big butt of fluff ‘n’ stuff in our room. None of us has to be afraid, as we can manage any obstacle put in front of us. And maybe that means we will need to redefine success to allow space for being uncomfortably human, but that doesn’t really sound so bad either. 

    So, wherever you are right now, please breathe. Do what you need to do to get out of your head. Forgive and take care.

  • Asynchronous Design Critique: Getting Feedback

    Asynchronous Design Critique: Getting Feedback

    ” Any feedback?” is perhaps one of the worst ways to ask for suggestions. It’s obscure and unfocused, and it doesn’t give a clear picture of what we’re looking for. Great comments begins sooner than we might anticipate: it begins with the demand.

    It might seem contradictory to start the process of receiving feedback with a problem, but that makes sense if we realize that getting feedback can be thought of as a form of design study. The best way to ask for feedback is to write down some insightful questions, just like we wouldn’t do any research without the correct questions to obtain the insight we need.

    Design analysis is not a one-time procedure. Sure, any great comments process continues until the project is finished, but this is especially true for layout because architecture work continues iteration after iteration, from a high level to the finest details. Each stage requires its unique set of questions.

    Lastly, we need to review what we received, get to the heart of its conclusions, and take action, like with any great exploration. Problem, generation, and evaluation. Let’s take a closer look at each of those.

    The query

    Being available to input is important, but we need to be specific about what we’re looking for. Any comments,” What do you think,” or” I’d love to hear your mind” at the end of a presentation are likely to garner a lot of different ideas, or worse, to make people follow the lead of the first speaker. And finally, we become irritated because ambiguous queries like those can result in people leaving reviews that don’t even consider keys. Which might be a savory matter, so it might be hard at that point to divert the crew to the topics that you had wanted to focus on.

    How do we enter this circumstance, though? A number of elements are involved. One is that we don’t often consider asking as a part of the input method. Another is how healthy it is to assume that everyone else will agree with the problem and leave it alone. Another is that there are frequently no need to be that exact in nonprofessional dialogues. In short, we tend to underestimate the importance of the concerns, so we don’t work on improving them.

    The work of asking insightful questions guidelines and concentrates the criticism. It also serves as a form of acceptance, outlining your willingness to make comments and the types of responses you want to receive. It puts people in the right emotional state, especially in situations when they weren’t expecting to give opinions.

    There isn’t a second best method to request suggestions. It only needs to be certain, which can take many forms. A design for design critique that I’ve found especially helpful in my training is the one of stage over depth.

    The term” period” refers to each stage of the process, specifically the design phase. The kind of feedback changes as the customer research moves forward to the final design. But within a single stage, one might also examine whether some assumptions are correct and whether there’s been a suitable language of the amassed input into updated designs as the job has evolved. The levels of customer experience may serve as a starting point for future inquiries. What do you want to learn about job goals? User requirements? Funnality? Articles? Contact design? Data structures Interface style Navigation style? physical architecture packaging?

    Here’re a some example questions that are specific and to the place that refer to different levels:

    • Features: Is it appealing to automate accounts creation?
    • Interaction style: Take a look at the updated flowing and let me know if there are any steps or error states I may have missed.
    • Information infrastructure: We have two competing bits of information on this site. Does the construction work to effectively communicate both of them?
    • User interface design: What do you think about the problem desk at the top of the page, which makes sure you see the following error even if it is outside the viewport?
    • Navigation style: From study, we identified these second-level routing items, but when you’re on the webpage, the list feels overly long and hard to understand. Are there any ways to deal with this?
    • The bottom-right corner’s slippery messages are clearly visible, but are they sufficient?

    The other plane of sensitivity is about how heavy you’d like to go on what’s being presented. For instance, we may have introduced a new end-to-end stream, but you might want to know more about a particular viewpoint you found challenging. This can be particularly helpful from one generation to the next when it’s crucial to identify the areas that have changed.

    There are other things that we can consider when we want to accomplish more specific—and more effective—questions.

    A quick fix is to get rid of the common qualifiers from issues like “good”, “well,” “nice,” “bad,” “okay,” and” cool.” Asking,” When the prevent opens and the switches appear, is this conversation great, for instance?” may seem precise, but you can place the “good” tournament, and transfer it to an even better query:” When the wall opens and the buttons appear, is it clear what the next action is”?

    Sometimes, we do need a lot of feedback. Although that is uncommon, it is possible. In that sense, you might still make it explicit that you’re looking for a wide range of opinions, whether at a high level or with details. Or perhaps just say,” At first glance, what do you think”? so that after someone’s first five seconds of viewing it, it becomes obvious that what you’re asking is open ended but focused on the subject.

    Sometimes the project is particularly expansive, and some areas may have already been explored in detail. In these circumstances, it might be helpful to state explicitly that some parts are already locked in and aren’t accessible for feedback. Although it’s not something I’d recommend in general, I’ve found it helpful in avoiding getting back into rabbit holes like those that could lead to further refinement but aren’t currently what matters most.

    Asking specific questions can completely change the quality of the feedback that you receive. People with less refined criticism will now be able to provide more actionable feedback, and even expert designers will appreciate the clarity and effectiveness gained from concentrating solely on what’s needed. It can save a lot of time and frustration.

    The iteration

    Design iterations are probably the most recognizable component of the design process, and they act as a natural feedback loop. Many design tools have inline commenting, but many of them only display changes as a single fluid stream in the same file. These types of design tools cause conversations to end after they are resolved, update shared UI components automatically, and require designers to always display the most recent version unless these would-be useful features were manually disabled. The implied goal that these design tools seem to have is to arrive at just one final copy with all discussions closed, probably because they inherited patterns from how written documents are collaboratively edited. That approach to design critiques is probably not the best approach, but some teams might benefit from it even if I don’t want to be too prescriptive.

    Create explicit checkpoints for discussion is the asynchronous design-critique strategy that I believe works the best. I’m going to use the term iteration post for this. It refers to a design iteration write-up or presentation followed by some sort of discussion thread. This can be used on any platform that can accommodate this structure. By the way, when I refer to a “write-up or presentation“, I’m including video recordings or other media too: as long as it’s asynchronous, it works.

    Using iteration posts has a number of benefits:

      The layouter can review the feedback from each iteration and get ready for the next one by creating a rhythm in the design work.
    • It makes decisions visible for future review, and conversations are likewise always available.
    • It keeps track of how the design evolved over time.
    • Depending on the tool, it might also make it simpler to collect and act on feedback.

    These posts of course don’t mean that no other feedback approach should be used, just that iteration posts could be the primary rhythm for a remote design team to use. And from there, there can develop additional feedback techniques ( such as live critique, pair designing, or inline comments ).

    There isn’t, in my opinion, a universal format for iteration posts. But there are a few high-level elements that make sense to include as a baseline:

    1. The objective is to achieve
    2. The layout
    3. The list of changes
    4. The querys

    A goal for each project is likely to be one that has already been condensed into a single sentence, such as the request for the project owner, the product manager, or the client brief. So this is something that I’d repeat in every iteration post—literally copy and pasting it. To avoid having to search through information from multiple posts, the goal is to provide context and repeat what is necessary to complete each iteration post. The most recent iteration post will have everything I need if I want to know about the most recent design.

    This copy-and-paste part introduces another relevant concept: alignment comes from repetition. Therefore, repeating information in posts helps to ensure that everyone is on the same page.

    The actual series of information-architecture outlines, diagrams, flows, maps, wireframes, screens, visuals, and any other design work that has been done is what is then called the design. In short, it’s any design artifact. In the work’s final stages, I prefer to use the term “blank” to emphasize that I’ll be displaying complete flows rather than individual screens to facilitate comprehension of the larger picture.

    Because it makes it easier to refer to the objects, it might also be helpful to have clear names on them. Write the post in a way that helps people understand the work. It’s not much different from creating a strong live presentation.

    A bullet list of the changes made in the previous iteration should also be included for a successful discussion so that attendees can concentrate on what’s changed. This is especially useful for larger works of work where keeping track, iteration after iteration, might prove difficult.

    And finally, as noted earlier, it’s essential that you include a list of the questions to drive the design critique in the direction you want. Creating a numbered list of questions can also make it simpler to refer to each one by its number.

    Not every iteration is the same. Earlier iterations don’t need to be as tightly focused—they can be more exploratory and experimental, maybe even breaking some of the design-language guidelines to see what’s possible. Then, later, the iterations begin coming to a decision and improving it until the feature development is complete.

    Even if these iteration posts are written and intended as checkpoints, I want to point out that they are not by any means required to be exhaustive. A post might be a draft—just a concept to get a conversation going—or it could be a cumulative list of each feature that was added over the course of each iteration until the full picture is done.

    I also started using particular labels for incremental iterations over time, such as i1, i2, i3, and so on. Although this may seem like a minor labeling tip, it can be useful in many ways:

    • Unique—It’s a clear unique marker. Everyone knows where to go to review things, and it’s simple to say” This was discussed in i4″ with each project.
    • Unassuming—It functions like versions ( such as v1, v2, and v3 ), but versions give the impression of something that is large, exhaustive, and complete. Iterations must be able to be exploratory, incomplete, partial.
    • Future proof—It resolves the “final” naming issue that versions can encounter. No more files with the title “final final complete no-really-its-done” Within each project, the largest number always represents the latest iteration.

    The wording release candidate (RC ) could be used to indicate when a design is finished enough to be worked on, even if there are some areas that still need improvement and, in turn, require more iterations, such as” with i8 we reached RC” or “i12 is an RC” to indicate when it is finished.

    The evaluation

    What usually happens during a design critique is an open discussion, with a back and forth between people that can be very productive. This strategy is particularly successful when synchronous feedback is being received live. However, using a different approach when we work asynchronously is more effective: adopting a user-research mindset. Written feedback from teammates, stakeholders, or others can be treated as if it were the result of user interviews and surveys, and we can analyze it accordingly.

    Asynchronous feedback is particularly effective because of this shift, especially around these friction points:

      It lessens the need to respond to everyone.
    1. It reduces the frustration from swoop-by comments.
    2. It lessens our own worth.

    The first friction point is having to press yourself to respond to each and every comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s simple, and there isn’t much to worry about. Sometimes, however, some solutions may require more in-depth discussions, and the number of responses can quickly rise, which can cause tension between trying to be a good team player by responding to everyone and attempting the next design iteration. This might be especially true if the person who’s replying is a stakeholder or someone directly involved in the project who we feel that we need to listen to. It’s human nature to try to accommodate those we care about, and we need to accept that this pressure is completely normal. When responding to all comments, it can be effective, but when we consider a design critique more like user research, we realize that we don’t need to respond to every comment, and there are alternatives in asynchronous spaces:

      One is to let the next iteration speak for itself. That is the response when the design changes and we publish a follow-up iteration. You could tag everyone in the previous discussion, but that’s just a choice, not a requirement.
    • Another is to briefly reply to acknowledge each comment, such as” Understood. Thank you,”” Good points— I’ll review,” or” Thanks. In the upcoming iteration, I’ll include these. In some cases, this could also be just a single top-level comment along the lines of” Thanks for all the feedback everyone—the next iteration is coming soon”!
    • One more thing is to quickly summarize the comments before proceeding. This may be particularly helpful if your workflow allows you to create a simplified checklist that you can use for the following iteration.

    The second friction point is the swoop-by comment, which is the kind of feedback that comes from someone outside the project or team who might not be aware of the context, restrictions, decisions, or requirements —or of the previous iterations ‘ discussions. One can hope that they will learn something from them, starting with acknowledging that they are doing this and making their location more explicit. Swoop-by comments frequently prompt the simple thought,” We’ve already discussed this,” and it can be frustrating to have to keep coming back and forth.

    Let’s begin by acknowledging again that there’s no need to reply to every comment. However, a brief response with a link to the previous discussion for additional information is typically sufficient if responding to a previously litigated point might be helpful. Remember that repetition results in alignment; therefore, it’s acceptable to occasionally repeat things!

    Swoop-by commenting can still be useful for two reasons: they might point out something that still isn’t clear, and they also have the potential to stand in for the point of view of a user who’s seeing the design for the first time. Yes, you’ll still be frustrated, but that might at least make things better for you.

    The personal stake we might have in relation to the design could be the third friction point, which might cause us to feel defensive if the review turned out to be more of a discussion. Treating feedback as user research helps us create a healthy distance between the people giving us feedback and our ego ( because yes, even if we don’t want to admit it, it’s there ). And in the end, presenting everything in aggregated form helps us to prioritize our work more.

    Remember to always remember that you don’t have to accept every piece of feedback, even though you need to listen to stakeholders, project owners, and specific advice. You have to analyze it and make a decision that you can justify, but sometimes “no” is the right answer.

    You are in charge of making that choice as the designer leading the project. In the end, everyone has their area of specialization, and the designer has the most background and knowledge to make the best choice. And by listening to the feedback that you’ve received, you’re making sure that it’s also the best and most balanced decision.

    Thanks to Mike Shelton and Brie Anne Demkiw for their contributions to the initial draft of this article.

  • Voice Content and Usability

    Voice Content and Usability

    We’ve been conversing for many thousands of years. Whether to present information, perform transactions, or just to check in on one another, people have yammered aside, chattering and gesticulating, through spoken discussion for many generations. Only recently have we begun to write our conversations, and only recently have we outsourced them to the system, a system that exhibits a far greater affection for written communications than for the vernacular rigors of spoken speech.

    Speech is more important in servers because it is more important than written speech in spoken and written writing. To have productive conversations with us, machines may struggle with the messiness of mortal speech: the disfluencies and pauses, the gestures and body language, and the variations in word choice and spoken dialect that is stymie even the most carefully crafted human-computer interaction. Speaking English also has the advantage of face-to-face contact, which enables us to perceive visual social cues in the human-to-human scenario.

    In contrast, written language develops its own fossil record of dated terms and phrases as we commit to recording and keeping usages long after they are no longer relevant in spoken communication ( for example, the salutation” To whom it may concern” ). Because it tends to be more consistent, smooth, and proper, written word is necessarily far easier for devices to interpret and know.

    Spoken speech lacks this luxury. There are verbal cues and vociferous behaviors that mimic conversation in complex ways, including how something is said, never what. These are the nonverbal cues that ornament conversations with emphasis and emotional context. Whether rapid-fire, low-pitched, or high-decibel, whether satirical, awkward, or groaning, our spoken speech conveys much more than the written word had ever muster. But as designers and content strategists, we face fascinating challenges when it comes to voice interfaces, the machines we use to perform spoken conversations.

    Voice Compositions

    We interact with voice interfaces for a variety of reasons, but according to Michael McTear, Zoraida Callejas, and David Griol in The Conversational Interface, those motivations by and large mirror the reasons we initiate conversations with other people, too ( ). We typically strike up a dialogue as a result:

    • we require something ( such as a transaction ),
    • we want to know something ( information of some sort ), or
    • We are sociable creatures, and we need a talk partner.

    A second talk from beginning to end that achieves some goal for the consumer, starting with the voice interface’s initial greeting and ending with the user exiting the interface, also fits into these three categories, which I refer to as interpersonal, technical, and prosocial. Note here that a conversation in our human sense—a chat between people that leads to some result and lasts an arbitrary length of time—could encompass multiple transactional, informational, and prosocial voice interactions in succession. In other words, a voice interaction is a conversation, but it must not be one particular voice interaction.

    Most voice interfaces are more gimmicky than captivating in pure prosocial conversations because most people find it difficult to trust their machines to actually understand how we’re doing and to give them the kind of glad-handing we crave. There’s also ongoing debate as to whether users actually prefer the sort of organic human conversation that begins with a prosocial voice interaction and shifts seamlessly into other types. In fact, Michael Cohen, James Giangola, and Jennifer Balogh advise sticking to user expectations by imitating how they interact with other voice interfaces rather than trying too hard to be human, which could lead to alienation of them ( ).

    That leaves two different types of conversations we can have with one another that a voice interface can also have easily, such as one that focuses on a transactional voice interaction ( buying iced tea ) and another on learning something new ( discuss a musical ).

    Transactional voice interactions

    When you order a Hawaiian pizza with extra pineapple, you’re typically having a conversation and a voice interaction when you’re tapping buttons on a food delivery app. The conversation quickly shifts from a brief smattering of neighborly small talk to ordering a pizza ( generously topped with pineapple, as it should be ) when we walk up to the counter and place an order.

    Alison: Hey, how’s it going?

    Burhan: Hello and welcome to Crust Deluxe! It’s chilly outside. How can I help you?

    Alison, can I get a pineapple-onion pizza in Hawaii?

    Burhan: Yes, but what size?

    Alison: Large.

    Burhan: Anything else?

    Alison: No, that’s it.

    Burhan: Something to drink?

    Alison, I’ll have a bottle of Coke.

    Burhan, you know what. That’ll be$ 13.55 and about fifteen minutes.

    A service rendered or a product delivered is the desired outcome of the transaction, and each progressive disclosure in this transactional conversation reveals more and more of it. Conversations that are transactional have certain characteristics: they are direct, concise, and cost-effective. They quickly dispense with pleasantries.

    Informational voice interactions

    While some conversations are primarily about obtaining information, some are. Though Alison might visit Crust Deluxe with the sole purpose of placing an order, she might not actually want to walk out with a pizza at all. She might be interested in trying kosher or halal dishes, trying gluten-free dishes, or something else entirely. Even though we have a prosocial mini-conversation once more at the beginning to practice politeness, we are after much more.

    Alison: Hey, how’s it going?

    Burhan: Hello and welcome to Crust Deluxe! It’s chilly outside. How can I help you?

    Alison: Can I ask a few questions?

    Burhan: Of course! Continue straight ahead.

    Alison: Do you have any halal options on the menu?

    Burhan: Totally! On request, we can make any pie halal. We also have lots of vegetarian, ovo-lacto, and vegan options. Do you have any other dietary restrictions in mind?

    Alison, what about pizzas that don’t contain gluten?

    Burhan: We can definitely do a gluten-free crust for you, no problem, for both our deep-dish and thin-crust pizzas. Anything else I can say to you to help?

    Alison: That’s it for now. Good to know. Thank you.

    Burhan: Anytime, please.

    This is a very different dialogue. Here, the goal is to obtain a particular set of facts. Informational conversations are research expeditions to gather data, news, or facts in search of the truth. Voice interactions that are informational might be more long-winded than transactional conversations by necessity. Responses are typically longer, more in-depth, and carefully communicated to ensure that the customer understands the main ideas.

    Voice interfaces

    At their core, voice interfaces employ speech to support users in reaching their goals. However, just because an interface has a voice component doesn’t mean that every user interaction with it is mediated by voice. We’re most concerned with pure voice interfaces, which are completely dependent on spoken conversation and lack any visual component, making them much more nuanced and challenging to deal with because multimodal voice interfaces can lean on visual components like screens as crutches.

    Though voice interfaces have long been integral to the imagined future of humanity in science fiction, only recently have those lofty visions become fully realized in genuine voice interfaces.

    IVR ( interactive voice response ) systems

    Written conversational interfaces have been a part of computing for many decades, but voice interfaces first started to appear in the early 1990s with text-to-speech ( TTS ) dictation programs that recited written text aloud as well as speech-enabled in-car systems that gave directions to a user-provided address. With the advent of interactive voice response ( IVR ) systems, intended as an alternative to overburdened customer service representatives, we became acquainted with the first true voice interfaces that engaged in authentic conversation.

    IVR systems made it easier for businesses to cut down on call centers, but they soon gained notoriety for their clunkiness. Similar to the corporate world, these systems were primarily created as metaphorical switchboards to direct customers to a real phone agent (” Say Reservations to book a flight or check an itinerary” ), and chances are you’ll have a conversation with one when you call an airline or hotel conglomerate. Despite their functional issues and users ‘ frustration with their inability to speak to an actual human right away, IVR systems proliferated in the early 1990s across a variety of industries (, PDF).

    IVR systems have a reputation for having less scintillating conversations than we’re used to in real life ( or even in science fiction ), despite being extremely repetitive and monotonous.

    Readers of screens

    Parallel to the evolution of IVR systems was the invention of the screen reader, a tool that transcribes visual content into synthesized speech. For Blind or visually impaired website users, it’s the predominant method of interacting with text, multimedia, or form elements. Readers of screens represent perhaps the closest equivalent we have today to an out-of-the-box implementation of content delivered through voice.

    Among the first screen readers known by that moniker was the Screen Reader for the BBC Micro and NEEC Portable developed by the Research Centre for the Education of the Visually Handicapped (RCEVH) at the University of Birmingham in 1986 ( ). In the same year, Jim Thatcher created the first IBM Screen Reader for text-based computers, which was later reworked for computers with graphical user interfaces ( GUIs ) ( ).

    With the rapid expansion of the web in the 1990s, there was an explosion in the demand for user-friendly tools for websites. Thanks to the introduction of semantic HTML and especially ARIA roles beginning in 2008, screen readers started facilitating speedy interactions with web pages that ostensibly allow disabled users to traverse the page as an aural and temporal space rather than a visual and physical one. In other words, web screen readers “provide mechanisms that translate visual design constructs—proximity, proportion, etc. —into useful information,” according to Aaron Gustafson in A List Apart. ” At least they do when documents are authored thoughtfully” ( ).

    There’s a big deal with screen readers: they’re difficult to use and relentlessly verbose, despite being incredibly instructive for voice interface designers. Sometimes unwieldy pronouncements that name every manipulable HTML element and announce every formatting change are made because the visual structures of websites and web navigation don’t translate well to screen readers. For many screen reader users, working with web-based interfaces exacts a cognitive toll.

    Accessibility advocate and voice engineer Chris Maury examines why the screen reader experience is not appropriate for users who rely on voice in Wired:

    I hated the way Screen Readers operated from the beginning. Why are they designed the way they are? It makes no sense to present information visually and then only to have that information translated into audio. All the effort and thought that goes into creating the ideal user experience for an app is wasted, or worse, having a negative effect on blind users ‘ experience. __ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    Well-designed voice interfaces can often be more effective than long-winded screen reader monologues in guiding users to their destination. After all, users of the visual interface have the advantage of freely scurrying around the viewport to find information without worrying about it. Blind users, meanwhile, are obligated to listen to every utterance synthesized into speech and therefore prize brevity and efficiency. Users with disabilities who have long had no choice but to use clumsy screen readers might find that voice interfaces, especially more contemporary voice assistants, provide a more streamlined experience.

    Voice-activated devices

    When we think of voice assistants (the subset of voice interfaces now commonplace in living rooms, smart homes, and offices), many of us immediately picture HAL from 2001: A Space Odyssey or hear Majel Barrett’s voice as the omniscient computer in Star Trek. Voice-activated devices are akin to personal concierges that can answer questions, schedule appointments, conduct searches, and perform other common day-to-day tasks. And they’re rapidly gaining more attention from accessibility advocates for their assistive potential.

    Before the earliest IVR systems found success in the enterprise, Apple published a demonstration video in 1987 depicting the Knowledge Navigator, a voice assistant that could transcribe spoken words and recognize human speech to a great degree of accuracy. Then, in 2001, Tim Berners-Lee and others created their vision for a” semantic web agent” that would carry out routine tasks like” checking calendars, making appointments, and finding locations” ( hinter paywall ). Apple’s Siri only became a reality until 2011 when it finally made voice assistants a reality for consumers.

    Thanks to the plethora of voice assistants available today, there is considerable variation in how programmable and customizable certain voice assistants are over others ( Fig 1.1 ). At one extreme, everything but vendor-provided features are locked down. For instance, at the time of their release, the core functionality of Apple’s Siri and Microsoft’s Cortana couldn’t be expanded beyond their already-existing capabilities. There are no other means by which developers can interact with Siri at a low level, aside from predefined categories of tasks like sending messages, hailing rideshares, making restaurant reservations, and other things, so even now it isn’t possible to program Siri to perform arbitrary functions.

    At the opposite end of the spectrum, voice assistants like Amazon Alexa and Google Home offer a core foundation on which developers can build custom voice interfaces. For this reason, developers who feel stifled by the limitations of Siri and Cortana are increasingly using programmable voice assistants that are capable of customization and extensibility. Google Home has the ability to program arbitrary Google Assistant skills, while Amazon offers the Alexa Skills Kit, a developer framework for creating custom voice interfaces for Amazon Alexa. Today, users can choose from among thousands of custom-built skills within both the Amazon Alexa and Google Assistant ecosystems.

    As businesses like Amazon, Apple, Microsoft, and Google continue to dominate their markets, they are also selling and open-sourcing an unmatched range of tools and frameworks for designers and developers, aiming to make creating voice interfaces as simple as possible, even without the use of any code.

    Often by necessity, voice assistants like Amazon Alexa tend to be monochannel—they’re tightly coupled to a device and can’t be accessed on a computer or smartphone instead. In contrast, many development platforms, such as Google’s Dialogflow, have omnichannel capabilities that allow users to create a single conversational interface that then becomes a voice interface, textual chatbot, and IVR system upon deployment. In this design-focused book, I don’t recommend any particular implementation strategies, but in Chapter 4 we’ll discuss some of the possible effects that these variables might have on how you construct your design artifacts.

    Voice Content

    Simply put, voice content is voice-transmitted content. Voice content must be free-flowing and organic, contextless and concise in order to preserve what makes human conversation so compelling in the first place. Everything written content is not.

    Our world is replete with voice content in various forms: screen readers reciting website content, voice assistants rattling off a weather forecast, and automated phone hotline responses governed by IVR systems. We’re most concerned with the audiobook content being delivered as a requirement rather than an option.

    Our initial foray into informational voice interfaces will likely be to provide user content, for many of us. There’s only one problem: any content we already have isn’t in any way ready for this new habitat. How can we make the content on our websites more conversational? And how do we create fresh copy that works with voice-activated text?

    Lately, we’ve begun slicing and dicing our content in unprecedented ways. Websites are, in many ways, massive vaults of what I call macrocontent: lengthy prose that can last for miles in a browser window while being viewed in microfilm format in newspaper archives. Microcontent was defined as permalinked pieces of content that could be read in any environment, such as email or text messages back in 2002, well before the present-day ubiquity of voice assistants.

    A day’s weather forcast]sic], the arrival and departure times for an airplane flight, an abstract from a long publication, or a single instant message can all be examples of microcontent. __ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    I would update Dash’s definition of microcontent to include all instances of bite-sized content that transcends written communiqués. After all, today we encounter microcontent in interfaces where a small snippet of copy is displayed alone, unmoored from the browser, like a textbot confirmation of a restaurant reservation. Informing delivery channels both established and novel, Microcontent provides the best opportunity to find out how your content can be stretched to the limits of its potential.

    Voice content stands out as being unique because it illustrates how content is experienced in space as opposed to time. We can glance at a digital sign underground for an instant and know when the next train is arriving, but voice interfaces hold our attention captive for periods of time that we can’t easily escape or skip, something screen reader users are all too familiar with.

    We need to make sure that our microcontent truly performs well as voice content because it is essentially composed of isolated blobs without any connection to the channels where they will eventually end up. This means focusing on the two most crucial characteristics of robust voice content: voice content legibility and voice content discoverability.

    Our voice content’s legibility and discoverability in general both depend on how it manifests in terms of perceived space and time.