Alex Ruiz’s Post

The pixel pusher, the perfectionist, low business acumen, "the artist who's not really good at product and business so they only get pulled in when it's time to make visuals" are common stereotypes designers often face. The truth is these aren't wrong 🙊🙈, these stereotypes do exist, but are just a few flavors of designer. Reality is there are designers who are antithetical to these stereotypes—they've moved past solely thinking of design (which all designers should do) and can hold multiple functional viewpoints. These designers are business thinkers, great communicators, can design exceptional experiences (at a great level of quality), walk & talk like PMs, can go deep with engineering, & unlock new realms of product innovation through creative thinking. The truth is the making part is the easiest part of the puzzle & is done with low effort. Let's call these folks "high-value designers". Here are a few principles to contextualize deeply to become a high-value designer, & not fall into the cliché stereotypes: 🟢 1. Good is better than perfect. Strive for progress over perfection by starting with "good enough", shipping it, & then refining things over time based on feedback & real-world learnings. Spending too much time on niceties too early has diminishing returns & delays true progress. Plus paints you as the perfectionist. 🛠️ 2. Tools are just that—tools. It's important to remember that operating a tool doesn't equate to mastering a skill. The real magic is in thinking beyond the tool, in critical and creative problem-solving. “No matter what tools you use to create, the true instrument is you.” — Rick Rubin. Note: executing quality design work is a pre-requisite to being a "designer", it's table stakes. You're expected to be good at your craft. 🌟 3. In business, design's true value is making strategy and tactics visible and tangible. What does this mean? It means a picture is worth a 1000 words, & a prototype is worth a 1000 meetings. Design is about turning abstract plans into something concrete that people can see, understand, & rally around. Run show & tell's often. Do a lot more showing than telling.     🎤 4. Master storytelling. Storytelling is crucial for designers. If you can't make people see & believe in the future you're designing, it's as good as non-existent. Paint the picture in a way that turns your ideas into a compelling story people can get behind.    ✍️ 5. Document your thinking. Writing's essential for clear thinking, buy-in, articulation, & thought distribution. Escaping the "pixel pusher" stereotype requires stepping out of tools like Figma & shifting to articulating broader strategies and tactics before diving into craft. Taking a moment to write before, during, & after you make something provides insight into your logic & positions you as a thinker & planner, not just a designer. Master these, and watch your "value" & impact as a designer increase.

This is a good list of areas designers address in orgs that manage design well. I’d add one more to the list: Design for knowledge management — for now, and for later. This is related to many other items already on the list, and comes back to the picture is worth a thousand words / the prototype is worth a thousand meetings. Further, making that 1000x value findable and contextualized, for now, and for later, is how that value is realized in your org (and your own practice). Over time, many orgs fall down on that “for later” value — and inadvertently redo design that was already done, or, even worse, “undo” design in the sense of breaking the existing design logic without understanding the breakdown. The total value of the design includes everything designed — and organizing the work to illuminate the story of what was vs wasn’t pursued further. Sometimes understanding the design that didn’t work is worth a thousand designs that did.

Designers have ruined design collaboration with their inferiority complex, constantly overcompensating and trying to monopolize the entire design idea production. There was a time when a wireframe was an artifact used by stakeholders to communicate ideas to designers. But somewhere along the journey, designers started complaining about this, saying that “their PM was trying to do their job.” And PMs are not stupid, so they were like: “Sure, you’re so insecure that I cannot even draw something in a napkin without you getting threatened by that, so please be my guest and do everything.” And designers were like: “Awesome! Now I have influence!” without realizing that not only did they have less influence by removing this agency from stakeholders, but now they have to work more to find alignment. That’s why the lo-fi / hi-fi artifact debate is so dumb. People say: “You should design in low fidelity to get the right feedback from stakeholders,” without even realizing that ultimately, it should be stakeholders, the ones expressing their ideas in low fidelity, not designers. Using low-fidelity, because supposedly that’s the only way to get the proper feedback from a stakeholder, reflects the designers' inability to assert themselves and express their views with authority. Designers, by definition, are producers of vision, and vision can only emerge in high fidelity. P.S.: I’m not saying you should stop designing in low fidelity. Do whatever works for you. I’m just saying that this idea of “I’ll draw you a wireframe so you can give me good feedback” is often less beneficial than people think.

I like drawing WITH clients. I have brought butcher paper to the table and pulled out crayons (YES, crayons) with executive stakeholders to get them in the mindset of professional play, where ideas aren't precious, to find meaningful solutions and create conversation. It's been a while - too long - and covid made so much virtual that it's hard to do this now. But the idea still stands - I hope that people draw. I hope that they do low-fi expressing of ideas. I can't tell you how many times a writer or developer could be found alongside me drawing on paper or a whiteboard. Just ask John Hawbaker or Meghan O., or Jesse Thompson, Ali Whittier, CHES® and Charles Moss. Or Jason Volpe as developer. The value in collaborative iteration is what design is all about. I will die on this hill. I love that Juan hit on the insecurity of design surrounding that conversation about value. We have spent so much time talking about bringing value that we're often the ones saying "I alone" can do this, when design's purpose is often best practiced as a joint venture. If I alone create something - that's art. And design as art has a place. But design, at least in this context, isn't art. It's a facilitated problem that we're solving. Together. Regardless of the product, the media, the outcome...the facilitation, the journey, that's where our value lies. #designleadership

I agree with the heart of this sentiment. It's less about wireframes but more about ego. I learned a long time ago that great ideas can come from anyone. It benefits the collective to include differing perspectives throughout the design process. Be open to and invite opinions otherwise a team can severely limit their idea pool. It becomes a challenge when prescriptive UX notes are baked into PM requirement documentation. If you are delivered a set of requirements with a problem statement AND solution already defined it removes UX from the strategic heart of the collaborative development process. This is where you'll find the tension and symptoms of the inferiority complex you mentioned. At my level it's easy to work around because I just see it as another idea or opinion to add to the mix. We need to encourage newer design professionals to listen, document, and discern. Take all the reasonable ideas, test them, and be cool with whichever solution solves the user problem best. It's not about us at the end of the day.

In the realm of design, we often champion terms like "inclusiveness" and "collaboration," yet we sometimes hesitate to embrace these concepts when stakeholders attempt to contribute their ideas. Dismissing these attempts as not their job misses a valuable opportunity for dialogue and fresh perspectives. I see every piece of feedback as a chance to collaborate and grow. Even after nearly 15 years in the field, it's challenging to hear that my work might not be clear to a stakeholder, a Product Owner, or a developer. However, being open to feedback and willing to seek help isn't a weakness; it's a cornerstone of collaboration and innovation. It's about staying receptive to new ideas that can refine our work and lead to better products for our users.

Wireframe vs Mockup vs Prototype: Unraveling the Differences Wireframes, mockups, and prototypes are all essential components in the process of designing and developing digital products. Each serves a distinct purpose in the product development lifecycle. Let's unravel the differences between wireframes, mockups, and prototypes: Wireframe: Definition: A wireframe is a low-fidelity, basic visual representation of a product's layout and structure. It focuses on the arrangement of elements on a page without including design details. Purpose: Wireframes help in outlining the overall structure and functionality of a product. They are used to plan and communicate the basic layout and flow of a user interface. Characteristics: Minimalistic design, usually grayscale or black-and-white. No detailed styling or visual elements. Emphasizes content placement and functionality. Acts as a blueprint for the design. Mockup: Definition: A mockup is a mid to high-fidelity static design representation that includes visual details such as colors, typography, and imagery. It provides a more realistic preview of the final product compared to wireframes. Purpose: Mockups are used to visualize the aesthetics and branding of a product. They serve as a bridge between wireframes and prototypes, offering a detailed look without interactive functionality. Characteristics: Incorporates design elements like colors, fonts, and images Represents the final visual appearance of the product. Provides a more polished and detailed view compared to wireframes. Static and non-interactive. Prototype: Definition: A prototype is an interactive, dynamic model of a product that simulates user interactions and provides a more realistic experience. It may or may not include the final design aesthetics. Purpose: Prototypes allow stakeholders to interact with a functional representation of the product. They help identify usability issues, validate concepts, and gather feedback before the final development phase. Characteristics: Interactive and clickable, allowing users to navigate through screens. May include basic functionality and transitions. Offers a more realistic user experience. Used for user testing and validation. Summary: Wireframes are basic, low-fidelity representations that focus on structure and layout. Mockups are static, high-fidelity designs that showcase the visual aspects of the product without interactivity. Prototypes are interactive models that simulate user interactions, providing a more realistic user experience for testing and validation. In a typical design workflow, you might start with wireframes to plan the layout, move on to mockups to design the visual aspects, and finally, create prototypes for user testing and validation before the actual development phase.

One of the biggest hurdles in Creators-Client collaborations lies in the realm of communication. Often, creators struggle to effectively convey design concepts to clients who lack a solid understanding of "design principles". This results in a frustrating cycle of - Misunderstandings - Misinterpretations Ultimately, a design that falls flat. The communication gap arises from a fundamental difference in perspectives: X- Content Creators: 1. Possess a deep understanding of design principles, aesthetics, and user experience. 2. Think in terms of visual elements, layouts, and color palettes. 3. Often use technical jargon and acronyms specific to the design field. Y- Clients: 1. May not have a background in design and lack familiarity with its intricacies. 2. Focus on functionalities, brand messaging, and achieving specific business goals. 3. May misinterpret technical jargon or miss subtle nuances in design choices. (Difficulty in design concepts) ⤵ A. Creators may struggle to simplify complex design ideas into digestible terms for non-designers. B. Jargon-heavy explanations can confuse clients and create a barrier to understanding. C. Visual references and mockups might not be enough to convey the full intent behind the design. (Misinterpretation of Feedback) ⤵ A. Clients may provide feedback based on personal preferences rather than design principles. B. Vague or subjective feedback can be difficult for creators to interpret and implement. C. Creators might misinterpret the client's intent, leading to revisions that miss the mark. Both parties need to take proactive steps: {Content Creators} : 4. Use plain language 5. Focus on benefits 6. Utilize visual aid 7. Actively listen and ask clarifying questions 8. Seek feedback early and often {Clients} : 4. Educate yourself on basic design principles 5. Focus on specific goals and objectives 6. Provide clear and concise feedback 7. Respect the expertise of creators 8. Ask questions and seek clarification P.S. Should I change my profile photo with this?

My typical design process involves a structured approach to ensure a comprehensive and successful outcome. Here is an overview of my design process from start to finish: 1. Project brief and Understanding Requirements: Begin by thoroughly understanding the client's goals, target audience, and any specific requirements for the project. Conduct meetings or discussions to gather information and insights that will guide the design process. 2. Moodboarding and Inspirations: Conduct research on industry trends, competitors, and design styles to gain inspiration and ensure the design is contemporary and relevant. Create mood boards or design collages to visually communicate potential directions. Conceptualization. I get my design inspiration from behance, dribble, Pinterest, lappa ninja. I actually share this out with my client. 3. Wireframing: Develop wireframes or rough sketches to outline the basic structure and layout of the design. Focus on the overall user experience and ensure key elements are appropriately placed. I share this out my client too. 4. Design Development: Start the detailed design process using graphic design software(Figma, Adobe Photoshop, Adobe illustrator, Webflow) Pay close attention to color schemes, typography, imagery, and other visual elements to create a cohesive and aesthetically pleasing design. 5. Iterative Review and feedbacks: Share initial design drafts with the client or team for feedback. Iterate on the design based on feedback, making necessary adjustments to improve the overall design. Prototyping: Create interactive prototypes if applicable, allowing stakeholders to experience the design in a more dynamic way. Test and refine the prototype based on user feedback and usability testing. 6. Finalization: Finalize the design, incorporating all feedback and making any necessary refinements. Ensure that the design is aligned with branding guidelines and responsive across various devices. 7. Collaboration with Development Team: Work closely with the development team to ensure a smooth transition from design to implementation. Provide necessary design assets and guidance during the development phase. 8. Quality Assurance: Conduct thorough quality assurance testing to identify and address any design-related issues before the project goes live. 9. Delivery: Deliver the final design assets to the client or development team. Provide any necessary documentation or style guides to ensure consistent implementation. 10. Post-Launch Support: Offer post-launch support to address any unforeseen issues and make minor adjustments if needed. This process is adaptable based on the specific needs of each project, and I believe in maintaining open communication with clients and stakeholders throughout the entire design journey

It's a game-changer folks, the design process just got a serious upgrade. 💻🚀 The tech industry's most innovative minds have been hard at work, and the results? Tech mockups that're taking the design world by storm. This isn't just about pretty pictures. It's about revolutionizing the way we approach design, from concept to execution. 🎨🔄 Imagine having the ability to visualize your design in a more enhanced way, to prototype interactively, and to communicate more efficiently with your team. This isn't a dream, it's the power of tech mockups. 🖥️✨ But don't just take my word for it. Check out this article, "Hi-Tech Presentation Mockups: 15+ Best Tech Mockups" to see how these tools are empowering designers to create compelling and impactful designs. Remember, design isn't just an art, it's also a science. And with these tech mockups, we're taking that science to new heights. Get ready, world. Design is about to get a whole lot more exciting. Read the full article here: [https://lnkd.in/g6QQns46) 👀🔥🚀 Let's embrace this new era of design! Check this out: https://lnkd.in/gDcUmKSp