From Beta to Bedrock: Build Products that Stick.

As a product builder over too many years to mention, I’ve lost count of the number of times I’ve seen promising ideas go from zero to hero in a few weeks, only to fizzle out within months.

Financial products, which is the field I work in, are no exception. With people’s real hard-earned money on the line, user expectations running high, and a crowded market, it’s tempting to throw as many features at the wall as possible and hope something sticks. But this approach is a recipe for disaster. Here’s why:

The pitfalls of feature-first development

When you start building a financial product from the ground up, or are migrating existing customer journeys from paper or telephony channels onto online banking or mobile apps, it’s easy to get caught up in the excitement of creating new features. You might think, “If I can just add one more thing that solves this particular user problem, they’ll love me!” But what happens when you inevitably hit a roadblock because the narcs (your security team!) don’t like it? When a hard-fought feature isn’t as popular as you thought, or it breaks due to unforeseen complexity?

This is where the concept of Minimum Viable Product (MVP) comes in. Jason Fried’s book Getting Real and his podcast Rework often touch on this idea, even if he doesn’t always call it that. An MVP is a product that provides just enough value to your users to keep them engaged, but not so much that it becomes overwhelming or difficult to maintain. It sounds like an easy concept but it requires a razor sharp eye, a ruthless edge and having the courage to stick by your opinion because it is easy to be seduced by “the Columbo Effect”… when there’s always “just one more thing…” that someone wants to add.

The problem with most finance apps, however, is that they often become a reflection of the internal politics of the business rather than an experience solely designed around the customer. This means that the focus is on delivering as many features and functionalities as possible to satisfy the needs and desires of competing internal departments, rather than providing a clear value proposition that is focused on what the people out there in the real world want. As a result, these products can very easily bloat to become a mixed bag of confusing, unrelated and ultimately unlovable customer experiences—a feature salad, you might say.

The importance of bedrock

So what’s a better approach? How can we build products that are stable, user-friendly, and—most importantly—stick?

That’s where the concept of “bedrock” comes in. Bedrock is the core element of your product that truly matters to users. It’s the fundamental building block that provides value and stays relevant over time.

In the world of retail banking, which is where I work, the bedrock has got to be in and around the regular servicing journeys. People open their current account once in a blue moon but they look at it every day. They sign up for a credit card every year or two, but they check their balance and pay their bill at least once a month.

Identifying the core tasks that people want to do and then relentlessly striving to make them easy to do, dependable, and trustworthy is where the gravy’s at.

But how do you get to bedrock? By focusing on the “MVP” approach, prioritizing simplicity, and iterating towards a clear value proposition. This means cutting out unnecessary features and focusing on delivering real value to your users.

It also means having some guts, because your colleagues might not always instantly share your vision to start with. And controversially, sometimes it can even mean making it clear to customers that you’re not going to come to their house and make their dinner. The occasional “opinionated user interface design” (i.e. clunky workaround for edge cases) might sometimes be what you need to use to test a concept or buy you space to work on something more important.

Practical strategies for building financial products that stick

So what are the key strategies I’ve learned from my own experience and research?

  1. Start with a clear “why”: What problem are you trying to solve? For whom? Make sure your mission is crystal clear before building anything. Make sure it aligns with your company’s objectives, too.
  2. Focus on a single, core feature and obsess on getting that right before moving on to something else: Resist the temptation to add too many features at once. Instead, choose one that delivers real value and iterate from there.
  3. Prioritize simplicity over complexity: Less is often more when it comes to financial products. Cut out unnecessary bells and whistles and keep the focus on what matters most.
  4. Embrace continuous iteration: Bedrock isn’t a fixed destination—it’s a dynamic process. Continuously gather user feedback, refine your product, and iterate towards that bedrock state.
  5. Stop, look and listen: Don’t just test your product as part of your delivery process—test it repeatedly in the field. Use it yourself. Run A/B tests. Gather user feedback. Talk to people who use it, and refine accordingly.

The bedrock paradox

There’s an interesting paradox at play here: building towards bedrock means sacrificing some short-term growth potential in favour of long-term stability. But the payoff is worth it—products built with a focus on bedrock will outlast and outperform their competitors, and deliver sustained value to users over time.

So, how do you start your journey towards bedrock? Take it one step at a time. Start by identifying those core elements that truly matter to your users. Focus on building and refining a single, powerful feature that delivers real value. And above all, test obsessively—for, in the words of Abraham Lincoln, Alan Kay, or Peter Drucker (whomever you believe!!), “The best way to predict the future is to create it.”

An Holistic Framework for Shared Design Leadership

Picture this: You’re in a meeting room at your tech company, and two people are having what looks like the same conversation about the same design problem. One is talking about whether the team has the right skills to tackle it. The other is diving deep into whether the solution actually solves the user’s problem. Same room, same problem, completely different lenses.

This is the beautiful, sometimes messy reality of having both a Design Manager and a Lead Designer on the same team. And if you’re wondering how to make this work without creating confusion, overlap, or the dreaded “too many cooks” scenario, you’re asking the right question.

The traditional answer has been to draw clean lines on an org chart. The Design Manager handles people, the Lead Designer handles craft. Problem solved, right? Except clean org charts are fantasy. In reality, both roles care deeply about team health, design quality, and shipping great work. 

The magic happens when you embrace the overlap instead of fighting it—when you start thinking of your design org as a design organism.

The Anatomy of a Healthy Design Team

Here’s what I’ve learned from years of being on both sides of this equation: think of your design team as a living organism. The Design Manager tends to the mind (the psychological safety, the career growth, the team dynamics). The Lead Designer tends to the body (the craft skills, the design standards, the hands-on work that ships to users).

But just like mind and body aren’t completely separate systems, so, too, do these roles overlap in important ways. You can’t have a healthy person without both working in harmony. The trick is knowing where those overlaps are and how to navigate them gracefully.

When we look at how healthy teams actually function, three critical systems emerge. Each requires both roles to work together, but with one taking primary responsibility for keeping that system strong.

The Nervous System: People & Psychology

Primary caretaker: Design Manager
Supporting role: Lead Designer

The nervous system is all about signals, feedback, and psychological safety. When this system is healthy, information flows freely, people feel safe to take risks, and the team can adapt quickly to new challenges.

The Design Manager is the primary caretaker here. They’re monitoring the team’s psychological pulse, ensuring feedback loops are healthy, and creating the conditions for people to grow. They’re hosting career conversations, managing workload, and making sure no one burns out.

But the Lead Designer plays a crucial supporting role. They’re providing sensory input about craft development needs, spotting when someone’s design skills are stagnating, and helping identify growth opportunities that the Design Manager might miss.

Design Manager tends to:

  • Career conversations and growth planning
  • Team psychological safety and dynamics
  • Workload management and resource allocation
  • Performance reviews and feedback systems
  • Creating learning opportunities

Lead Designer supports by:

  • Providing craft-specific feedback on team member development
  • Identifying design skill gaps and growth opportunities
  • Offering design mentorship and guidance
  • Signaling when team members are ready for more complex challenges

The Muscular System: Craft & Execution

Primary caretaker: Lead Designer
Supporting role: Design Manager

The muscular system is about strength, coordination, and skill development. When this system is healthy, the team can execute complex design work with precision, maintain consistent quality, and adapt their craft to new challenges.

The Lead Designer is the primary caretaker here. They’re setting design standards, providing craft coaching, and ensuring that shipping work meets the quality bar. They’re the ones who can tell you if a design decision is sound or if we’re solving the right problem.

But the Design Manager plays a crucial supporting role. They’re ensuring the team has the resources and support to do their best craft work, like proper nutrition and recovery time for an athlete.

Lead Designer tends to:

  • Definition of design standards and system usage
  • Feedback on what design work meets the standard
  • Experience direction for the product
  • Design decisions and product-wide alignment
  • Innovation and craft advancement

Design Manager supports by:

  • Ensuring design standards are understood and adopted across the team
  • Confirming experience direction is being followed
  • Supporting practices and systems that scale without bottlenecking
  • Facilitating design alignment across teams
  • Providing resources and removing obstacles to great craft work

The Circulatory System: Strategy & Flow

Shared caretakers: Both Design Manager and Lead Designer

The circulatory system is about how information, decisions, and energy flow through the team. When this system is healthy, strategic direction is clear, priorities are aligned, and the team can respond quickly to new opportunities or challenges.

This is where true partnership happens. Both roles are responsible for keeping the circulation strong, but they’re bringing different perspectives to the table.

Lead Designer contributes:

  • User needs are met by the product
  • Overall product quality and experience
  • Strategic design initiatives
  • Research-based user needs for each initiative

Design Manager contributes:

  • Communication to team and stakeholders
  • Stakeholder management and alignment
  • Cross-functional team accountability
  • Strategic business initiatives

Both collaborate on:

  • Co-creation of strategy with leadership
  • Team goals and prioritization approach
  • Organizational structure decisions
  • Success measures and frameworks

Keeping the Organism Healthy

The key to making this partnership sing is understanding that all three systems need to work together. A team with great craft skills but poor psychological safety will burn out. A team with great culture but weak craft execution will ship mediocre work. A team with both but poor strategic circulation will work hard on the wrong things.

Be Explicit About Which System You’re Tending

When you’re in a meeting about a design problem, it helps to acknowledge which system you’re primarily focused on. “I’m thinking about this from a team capacity perspective” (nervous system) or “I’m looking at this through the lens of user needs” (muscular system) gives everyone context for your input.

This isn’t about staying in your lane. It’s about being transparent as to which lens you’re using, so the other person knows how to best add their perspective.

Create Healthy Feedback Loops

The most successful partnerships I’ve seen establish clear feedback loops between the systems:

Nervous system signals to muscular system: “The team is struggling with confidence in their design skills” → Lead Designer provides more craft coaching and clearer standards.

Muscular system signals to nervous system: “The team’s craft skills are advancing faster than their project complexity” → Design Manager finds more challenging growth opportunities.

Both systems signal to circulatory system: “We’re seeing patterns in team health and craft development that suggest we need to adjust our strategic priorities.”

Handle Handoffs Gracefully

The most critical moments in this partnership are when something moves from one system to another. This might be when a design standard (muscular system) needs to be rolled out across the team (nervous system), or when a strategic initiative (circulatory system) needs specific craft execution (muscular system).

Make these transitions explicit. “I’ve defined the new component standards. Can you help me think through how to get the team up to speed?” or “We’ve agreed on this strategic direction. I’m going to focus on the specific user experience approach from here.”

Stay Curious, Not Territorial

The Design Manager who never thinks about craft, or the Lead Designer who never considers team dynamics, is like a doctor who only looks at one body system. Great design leadership requires both people to care about the whole organism, even when they’re not the primary caretaker.

This means asking questions rather than making assumptions. “What do you think about the team’s craft development in this area?” or “How do you see this impacting team morale and workload?” keeps both perspectives active in every decision.

When the Organism Gets Sick

Even with clear roles, this partnership can go sideways. Here are the most common failure modes I’ve seen:

System Isolation

The Design Manager focuses only on the nervous system and ignores craft development. The Lead Designer focuses only on the muscular system and ignores team dynamics. Both people retreat to their comfort zones and stop collaborating.

The symptoms: Team members get mixed messages, work quality suffers, morale drops.

The treatment: Reconnect around shared outcomes. What are you both trying to achieve? Usually it’s great design work that ships on time from a healthy team. Figure out how both systems serve that goal.

Poor Circulation

Strategic direction is unclear, priorities keep shifting, and neither role is taking responsibility for keeping information flowing.

The symptoms: Team members are confused about priorities, work gets duplicated or dropped, deadlines are missed.

The treatment: Explicitly assign responsibility for circulation. Who’s communicating what to whom? How often? What’s the feedback loop?

Autoimmune Response

One person feels threatened by the other’s expertise. The Design Manager thinks the Lead Designer is undermining their authority. The Lead Designer thinks the Design Manager doesn’t understand craft.

The symptoms: Defensive behavior, territorial disputes, team members caught in the middle.

The treatment: Remember that you’re both caretakers of the same organism. When one system fails, the whole team suffers. When both systems are healthy, the team thrives.

The Payoff

Yes, this model requires more communication. Yes, it requires both people to be secure enough to share responsibility for team health. But the payoff is worth it: better decisions, stronger teams, and design work that’s both excellent and sustainable.

When both roles are healthy and working well together, you get the best of both worlds: deep craft expertise and strong people leadership. When one person is out sick, on vacation, or overwhelmed, the other can help maintain the team’s health. When a decision requires both the people perspective and the craft perspective, you’ve got both right there in the room.

Most importantly, the framework scales. As your team grows, you can apply the same system thinking to new challenges. Need to launch a design system? Lead Designer tends to the muscular system (standards and implementation), Design Manager tends to the nervous system (team adoption and change management), and both tend to circulation (communication and stakeholder alignment).

The Bottom Line

The relationship between a Design Manager and Lead Designer isn’t about dividing territories. It’s about multiplying impact. When both roles understand they’re tending to different aspects of the same healthy organism, magic happens.

The mind and body work together. The team gets both the strategic thinking and the craft excellence they need. And most importantly, the work that ships to users benefits from both perspectives.

So the next time you’re in that meeting room, wondering why two people are talking about the same problem from different angles, remember: you’re watching shared leadership in action. And if it’s working well, both the mind and body of your design team are getting stronger.

Peacemaker Just Brought an Unlikely Team of Superman Villains to the DCU

This post contains spoilers for Peacemaker season 2 episode 3. By this point, we shouldn’t be surprised when James Gunn pulls an obscure DC Comics character for one of his projects, but he may have outdone himself in the latest episode of Peacemaker. While visiting the alternate reality where he’s a beloved hero, Chris Smith […]

The post Peacemaker Just Brought an Unlikely Team of Superman Villains to the DCU appeared first on Den of Geek.

Since 2002, John Cena embodied a mythos usually reserved for comic book characters. Now his wrestling retirement run has felt less like a farewell and more like the final act of a saga that has spanned across different timelines. It’s a significant event that challenges everyone who has been on this journey with him to appreciate everything he’s done and who he was for the business of professional wrestling as WWE continues to reinvent itself.

What makes the timing interesting is the irony of Cena closing the door on his run as WWE’s enduring superhero, while having begun a new start as another one in an entirely new universe. When James Gunn cast the wrestler as Chris Smith a.k.a. Peacemaker in The Suicide Squad, he placed Cena in a role that he was already prepared for. That’s because his career mirrored the very person that he was tasked to portray. He embodied the same duality and complexity in the WWE that Peacemaker carries in the DC Universe. 

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

}).render(“0270c398a82f44f49c23c16122516796”);
});

Cena’s on-screen evolution in Hollywood became a reinforcement of what wrestling was already writing about him out in the open. In WWE’s case, it was him holding up the company on his back when legacy fans were turning away from the product. For DC, it’s Christopher Smith’s pursuit of justice by any means that led him to reach absolution. And like WWE, James Gunn saw something in Cena’s ability to be a main character as he sought to rewrite the perception of DC, helping turn Cena into the kind of critically-acclaimed actor that had been just out of reach as he pursued Hollywood.

Peacemaker’s contradictions, his earnestness and sincerity that collides with violence and absurdity is the very paradox that defined Cena’s in-ring career. His retirement run and Peacemaker trajectory aren’t separate stories. They are the same legend told in different mediums. He was the WWE’s misunderstood hero and is now the DC Universe’s misunderstood hero too. Both have an origin story. Cena’s began a few short years after the world entered into the year 2000 in a squared-circle. 

The New Millenium’s Superhero

The wrestling industry is as fickle as the careers inside of it. Stars can rise or vanish almost overnight. Cena’s debut in June 2002 against Kurt Angle could have been pulled directly from the splash page of a graphic novel. Fans watched a confident rookie shout “ruthless aggression” before putting on a now-legendary match with one of the company’s most decorated performers. It was a dynamic introduction, but nobody could have predicted that Cena would become the company’s most notable standard-bearer for the next two decades, even if this moment all but signaled their belief in him.

What made his arrival more poignant was its timing. That debut came less than a year after the September 11 attacks, a moment when wrestling, like much of the United States, was searching for optimism and a renewed sense of national spirit. WWE leaned heavily on patriotic storytelling throughout 2001 and 2002 and is famously known as the first public gathering broadcast after the attacks. However, with tragedy looming over the country as a whole, the search for a new and fresh face that could transform into their vessel of American resilience. 

Cena fit that mold and his cleancut look would be paired with a military salute, the mantra of “Hustle, Loyalty, Respect” that reflected the core values of America, and was presented as an underdog who would, “Never Give Up.” He also frequently started wearing camouflage gear and was booked in roles that cast him as the face of American perseverance. In many ways, he was looked to as WWE’s soldier for the company. He was a direct contrast of the dying Attitude Era when the company wanted to tone down their edge in the midst of crisis and rebrand into a company that was centered around stability and hope through a main character.

To this day, Cena is still the gravitational center of WWE. He survived shifts in leadership, cultural changes, and fan rebellions, carrying the company on his back during its most fragile transitions. He was always their lightning rod, their anchor, and much more than a reliable hand. He was the hand.

Cena’s retirement arc supersedes nostalgia. It is a resolution. It reads like the last issue of a long-running comic book, where every single moment suddenly connects as one. This completes the superhero story wrestling had been writing about him in plain sight since the beginning.

Hero of The PG Era

In 2008, when WWE fully embraced PG programming, the company needed more than a figurehead. They needed someone who could withstand scrutiny and embody stability. Cena became that figure, wholesome and endlessly promotable, the brand’s most visible face.

That shift was monumental. The Attitude Era took liberties with raunchiness, blood, swearing, and antiheroes like Stone Cold Steve Austin and now, that excess was gone. In its place came a more family-friendly storytelling, partnership-focused vision from the top of the company. This brought in collaborations with entities like Mattel and Post Consumer Brands. Sponsorships and a sudden uptick in mainstream appeal triggered one of the loudest fan rebellions in wrestling history. Die-hards rejected the tamer product typified by Cena, and crowds responded in person. They threw his shirts back at him, brought signs with them that said things like, “If Cena Wins, We Riot.” They cheered the bad guys, hijacked his promos, and filled arenas with chants like, “You can’t wrestle.” Fans directed their frustration at the man they believed was the herald of this new direction. 

Anti-Cena sentiment wasn’t fringe. It was common and he took the brunt of every grievance that had been building between the audience and the business. The people wanted rebellion and they got respectability instead. Below the surface, this was a chaotic time, but Cena was still there, standing as a constant through it all. 

Very few people in modern entertainment can say they worked seven days a week. Cena did. For more than a decade, he lived a punishing schedule that saw him wrestle more than 250 nights a year, travel internationally, appear at live events, headline television and pay-per-views, and still manage early morning talk shows and late-night interviews. On top of that, he became the most requested celebrity for Make-A-Wish, granting more than 650 wishes and setting a record no one has come close to. His life was relentless, structured almost entirely around WWE’s demands, and yet he carried that responsibility without faltering. He never once complained. He always showed up. He worked through injuries and gave his best day in and day out.

His presence was not only cultural, but financial. In 2018, Cena was working part-time and only second to Roman Reigns in sales. He headlined more pay-per-views than anyone else in company history and was a ratings stabilizer when Monday Night Raw was averaging around 3.5 million weekly viewers. During that run, WWE’s annual revenue climbed from roughly $485 million in 2007 to $729 million in 2016, with live event gates and merchandise sales strongly tied to Cena’s drawing power.

Streaming numbers proved his drawing power too. Cena’s 2021 return to face Roman Reigns in the main event of SummerSlam drove the occasion to become the most-watched SummerSlam in WWE history on Peacock at the time. His 2023 SmackDown comeback in September led to one of the brand’s largest viewership surges of that year. Cena’s presence produced measurable business lifts.

Fans, however, didn’t appreciate how those numbers translated into their experience and often did not care to see the superhero either. What was happening on camera wasn’t the shock and awe or the edge that they demanded. At that very moment, antiheroes were dominating pop culture and Cena’s squeaky-clean persona was unwelcome. Events rang with chants of “Cena sucks.” He faced continuous criticism of his wrestling ability and his infamous “Five Moves of Doom” and promos that sounded almost too good. He never bent. He walked into the fire every night, in the midst of a brutal and grueling schedule that preceded his appearances and waited for him afterwards. He became Superman made flesh onscreen and off of it too, when the world thought they wanted him to change and be something different.

His rivalry with Randy Orton became the backbone of the PG Era, a battle of morality against rebellion that proved WWE could endure when anchored by one man who refused to compromise. He was a part of the brand that was necessary. He took up a mantle, one that presented itself as desirable, but was paired with an incredible cost. This is why his retirement isn’t normal. It’s the end of one of the greatest stories ever told in a professional sport. Very few have ever walked in shoes like these and got their chance to leave gracefully.

John Cena’s Comic Book Saga

Cena’s career has been full of larger-than-life matchups. His rivalry with Edge was chaos against order. His feud with CM Punk was establishment against revolution. His battles with The Rock were staged like crossover summer blockbusters. Each pairing carried meaningful stakes with them and they all contributed to his larger mythology.

The nickname “Super Cena” was not wrong. Fans were correctly identifying the archetype Cena portrayed even as they resisted it. They wanted him, but only on their terms. Still, Cena’s presence kept the company intact. He was a total performer who was shouldering complex burdens: headlining pay-per-views, filming charity spots, handling endless media, and wrestling night after night with the same effort. He was important not just because of championships, but because of his endurance too. And he never became nasty and resentful after fulfilling his duties time and time again. He just kept going. That is the essence of a hero and someone who deserves their endless flowers.

For years, Cena was defined by rejection. Now, arenas thunder in gratitude. The same fans who once booed him for being too perfect now recognize that he was a special talent the likes of which they may never see again.

Cena’s final appearances have electrified crowds because of the weight of finality. The sight of him saluting at the top of the ramp has regained its luster. They are the last frames of a story that has been building for as long as some can even remember. Every word he has spoken has landed differently, laced with subtle hints of his legacy and of his goodbye.

Wrestlepalooza, WWE’s first under the TKO banner, highlights Cena’s place in the company and the need to have someone ready to be their franchise player who provides continuity while Cena provides closure. The speculation over his final opponent now feels less like booking chatter and more like mythology being written in real time. If Orton is the rival who defines his arc, if Roman Reigns is the franchise who succeeded him, or if a younger talent is chosen to stand across from him, the choice will symbolize more than a match. It will represent the final page and hopefully the passing of the torch to the new standard bearer and generational talent for the next 20 years.

Cena’s last appearance on the Friday Night Smackdown brand is on the same show and in the same building where he made his debut against Kurt Angle in 2002: Chicago’s Allstate Arena. The setting is the final metamorphosis of a hero’s journey that’s been unfolding throughout the years. The return there more than two decades later, at the close of his career, transforms September 5, 2025 into something larger than nostalgia. It becomes sacred ground where Cena and his audience can share in closure together.

As this chapter closes, Cena doesn’t just leave behind championships or catchphrases. With his retirement ends the last great story of the PG Era, an entire era of professional wrestling that he carried through sheer stamina, consistency, and sacrifice. And for once, in both WWE and Hollywood, the world seems ready to admit they had been watching a superhero all along.

The post John Cena’s Retirement Is the Final Chapter of a Superhero Story appeared first on Den of Geek.

Why Peacemaker Season 2 Does the Multiverse Right

This post contains spoilers for Peacemaker season 2 episodes 1-3. “Best. Universe. Ever.” That’s how the Peacemaker Chris Smith describes the alternate reality he visits throughout the second season of the show that bears his name. While it was a cheering crowd—complete with a child moved to tears and a woman moved to bare her […]

The post Why Peacemaker Season 2 Does the Multiverse Right appeared first on Den of Geek.

Since 2002, John Cena embodied a mythos usually reserved for comic book characters. Now his wrestling retirement run has felt less like a farewell and more like the final act of a saga that has spanned across different timelines. It’s a significant event that challenges everyone who has been on this journey with him to appreciate everything he’s done and who he was for the business of professional wrestling as WWE continues to reinvent itself.

What makes the timing interesting is the irony of Cena closing the door on his run as WWE’s enduring superhero, while having begun a new start as another one in an entirely new universe. When James Gunn cast the wrestler as Chris Smith a.k.a. Peacemaker in The Suicide Squad, he placed Cena in a role that he was already prepared for. That’s because his career mirrored the very person that he was tasked to portray. He embodied the same duality and complexity in the WWE that Peacemaker carries in the DC Universe. 

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

}).render(“0270c398a82f44f49c23c16122516796”);
});

Cena’s on-screen evolution in Hollywood became a reinforcement of what wrestling was already writing about him out in the open. In WWE’s case, it was him holding up the company on his back when legacy fans were turning away from the product. For DC, it’s Christopher Smith’s pursuit of justice by any means that led him to reach absolution. And like WWE, James Gunn saw something in Cena’s ability to be a main character as he sought to rewrite the perception of DC, helping turn Cena into the kind of critically-acclaimed actor that had been just out of reach as he pursued Hollywood.

Peacemaker’s contradictions, his earnestness and sincerity that collides with violence and absurdity is the very paradox that defined Cena’s in-ring career. His retirement run and Peacemaker trajectory aren’t separate stories. They are the same legend told in different mediums. He was the WWE’s misunderstood hero and is now the DC Universe’s misunderstood hero too. Both have an origin story. Cena’s began a few short years after the world entered into the year 2000 in a squared-circle. 

The New Millenium’s Superhero

The wrestling industry is as fickle as the careers inside of it. Stars can rise or vanish almost overnight. Cena’s debut in June 2002 against Kurt Angle could have been pulled directly from the splash page of a graphic novel. Fans watched a confident rookie shout “ruthless aggression” before putting on a now-legendary match with one of the company’s most decorated performers. It was a dynamic introduction, but nobody could have predicted that Cena would become the company’s most notable standard-bearer for the next two decades, even if this moment all but signaled their belief in him.

What made his arrival more poignant was its timing. That debut came less than a year after the September 11 attacks, a moment when wrestling, like much of the United States, was searching for optimism and a renewed sense of national spirit. WWE leaned heavily on patriotic storytelling throughout 2001 and 2002 and is famously known as the first public gathering broadcast after the attacks. However, with tragedy looming over the country as a whole, the search for a new and fresh face that could transform into their vessel of American resilience. 

Cena fit that mold and his cleancut look would be paired with a military salute, the mantra of “Hustle, Loyalty, Respect” that reflected the core values of America, and was presented as an underdog who would, “Never Give Up.” He also frequently started wearing camouflage gear and was booked in roles that cast him as the face of American perseverance. In many ways, he was looked to as WWE’s soldier for the company. He was a direct contrast of the dying Attitude Era when the company wanted to tone down their edge in the midst of crisis and rebrand into a company that was centered around stability and hope through a main character.

To this day, Cena is still the gravitational center of WWE. He survived shifts in leadership, cultural changes, and fan rebellions, carrying the company on his back during its most fragile transitions. He was always their lightning rod, their anchor, and much more than a reliable hand. He was the hand.

Cena’s retirement arc supersedes nostalgia. It is a resolution. It reads like the last issue of a long-running comic book, where every single moment suddenly connects as one. This completes the superhero story wrestling had been writing about him in plain sight since the beginning.

Hero of The PG Era

In 2008, when WWE fully embraced PG programming, the company needed more than a figurehead. They needed someone who could withstand scrutiny and embody stability. Cena became that figure, wholesome and endlessly promotable, the brand’s most visible face.

That shift was monumental. The Attitude Era took liberties with raunchiness, blood, swearing, and antiheroes like Stone Cold Steve Austin and now, that excess was gone. In its place came a more family-friendly storytelling, partnership-focused vision from the top of the company. This brought in collaborations with entities like Mattel and Post Consumer Brands. Sponsorships and a sudden uptick in mainstream appeal triggered one of the loudest fan rebellions in wrestling history. Die-hards rejected the tamer product typified by Cena, and crowds responded in person. They threw his shirts back at him, brought signs with them that said things like, “If Cena Wins, We Riot.” They cheered the bad guys, hijacked his promos, and filled arenas with chants like, “You can’t wrestle.” Fans directed their frustration at the man they believed was the herald of this new direction. 

Anti-Cena sentiment wasn’t fringe. It was common and he took the brunt of every grievance that had been building between the audience and the business. The people wanted rebellion and they got respectability instead. Below the surface, this was a chaotic time, but Cena was still there, standing as a constant through it all. 

Very few people in modern entertainment can say they worked seven days a week. Cena did. For more than a decade, he lived a punishing schedule that saw him wrestle more than 250 nights a year, travel internationally, appear at live events, headline television and pay-per-views, and still manage early morning talk shows and late-night interviews. On top of that, he became the most requested celebrity for Make-A-Wish, granting more than 650 wishes and setting a record no one has come close to. His life was relentless, structured almost entirely around WWE’s demands, and yet he carried that responsibility without faltering. He never once complained. He always showed up. He worked through injuries and gave his best day in and day out.

His presence was not only cultural, but financial. In 2018, Cena was working part-time and only second to Roman Reigns in sales. He headlined more pay-per-views than anyone else in company history and was a ratings stabilizer when Monday Night Raw was averaging around 3.5 million weekly viewers. During that run, WWE’s annual revenue climbed from roughly $485 million in 2007 to $729 million in 2016, with live event gates and merchandise sales strongly tied to Cena’s drawing power.

Streaming numbers proved his drawing power too. Cena’s 2021 return to face Roman Reigns in the main event of SummerSlam drove the occasion to become the most-watched SummerSlam in WWE history on Peacock at the time. His 2023 SmackDown comeback in September led to one of the brand’s largest viewership surges of that year. Cena’s presence produced measurable business lifts.

Fans, however, didn’t appreciate how those numbers translated into their experience and often did not care to see the superhero either. What was happening on camera wasn’t the shock and awe or the edge that they demanded. At that very moment, antiheroes were dominating pop culture and Cena’s squeaky-clean persona was unwelcome. Events rang with chants of “Cena sucks.” He faced continuous criticism of his wrestling ability and his infamous “Five Moves of Doom” and promos that sounded almost too good. He never bent. He walked into the fire every night, in the midst of a brutal and grueling schedule that preceded his appearances and waited for him afterwards. He became Superman made flesh onscreen and off of it too, when the world thought they wanted him to change and be something different.

His rivalry with Randy Orton became the backbone of the PG Era, a battle of morality against rebellion that proved WWE could endure when anchored by one man who refused to compromise. He was a part of the brand that was necessary. He took up a mantle, one that presented itself as desirable, but was paired with an incredible cost. This is why his retirement isn’t normal. It’s the end of one of the greatest stories ever told in a professional sport. Very few have ever walked in shoes like these and got their chance to leave gracefully.

John Cena’s Comic Book Saga

Cena’s career has been full of larger-than-life matchups. His rivalry with Edge was chaos against order. His feud with CM Punk was establishment against revolution. His battles with The Rock were staged like crossover summer blockbusters. Each pairing carried meaningful stakes with them and they all contributed to his larger mythology.

The nickname “Super Cena” was not wrong. Fans were correctly identifying the archetype Cena portrayed even as they resisted it. They wanted him, but only on their terms. Still, Cena’s presence kept the company intact. He was a total performer who was shouldering complex burdens: headlining pay-per-views, filming charity spots, handling endless media, and wrestling night after night with the same effort. He was important not just because of championships, but because of his endurance too. And he never became nasty and resentful after fulfilling his duties time and time again. He just kept going. That is the essence of a hero and someone who deserves their endless flowers.

For years, Cena was defined by rejection. Now, arenas thunder in gratitude. The same fans who once booed him for being too perfect now recognize that he was a special talent the likes of which they may never see again.

Cena’s final appearances have electrified crowds because of the weight of finality. The sight of him saluting at the top of the ramp has regained its luster. They are the last frames of a story that has been building for as long as some can even remember. Every word he has spoken has landed differently, laced with subtle hints of his legacy and of his goodbye.

Wrestlepalooza, WWE’s first under the TKO banner, highlights Cena’s place in the company and the need to have someone ready to be their franchise player who provides continuity while Cena provides closure. The speculation over his final opponent now feels less like booking chatter and more like mythology being written in real time. If Orton is the rival who defines his arc, if Roman Reigns is the franchise who succeeded him, or if a younger talent is chosen to stand across from him, the choice will symbolize more than a match. It will represent the final page and hopefully the passing of the torch to the new standard bearer and generational talent for the next 20 years.

Cena’s last appearance on the Friday Night Smackdown brand is on the same show and in the same building where he made his debut against Kurt Angle in 2002: Chicago’s Allstate Arena. The setting is the final metamorphosis of a hero’s journey that’s been unfolding throughout the years. The return there more than two decades later, at the close of his career, transforms September 5, 2025 into something larger than nostalgia. It becomes sacred ground where Cena and his audience can share in closure together.

As this chapter closes, Cena doesn’t just leave behind championships or catchphrases. With his retirement ends the last great story of the PG Era, an entire era of professional wrestling that he carried through sheer stamina, consistency, and sacrifice. And for once, in both WWE and Hollywood, the world seems ready to admit they had been watching a superhero all along.

The post John Cena’s Retirement Is the Final Chapter of a Superhero Story appeared first on Den of Geek.

The Conjuring: Last Rites Turns the Horror Franchise into a Schmaltzy Soap Opera

This post contains full spoilers for The Conjuring: Last RiTES. It all ends with a wedding. In the final moments of The Conjuring: Last Rites, paranormal investigators Ed and Lorraine Warren (Patrick Wilson and Vera Farmiga) dance together at the wedding of their daughter Judy (Mia Tomlinson) and new son-in-law Tony (Ben Hardy), surrounded by […]

The post The Conjuring: Last Rites Turns the Horror Franchise into a Schmaltzy Soap Opera appeared first on Den of Geek.

Since 2002, John Cena embodied a mythos usually reserved for comic book characters. Now his wrestling retirement run has felt less like a farewell and more like the final act of a saga that has spanned across different timelines. It’s a significant event that challenges everyone who has been on this journey with him to appreciate everything he’s done and who he was for the business of professional wrestling as WWE continues to reinvent itself.

What makes the timing interesting is the irony of Cena closing the door on his run as WWE’s enduring superhero, while having begun a new start as another one in an entirely new universe. When James Gunn cast the wrestler as Chris Smith a.k.a. Peacemaker in The Suicide Squad, he placed Cena in a role that he was already prepared for. That’s because his career mirrored the very person that he was tasked to portray. He embodied the same duality and complexity in the WWE that Peacemaker carries in the DC Universe. 

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

}).render(“0270c398a82f44f49c23c16122516796”);
});

Cena’s on-screen evolution in Hollywood became a reinforcement of what wrestling was already writing about him out in the open. In WWE’s case, it was him holding up the company on his back when legacy fans were turning away from the product. For DC, it’s Christopher Smith’s pursuit of justice by any means that led him to reach absolution. And like WWE, James Gunn saw something in Cena’s ability to be a main character as he sought to rewrite the perception of DC, helping turn Cena into the kind of critically-acclaimed actor that had been just out of reach as he pursued Hollywood.

Peacemaker’s contradictions, his earnestness and sincerity that collides with violence and absurdity is the very paradox that defined Cena’s in-ring career. His retirement run and Peacemaker trajectory aren’t separate stories. They are the same legend told in different mediums. He was the WWE’s misunderstood hero and is now the DC Universe’s misunderstood hero too. Both have an origin story. Cena’s began a few short years after the world entered into the year 2000 in a squared-circle. 

The New Millenium’s Superhero

The wrestling industry is as fickle as the careers inside of it. Stars can rise or vanish almost overnight. Cena’s debut in June 2002 against Kurt Angle could have been pulled directly from the splash page of a graphic novel. Fans watched a confident rookie shout “ruthless aggression” before putting on a now-legendary match with one of the company’s most decorated performers. It was a dynamic introduction, but nobody could have predicted that Cena would become the company’s most notable standard-bearer for the next two decades, even if this moment all but signaled their belief in him.

What made his arrival more poignant was its timing. That debut came less than a year after the September 11 attacks, a moment when wrestling, like much of the United States, was searching for optimism and a renewed sense of national spirit. WWE leaned heavily on patriotic storytelling throughout 2001 and 2002 and is famously known as the first public gathering broadcast after the attacks. However, with tragedy looming over the country as a whole, the search for a new and fresh face that could transform into their vessel of American resilience. 

Cena fit that mold and his cleancut look would be paired with a military salute, the mantra of “Hustle, Loyalty, Respect” that reflected the core values of America, and was presented as an underdog who would, “Never Give Up.” He also frequently started wearing camouflage gear and was booked in roles that cast him as the face of American perseverance. In many ways, he was looked to as WWE’s soldier for the company. He was a direct contrast of the dying Attitude Era when the company wanted to tone down their edge in the midst of crisis and rebrand into a company that was centered around stability and hope through a main character.

To this day, Cena is still the gravitational center of WWE. He survived shifts in leadership, cultural changes, and fan rebellions, carrying the company on his back during its most fragile transitions. He was always their lightning rod, their anchor, and much more than a reliable hand. He was the hand.

Cena’s retirement arc supersedes nostalgia. It is a resolution. It reads like the last issue of a long-running comic book, where every single moment suddenly connects as one. This completes the superhero story wrestling had been writing about him in plain sight since the beginning.

Hero of The PG Era

In 2008, when WWE fully embraced PG programming, the company needed more than a figurehead. They needed someone who could withstand scrutiny and embody stability. Cena became that figure, wholesome and endlessly promotable, the brand’s most visible face.

That shift was monumental. The Attitude Era took liberties with raunchiness, blood, swearing, and antiheroes like Stone Cold Steve Austin and now, that excess was gone. In its place came a more family-friendly storytelling, partnership-focused vision from the top of the company. This brought in collaborations with entities like Mattel and Post Consumer Brands. Sponsorships and a sudden uptick in mainstream appeal triggered one of the loudest fan rebellions in wrestling history. Die-hards rejected the tamer product typified by Cena, and crowds responded in person. They threw his shirts back at him, brought signs with them that said things like, “If Cena Wins, We Riot.” They cheered the bad guys, hijacked his promos, and filled arenas with chants like, “You can’t wrestle.” Fans directed their frustration at the man they believed was the herald of this new direction. 

Anti-Cena sentiment wasn’t fringe. It was common and he took the brunt of every grievance that had been building between the audience and the business. The people wanted rebellion and they got respectability instead. Below the surface, this was a chaotic time, but Cena was still there, standing as a constant through it all. 

Very few people in modern entertainment can say they worked seven days a week. Cena did. For more than a decade, he lived a punishing schedule that saw him wrestle more than 250 nights a year, travel internationally, appear at live events, headline television and pay-per-views, and still manage early morning talk shows and late-night interviews. On top of that, he became the most requested celebrity for Make-A-Wish, granting more than 650 wishes and setting a record no one has come close to. His life was relentless, structured almost entirely around WWE’s demands, and yet he carried that responsibility without faltering. He never once complained. He always showed up. He worked through injuries and gave his best day in and day out.

His presence was not only cultural, but financial. In 2018, Cena was working part-time and only second to Roman Reigns in sales. He headlined more pay-per-views than anyone else in company history and was a ratings stabilizer when Monday Night Raw was averaging around 3.5 million weekly viewers. During that run, WWE’s annual revenue climbed from roughly $485 million in 2007 to $729 million in 2016, with live event gates and merchandise sales strongly tied to Cena’s drawing power.

Streaming numbers proved his drawing power too. Cena’s 2021 return to face Roman Reigns in the main event of SummerSlam drove the occasion to become the most-watched SummerSlam in WWE history on Peacock at the time. His 2023 SmackDown comeback in September led to one of the brand’s largest viewership surges of that year. Cena’s presence produced measurable business lifts.

Fans, however, didn’t appreciate how those numbers translated into their experience and often did not care to see the superhero either. What was happening on camera wasn’t the shock and awe or the edge that they demanded. At that very moment, antiheroes were dominating pop culture and Cena’s squeaky-clean persona was unwelcome. Events rang with chants of “Cena sucks.” He faced continuous criticism of his wrestling ability and his infamous “Five Moves of Doom” and promos that sounded almost too good. He never bent. He walked into the fire every night, in the midst of a brutal and grueling schedule that preceded his appearances and waited for him afterwards. He became Superman made flesh onscreen and off of it too, when the world thought they wanted him to change and be something different.

His rivalry with Randy Orton became the backbone of the PG Era, a battle of morality against rebellion that proved WWE could endure when anchored by one man who refused to compromise. He was a part of the brand that was necessary. He took up a mantle, one that presented itself as desirable, but was paired with an incredible cost. This is why his retirement isn’t normal. It’s the end of one of the greatest stories ever told in a professional sport. Very few have ever walked in shoes like these and got their chance to leave gracefully.

John Cena’s Comic Book Saga

Cena’s career has been full of larger-than-life matchups. His rivalry with Edge was chaos against order. His feud with CM Punk was establishment against revolution. His battles with The Rock were staged like crossover summer blockbusters. Each pairing carried meaningful stakes with them and they all contributed to his larger mythology.

The nickname “Super Cena” was not wrong. Fans were correctly identifying the archetype Cena portrayed even as they resisted it. They wanted him, but only on their terms. Still, Cena’s presence kept the company intact. He was a total performer who was shouldering complex burdens: headlining pay-per-views, filming charity spots, handling endless media, and wrestling night after night with the same effort. He was important not just because of championships, but because of his endurance too. And he never became nasty and resentful after fulfilling his duties time and time again. He just kept going. That is the essence of a hero and someone who deserves their endless flowers.

For years, Cena was defined by rejection. Now, arenas thunder in gratitude. The same fans who once booed him for being too perfect now recognize that he was a special talent the likes of which they may never see again.

Cena’s final appearances have electrified crowds because of the weight of finality. The sight of him saluting at the top of the ramp has regained its luster. They are the last frames of a story that has been building for as long as some can even remember. Every word he has spoken has landed differently, laced with subtle hints of his legacy and of his goodbye.

Wrestlepalooza, WWE’s first under the TKO banner, highlights Cena’s place in the company and the need to have someone ready to be their franchise player who provides continuity while Cena provides closure. The speculation over his final opponent now feels less like booking chatter and more like mythology being written in real time. If Orton is the rival who defines his arc, if Roman Reigns is the franchise who succeeded him, or if a younger talent is chosen to stand across from him, the choice will symbolize more than a match. It will represent the final page and hopefully the passing of the torch to the new standard bearer and generational talent for the next 20 years.

Cena’s last appearance on the Friday Night Smackdown brand is on the same show and in the same building where he made his debut against Kurt Angle in 2002: Chicago’s Allstate Arena. The setting is the final metamorphosis of a hero’s journey that’s been unfolding throughout the years. The return there more than two decades later, at the close of his career, transforms September 5, 2025 into something larger than nostalgia. It becomes sacred ground where Cena and his audience can share in closure together.

As this chapter closes, Cena doesn’t just leave behind championships or catchphrases. With his retirement ends the last great story of the PG Era, an entire era of professional wrestling that he carried through sheer stamina, consistency, and sacrifice. And for once, in both WWE and Hollywood, the world seems ready to admit they had been watching a superhero all along.

The post John Cena’s Retirement Is the Final Chapter of a Superhero Story appeared first on Den of Geek.

John Cena’s Retirement Is the Final Chapter of a Superhero Story

Since 2002, John Cena embodied a mythos usually reserved for comic book characters. Now his wrestling retirement run has felt less like a farewell and more like the final act of a saga that has spanned across different timelines. It’s a significant event that challenges everyone who has been on this journey with him to […]

The post John Cena’s Retirement Is the Final Chapter of a Superhero Story appeared first on Den of Geek.

Since 2002, John Cena embodied a mythos usually reserved for comic book characters. Now his wrestling retirement run has felt less like a farewell and more like the final act of a saga that has spanned across different timelines. It’s a significant event that challenges everyone who has been on this journey with him to appreciate everything he’s done and who he was for the business of professional wrestling as WWE continues to reinvent itself.

What makes the timing interesting is the irony of Cena closing the door on his run as WWE’s enduring superhero, while having begun a new start as another one in an entirely new universe. When James Gunn cast the wrestler as Chris Smith a.k.a. Peacemaker in The Suicide Squad, he placed Cena in a role that he was already prepared for. That’s because his career mirrored the very person that he was tasked to portray. He embodied the same duality and complexity in the WWE that Peacemaker carries in the DC Universe. 

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

}).render(“0270c398a82f44f49c23c16122516796”);
});

Cena’s on-screen evolution in Hollywood became a reinforcement of what wrestling was already writing about him out in the open. In WWE’s case, it was him holding up the company on his back when legacy fans were turning away from the product. For DC, it’s Christopher Smith’s pursuit of justice by any means that led him to reach absolution. And like WWE, James Gunn saw something in Cena’s ability to be a main character as he sought to rewrite the perception of DC, helping turn Cena into the kind of critically-acclaimed actor that had been just out of reach as he pursued Hollywood.

Peacemaker’s contradictions, his earnestness and sincerity that collides with violence and absurdity is the very paradox that defined Cena’s in-ring career. His retirement run and Peacemaker trajectory aren’t separate stories. They are the same legend told in different mediums. He was the WWE’s misunderstood hero and is now the DC Universe’s misunderstood hero too. Both have an origin story. Cena’s began a few short years after the world entered into the year 2000 in a squared-circle. 

The New Millenium’s Superhero

The wrestling industry is as fickle as the careers inside of it. Stars can rise or vanish almost overnight. Cena’s debut in June 2002 against Kurt Angle could have been pulled directly from the splash page of a graphic novel. Fans watched a confident rookie shout “ruthless aggression” before putting on a now-legendary match with one of the company’s most decorated performers. It was a dynamic introduction, but nobody could have predicted that Cena would become the company’s most notable standard-bearer for the next two decades, even if this moment all but signaled their belief in him.

What made his arrival more poignant was its timing. That debut came less than a year after the September 11 attacks, a moment when wrestling, like much of the United States, was searching for optimism and a renewed sense of national spirit. WWE leaned heavily on patriotic storytelling throughout 2001 and 2002 and is famously known as the first public gathering broadcast after the attacks. However, with tragedy looming over the country as a whole, the search for a new and fresh face that could transform into their vessel of American resilience. 

Cena fit that mold and his cleancut look would be paired with a military salute, the mantra of “Hustle, Loyalty, Respect” that reflected the core values of America, and was presented as an underdog who would, “Never Give Up.” He also frequently started wearing camouflage gear and was booked in roles that cast him as the face of American perseverance. In many ways, he was looked to as WWE’s soldier for the company. He was a direct contrast of the dying Attitude Era when the company wanted to tone down their edge in the midst of crisis and rebrand into a company that was centered around stability and hope through a main character.

To this day, Cena is still the gravitational center of WWE. He survived shifts in leadership, cultural changes, and fan rebellions, carrying the company on his back during its most fragile transitions. He was always their lightning rod, their anchor, and much more than a reliable hand. He was the hand.

Cena’s retirement arc supersedes nostalgia. It is a resolution. It reads like the last issue of a long-running comic book, where every single moment suddenly connects as one. This completes the superhero story wrestling had been writing about him in plain sight since the beginning.

Hero of The PG Era

In 2008, when WWE fully embraced PG programming, the company needed more than a figurehead. They needed someone who could withstand scrutiny and embody stability. Cena became that figure, wholesome and endlessly promotable, the brand’s most visible face.

That shift was monumental. The Attitude Era took liberties with raunchiness, blood, swearing, and antiheroes like Stone Cold Steve Austin and now, that excess was gone. In its place came a more family-friendly storytelling, partnership-focused vision from the top of the company. This brought in collaborations with entities like Mattel and Post Consumer Brands. Sponsorships and a sudden uptick in mainstream appeal triggered one of the loudest fan rebellions in wrestling history. Die-hards rejected the tamer product typified by Cena, and crowds responded in person. They threw his shirts back at him, brought signs with them that said things like, “If Cena Wins, We Riot.” They cheered the bad guys, hijacked his promos, and filled arenas with chants like, “You can’t wrestle.” Fans directed their frustration at the man they believed was the herald of this new direction. 

Anti-Cena sentiment wasn’t fringe. It was common and he took the brunt of every grievance that had been building between the audience and the business. The people wanted rebellion and they got respectability instead. Below the surface, this was a chaotic time, but Cena was still there, standing as a constant through it all. 

Very few people in modern entertainment can say they worked seven days a week. Cena did. For more than a decade, he lived a punishing schedule that saw him wrestle more than 250 nights a year, travel internationally, appear at live events, headline television and pay-per-views, and still manage early morning talk shows and late-night interviews. On top of that, he became the most requested celebrity for Make-A-Wish, granting more than 650 wishes and setting a record no one has come close to. His life was relentless, structured almost entirely around WWE’s demands, and yet he carried that responsibility without faltering. He never once complained. He always showed up. He worked through injuries and gave his best day in and day out.

His presence was not only cultural, but financial. In 2018, Cena was working part-time and only second to Roman Reigns in sales. He headlined more pay-per-views than anyone else in company history and was a ratings stabilizer when Monday Night Raw was averaging around 3.5 million weekly viewers. During that run, WWE’s annual revenue climbed from roughly $485 million in 2007 to $729 million in 2016, with live event gates and merchandise sales strongly tied to Cena’s drawing power.

Streaming numbers proved his drawing power too. Cena’s 2021 return to face Roman Reigns in the main event of SummerSlam drove the occasion to become the most-watched SummerSlam in WWE history on Peacock at the time. His 2023 SmackDown comeback in September led to one of the brand’s largest viewership surges of that year. Cena’s presence produced measurable business lifts.

Fans, however, didn’t appreciate how those numbers translated into their experience and often did not care to see the superhero either. What was happening on camera wasn’t the shock and awe or the edge that they demanded. At that very moment, antiheroes were dominating pop culture and Cena’s squeaky-clean persona was unwelcome. Events rang with chants of “Cena sucks.” He faced continuous criticism of his wrestling ability and his infamous “Five Moves of Doom” and promos that sounded almost too good. He never bent. He walked into the fire every night, in the midst of a brutal and grueling schedule that preceded his appearances and waited for him afterwards. He became Superman made flesh onscreen and off of it too, when the world thought they wanted him to change and be something different.

His rivalry with Randy Orton became the backbone of the PG Era, a battle of morality against rebellion that proved WWE could endure when anchored by one man who refused to compromise. He was a part of the brand that was necessary. He took up a mantle, one that presented itself as desirable, but was paired with an incredible cost. This is why his retirement isn’t normal. It’s the end of one of the greatest stories ever told in a professional sport. Very few have ever walked in shoes like these and got their chance to leave gracefully.

John Cena’s Comic Book Saga

Cena’s career has been full of larger-than-life matchups. His rivalry with Edge was chaos against order. His feud with CM Punk was establishment against revolution. His battles with The Rock were staged like crossover summer blockbusters. Each pairing carried meaningful stakes with them and they all contributed to his larger mythology.

The nickname “Super Cena” was not wrong. Fans were correctly identifying the archetype Cena portrayed even as they resisted it. They wanted him, but only on their terms. Still, Cena’s presence kept the company intact. He was a total performer who was shouldering complex burdens: headlining pay-per-views, filming charity spots, handling endless media, and wrestling night after night with the same effort. He was important not just because of championships, but because of his endurance too. And he never became nasty and resentful after fulfilling his duties time and time again. He just kept going. That is the essence of a hero and someone who deserves their endless flowers.

For years, Cena was defined by rejection. Now, arenas thunder in gratitude. The same fans who once booed him for being too perfect now recognize that he was a special talent the likes of which they may never see again.

Cena’s final appearances have electrified crowds because of the weight of finality. The sight of him saluting at the top of the ramp has regained its luster. They are the last frames of a story that has been building for as long as some can even remember. Every word he has spoken has landed differently, laced with subtle hints of his legacy and of his goodbye.

Wrestlepalooza, WWE’s first under the TKO banner, highlights Cena’s place in the company and the need to have someone ready to be their franchise player who provides continuity while Cena provides closure. The speculation over his final opponent now feels less like booking chatter and more like mythology being written in real time. If Orton is the rival who defines his arc, if Roman Reigns is the franchise who succeeded him, or if a younger talent is chosen to stand across from him, the choice will symbolize more than a match. It will represent the final page and hopefully the passing of the torch to the new standard bearer and generational talent for the next 20 years.

Cena’s last appearance on the Friday Night Smackdown brand is on the same show and in the same building where he made his debut against Kurt Angle in 2002: Chicago’s Allstate Arena. The setting is the final metamorphosis of a hero’s journey that’s been unfolding throughout the years. The return there more than two decades later, at the close of his career, transforms September 5, 2025 into something larger than nostalgia. It becomes sacred ground where Cena and his audience can share in closure together.

As this chapter closes, Cena doesn’t just leave behind championships or catchphrases. With his retirement ends the last great story of the PG Era, an entire era of professional wrestling that he carried through sheer stamina, consistency, and sacrifice. And for once, in both WWE and Hollywood, the world seems ready to admit they had been watching a superhero all along.

The post John Cena’s Retirement Is the Final Chapter of a Superhero Story appeared first on Den of Geek.

Mediterranean Mega Fires Burn Record Land as Climate Change Fuels Extreme Heat and Drought

Firefighters in Europe At the start of August, wildfires exploded across the Mediterranean basin, fueled by a wicked trio of extreme heat, drought and wind. In southern France, the Aude region around Carcassonne saw the country’s largest blaze since 1949, burning more than 16,000 hectares. In Spain, a 16-day heatwave — described by the national […]

The post Mediterranean Mega Fires Burn Record Land as Climate Change Fuels Extreme Heat and Drought appeared first on Green Prophet.

Mediterranean Mega Fires Burn Record Land as Climate Change Fuels Extreme Heat and Drought

Firefighters in Europe

At the start of August, wildfires exploded across the Mediterranean basin, fueled by a wicked trio of extreme heat, drought and wind. In southern France, the Aude region around Carcassonne saw the country’s largest blaze since 1949, burning more than 16,000 hectares. In Spain, a 16-day heatwave — described by the national weather service as the most intense on record — set the stage for weeks of fire in the northwest near Zamora.

Greece endured simultaneous outbreaks around Patras, several Ionian islands, and Chios; satellites showed ~100,000 acres burned in just two days. By early September, the EU’s science hub estimated roughly one million hectares scorched across Europe in 2025 — an area bigger than Cyprus — with emissions and fire counts well above last year.

This isn’t just “bad luck.” Rapid attribution studies from World Weather Attribution find that the specific cocktail of hot, dry and windy weather that supercharged fires in Türkiye, Greece and Cyprus this summer is ~10 times more likely because of human-caused climate change. A separate WWA analysis shows extreme fire weather in Spain and Portugal is now effectively “common” in a warming world — a grim new baseline we’ll have to plan around, not a blip we can just ride out.

What it feels like on the ground

Fires today don’t behave like the fires our grandparents knew. Structures ignite faster; smoke is a toxic stew; embers leap roads like they weren’t even there. Our own reporting on smoke’s health harms — even from far-away blazes — is sobering: see how wildfire smoke damages lungs and hearts.

In Israel, we’ve documented both the on-the-line response and long-tail recovery, from front-line firefighting and evacuations to lessons from the Carmel blaze a decade ago — when, counter-intuitively, letting nature lead regrowth proved wiser than rushing in with well-meant tree plantings.

A warmer Mediterranean from climate change means longer fire seasons, drier fuels and stronger heat waves. We’ve reported on this shift for years — from early signals of Mediterranean winter drought trends to the uncomfortable truth that it’s not “just warming” but global scorching.

Add land-use change — abandoned farms, flammable plantations, dense edge housing — and fires spread faster and hit more people. Meanwhile, climate whiplash is reshaping risk across our region; the same storm systems that flood deserts are part of a new normal we covered in MENA’s flash-flood wave.

What we can do next (like, starting yesterday)

Prevention isn’t sexy, but it works. We can make homes less flammable, communities more prepared, and landscapes less primed to explode. That looks like smarter codes and materials — even bio-based ones. Our look at hemp-lime blocks found they smolder slowly and hold structure in fire tests,buying valuable minutes for firefighters  and families alike. For deeper resilience, check out Earthship-style off-grid homes that reduce dependence on fragile grids when heat waves knock power and comms offline.

We also need to treat mental resilience as climate infrastructure. Neighborhood-scale actions can ease eco-anxiety while cutting risk: placemaking to build social ties, shrinking our personal footprints, and backing projects that restore ecosystems at scale — from community-led reforestation in Iran to ambitious corporate pledges like doTERRA’s native tree plantings in Hawaii.

Policy matters too — and we’ll keep holding leaders to account (see our coverage of health-protective climate rules).

What Green Prophet readers can do

Feeling overwhelmed is normal, but it’s not the end of the story. Start where you live: create defensible space (clear brush, prune trees), swap to ember-resistant vents, and ask your city for shaded “cool corridors” and community fire drills. Learn the health basics for smoky days (N95s > cloth masks), keep HEPA purifiers on hand, and check in on elders and neighbors. Put your money and voice behind solutions: fund local ecological grazing and prescribed burns; back nature-positive jobs; and push for serious climate policy, not just slogans.

And yes, keep sharing rigorous reporting — amplify scientists, firefighters, and the communities living on the frontlines. Together, we can make the next fire season a little less brutal, and a little more survivable. Even small steps add up, promise.

The post Mediterranean Mega Fires Burn Record Land as Climate Change Fuels Extreme Heat and Drought appeared first on Green Prophet.

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.

Asynchronous Design Critique: Getting Feedback

“Any comment?” is probably one of the worst ways to ask for feedback. It’s vague and open ended, and it doesn’t provide any indication of what we’re looking for. Getting good feedback starts earlier than we might expect: it starts with the request. 

It might seem counterintuitive to start the process of receiving feedback with a question, but that makes sense if we realize that getting feedback can be thought of as a form of design research. In the same way that we wouldn’t do any research without the right questions to get the insights that we need, the best way to ask for feedback is also to craft sharp questions.

Design critique is not a one-shot process. Sure, any good feedback workflow continues until the project is finished, but this is particularly true for design because design work continues iteration after iteration, from a high level to the finest details. Each level needs its own set of questions.

And finally, as with any good research, we need to review what we got back, get to the core of its insights, and take action. Question, iteration, and review. Let’s look at each of those.

The question

Being open to feedback is essential, but we need to be precise about what we’re looking for. Just saying “Any comment?”, “What do you think?”, or “I’d love to get your opinion” at the end of a presentation—whether it’s in person, over video, or through a written post—is likely to get a number of varied opinions or, even worse, get everyone to follow the direction of the first person who speaks up. And then… we get frustrated because vague questions like those can turn a high-level flows review into people instead commenting on the borders of buttons. Which might be a hearty topic, so it might be hard at that point to redirect the team to the subject that you had wanted to focus on.

But how do we get into this situation? It’s a mix of factors. One is that we don’t usually consider asking as a part of the feedback process. Another is how natural it is to just leave the question implied, expecting the others to be on the same page. Another is that in nonprofessional discussions, there’s often no need to be that precise. In short, we tend to underestimate the importance of the questions, so we don’t work on improving them.

The act of asking good questions guides and focuses the critique. It’s also a form of consent: it makes it clear that you’re open to comments and what kind of comments you’d like to get. It puts people in the right mental state, especially in situations when they weren’t expecting to give feedback.

There isn’t a single best way to ask for feedback. It just needs to be specific, and specificity can take many shapes. A model for design critique that I’ve found particularly useful in my coaching is the one of stage versus depth.

Stage” refers to each of the steps of the process—in our case, the design process. In progressing from user research to the final design, the kind of feedback evolves. But within a single step, one might still review whether some assumptions are correct and whether there’s been a proper translation of the amassed feedback into updated designs as the project has evolved. A starting point for potential questions could derive from the layers of user experience. What do you want to know: Project objectives? User needs? Functionality? Content? Interaction design? Information architecture? UI design? Navigation design? Visual design? Branding?

Here’re a few example questions that are precise and to the point that refer to different layers:

  • Functionality: Is automating account creation desirable?
  • Interaction design: Take a look through the updated flow and let me know whether you see any steps or error states that I might’ve missed.
  • Information architecture: We have two competing bits of information on this page. Is the structure effective in communicating them both?
  • UI design: What are your thoughts on the error counter at the top of the page that makes sure that you see the next error, even if the error is out of the viewport? 
  • Navigation design: From research, we identified these second-level navigation items, but once you’re on the page, the list feels too long and hard to navigate. Are there any suggestions to address this?
  • Visual design: Are the sticky notifications in the bottom-right corner visible enough?

The other axis of specificity is about how deep you’d like to go on what’s being presented. For example, we might have introduced a new end-to-end flow, but there was a specific view that you found particularly challenging and you’d like a detailed review of that. This can be especially useful from one iteration to the next where it’s important to highlight the parts that have changed.

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

A simple trick is to remove generic qualifiers from your questions like “good,” “well,” “nice,” “bad,” “okay,” and “cool.” For example, asking, “When the block opens and the buttons appear, is this interaction good?” might look specific, but you can spot the “good” qualifier, and convert it to an even better question: “When the block opens and the buttons appear, is it clear what the next action is?”

Sometimes we actually do want broad feedback. That’s rare, but it can happen. 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 maybe just say, “At first glance, what do you think?” so that it’s clear that what you’re asking is open ended but focused on someone’s impression after their first five seconds of looking at it.

Sometimes the project is particularly expansive, and some areas may have already been explored in detail. In these situations, it might be useful to explicitly say that some parts are already locked in and aren’t open to feedback. It’s not something that I’d recommend in general, but I’ve found it useful to avoid falling again into rabbit holes of the sort that might lead to further refinement but aren’t what’s most important right now.

Asking specific questions can completely change the quality of the feedback that you receive. People with less refined critique skills will now be able to offer more actionable feedback, and even expert designers will welcome the clarity and efficiency that comes from focusing only on what’s needed. It can save a lot of time and frustration.

The iteration

Design iterations are probably the most visible part of the design work, and they provide a natural checkpoint for feedback. Yet a lot of design tools with inline commenting tend to show changes as a single fluid stream in the same file, and those types of design tools make conversations disappear once they’re resolved, update shared UI components automatically, and compel designs to always show the latest version—unless these would-be helpful features were to be manually turned off. 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’s probably not the best way to approach design critiques, but even if I don’t want to be too prescriptive here: that could work for some teams.

The asynchronous design-critique approach that I find most effective is to create explicit checkpoints for discussion. I’m going to use the term iteration post for this. It refers to a write-up or presentation of the design iteration followed by a discussion thread of some kind. Any platform that can accommodate this structure can use this. 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 many advantages:

  • It creates a rhythm in the design work so that the designer can review feedback from each iteration and prepare for the next.
  • It makes decisions visible for future review, and conversations are likewise always available.
  • It creates a record of how the design changed over time.
  • Depending on the tool, it might also make it easier to collect feedback and act on it.

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 other feedback approaches (such as live critique, pair designing, or inline comments) can build from there.

I don’t think there’s a standard format for iteration posts. But there are a few high-level elements that make sense to include as a baseline:

  1. The goal
  2. The design
  3. The list of changes
  4. The questions

Each project is likely to have a goal, and hopefully it’s something that’s already been summarized in a single sentence somewhere else, such as the client brief, the product manager’s outline, or the project owner’s request. So this is something that I’d repeat in every iteration post—literally copy and pasting it. The idea is to provide context and to repeat what’s essential to make each iteration post complete so that there’s no need to find information spread across multiple posts. If I want to know about the latest design, the latest iteration post will have all that I need.

This copy-and-paste part introduces another relevant concept: alignment comes from repetition. So having posts that repeat information is actually very effective toward making sure that everyone is on the same page.

The design is then the actual series of information-architecture outlines, diagrams, flows, maps, wireframes, screens, visuals, and any other kind of design work that’s been done. In short, it’s any design artifact. For the final stages of work, I prefer the term blueprint to emphasize that I’ll be showing full flows instead of individual screens to make it easier to understand the bigger picture. 

It can also be useful to label the artifacts with clear titles because that can make it easier to refer to them. Write the post in a way that helps people understand the work. It’s not too different from organizing a good live presentation. 

For an efficient discussion, you should also include a bullet list of the changes from the previous iteration to let people focus on what’s new, which can be especially useful for larger pieces of work where keeping track, iteration after iteration, could become a challenge.

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. Doing this as a numbered list can also help make it easier to refer to each question by its number.

Not all iterations are 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 start settling on a solution and refining it until the design process reaches its end and the feature ships.

I want to highlight that even if these iteration posts are written and conceived as checkpoints, by no means do they need 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.

Over time, I also started using specific labels for incremental iterations: i1, i2, i3, and so on. This might look like a minor labelling tip, but it can help in multiple ways:

  • Unique—It’s a clear unique marker. Within each project, one can easily say, “This was discussed in i4,” and everyone knows where they can go to review things.
  • Unassuming—It works like versions (such as v1, v2, and v3) but in contrast, versions create the impression of something that’s big, exhaustive, and complete. Iterations must be able to be exploratory, incomplete, partial.
  • Future proof—It resolves the “final” naming problem that you can run into with versions. No more files named “final final complete no-really-its-done.” Within each project, the largest number always represents the latest iteration.

To mark when a design is complete enough to be worked on, even if there might be some bits still in need of attention and in turn more iterations needed, the wording release candidate (RC) could be used to describe it: “with i8, we reached RC” or “i12 is an RC.”

The review

What usually happens during a design critique is an open discussion, with a back and forth between people that can be very productive. This approach is particularly effective during live, synchronous feedback. But when we work asynchronously, it’s more effective to use a different approach: we can shift to 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.

This shift has some major benefits that make asynchronous feedback particularly effective, especially around these friction points:

  1. It removes the pressure to reply to everyone.
  2. It reduces the frustration from swoop-by comments.
  3. It lessens our personal stake.

The first friction point is feeling a pressure to reply to every single comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s easy, and it doesn’t feel like a problem. But other times, some solutions might require more in-depth discussions, and the amount of replies can quickly increase, which can create a tension between trying to be a good team player by replying to everyone and doing 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. We need to accept that this pressure is absolutely normal, and it’s human nature to try to accommodate people who we care about. Sometimes replying to all comments can be effective, but if we treat a design critique more like user research, we realize that we don’t have to reply to every comment, and in asynchronous spaces, there are alternatives:

  • One is to let the next iteration speak for itself. When the design evolves and we post a follow-up iteration, that’s the reply. You might tag all the people who were involved in the previous discussion, but even that’s 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. I’ll include these in the next iteration.” 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!”
  • Another is to provide a quick summary of the comments before moving on. Depending on your workflow, this can be particularly useful as it can provide a simplified checklist that you can then use for the next 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. On their side, there’s something that one can hope that they might learn: they could start to acknowledge that they’re doing this and they could be more conscious in outlining where they’re coming from. Swoop-by comments often trigger the simple thought “We’ve already discussed this…”, and it can be frustrating to have to repeat the same reply over and over.

Let’s begin by acknowledging again that there’s no need to reply to every comment. If, however, replying to a previously litigated point might be useful, a short reply with a link to the previous discussion for extra details is usually enough. Remember, alignment comes from repetition, so it’s okay to repeat things sometimes!

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. Sure, you’ll still be frustrated, but that might at least help in dealing with it.

The third friction point is the personal stake we could have with the design, which could make us feel defensive if the review were to feel more like 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 ultimately, treating everything in aggregated form allows us to better prioritize our work.

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

As the designer leading the project, you’re in charge of that decision. Ultimately, everyone has their specialty, and as the designer, you’re the one who has the most knowledge and the most context to make the right decision. 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 Brie Anne Demkiw and Mike Shelton for reviewing the first draft of this article.

Designing for the Unexpected

I’m not sure when I first heard this quote, but it’s something that has stayed with me over the years. How do you create services for situations you can’t imagine? Or design products that work on devices yet to be invented?

Flash, Photoshop, and responsive design

When I first started designing websites, my go-to software was Photoshop. I created a 960px canvas and set about creating a layout that I would later drop content in. The development phase was about attaining pixel-perfect accuracy using fixed widths, fixed heights, and absolute positioning.

Ethan Marcotte’s talk at An Event Apart and subsequent article “Responsive Web Design” in A List Apart in 2010 changed all this. I was sold on responsive design as soon as I heard about it, but I was also terrified. The pixel-perfect designs full of magic numbers that I had previously prided myself on producing were no longer good enough.

The fear wasn’t helped by my first experience with responsive design. My first project was to take an existing fixed-width website and make it responsive. What I learned the hard way was that you can’t just add responsiveness at the end of a project. To create fluid layouts, you need to plan throughout the design phase.

A new way to design

Designing responsive or fluid sites has always been about removing limitations, producing content that can be viewed on any device. It relies on the use of percentage-based layouts, which I initially achieved with native CSS and utility classes:

.column-span-6 {
  width: 49%;
  float: left;
  margin-right: 0.5%;
  margin-left: 0.5%;
}


.column-span-4 {
  width: 32%;
  float: left;
  margin-right: 0.5%;
  margin-left: 0.5%;
}

.column-span-3 {
  width: 24%;
  float: left;
  margin-right: 0.5%;
  margin-left: 0.5%;
}

Then with Sass so I could take advantage of @includes to re-use repeated blocks of code and move back to more semantic markup:

.logo {
  @include colSpan(6);
}

.search {
  @include colSpan(3);
}

.social-share {
  @include colSpan(3);
}

Media queries

The second ingredient for responsive design is media queries. Without them, content would shrink to fit the available space regardless of whether that content remained readable (The exact opposite problem occurred with the introduction of a mobile-first approach).

Media queries prevented this by allowing us to add breakpoints where the design could adapt. Like most people, I started out with three breakpoints: one for desktop, one for tablets, and one for mobile. Over the years, I added more and more for phablets, wide screens, and so on. 

For years, I happily worked this way and improved both my design and front-end skills in the process. The only problem I encountered was making changes to content, since with our Sass grid system in place, there was no way for the site owners to add content without amending the markup—something a small business owner might struggle with. This is because each row in the grid was defined using a div as a container. Adding content meant creating new row markup, which requires a level of HTML knowledge.

Row markup was a staple of early responsive design, present in all the widely used frameworks like Bootstrap and Skeleton.

1 of 7
2 of 7
3 of 7
4 of 7
5 of 7
6 of 7
7 of 7

Another problem arose as I moved from a design agency building websites for small- to medium-sized businesses, to larger in-house teams where I worked across a suite of related sites. In those roles I started to work much more with reusable components. 

Our reliance on media queries resulted in components that were tied to common viewport sizes. If the goal of component libraries is reuse, then this is a real problem because you can only use these components if the devices you’re designing for correspond to the viewport sizes used in the pattern library—in the process not really hitting that “devices that don’t yet exist”  goal.

Then there’s the problem of space. Media queries allow components to adapt based on the viewport size, but what if I put a component into a sidebar, like in the figure below?

Container queries: our savior or a false dawn?

Container queries have long been touted as an improvement upon media queries, but at the time of writing are unsupported in most browsers. There are JavaScript workarounds, but they can create dependency and compatibility issues. The basic theory underlying container queries is that elements should change based on the size of their parent container and not the viewport width, as seen in the following illustrations.

One of the biggest arguments in favor of container queries is that they help us create components or design patterns that are truly reusable because they can be picked up and placed anywhere in a layout. This is an important step in moving toward a form of component-based design that works at any size on any device.

In other words, responsive components to replace responsive layouts.

Container queries will help us move from designing pages that respond to the browser or device size to designing components that can be placed in a sidebar or in the main content, and respond accordingly.

My concern is that we are still using layout to determine when a design needs to adapt. This approach will always be restrictive, as we will still need pre-defined breakpoints. For this reason, my main question with container queries is, How would we decide when to change the CSS used by a component? 

A component library removed from context and real content is probably not the best place for that decision. 

As the diagrams below illustrate, we can use container queries to create designs for specific container widths, but what if I want to change the design based on the image size or ratio?

In this example, the dimensions of the container are not what should dictate the design; rather, the image is.

It’s hard to say for sure whether container queries will be a success story until we have solid cross-browser support for them. Responsive component libraries would definitely evolve how we design and would improve the possibilities for reuse and design at scale. But maybe we will always need to adjust these components to suit our content.

CSS is changing

Whilst the container query debate rumbles on, there have been numerous advances in CSS that change the way we think about design. The days of fixed-width elements measured in pixels and floated div elements used to cobble layouts together are long gone, consigned to history along with table layouts. Flexbox and CSS Grid have revolutionized layouts for the web. We can now create elements that wrap onto new rows when they run out of space, not when the device changes.

.wrapper {
  display: grid;
  grid-template-columns: repeat(auto-fit, 450px);
  gap: 10px;
}

The repeat() function paired with auto-fit or auto-fill allows us to specify how much space each column should use while leaving it up to the browser to decide when to spill the columns onto a new line. Similar things can be achieved with Flexbox, as elements can wrap over multiple rows and “flex” to fill available space. 

.wrapper {
  display: flex;
  flex-wrap: wrap;
  justify-content: space-between;
}

.child {
  flex-basis: 32%;
  margin-bottom: 20px;
}

The biggest benefit of all this is you don’t need to wrap elements in container rows. Without rows, content isn’t tied to page markup in quite the same way, allowing for removals or additions of content without additional development.

This is a big step forward when it comes to creating designs that allow for evolving content, but the real game changer for flexible designs is CSS Subgrid. 

Remember the days of crafting perfectly aligned interfaces, only for the customer to add an unbelievably long header almost as soon as they’re given CMS access, like the illustration below?

Subgrid allows elements to respond to adjustments in their own content and in the content of sibling elements, helping us create designs more resilient to change.

.wrapper {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(150px, 1fr));
     grid-template-rows: auto 1fr auto;
  gap: 10px;
}

.sub-grid {
  display: grid;
  grid-row: span 3;
  grid-template-rows: subgrid; /* sets rows to parent grid */
}

CSS Grid allows us to separate layout and content, thereby enabling flexible designs. Meanwhile, Subgrid allows us to create designs that can adapt in order to suit morphing content. Subgrid at the time of writing is only supported in Firefox but the above code can be implemented behind an @supports feature query. 

Intrinsic layouts 

I’d be remiss not to mention intrinsic layouts, the term created by Jen Simmons to describe a mixture of new and old CSS features used to create layouts that respond to available space. 

Responsive layouts have flexible columns using percentages. Intrinsic layouts, on the other hand, use the fr unit to create flexible columns that won’t ever shrink so much that they render the content illegible.

fr units is a way to say I want you to distribute the extra space in this way, but…don’t ever make it smaller than the content that’s inside of it.

—Jen Simmons, “Designing Intrinsic Layouts”

Intrinsic layouts can also utilize a mixture of fixed and flexible units, allowing the content to dictate the space it takes up.

What makes intrinsic design stand out is that it not only creates designs that can withstand future devices but also helps scale design without losing flexibility. Components and patterns can be lifted and reused without the prerequisite of having the same breakpoints or the same amount of content as in the previous implementation. 

We can now create designs that adapt to the space they have, the content within them, and the content around them. With an intrinsic approach, we can construct responsive components without depending on container queries.

Another 2010 moment?

This intrinsic approach should in my view be every bit as groundbreaking as responsive web design was ten years ago. For me, it’s another “everything changed” moment. 

But it doesn’t seem to be moving quite as fast; I haven’t yet had that same career-changing moment I had with responsive design, despite the widely shared and brilliant talk that brought it to my attention. 

One reason for that could be that I now work in a large organization, which is quite different from the design agency role I had in 2010. In my agency days, every new project was a clean slate, a chance to try something new. Nowadays, projects use existing tools and frameworks and are often improvements to existing websites with an existing codebase. 

Another could be that I feel more prepared for change now. In 2010 I was new to design in general; the shift was frightening and required a lot of learning. Also, an intrinsic approach isn’t exactly all-new; it’s about using existing skills and existing CSS knowledge in a different way. 

You can’t framework your way out of a content problem

Another reason for the slightly slower adoption of intrinsic design could be the lack of quick-fix framework solutions available to kick-start the change. 

Responsive grid systems were all over the place ten years ago. With a framework like Bootstrap or Skeleton, you had a responsive design template at your fingertips.

Intrinsic design and frameworks do not go hand in hand quite so well because the benefit of having a selection of units is a hindrance when it comes to creating layout templates. The beauty of intrinsic design is combining different units and experimenting with techniques to get the best for your content.

And then there are design tools. We probably all, at some point in our careers, used Photoshop templates for desktop, tablet, and mobile devices to drop designs in and show how the site would look at all three stages.

How do you do that now, with each component responding to content and layouts flexing as and when they need to? This type of design must happen in the browser, which personally I’m a big fan of. 

The debate about “whether designers should code” is another that has rumbled on for years. When designing a digital product, we should, at the very least, design for a best- and worst-case scenario when it comes to content. To do this in a graphics-based software package is far from ideal. In code, we can add longer sentences, more radio buttons, and extra tabs, and watch in real time as the design adapts. Does it still work? Is the design too reliant on the current content?

Personally, I look forward to the day intrinsic design is the standard for design, when a design component can be truly flexible and adapt to both its space and content with no reliance on device or container dimensions.

Content first 

Content is not constant. After all, to design for the unknown or unexpected we need to account for content changes like our earlier Subgrid card example that allowed the cards to respond to adjustments to their own content and the content of sibling elements.

Thankfully, there’s more to CSS than layout, and plenty of properties and values can help us put content first. Subgrid and pseudo-elements like ::first-line and ::first-letter help to separate design from markup so we can create designs that allow for changes.

Instead of old markup hacks like this—

First line of text with different styling...

—we can target content based on where it appears.

.element::first-line {
  font-size: 1.4em;
}

.element::first-letter {
  color: red;
}

Much bigger additions to CSS include logical properties, which change the way we construct designs using logical dimensions (start and end) instead of physical ones (left and right), something CSS Grid also does with functions like min(), max(), and clamp().

This flexibility allows for directional changes according to content, a common requirement when we need to present content in multiple languages. In the past, this was often achieved with Sass mixins but was often limited to switching from left-to-right to right-to-left orientation.

In the Sass version, directional variables need to be set.

$direction: rtl;
$opposite-direction: ltr;

$start-direction: right;
$end-direction: left;

These variables can be used as values—

body {
  direction: $direction;
  text-align: $start-direction;
}

—or as properties.

margin-#{$end-direction}: 10px;
padding-#{$start-direction}: 10px;

However, now we have native logical properties, removing the reliance on both Sass (or a similar tool) and pre-planning that necessitated using variables throughout a codebase. These properties also start to break apart the tight coupling between a design and strict physical dimensions, creating more flexibility for changes in language and in direction.

margin-block-end: 10px;
padding-block-start: 10px;

There are also native start and end values for properties like text-align, which means we can replace text-align: right with text-align: start.

Like the earlier examples, these properties help to build out designs that aren’t constrained to one language; the design will reflect the content’s needs.

Fixed and fluid 

We briefly covered the power of combining fixed widths with fluid widths with intrinsic layouts. The min() and max() functions are a similar concept, allowing you to specify a fixed value with a flexible alternative. 

For min() this means setting a fluid minimum value and a maximum fixed value.

.element {
  width: min(50%, 300px);
}

The element in the figure above will be 50% of its container as long as the element’s width doesn’t exceed 300px.

For max() we can set a flexible max value and a minimum fixed value.

.element {
  width: max(50%, 300px);
}

Now the element will be 50% of its container as long as the element’s width is at least 300px. This means we can set limits but allow content to react to the available space. 

The clamp() function builds on this by allowing us to set a preferred value with a third parameter. Now we can allow the element to shrink or grow if it needs to without getting to a point where it becomes unusable.

.element {
  width: clamp(300px, 50%, 600px);
}

This time, the element’s width will be 50% (the preferred value) of its container but never less than 300px and never more than 600px.

With these techniques, we have a content-first approach to responsive design. We can separate content from markup, meaning the changes users make will not affect the design. We can start to future-proof designs by planning for unexpected changes in language or direction. And we can increase flexibility by setting desired dimensions alongside flexible alternatives, allowing for more or less content to be displayed correctly.

Situation first

Thanks to what we’ve discussed so far, we can cover device flexibility by changing our approach, designing around content and space instead of catering to devices. But what about that last bit of Jeffrey Zeldman’s quote, “…situations you haven’t imagined”?

It’s a very different thing to design for someone seated at a desktop computer as opposed to someone using a mobile phone and moving through a crowded street in glaring sunshine. Situations and environments are hard to plan for or predict because they change as people react to their own unique challenges and tasks.

This is why choice is so important. One size never fits all, so we need to design for multiple scenarios to create equal experiences for all our users.

Thankfully, there is a lot we can do to provide choice.

Responsible design 

“There are parts of the world where mobile data is prohibitively expensive, and where there is little or no broadband infrastructure.”

I Used the Web for a Day on a 50 MB Budget

Chris Ashton

One of the biggest assumptions we make is that people interacting with our designs have a good wifi connection and a wide screen monitor. But in the real world, our users may be commuters traveling on trains or other forms of transport using smaller mobile devices that can experience drops in connectivity. There is nothing more frustrating than a web page that won’t load, but there are ways we can help users use less data or deal with sporadic connectivity.

The srcset attribute allows the browser to decide which image to serve. This means we can create smaller ‘cropped’ images to display on mobile devices in turn using less bandwidth and less data.

Image alt text

The preload attribute can also help us to think about how and when media is downloaded. It can be used to tell a browser about any critical assets that need to be downloaded with high priority, improving perceived performance and the user experience. 

 
 

There’s also native lazy loading, which indicates assets that should only be downloaded when they are needed.

…

With srcset, preload, and lazy loading, we can start to tailor a user’s experience based on the situation they find themselves in. What none of this does, however, is allow the user themselves to decide what they want downloaded, as the decision is usually the browser’s to make. 

So how can we put users in control?

The return of media queries 

Media queries have always been about much more than device sizes. They allow content to adapt to different situations, with screen size being just one of them.

We’ve long been able to check for media types like print and speech and features such as hover, resolution, and color. These checks allow us to provide options that suit more than one scenario; it’s less about one-size-fits-all and more about serving adaptable content. 

As of this writing, the Media Queries Level 5 spec is still under development. It introduces some really exciting queries that in the future will help us design for multiple other unexpected situations.

For example, there’s a light-level feature that allows you to modify styles if a user is in sunlight or darkness. Paired with custom properties, these features allow us to quickly create designs or themes for specific environments.

@media (light-level: normal) {
  --background-color: #fff;
  --text-color: #0b0c0c;  
}

@media (light-level: dim) {
  --background-color: #efd226;
  --text-color: #0b0c0c;
}

Another key feature of the Level 5 spec is personalization. Instead of creating designs that are the same for everyone, users can choose what works for them. This is achieved by using features like prefers-reduced-data, prefers-color-scheme, and prefers-reduced-motion, the latter two of which already enjoy broad browser support. These features tap into preferences set via the operating system or browser so people don’t have to spend time making each site they visit more usable. 

Media queries like this go beyond choices made by a browser to grant more control to the user.

Expect the unexpected

In the end, the one thing we should always expect is for things to change. Devices in particular change faster than we can keep up, with foldable screens already on the market.

We can’t design the same way we have for this ever-changing landscape, but we can design for content. By putting content first and allowing that content to adapt to whatever space surrounds it, we can create more robust, flexible designs that increase the longevity of our products. 

A lot of the CSS discussed here is about moving away from layouts and putting content at the heart of design. From responsive components to fixed and fluid units, there is so much more we can do to take a more intrinsic approach. Even better, we can test these techniques during the design phase by designing in-browser and watching how our designs adapt in real-time.

When it comes to unexpected situations, we need to make sure our products are usable when people need them, whenever and wherever that might be. We can move closer to achieving this by involving users in our design decisions, by creating choice via browsers, and by giving control to our users with user-preference-based media queries. 

Good design for the unexpected should allow for change, provide choice, and give control to those we serve: our users themselves.