Must-Haves, Moonshots, Minecraft, and Meaty Friendships

Somethings Novel — Issue #23

✍️ Something I’m writing…

Your UX Design EDC (Every Day Carry)
5 Frameworks that will Save Your Butt…and Help You Kick Some

Imagine you’re in a stakeholder meeting explaining your design direction when the questions begin: “Why did you make it this way? I don’t think users want it like that.” And suddenly, you’re stammering about “user experience” while watching your credibility evaporate in real time.

The problem isn’t your talent. No, it’s not even them. It’s your toolkit. Too many designers rely on intuition and gut feeling without the reasoning to back it up. When the pressure’s on, good instincts aren’t enough. You need frameworks that transform how you diagnose problems, explain decisions, and speak the language of strategy.

This article introduces five time-tested frameworks that separate pixel-pushers from strategic partners. Think of it as your professional “every day carry”…the essential tools that help you influence product direction instead of just executing orders.

When stakeholders challenge your decisions, these tools help you calmly explain why your approach reduces user error by 40% and supports the business goal of faster onboarding…not fumble through design-speak.

👉🏻 Read it in 8 minutes

🧐 Something I’m thinking about…

How often do you think about risk tolerance? It’s the invisible (impenetrable) force that shapes all design work, yet most teams never talk about it explicitly…or even consider it in their work.

Does your business want predictable, easy to execute solutions? Or are they truly trying to disrupt and do something completely different? The answer changes everything about how you should approach problem-solving.

Consider the Apollo missions. We put humans on the moon with calculator-level technology through sheer ingenuity, massive investment, and willingness to develop entirely new approaches. In that era, we were even willing to put lives on the line. That’s a lot of risk tolerance. Because America saw the risk of failure as greater than the risk of investing. They had to succeed. That’s what happens when an organization has genuine appetite for breakthrough innovation—they’re willing to invent new technologies, processes, and ways of thinking to reach an impossible goal.

Most businesses say they want innovation, but what they really want is renovation. They’re looking to improve existing experiences, not revolutionize entire industries. And even if they do want radical innovation, they aren’t typically prepared to accept the risk associated with that kind of innovation. And…there’s nothing wrong with that. But as designers, we need to understand where our organization truly sits on this spectrum.

Are they ready to gamble big on uncharted territory, investing in genuinely disruptive solutions that might fail spectacularly? Or are they looking for smart, incremental improvements that reduce risk while moving the needle forward?

Your solution proposals have to match their actual risk tolerance, not their aspirational language about “innovation.” Because designing moonshots for teams that really want a slightly faster engine wastes everyone’s time and burns your credibility.

📚 Something I’m reading…

Minecraft: The Shipwreck
by C. B. Lee

My kids are into Minecraft. And honestly, so am I. There’s something captivating about a game with truly endless creative possibilities. While most of the Minecraft book series ranges from mediocre to surprisingly good, this one came recommended by my kids as one of the better books in the Minecraft series.

Is it an epic tale? No, not really. But, it’s a fun adventure story set in the real world where kids discover a mysterious custom world full of hidden secrets. The writing is easy to read without being overly simplistic, and it captures that sense of discovery and cooperative problem-solving that makes both Minecraft and good design work so compelling.

If you or your kids are into Minecraft, this is a quick, enjoyable read that bridges the gap between screen time and book time.

🔗 Get the book

🤩 Something I’m enjoying…

About once a month, a couple of friends and I get together, sit around a table, and demolish some serious burgers. We call it “Burger Buddies”.

It’s a bit of an unlikely group with different backgrounds and interests, but that’s what makes it so much fun. Our conversations bounce from Sasquatch sightings to UFO theories to deep biblical theology, sometimes all in the span of a few minutes.

There’s something about exploring ideas without judgment that reminds me why diverse perspectives make everything better, whether you’re designing products or debating UFOs. I’m incredibly grateful for the people in my life who make space for both meaningful conversation and completely ridiculous tangents. Plus, the beef and buns definitely grease the conversational wheels.

• • • • •

Yes, I use affiliate links for the products and books I share. Think of it as contributing to the cost of my monthly burger expenses while I write this content in my spare time. Every click helps, and I’m grateful for your support.

Design Endurance, Framework Fundamentals, UFOs, and Mice

Somethings Novel — Issue #22

✍️ Something I’m writing…

Building Design Endurance
What a 58-mile bike ride taught me about thriving in design careers

What does grinding through 58 miles of Ohio countryside on a bike have to do with your design career? More than you'd think. When my legs were screaming at mile 48 and I was questioning my life choices, I discovered five powerful truths about building the kind of endurance that separates thriving designers from those who burn out. From the unexpected power of adding one small word to your vocabulary to why being an encourager actually makes you stronger, these lessons from the saddle will shift how you think about persistence, community, and what it really takes to go the distance in design.

👉🏻 Read it in 9 minutes

🧐 Something I’m thinking about…

Too many designers are riding on empathy with their design decisions. They rely on gut feelings, the lates “best practice" they picked up from a Medium article, or whatever monetized framework they learned in their bootcamp. Then when stakeholders challenge their work, they're left stammering about "user happiness" while everyone else rolls their eyes.

But…we already have objective, time-tested frameworks that work. Frameworks that can hold up under scrutiny and actually persuade people who control budgets and timelines. The problem? Most designers have never heard of them.

Instead of reaching for the latest design fad, what if we grounded our work in principles that have been proven over decades? What if we could walk into any room with the confidence that comes from understanding the fundamentals?

I'm thinking it's time we change that conversation.

📚 Something I’m reading…

Imminent: Inside the Pentagon's Hunt for UFOs
By Luis Elizondo

Growing up watching Star Trek TNG made me wonder about what's really out there among the stars. And, the more I think about it, the government hasn't exactly been in the business of declassifying our most advanced tech since the 60s or 70s, so there's a lot we don't know about how far our technology has actually advanced.

That's part of why UAP (unidentified aerial phenomena) fascinates me. Luis Elizondo gives us a rare insider's look into the Department of Defense's research into these phenomena. The patterns that emerged, the technology that defies our current understanding, the bureaucratic maze of investigating the unknown. Whether you're a skeptic or a believer, it's a compelling dive into how our government approaches the unexplained.

If you're into this kind of deep-dive investigative stuff, it's worth the read.

🔗 Get the book

🤩 Something I’m enjoying…

My Logitech MX Master 3S mouse. I've tried switching to different mice over the years, thinking maybe there was something better out there. But I keep coming back to this one. The ergonomic grip actually fits my hand and prevents the wrist pain that comes from hours of use. The accuracy is spot-on when I'm from nudging pixels in Figma. The multi-bluetooth connection lets me swap between devices with just a clip.

But my favorite part is that slick, weighted scroll wheel. It's one of those small details that makes a huge difference when you're navigating long documents or endless design files. Since I use this thing every single day, the investment has been more than worth it.

Sometimes the best tools are the ones you stop noticing because they just work.

• • • • •

Confession, I use affiliate links. You can consider them my digital tip jar. When you use these links, I get a few bucks to fund this newsletter. Thanks for keeping the dream alive.

Crap, Apples, Excellence, and Donuts

Somethings Novel — Issue #21

✍️ Something I’m writing…

Designing Terrible Solutions Makes You a Better Designer

Applying the Anchoring Effect to Design Practice

Most designers jump straight to "acceptable" solutions, never exploring what makes them actually good. But what if the fastest path to breakthrough design thinking requires a detour through terrible ideas? This piece challenges the efficiency myth by revealing how intentionally designing awful solutions teaches you about problem boundaries that good solutions often miss. Through systematic questions and controlled failure, you'll discover why understanding what doesn't work gives you unprecedented clarity about what does, and why your next design breakthrough might be hiding in the wasteland of ideas you'd never ship.

👉🏻 Read it in 8 minutes

🧐 Something I’m thinking about…

Let me tell you about my favorite apple. It’s delicious. When you see it hanging on a tree, its color compliments the color of the leaves so well. When it’s ripe, the flavor is amazing. Biting into it introduces you to a delightfully pleasing texture.

Now, describe the apple you imagined. Was it red, green, or yellow? Was the taste tart, sweet, or mild? Where did you imagine that tree, in a field, back yard, or in an orchard? Every person reading that description probably had a different kind of apple in mind. Yet, we’re all speaking the same language, using the same terms to talk about an apple. The language is the same, but ideas in our head are different.

This is what I call the “illusion of alignment”, and it’s detrimental to projects and relationships. It causes friction and frustration. It wastes time and money. And it’s kryptonite when coordinating lots of people are involved across many departments. But it’s avoidable. If we spend the time digging in to understand what’s in each other’s head. To get clear not only on what the goals are, but also how we intend to move forward. And to use examples to draw out the misalignment.

📚 Something I’m reading…

Motorcycle Safety Foundation: Motorcycle Excellence

I recently picked up a minimoto (small motorcycle) and have been riding it around this summer. After taking the Ohio motorcycle safety course, I wanted to continue learning about motorcycle safety and riding best practices to stay sharp and decrease my risk while riding. This book was a fantastic refresher of much of the content I learned in my course. It’s full of practical advice and tactics that you can use while riding to decrease (not eliminate) risk while riding. The content is backed with lots of research and been proven over decades of riders. I highly recommend this book if you’re a rider.

When I think about how this relates to design, it’s not much different. There are a host of great resources that are time tested and backed by lots of research. If you want to increase your confidence as a designer and decrease the risk of your design work going bad, pick up a book and learn from others.

🔗 Get the book

🤩 Something I’m enjoying…

Last weekend I participated in Troy, Ohio’s Tour De Donut. Officially it’s a challenge (not a race), but it was a lot of fun. I rode 58 miles through the rolling cornfields of midwestern Ohio, with plenty of opportunity to hammer down some donuts along the ride. I love cycling for a number of reasons. You can cover lots of ground quickly, it’s low impact on my genetically poor knees, and it’s a great workout. During my 4 hour ride, I had plenty of time to think to myself and come up with more design topics to write about. If you’re ever in the neighborhood around this time of year, and you’re into cycling, check out the Tour De Donut. It’s a rewarding and fun experience.

"Good UX", Terrible Solutions, Leadership Tactics, and Helmets

Somethings Novel — Issue #20

✍️ Something I’m writing…

Why Good UX Isn't Enough
Lessons from the internal combustion engine

Picture this: your team just shipped the most elegant interface you've ever created. Users sailed through usability testing. Six months later, you're staring at disappointing adoption numbers and renewal rates that make your stomach drop.

Sound familiar? The problem may not have been "usability”…it may be tunnel vision.

While most UX teams obsess over perfecting usability, they're missing the bigger picture that determines whether products actually succeed. Think of it like building the world's most efficient engine but forgetting the transmission and fuel system. Great engineering, terrible car.

This article uses Peter Morville's honeycomb framework and a motorcycle engine metaphor to reveal why polished interfaces fail when they ignore the other essential dimensions of product value.

👉🏻 Read it in 9 minutes

🧐 Something I’m thinking about…

Here's a nutty idea: designing terrible solutions makes you better at design.

I know that sounds backwards, but hang with me. There's real value in understanding what doesn't work and why. Bad solutions point you in clearer directions. They help you understand what problem actually needs solving. And they give you something concrete to judge your "good solutions" against.

Most designers avoid failure like it's contagious. But what if we leaned into it? What if we spent a little time deliberately exploring the worst possible approaches first, just to map the boundaries of the problem space?

Sometimes the fastest path to breakthrough thinking is through the wasteland of terrible ideas.

📚 Something I’m reading…

Leadership Strategy and Tactics
By Jocko Willink

I’m about 1/3 of the way through this one, and I'm struck by how applicable military leadership principles are to design leadership.

Jocko talks about being detached from situations to get a broader perspective, which hit me hard. As design leaders, we get so buried in day-to-day critique sessions and sprint planning that we lose sight of the strategic picture.

There's a story about a new platoon leader who earned respect by being humble and serving his team—literally taking out the garbage. It reminded me that leadership isn't about your title.

My favorite insight so far is an old military maxim: "In the absence of orders, lead." This resonates deeply for anyone working in ambiguous problem spaces. Sometimes waiting for perfect clarity means missing the moment to create clarity for others.

🔗 Get the book

🤩 Something I’m enjoying…

My ILM dual sport helmet for motorcycle rides.

After a few weeks with a basic (uncomfortable) helmet, I finally upgraded to something designed for both on-road and off-road adventures. What I love most isn't the off-road look (though it does make me feel slightly more adventurous), it's the thoughtful design details.

The internal lining is plush and soft against your head during longer rides. The face shield opening is massive, giving you almost panoramic visibility. And while some riders complain about it, I'm genuinely loving the integrated visor. It's like having built-in sunglasses that actually stay put when you're leaning into turns.

Sometimes the best products are the ones that solve problems you didn't even realize you had.

• • • • •

Yes, I use affiliate links for the products and books I share. Think of it as a tip for being your personal butler for design and personal growth. It doesn’t pay much…but I appreciate any help you’re willing to throw my way.

Accessibility Infrastructures, Honeycomb, AI Productivity Illusion, and Remembering

Somethings Novel — Issue #19

✍️ Something I’m writing…

Unlocking Accessibility through Design Systems

How wartime thinking transforms accessibility infrastructure

Your team looks like deer in the headlights when accessibility comes up in product meetings. It’s the looming constraint that can unexpectedly rear its head if you’re not careful. But what if that "constraint" is actually your secret weapon? Just like wartime manufacturing transformed American industry by forcing smarter systems, accessibility requirements can transform your design infrastructure into a competitive advantage. I wanted to explore how teams can stop paying the "afterthought tax" of retrofitting accessibility and instead build it as invisible infrastructure that makes better design decisions the default choice.

👉🏻 Read it in 7 minutes

🧐 Something I’m thinking about…

The Morville value honeycomb. Peter Morville's framework reminds us that a product experience thrives on many factors beyond usability and usefulness to derive value. Useful, usable, findable, credible, accessible, desirable…all contribute to what’s “valuable”.

I've been reflecting on how teams often focus on one or two dimensions while neglecting the others. A product can be perfectly usable but completely undesirable. Highly accessible but not credible. The magic happens when these dimensions work together as a system, not competing priorities.

I've wanted to write deeply on this topic for a long time (over a year). I think next week is the week. The honeycomb isn't just a nice framework. It's a lens for diagnosing why good products sometimes fail and mediocre products sometimes thrive.

📚 Something I’m reading…

Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity

A recent study by METR

I stumbled across a fascinating study that challenges what we assume about AI and productivity. Participants felt 20% more productive when using AI tools, but the data told a different story. They were actually slower…19% slower.

This makes me think a lot about the use of AI in design. The disconnect between perception and reality is striking. We feel faster, smarter, more capable. But feelings aren't reality. Our impressions are mere shadows and interpretations of reality.

This doesn't make me anti-AI. No, quite the opposite. I believe there are powerful uses for AI in design work. But it all comes down to how you use it and how you measure success. "Is AI working for us?" should be based on measurable outcomes, not on vibes.

When we judge whether AI is valuable in design, we should evaluate it with concrete factors:

• Is the quality verifiably higher?

• Did it produce demonstrably better solutions?

• Did it actually reduce time without sacrificing depth of thinking?

I'm pro-AI. But I want to do it well, with eyes wide open to both its promise and its pitfalls.

🔗 Read the study

🤩 Something I’m enjoying…

My good friend Steven passed away unexpectedly this past weekend. I was asked to deliver his eulogy…an honor that comes wrapped in grief and joy.

As I've been preparing, I'm grateful for the memories with him. The laughs. The way he encouraged others. The way he served and poured into others that many people never saw. He loved people, because Jesus loved them.

He bolstered my faith through his example and gave me countless demonstrations of what humble service actually looks like in practice. I’m grateful to reflect on his life well-lived. I grieve his loss, but filled with hope.

I'm thankful for the blessing he was in my life, even as I'll miss his friendship deeply. I don’t like the word “legacy”, but Steven’s life reminds me of the positive impact we can have on others.

We’ll all miss you, Steven. I’ll miss you, Steven.

• • • • •

No affiliate links this week. Relax and take a load off.