How do you present your UI design?

Think of presenting as a blend of storytelling and selling. Imagine you're a storyteller on a quest to win over your audience. To do that, you must be a mind reader, understanding what tickles them. Just like a masterful salesperson, your design should be a compelling tale. Pick a character and let their journey through your design unfold like an epic story. Your audience should be so attached to it that they step into the character's shoes, feeling what they feel. Adjust your story for different types of audiences. And remember, your ultimate goal is to paint smiles on their faces.

In my opinion the most important thing is you know about the eye movement of your users. Eye movement tell an amazing story about the visual behaviors of user and surprisingly let me know how engaged user attention. Further more UI design need knowledge in both behavioral and physiological actions of user. In behavioral task or Questionnaire you find data about your users behavior that sometimes are biased and intentional. But in physiological task you find data about the unconscious behavior of users mind. I use neuroscience in my design that make my product or service assessable by neurodesign criteria and make it valid

Build an experience that sells the experience. It seems obvious but when you walk through your stakeholders (customers, the delivery team, and business owners) through the new experience do so in a way that is hands on, and clearly IMPARTS THE IMPACT of the new way. Ideally you are simply letting them reach the right conclusion through subtle prompting as they go through the experience, after all, "Don't make me think" doesn't just apply to UX.

In UI design, simplicity often reigns supreme. Take the Google vs. Yahoo search engines as prime examples. Google's clean, minimalist homepage is a masterclass in focusing on the user's primary intent - searching. The absence of clutter directs your attention to the search bar, creating an efficient and enjoyable experience. On the flip side, Yahoo's homepage used to be a bustling marketplace of information, which, while informative, could be overwhelming for users just wanting to search. Simplicity isn't just for search engines. Consider Airbnb's booking process - minimal steps ensure a smooth experience. In UI design, it's often what you leave out that matters most. ??

When sharing UI designs, keep it simple. Start with the big picture and essential concepts, and only dive into the nitty-gritty details when required. I've learned that bombarding people with too much information upfront can sometimes hinder the feedback process.

Story telling is the best approach to presenting our idea and the concept behind it and with the story we are able to get attention and that makes overall conversation effective and powerful to present our concept and idea.

In addition to the above insights, highlighting a user-centered approach in UI design presentations is crucial. Emphasize the iterative process, showcasing how user feedback shaped the design. This demonstrates dedication to user satisfaction and reveals the design's evolution, making the presentation engaging. Addressing accessibility is crucial. Explain how you ensured usability for individuals with disabilities, aligning with inclusivity and compliance standards. This reflects ethical design principles and broadens the potential user base. Lastly, discuss the design's future prospects. Share your vision for adaptability as user needs change or new technologies emerge. It leaves a lasting impression, fostering engagement for UI design.

Remember the audience + Build a narrative. Everyone loves good stories. More than walking through background data, that will organically come up during Q&A, introduce the problem for a bit (if that hasn't been done already) and get into story telling of the user journey. This is of course going to depend on how much storytelling the PM is doing, and how much context the audience have, and how big of a design demo it is. Regardless, this continues to be a broad framework. Understand your audience + Get the right narrative.

I recently realized the power of storytelling in design. When you tell a story, your audience can connect more with your users and thus, be able to understand the importance and effectiveness of your solution better. Use cases can be a good way to start and they help the reader imagine a situation where the solution could be more useful and helpful to someone. Using good visual elements such as imagery and motion could also help keep readers engaged and interested as they scroll. It could also help for memorability of your project. You could introduce characters and show their journey from before using or implementing the solution to after. This could be tricky however and should be done carefully.

Yeah I also agree with that point. Our presentation should be a story our problems identification to the solution we proposed. As I recently read a quote by Mary Catherine Bateson stated as “The human species thinks in metaphors and learns through stories.”

Another important aspect of UI design is usability. While visuals and animations can enhance the appeal of a design, it's crucial to prioritize the user experience. A well-designed user interface should be intuitive and user-friendly. This involves ensuring that navigation is straightforward, elements are easily clickable or tappable, and information is presented in a logical and accessible manner. Balancing aesthetics with usability is key to creating a successful UI design that not only looks good but also functions effectively for the intended audience.

If time permits, please do build a prototype. It's about as close as someone can get to a finished product, and with mock data, and sufficient screens, can be amazing to create a near-real experience. Interactive Prototype > Design > Doc (Atleast when it comes to storytelling) Super important that as humans we're very tactile and the moment you can interact with something, you have a way better understanding of it, than just seeing it as design, or a text problem statement.

In making UI presentations, go BIG on visuals. That is because most people tend to SCAN presentations, not read them. Go less on texts, and do more with visuals. A key part of user experience is usability, so make it easy for your audience to find what they are looking for. - Use infographics for metrics, impacts, and results - Use graphics to break up pieces of text - If you can, use animations over static screens. You can put 5 screenshots into a 3 seconds auto-play prototype. Apart from saving the audience some time, it also tells a better story about the user flow.

Utilizing visuals in UI presentations can elevate engagement and persuasiveness. While there are tools like Sketch, Adobe XD, and InVision, Figma stands unrivaled for creating high-fidelity mockups and prototypes. However, it's vital to avoid overly complex visuals that may distract and to maintain a clear, brand-aligned aesthetic.

It is popularly said that design is not just how it looks, it is actually problem-solving. That means every design decision should be deliberate. A designer must be able to explain the WHYs to virtually all decisions made. "How do I present this to my audience?" Writing long text for explanation can be boring. - You can make use of coach marks and short notes/annotations beside your screens. It is easier to understand when comments are close to the context. - Use a 'before' and 'after' approach so that the impact of your iterations can be seen. - Include relevant primary and secondary data where necessary to drive home your points.

Yeah, I completely agree. I think that by explaining our reasoning, we can provide the audience the answers to the unspoken concerns they may have about UI design. Everyone has their own perspectives, ideas, and approaches to the problem at hand. Therefore, when we show our ideas and explain the reasoning behind them, the audience will be able to travel to the same spot. as us and see the designs and needs through our eyes.

Design rationale also helps understand why certain things looks in a specific way and how it helps it's users. There are times when you would go against the trend and this is be because the best way you're solving a specific user problem. You can also back with artifacts you collected during your research.

It’s all about the structure. Instead of immediately delving into the user interface (UI), it's beneficial to begin by narrating the story behind your objectives. This helps set the context and purpose. Furthermore, it's essential not to simply showcase random UI screens but to initiate the process with a well-crafted prototype. By sharing the prototype with a diverse group of stakeholders, you allow them to immerse themselves in the user experience, which is key. Encouraging feedback based on the experience they had with your UI can yield more valuable insights. It's important to remember that UI design is somewhat subjective, so the goal is to minimize subjectivity and target feedback that aligns with the intended purpose.

If you are getting vague feedback like "I am not sure I like the color" or "can you make it pop a bit more," try to ask probing questions to understand the why a bit better. However, asking "why do you say that?" usually doesn't get to the heart of it. Instead try these: * Which of our key outcomes do you think that change would impact? * Why do you think it would have that impact on our users? * What could we measure to evaluate that? By asking questions like this, we move the conversation towards user behaviors and business goals, it opens the door to more productive critique, and it allows us to (if needed) determine how we can empirically measure the option(s).

Any experienced designer knows no successful product is built in silo. The concept of iteration itself shows that a design solution is almost never achieved on the first try. It requires continuous improvement! And because; - Of our biases - Limited experience/knowledge - We are not the users in most cases, we need input from different stakeholders. We might need visual and interaction design inputs from fellow designers who could notice things we missed out on. Inputs from developers on technical feasibility. Inputs from the product team on business goals, constraints, and systems thinking. And, maybe most importantly, input from prospective users via usability testing to gauge experience before and after shipping.

Aim for simplicity. When presenting UI designs, try to reduce complexity as much as possible while conveying high-level concepts and ideas. Always be prepared to go into more detail when necessary, but I've found that overloading the recipients with information can backfire and prevent critical feedback.

At Factory 39, we use of prototypes a lot, particularly via Figma, to bring our UI designs to life before they go into development. Prototypes aren't just static visuals; they're interactive experiences that give clients a tangible feel of the final product, way before a single line of code is written. This not only excites clients like nothing else because they can see, touch, and interact with their vision, but also help the dev team understand what they will be working on. Honestly, this is a game-changer in client presentations and relationships when it comes to UI projects. So, if you're looking to impress, show don;t tell!

Here a short instance from my past 'Once upon a time, in the year 2021, a legal team presentation took place at my friend's workplace on the introduction of new policies. I was there. Typically, I don't?these kinda?presentations since they tend to be text-heavy, have a lot of slides, and the speaker primarily reads the content from the slides. They are also tedious and stressful. This time, though, something unusual occurs: there are fewer slides, text, attractive visuals, and a lot of positive anecdotes. I think fewer slides with visual aids enable me to concentrate on the presentation well, and the stories?and its characters help me recall the policies up to this point. I think this was one of the better presentations I've seen.'