Bookset’s Post

To follow up on my last post, I’d like to go deeper into the meaning of product design today. Some of you said it covers both digital and physical — and I agree. But here’s my doubt: does using the same word product for both worlds really make sense? Or does it create confusion instead of clarity? When I say product, I think of something tangible: a lamp, a chair, a switch, a machine. Objects that exist in space, that we touch, that shape our emotions and daily rituals. Of course, design today is about more than the object itself — it’s about the whole experience around it. Still, I can’t help but wonder: if we merge everything under the same label, don’t we risk flattening the richness of our disciplines? Should we keep using product design for both worlds, or is it time to rethink the terminology?

The definition of design keeps getting bigger. I started in small environments, sometimes acting as a creative department of one. That meant doing my job and parts of several others. It wasn’t always ideal, but it made me a rounded designer. I learned to think creatively, interact with clients, ask why before what, and focus on outcomes. For a while, that kind of breadth felt like the exception. Now it feels like the norm. With AI tools collapsing the distance from idea to functional product, everyone is doing everything. My brain doesn’t naturally click with code, but now there’s a tool for that. I can uncover a problem, generate a solution, and ship it faster than ever. At first it was frustrating. Too many hats, too much noise. But over time I built a few small tools for myself, and they worked. That was the aha moment: design really is becoming more democratic. If you thought it was accessible before, just wait. The definition of design keeps getting bigger. And I really think that’s a good thing. Image Caption:
 Design: bigger, faster, wider.

Everyone thinks design is about polish. But It’s a signal. Not to the tech. Not to the features. To the intention behind them. Here’s the pattern: At pre-seed, the only signal that matters is usability. Can someone actually demo it without breaking? At seed, the signal shifts. Investors, customers, and hires want to know who you are. That’s when a landing page and an identity with some shelf life carry you into Series A. By Series A, the signal is scalability. Conversion, clarity, and consistency across every touchpoint. That’s when most rebrands happen. I’ve seen it play out over and over. The teams that invest in design at the right moment raise faster, attract users more naturally, and build teams that are proud to stand behind their product. The mistake is thinking design is just polish. It isn’t. Design is a signal. It shows the world you’re intentional. And intention is what buys you time with the people who matter most.

💡 Design at scale: the quietest — yet most transformative — kind of work. Not every great design needs to be flashy. Often, real impact comes from the work happening behind the scenes: systems that run smoothly, experiences that stay consistent, and decisions made for millions of different users. This It's Nice That That article about Grammarly’s design approach brings an inspiring reflection on how designing at scale requires balance between consistency, adaptability, and empathy. At Novatics, we believe design is a strategic pillar, a driving force behind digital products that grow, evolve, and continue to make sense as they scale. If you’re also interested in how great product teams tackle these challenges, this read is worth your time. 🔗 Design at scale isn’t flashy – but it’s the most interesting work in the room: https://lnkd.in/dAj4W-Xd

🏆 𝐆𝐫𝐞𝐚𝐭 𝐝𝐞𝐬𝐢𝐠𝐧 𝐝𝐨𝐞𝐬𝐧’𝐭 𝐦𝐚𝐤𝐞 𝐲𝐨𝐮𝐫 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐩𝐞𝐫𝐟𝐞𝐜𝐭 — 𝐨𝐧𝐥𝐲 𝐚 𝐯𝐚𝐥𝐢𝐝𝐚𝐭𝐞𝐝 𝐨𝐧𝐞 𝐝𝐨𝐞𝐬! As designers and stakeholders, we often fall in love with our ideas — whether it’s a visual decision like layouts, colors, or clever interactions, or a business decision that promises greater revenue. But none of these are about what we think looks or feels right. It’s about what actually works for the people using it. A beautiful interface can fail if it doesn’t solve the real problem. A great feature may not live up to expectations. That’s why validation is the most critical part of design. ⌛️Test early — even with rough prototypes. 👂Listen carefully to user feedback. 💫Iterate based on insights, not opinions. When you validate, you’re not just designing — you’re de-risking decisions, improving usability, and aligning the product with real user needs. Let’s keep designing with curiosity — and validating with users. ✨ What’s your favorite way to validate design decisions in a SaaS product?

In a world where design solutions are often 𝐩𝐫𝐞𝐝𝐢𝐜𝐭𝐚𝐛𝐥𝐞, playing it safe leads to blending in. 𝐒𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐨𝐮𝐭? 𝐓𝐡𝐚𝐭 𝐭𝐚𝐤𝐞𝐬 𝐬𝐨𝐦𝐞𝐭𝐡𝐢𝐧𝐠 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭. Here’s the truth: 𝐫𝐮𝐥𝐞𝐬 𝐚𝐫𝐞 𝐦𝐞𝐚𝐧𝐭 𝐭𝐨 𝐛𝐞 𝐜𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞𝐝. Following the standard design playbook is the best way to stay unnoticed. • 𝐔𝐈 𝐜𝐨𝐧𝐯𝐞𝐧𝐭𝐢𝐨𝐧𝐬? Toss them. Create layouts that surprise, engage, and keep users curious. • 𝐁𝐫𝐚𝐧𝐝 𝐜𝐥𝐢𝐜𝐡é𝐬? Forget them. Design something authentic, memorable, and aligned with the brand's true essence—not the latest trend. • 𝐂𝐨𝐦𝐟𝐨𝐫𝐭 𝐳𝐨𝐧𝐞𝐬? Step out. Experiment, fail, learn, and build something bold. These designs don’t just fit in; they make a statement, spark conversations, and stand the test of time. 𝐊𝐞𝐲 𝐭𝐚𝐤𝐞𝐚𝐰𝐚𝐲: If your design feels like it’s been done before, it’s time to 𝐛𝐫𝐞𝐚𝐤 𝐭𝐡𝐞 𝐦𝐨𝐮𝐥𝐝. The best ideas don’t follow trends; they start new ones.

The Design Truth: Why Great Ideas Sometimes Die Early in my career, I designed a feature that I was incredibly proud of. It was beautiful, easy to use, and during testing, users loved it. But a few months after launch, it was removed. Why? It solved a user problem, but it didn't help the business. In fact, it was costing the company money. That was a hard but valuable lesson. The Designer's Core Mission: Our job as designers isn't just to make users happy. It's to help the business succeed by making users happy. This is the crucial intersection. It's easy to fall into a trap: → Building things that users love but the business can't sustain. → Building things the business wants but users hate. Finding the "Win-Win" Sweet Spot: The real magic happens when you stop seeing user needs and business goals as two separate objectives. The best designers I know act as expert translators. They listen deeply to the user's frustrations. They listen intently to the business's strategic goals. And then, they find the single solution that elegantly speaks to both. My Two Guiding Questions: Before starting any design now, I ask myself two simple questions: → How does this make our user's life easier or better? → How does that improvement directly help our business grow or succeed? Great design isn't about choosing a side. It's about building an essential bridge between them. I’ve added two practical tips in the comments to help you put this into action.

A design’s true value isn’t in the pixels — it’s in the impact. Pretty interfaces can win hearts, but do they win business? As designers, we sometimes obsess over aesthetics while forgetting the bigger question: is this solving the client’s problem AND the user’s problem? In Ep 36 of Kenyan Design Konversations, we dig into Clients vs Users — and why a design’s success is measured by more than just visual polish. 👉 Listen in here: Ep 36: Clients vs Users - https://lnkd.in/dhf96Bed If it resonates, subscribe, share with your people, and let’s grow this konversation together. 💚 What do you think — should design lean more toward client goals or user needs?

Good products fail when people can’t use them easily. That’s why design is not just about how a product looks it’s about how it works for real people. My goal is simple: take complex ideas and make them easy to use.

"That’s the thing about designing at scale. It’s not just about maintaining consistency or keeping things usable. It’s about shaping systems, quietly and invisibly, that can carry people through complexity, adapt to difference, and still leave room for surprise." https://lnkd.in/ezBhwE4Y