<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Khatchadour Israelyan on Medium]]></title>
        <description><![CDATA[Stories by Khatchadour Israelyan on Medium]]></description>
        <link>https://medium.com/@khatchadourisraelyan?source=rss-952bf1f4616------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7qXMxiJDiqPlGDEngmu6tw.jpeg</url>
            <title>Stories by Khatchadour Israelyan on Medium</title>
            <link>https://medium.com/@khatchadourisraelyan?source=rss-952bf1f4616------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:52:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@khatchadourisraelyan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The role and application of arrow buttons in user interface design]]></title>
            <link>https://medium.com/design-bootcamp/the-role-and-application-of-arrow-buttons-in-user-interface-design-7d2277c45bff?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d2277c45bff</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[button]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[element-ui]]></category>
            <category><![CDATA[perception]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Wed, 16 Apr 2025 13:34:42 GMT</pubDate>
            <atom:updated>2025-04-16T15:38:57.951Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbhtRT2bFTWVDKGbRr2XfA.png" /></figure><p>Arrow icons are a prevalent element in user interfaces across both web and mobile platforms. Their frequent use underscores their potential to effectively guide users and enhance interaction. However, the simplicity of the arrow symbol belies the complexity of its application. A nuanced understanding of when and how to employ arrow buttons is crucial for user experience professionals to ensure clarity, predictability, and ultimately, usability. This report aims to provide a comprehensive analysis of arrow buttons, exploring their diverse functionalities, key design considerations, and established best practices in the field of UX design. By examining various contexts and the rationale behind arrow button usage, this analysis seeks to serve as a valuable resource for practitioners aiming to leverage this common UI element effectively.</p><p><strong>II. The Core Functionality: Navigating Beyond or Acting Within? Examining the primary roles of arrow buttons.</strong></p><p>A fundamental consideration when using arrow buttons is whether they primarily indicate navigation to another page or signify an action to be performed within the current view. This distinction impacts user expectations and the overall flow of the interface. The presence of a right-facing arrow on a button often creates an expectation that clicking <strong>it will lead the user to a new page or a different section</strong>. This association stems from established web conventions where such an icon typically signifies forward movement or progression to the next step in a process. Consequently, users anticipate a transition rather than an immediate action confined to the current screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2U4DU8fwSWdHkIRmVVk0g.png" /></figure><p>Furthermore, incorporating an arrow into a button’s design can enhance its prominence, effectively drawing the user’s attention to it and the associated action. This increased salience is particularly beneficial for key call-to-action buttons where the goal is to encourage user engagement. In essence, the arrow acts as a visual affordance, hinting at the consequence of interacting with the button. Specifically, when used on buttons, an arrow strongly suggests inter-page navigation, differentiating these buttons from those intended for on-screen actions. The explicit indication of moving to “another page” reinforces the understanding that clicking the button will result in a change of context or location within the application or website. Therefore, designers must carefully consider the intended outcome of a button click to determine if an arrow is an appropriate and effective visual cue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rZip6dTek9pMdeOsw4Ks1Q.png" /></figure><h3><strong>Arrows for Navigation and Flow.</strong></h3><h4><strong>Next, Previous, and Back Navigation</strong></h4><p>Left-facing arrows have a strong association with the “back” function, particularly within navigation bars. This pattern is deeply ingrained in user experience due to its widespread adoption across operating systems and mobile applications, establishing a clear expectation for this directional cue. In the context of pagination, arrow buttons, often presented without accompanying text or borders, are commonly used to navigate between pages, with left and right arrows intuitively indicating movement to previous and next pages, respectively. The surrounding UI elements play a crucial role in this interpretation. When arrows are grouped within a pagination component, their function as navigation controls becomes readily apparent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S6ARNL-x9FE2_Vw0ve-Lnw.png" /></figure><p>Different visual styles of arrows can serve the same purpose of back navigation. For instance, Apple’s native iOS apps often favor the <strong>chevron style </strong>for their back buttons. This highlights that while the core meaning remains “back,” the visual presentation can vary based on aesthetic preferences and platform-specific design guidelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/0*evsKGZ4UWWDJ6WIY.png" /></figure><p>Factors such as available visual space and the potential for animation might also influence the choice between a literal arrow and a chevron. Moreover, arrows are frequently employed in carousels and sliders to indicate directional movement, allowing users to navigate through content horizontally using left and right arrows positioned on either side of the interface. This has become a standard pattern that users readily recognize for progressing through a sequence of items.</p><h4><strong>Carousels and Sliders</strong></h4><p>Arrows serve as direct visual prompts for interacting with carousels, clearly indicating the ability to swipe or click to view additional content. In interfaces featuring horizontally scrolling content, these arrows explicitly communicate the presence of more items beyond the currently visible area. In scenarios where users can move both forward and backward through a set of items, such as an image carousel, arrows pointing in opposite directions (left and right) effectively signal this bidirectional navigation. This visual cue reinforces the interactive nature of the component and informs users about the available navigation options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qggPabPG-sl46KwigSm0UA.png" /></figure><h4><strong>Indicating direction within a Flow or Process</strong></h4><p>Arrows can also be valuable in visually representing the progression through a multi-step process. By acting as visual signposts, they help users understand their current location within the flow and the direction they are moving. This is particularly useful in scenarios like checkout processes or form completion, where a sequence of actions is required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WLaxMjTcRibsJ3-HcoMyNw.png" /></figure><h4><strong>Arrows in Progressive Disclosure</strong></h4><p>Arrows are a common visual indicator for expandable and collapsible sections of content, a design pattern known as progressive disclosure. However, inconsistencies in their placement and direction across different interfaces can sometimes lead to user confusion. While not entirely standardized, a downward-pointing arrow or chevron is frequently used to signify that clicking it will expand a section to reveal more content, while an upward-pointing arrow often indicates the ability to collapse the section. The placement of the arrow relative to the text it controls (either to the left or right) and its direction when the content is closed (right, left, or down) can vary, contributing to the observed inconsistencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*pah_loM6_VermWBHntYbPw.png" /></figure><h4><strong>Arrows for Sorting and Direction</strong></h4><p>In the context of data tables, upward and downward-pointing arrows within table headers have become a standard convention for indicating the sort order of the data. An upward arrow typically signifies that the column is sorted in ascending order, while a downward arrow indicates a descending sort. Users have come to expect that clicking on a table header containing an arrow will sort the corresponding column according to the direction of the arrow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fd8XfLF6zJp_rpFvv_PTow.png" /></figure><h4><strong>Niche Uses of Arrow Buttons</strong></h4><p>The versatility of arrow icons extends beyond standard navigation and interaction patterns. They can be effectively employed as general directional cues to draw the user’s attention to important elements on a page, acting as visual prompts. For instance, stylized arrows, such as hand-drawn versions, can be used to specifically point to opt-in forms, call-to-action buttons, or to visually guide users to scroll down the page for more content. The inherent directional quality of arrows makes them a powerful tool for creating a clear visual hierarchy and leading users towards desired actions or information. Furthermore, curved arrows can offer a slightly different visual connotation, potentially suggesting a return to a previous point or a looping action, making them suitable for links, back buttons, or for indicating the end of a list or gallery with an option to return to the beginning. The shape of the arrow can subtly influence its perceived meaning, allowing for more nuanced communication of functionality.</p><h4><strong>Arrow Orientation</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/1*kW3T7_BGGLmuKX0m49f8-g.png" /></figure><p>The direction of an arrow in a user interface is a key element in conveying its intended function. Specific orientations have become associated with particular actions and meanings through established conventions. A right-pointing arrow (→, ▶, &gt;) commonly indicates “Next,” “Forward,” or the act of navigating to another page or step in a process. It is frequently seen in pagination controls, on “Learn More” buttons, and as part of progress indicators.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*ccNbuWFxMcawBBuUZpZU2w.png" /></figure><p>Conversely, a left-pointing arrow (←, ◀, &lt;) is primarily associated with “Back,” “Previous,” or returning to a prior state. This direction is typically used for back buttons in navigation bars and in pagination controls for moving to earlier content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*L8-cF7977A4mxW9pucrkbw.png" /></figure><p>Upward-pointing arrows (↑, ∧) are often used in table headers to signify the sorting of data in ascending order. They can also be used in progressive disclosure elements to indicate the action of collapsing content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/343/1*bzFLXmn0gQnia01oE8jQPg.png" /></figure><p>Downward-pointing arrows (↓, ∨) frequently indicate the sorting of data in descending order within tables. Additionally, they are commonly used to signify the ability to expand a section and reveal more content in progressive disclosure patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*64mhAQTCuKz3exE-P9CHzg.png" /></figure><p>The arrow pointing to the top right of the screen typically indicates an external link, suggesting that a new tab will open.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*NiraWYD_HEOi2ECSx6pSpA.png" /></figure><p>This arrow indicates that an action will occur in the top left corner of the screen. You’ll see this in the Google Chrome mobile interface when the browser suggests search keywords. When the user clicks on the arrow, the selected keyword is added to the URL input field.</p><h3><strong>Best Practices in Arrow Button Design</strong></h3><p>Several factors contribute to the effectiveness of arrow buttons, including the size, placement, and clarity of the arrow icon. The arrow should be appropriately sized in relation to any accompanying button text and other UI elements to ensure legibility and ease of interaction, particularly on touchscreen devices. The placement of the arrow relative to the text can also influence its interpretation. For navigation buttons indicating “next,” the arrow often follows the text, while for “previous” or “back” buttons, it typically precedes the text. In expand/collapse elements, the arrow is frequently positioned to the left of the text.</p><p>The arrow icon itself should be easily recognizable and its direction unambiguous. Consistency in the visual style of arrows (e.g., filled, outlined, literal, chevron) throughout an application or website is crucial for creating a cohesive and predictable user experience. Inconsistent styles can confuse users and hinder their ability to quickly understand the function of different arrow buttons. Arrows can also have secondary meanings depending on the context and any accompanying text. For example, an arrow icon on a button might indicate that a dropdown menu will appear when clicked. In such cases, the combination of the arrow and the text label provides more specific information about the button’s action beyond simple navigation. Ultimately, arrow buttons should adhere to general button design best practices to ensure they are perceived as interactive and their primary action is clear. The inclusion of an arrow does not negate the need for the button itself to be well-designed in terms of shape, size, and visual feedback.</p><h3><strong>The Context is King</strong></h3><h4><strong>The surrounding UI influences arrow button interpretation.</strong></h4><p>The meaning and usability of arrow buttons are heavily reliant on the context provided by the surrounding user interface elements. Users interpret icons and symbols based on their past experiences and the visual cues offered by the context in which they appear. For example, an arrow placed within a set of pagination controls is readily understood to mean “Next” or “Previous page.” Similarly, an arrow found in the header of a data table is typically interpreted as an indicator for sorting the data in that column. Even an arrow positioned next to a comment might be understood as an affordance for upvoting or downvoting.</p><p>Without sufficient contextual cues, the meaning of an arrow button can become ambiguous. For instance, a left-pointing arrow, to be clearly understood as a “go back” button, often relies on the convention of being located within a navigation bar or being paired with breadcrumbs that visually represent the user’s navigation history. A standalone arrow, without such contextual reinforcement, might not always clearly communicate its intended purpose. Therefore, providing adequate context through labels, placement within established UI patterns, or the inclusion of accompanying elements is essential for ensuring the effective communication of an arrow button’s function. Furthermore, directional cues, including arrows, can contribute to the overall flow and structure of a page, guiding the user’s attention and indicating possible pathways for interaction.</p><h4><strong>The role of animation in enhancing arrow button usability.</strong></h4><p>Incorporating animation into arrow buttons can be a powerful way to enhance their usability and user engagement. Animated arrows can effectively capture the user’s attention and incentivize them to interact with the element. For example, an animated arrow pointing downwards can clearly indicate that there is more content to scroll below the fold. Similarly, using subtle animation on arrow buttons, such as an on-hover effect, can provide visual feedback and encourage interaction. Technologies like CSS offer designers the tools to easily implement a variety of arrow animations for different purposes, including hover states and scroll indicators. This ability to add motion provides designers with flexibility in enhancing user interaction and potentially improving the user’s understanding of the button’s purpose or the availability of further interaction.</p><h4><strong>Ensuring Accessibility</strong></h4><p>Designing accessible arrow buttons is crucial to ensure that all users, including those with disabilities, can effectively interact with the interface. Several accessibility best practices should be considered. It is important to ensure sufficient color contrast between the arrow icon and the button’s background to meet accessibility guidelines for visual clarity. For icon-only arrow buttons, providing clear and descriptive alternative text for screen readers is essential so that users relying on assistive technologies can understand the button’s function. On mobile devices, ensuring that arrow buttons have an adequate touch target size is important for users with motor impairments. Additionally, designers should consider keyboard navigation and provide clear focus states for arrow buttons to accommodate users who navigate without a mouse. The use of semantic HTML and the provision of appropriate alternative text for arrow icons are fundamental for making interfaces accessible to everyone. While visual design plays a significant role in the user experience, ensuring that the functionality and meaning of arrow buttons are conveyed to all users, including those who rely on assistive technologies, is paramount.</p><h3><strong>Key Valuable Tables</strong></h3><h4><strong>Arrow Direction and Typical Function</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vifDZsJY64-UF1tKhSuBTA.png" /></figure><h4><strong>Arrow Button Use Cases and Design Considerations</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eya0A_q4TI9Y4Q4sElrNgA.png" /></figure><p>If you enjoy my work and want to show some love, consider treating me to a coffee! Your support means the world to me☕ <a href="https://buymeacoffee.com/khisraelyan">https://buymeacoffee.com/khisraelyan</a></p><p>Follow me on LinkedIn: <a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d2277c45bff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-role-and-application-of-arrow-buttons-in-user-interface-design-7d2277c45bff">The role and application of arrow buttons in user interface design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Birth of the Term “UX”: A Story of Collaboration and Innovation]]></title>
            <link>https://medium.com/@khatchadourisraelyan/the-birth-of-the-term-ux-a-story-of-collaboration-and-innovation-5d3b4c7e1c3b?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d3b4c7e1c3b</guid>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Tue, 08 Apr 2025 09:51:19 GMT</pubDate>
            <atom:updated>2025-04-08T09:51:19.550Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever wondered where the term “UX” originated? The story goes back to the early 1990s and the halls of Apple, where a revolution in user-centered design was brewing. Don Norman, a renowned designer and researcher, found himself in the unique position of <strong>“Apple Fellow” </strong>— a role with immense freedom to explore new ideas.</p><p>Upon joining Apple in 1993, Norman observed a concerning trend: Apple’s once stellar reputation for user-friendliness was fading. Determined to address this, he assembled a team — Tom Erickson and Harry Saddler — and together they formed “The User Experience Architect’s Office.” Norman himself took the title of Apple’s first “User Experience Architect.”</p><p>While the exact origin of the term remains slightly fuzzy, Norman credits the collaborative spirit of the team. They aimed to broaden the scope beyond just interfaces, encompassing the entire user journey — from product design and graphics to physical interaction and user manuals. Their efforts were impactful. User experience was elevated to an equal footing with engineering and marketing, ensuring every product decision considered its impact on the user.</p><p>Norman humbly downplays his role in coining “UX,” suggesting it might be a collective brainchild of the team. However, his influence on the field is undeniable. It was at Apple that the term “UX” gained traction, forever changing how we approach product design.</p><p>But the story doesn’t end there. A fascinating twist emerged when Norman consulted a large database to pinpoint the term’s origin. He discovered an earlier reference — a 1986 book chapter by Brenda Laurel titled “Interface as Mimesis” where she used the phrase “user experience.” While Norman acknowledges his awareness of Laurel’s work, he believes the Apple team’s use as a job title solidified the term’s meaning and application within the industry.</p><p>This discovery highlights the collaborative nature of innovation. Ideas often build upon previous work, and breakthroughs rarely happen in isolation. Both Norman and Laurel played crucial roles in shaping the user-centered design philosophy that “UX” embodies.</p><p>The quest to understand the origin of “UX” also unearthed a debate about the term itself. Norman, concerned about the potential for a misinterpreted “faceless user,” suggests focusing on “the user’s experience” to emphasize individual needs. This perspective encourages designers to consider the diverse range of users they’re creating for.</p><blockquote><strong>Follow me on Linkedin: </strong><a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d3b4c7e1c3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How text style shapes hierarchy]]></title>
            <link>https://medium.com/design-bootcamp/how-text-style-shapes-hierarchy-7fba378701ad?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fba378701ad</guid>
            <category><![CDATA[style]]></category>
            <category><![CDATA[hierarchy]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[perception]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Tue, 08 Apr 2025 09:36:55 GMT</pubDate>
            <atom:updated>2025-04-16T13:36:22.507Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of content, whether it’s a website, a document, or even a social media post, how you present your text is just as important as what you say. The strategic use of text styles isn’t just about aesthetics; it’s a powerful tool for establishing a clear visual hierarchy that guides your reader and enhances understanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*O6op-AuDXmCH4T6ej6xuPA.png" /></figure><p>Think of the text hierarchy as a roadmap for your content. It tells the reader which pieces of information are the most important, how different sections relate to each other, and what details are supplementary. A well-defined hierarchy makes your content scannable, digestible, and ultimately more effective.</p><p>So, how does text style contribute to this crucial hierarchy? Let’s break down the key elements:</p><h3>- Text Style Attributes</h3><p>Several text style attributes work together to create a sense of visual importance and structure. Let’s explore some of the most impactful ones:</p><h3><strong>Capitalization</strong></h3><p><strong>Signaling Importance</strong></p><p>As demonstrated in the example below, the way you capitalize text can immediately signal its level of importance:</p><h4><strong>HIGHEST: ALL CAPS</strong></h4><p><strong>e.g., THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG</strong></p><p>Using all uppercase letters commands attention and often indicates the most important information, such as main page titles or prominent calls to action. However, overuse can make text feel overwhelming.</p><h4><strong>HIGH: Title Case</strong></h4><p><strong>e.g., The Quick Brown Fox Jumps Over The Lazy Dog</strong></p><p>Capitalizing the first letter of each word (except for minor words) is commonly used for headings, subheadings, and key phrases. It denotes a high level of importance without the intensity of all caps.</p><h4><strong>REGULAR: Sentence case</strong></h4><p><strong>e.g., The quick brown fox jumps over the lazy dog</strong></p><p>This is the standard capitalization for body text and general content. It provides the bulk of the information in a readable format.</p><h4><strong>LOW: Lowercase</strong></h4><p><strong>e.g., the quick brown fox jumps over the lazy dog</strong></p><p>Using all lowercase can indicate less significant details, captions, or supplementary information. It often has a softer visual impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bcbICcOUZ3oHn9BQRUW1Kw.png" /></figure><h3><strong>Font Size</strong></h3><p><strong>Making the Important Bigger</strong></p><p>Font size is perhaps the most intuitive way to establish hierarchy. Larger fonts naturally draw the eye and signify greater importance, making them ideal for main headings and key messages. Smaller fonts are typically used for body text, captions, and less critical information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S_kXPEe-gdTUIr4xKusTHg.png" /></figure><h3><strong>Font Weight (Boldness)</strong></h3><p><strong>Adding Emphasis</strong></p><p>Bold text is a powerful tool for highlighting specific words, phrases, or subheadings within a block of text. It creates a visual distinction that draws the reader’s attention to key information and helps to break up large chunks of text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WelqjdBIjqfE5qkr4kNvSg.png" /></figure><h3><strong>Color</strong></h3><p><strong>Highlighting and Differentiating</strong></p><p>Color can be used strategically to highlight specific levels of information or to visually separate different sections of content. For example, headings might be a different color than the body text, or important links could be emphasized with a distinct color.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AAdXY_-0zh87L9ej3HMnA.png" /></figure><h3>Putting It All Together: Examples in Action</h3><p>Consider how these text styles might be used in different contexts:</p><p><strong>Website:</strong> A website might use a large, bold, all-caps font for the main page title (HIGHEST), followed by title case headings for sections (HIGH), sentence case for the main body text (REGULAR), and smaller, lowercase text for image captions (LOW).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CUzLuSC7NTeQhP7CuL0gmw.png" /></figure><p><strong>Article:</strong> An article might feature a large, bold title in title case (HIGHEST), followed by slightly smaller, bold subheadings in title case (HIGH), and then the main content in sentence case (REGULAR). Footnotes might be in a smaller font size and lowercase (LOW).</p><p><strong>Social media post: </strong>It may use all caps, bold, black, big title (HIGHEST from all perspectives) and a small, regular, grayish descriptor (LOWEST).</p><h3>Tips for Implementing Effective Text Hierarchy</h3><ul><li><strong>Consistency is Key:</strong> Maintain a consistent approach to your text styles throughout your content. This creates a predictable and easy-to-follow structure for the reader.</li><li><strong>Start Broad, Then Narrow:</strong> Begin by defining the most important elements and then progressively use less prominent styles for supporting details.</li><li><strong>Consider Your Audience:</strong> Choose text styles that are appropriate for your target audience and the overall tone of your content.</li><li><strong>Don’t Overdo It:</strong> Avoid using too many different text styles, as this can create visual clutter and confuse your readers. Aim for a clear and simple system.</li></ul><h3>Accessibility Matters: Beyond Visuals</h3><p>While visual hierarchy is crucial, it’s also important to consider accessibility. In web content, using semantic HTML elements like &lt;h1&gt;, &lt;h2&gt;, &lt;p&gt;, and so on, reinforces the visual hierarchy for screen readers and other assistive technologies. Additionally, ensure sufficient color contrast between text and background for readability, especially for users with visual impairments.</p><p>Mastering the art of using text styles to create a clear visual hierarchy is essential for effective communication. By strategically applying capitalization, font size, font weight, color, and spacing, you can guide your readers through your content, highlight key information, and ultimately enhance their understanding and engagement. So, next time you’re crafting content, remember that your text style is a powerful tool in shaping how your message is received.</p><blockquote>If you enjoy my work and want to show some love, consider treating me to a coffee! Your support means the world to me☕ <a href="https://buymeacoffee.com/khisraelyan">https://buymeacoffee.com/khisraelyan</a></blockquote><blockquote><strong>Follow me for more posts on Linkedin: </strong><a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fba378701ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-text-style-shapes-hierarchy-7fba378701ad">How text style shapes hierarchy</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Typography of Severance]]></title>
            <link>https://medium.com/design-bootcamp/typography-of-severance-53f99d05169a?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/53f99d05169a</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[severance]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Mon, 24 Mar 2025 07:32:22 GMT</pubDate>
            <atom:updated>2025-04-16T13:37:02.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDGIE02Ohor7OwsLYV2M1Q.jpeg" /></figure><p>I’ve just started watching the “Severance” TV series, and the design and style used to highlight the story are really stunning.</p><p>Most shows use design as just something in the background. But in “Severance,” the company itself, Lumon, feels like the bad guy, and its logo and text styles are a big part of that. They’re not just there to look good; they actually help create this creepy, controlling vibe.</p><h4>Let’s look at some of the fonts they use:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*akB7IpASZxKpiF4GWgHh2w.jpeg" /></figure><h4>Manifold Extended CF</h4><p>This font is used for important stuff at Lumon, like signs and even in their logo. It looks very clean, precise, and almost robotic. It makes Lumon feel like a powerful, cold corporation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hr7CJoSYZO0jcfPb3GhHCQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bR6mBMdHItcCaNxmJFIRtA.jpeg" /></figure><h4>Former DJR</h4><p>This font is for internal documents, like when they need to say sorry for an accident or give safety instructions. It looks a bit like Helvetica, which is a common business font, but something feels a bit off about it. It’s like getting a polite but passive-aggressive, quite cold email from HR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsdhwAVbYBI6Xs-rhaD7yw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_o0YVOVsgGzipu0xctU4BQ.jpeg" /></figure><h4>Optima</h4><p>You’ll see this font when they talk about Kier Eagan, the founder of Lumon, who they almost treat like a god. It’s a font that often suggests power and importance. It’s like this is the font of their internal “cult” around their founder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4JaRIVmZQ49itj8_cX5eA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7khCkyQlcFI-PaSqKSiQEQ.jpeg" /></figure><h4>Input Sans</h4><p>This is the font you see everywhere on the screens and interfaces in the show. It was made to be easy to read on computers, but in “Severance,” it feels a bit sinister. It’s used in those creepy statements they make employees repeat, and the cold, data-like look of the text adds to the unsettling feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*leXxSxsDhv6TRySZ0UwcLw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6b46WWg2WkekT-_ezYZ9sQ.jpeg" /></figure><h4>Scriptorama Trade Show JF</h4><p>This one’s interesting! It’s a retro, friendly-looking font that they use for things like recycling signs. It feels totally out of place in the serious world of Lumon. It’s like a big company trying way too hard to seem fun and approachable but failing miserably.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k6BJmiAvXiHmSF1r6jhaOg.jpeg" /></figure><p>The design in “Severance,” especially the choice of these fonts, is brilliant. It really helps to show how controlling and divided this company is. The typography isn’t just text; it’s like a quiet, scary force that makes you feel the unease of the show.</p><blockquote>If you enjoy my work and want to show some love, consider treating me to a coffee! Your support means the world to me☕ <a href="https://buymeacoffee.com/khisraelyan">https://buymeacoffee.com/khisraelyan</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53f99d05169a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/typography-of-severance-53f99d05169a">Typography of Severance</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX UI Product Design աշխատավարձերը Հայաստանում (2024 Հունիս)]]></title>
            <link>https://medium.com/@khatchadourisraelyan/ux-ui-product-design-%D5%A1%D5%B7%D5%AD%D5%A1%D5%BF%D5%A1%D5%BE%D5%A1%D6%80%D5%B1%D5%A5%D6%80%D5%A8-%D5%B0%D5%A1%D5%B5%D5%A1%D5%BD%D5%BF%D5%A1%D5%B6%D5%B8%D6%82%D5%B4-2024-%D5%B0%D5%B8%D6%82%D5%B6%D5%AB%D5%BD-80d935600e1c?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/80d935600e1c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[salary]]></category>
            <category><![CDATA[ux-ui-product-designer]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Fri, 31 Jan 2025 14:54:03 GMT</pubDate>
            <atom:updated>2025-01-31T14:54:03.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wjsIsx8QWDrB-EKxQHboZw.png" /></figure><p>Անցած տարվա, 2023 թվականի մայիսին UX UI PD աշխատավարձների հետ կապված անանուն հարցում անցկացրեցինք ու <a href="https://medium.com/@khatchadourisraelyan/ux-ui-product-design-%D5%A1%D5%B7%D5%AD%D5%A1%D5%BF%D5%A1%D5%BE%D5%A1%D6%80%D5%B1%D5%A5%D6%80%D5%A8-%D5%B0%D5%A1%D5%B5%D5%A1%D5%BD%D5%BF%D5%A1%D5%B6%D5%B8%D6%82%D5%B4-2023-%D5%B4%D5%A1%D5%B5%D5%AB%D5%BD-bf26792bbede"><strong>արդյունքները համակարգեցինք մեկ հոդվածում</strong></a>, ժամանակն է տվյալները թարմացնելու, դինամիկան հասկանալու</p><p><strong>2024 թվականի հունիս ամսի հարցումն ակտիվ էր մեկ շաբաթ։</strong><br>🚀Ի դեպ, ձեր խնդրանքով, այս անգամ ավելացվել էին մի քանի հարցեր․<br>1․ Ընկերության ոլորտը<br>2․ Ընկերության տիպը<br>3․ Աշխատանքային պայմանավորվածությունը<br>4․ Աշխատավայրի գտնվելու երկիրը</p><p>ℹ️ Տարբերակների ձևակերպումների ոչ լիարժեք կոնկրետության նպատակը մասնակիցների առավելագույն անանունություն ապահովելն էր։</p><p>Այսպիսով՝ աշխատավարձերի միջակայքերի մասին<br>2024 թվականի հունիսին արված հարցման արդյունքում ստացանք 63 տվյալ, Intern, Junior, Junior+, Mid, Mid+, Senior, Senior/Lead, Lead, Design manager, Head of department հաստիքների համար։</p><h4>Սկսենք Ինտերններից</h4><p>Ունենք մեկ տվյալ, մի ուսումնական կենտրոնից (անունը չենք հրապարակի տվյալների գաղտնիությունը պահպանելու նպատակով), աշխատավարձը նշված է 0 դրամ, օֆիսային, կես դրույք։</p><p>Ինչքանո՞վ է փոխհատուցվում ինտերնի օրական սննդի և տրանսպորտի նվազագույն ծախսերը, ինչքանո՞վ է օրինական, և ի՞նչ դեպքերում է ընդունելի, եկեք քննարկենք քոմենթներում 💬</p><h4>Ջունիորներ</h4><p>Ջունիորների աշխատավարձերը տատանվում են 100,000 դրամից մինչև 582,000 դրամը՝ լրիվ դրույք աշխատանքի համար (նախորդ տարվա հետազոտությունում միջակայքը 75,000–300,000 էր)</p><p>Նաև, job-title-ներից պարզեցինք, որ տվյալ Strong junior-ը ստանում է շատ Junior position-ներից ցածր աշխատավարձ։</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c6E9skBAv_-8Dzq14Uo17A.png" /></figure><h4>Middle-ներ</h4><p>Middle-ների աշխատավարձերը Հայաստանում հիմնականում տատանվում են 250,000–650,000 դրամի շրջակայքում, հետաքրքիր է, որ բավականին շատ խաղադրույքներով խաղերի դիզայնով զբաղվողների տվյալներ ունենք (9 տվյալ), նրանց աշխատավարձերը տատանվում են 300,000 դրամից մինչև 650,000 դրամ՝ Հայաստանում, և մինչև 2,500,000 դրամ՝ Արաբական Միացյալ էմիրություններում՝ Դուբայ։ Ճիշտն ասած ավելի բարձր թվեր էին սպասվում։ Կարծում եմ աճելու տեղ ունեն, հաշվի առնելով ոլորտի ահռելի շրջանառությունն ու խնդրահարույց էթիկայի հանգամանքը։</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDh-7Z1FvnN4jaC1p1qbUg.png" /></figure><h4>Senior-ներ</h4><p>Senior-ների աշխատավարձերը տատանվում են 350,000 կամ 500,000 դրամից մինչև 1,250,000 դրամ միջակայքում (հիմնվելով տրամադրված 7 տվյալների վրա) ինչը ավելի քիչ է քան նախորդ տարվա միջակայքը (400,000–1,800,000դրամ)։ Այս տարի ունենք նաև Senior-Lead կատեգորիա, դա՝ հաջորդիվ։</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0thiNv7XFoag8_ei5VmRkg.png" /></figure><h4>Senior/Lead-եր</h4><p>Senior/Lead-երի աշխատավարձերը, ըստ տրամադրված 5 տվյալների, տատանվում է 350,000–2,200,000 դրամի միջակայքում</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPVSneQW16s7Ae9mWeCLOA.png" /></figure><blockquote><em>Հարցերի, քննարկումների, և հետագա հարցումներին մասնակցելու համար հետևեք ինձ </em>Linkedin-ում․ <a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></blockquote><blockquote><em>Եվ հետևեք տելեգրամյան ալիքին հայերենով՝ </em><a href="https://t.me/UXPOV"><em>https://t.me/UXPOV</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80d935600e1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Observer Effect: When Measurement Shapes User Behavior (and What UX Designers Can Do About It)]]></title>
            <link>https://medium.com/design-bootcamp/the-observer-effect-when-measurement-shapes-user-behavior-and-what-ux-designers-can-do-about-it-1da9946cfd65?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/1da9946cfd65</guid>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[effect]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[observation]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Fri, 22 Mar 2024 06:01:55 GMT</pubDate>
            <atom:updated>2024-03-22T08:23:41.699Z</atom:updated>
            <content:encoded><![CDATA[<p>We strive to create intuitive and delightful experiences. We obsess over user flows, conduct usability testing, and craft interfaces. But what if the very act of measuring user behavior is subtly influencing it, potentially skewing our results?</p><p><strong>This, my friends, is the observer effect in action.</strong></p><h3>The Hawthorne Effect</h3><p>is a phenomenon in which simply observing participants in a study can alter their behavior. It was first observed in a series of experiments conducted at the Hawthorne Works factory near Chicago in the 1920s. Researchers were investigating the effect of lighting on worker productivity. They increased and decreased the light levels in the workplace, expecting to see a clear correlation between light levels and output.</p><p>However, to their surprise, productivity went up in almost every condition, regardless of the actual light level. It turned out that the workers were responding to the fact that they were being singled out and observed, not necessarily the change in light. The attention itself motivated them to work harder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AZJdhTaGieKl4Cy7MY6qUA.png" /><figcaption>Observation changes behavior. Hawthorn effect</figcaption></figure><p>This highlights the importance of considering potential observer effects in experiments. The act of measuring performance can sometimes influence the behavior being measured, making it difficult to isolate the true effect of the independent variable (in this case, light levels).</p><h4>Let’s apply that to the UX</h4><p>Imagine testing a new checkout process — users might act differently knowing their actions are being monitored. This can lead to inflated task completion rates or a hesitation to explore new features.</p><p>So, how can we, ensure our findings paint an accurate picture of the user journey? Here are some strategies:</p><p><strong>1. Embrace Observational Research:</strong> Move beyond lab settings and observe users in their natural habitat. Tools like session recordings and heatmaps can provide valuable insights without directly interfering with their experience.</p><p><strong>2. Prioritize Passive Data:</strong> Utilize website analytics and user logs to understand real-world usage patterns. This data reveals what users actually do, not what they might do under the eye of a researcher.</p><p><strong>3. Focus on Qualitative Feedback:</strong> Conduct user interviews to understand the “why” behind user behavior. Open-ended questions can reveal frustrations and motivations that quantitative data might miss.</p><p><strong>4. Transparency is Key:</strong> Be upfront with users about any research methods. Explain the purpose of your study and how their data will be used. This fosters trust and reduces the chance of them altering their behavior.</p><p>Remember, the goal is to understand users in their natural state. By using a combination of research methods and being mindful of the observer effect, we can design experiences that truly resonate with them. After all, the best designs are informed by authentic user behavior, not an illusion created by the act of measurement itself.</p><p><strong>Let’s continue the conversation!</strong> Share your thoughts and experiences with the observer effect in the comments below.</p><p>For more interesting stuff connect me on LinkedIn: <a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1da9946cfd65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-observer-effect-when-measurement-shapes-user-behavior-and-what-ux-designers-can-do-about-it-1da9946cfd65">The Observer Effect: When Measurement Shapes User Behavior (and What UX Designers Can Do About It)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning from the Rise and Fall of Clubhouse]]></title>
            <link>https://medium.com/design-bootcamp/learning-from-the-rise-and-fall-of-clubhouse-d8257433f90d?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8257433f90d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[fail]]></category>
            <category><![CDATA[clubhouse]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Mon, 11 Mar 2024 12:18:21 GMT</pubDate>
            <atom:updated>2024-03-11T19:45:08.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*sWLrVCEILyBGBsifAYHMFQ.jpeg" /><figcaption>Clubhouse app on AppStore</figcaption></figure><p>In March 2020, at the height of the global pandemic, a new social media platform emerged. Clubhouse, an audio-based social media app, was launched by Paul Davison and Rohan Seth. It quickly gained popularity, attracting celebrities and entrepreneurs alike. The app’s invite-only policy created a sense of exclusivity and hype, with some invite codes even being sold on eBay for $400. However, despite its initial success, Clubhouse couldn’t sustain its popularity and has since dropped off the App Store charts. So, what went wrong?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*lQGcrwZ6TqLac-7Xqp6ACg.png" /></figure><p>Several factors contributed to Clubhouse’s decline:</p><ol><li><strong>Inability to Monetize</strong>: Despite its popularity, the creators of Clubhouse struggled to successfully monetize the platform.</li><li><strong>Competition</strong>: Other social media platforms, including Spotify, Twitter, and Facebook, launched similar features, diluting Clubhouse’s unique selling point.</li><li><strong>Lack of Innovation</strong>: The app failed to introduce new features and updates to keep users engaged.</li><li><strong>Removal of Invite Requirement</strong>: The removal of the invite requirement led to a loss of interest as it diluted the sense of exclusivity.</li></ol><p>Clubhouse’s failure offers valuable lessons for both entrepreneurs and users of social media platforms.</p><p>A key takeaway from Clubhouse’s downfall is the importance of having a clear monetization strategy. Despite having a large user base, Clubhouse struggled to generate revenue. This highlights the need for social media platforms to have a solid business model that goes beyond just attracting users.</p><p>Clubhouse’s decline was accelerated by the launch of similar features by other social media giants. This underscores the importance of continually innovating and staying ahead of the competition,</p><p>The removal of Clubhouse’s invite-only requirement led to a loss of interest among users. This suggests that a sense of exclusivity can be a powerful tool in attracting and retaining users. However, it’s also important to strike a balance, as too much exclusivity can limit a platform’s growth.</p><p>While Clubhouse’s future remains uncertain, the lessons from its rise and fall are clear. As we navigate the ever-evolving landscape of social media, it’s crucial to remember that success is not just about attracting users, but also about offering value, staying ahead of the competition, and having a sustainable business model.</p><p><em>For more insights and interesting posts, feel free to connect with me on LinkedIn. Let’s continue the conversation there!</em></p><p><a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8257433f90d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/learning-from-the-rise-and-fall-of-clubhouse-d8257433f90d">Learning from the Rise and Fall of Clubhouse</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RIZEN Framework: Prompt engineering]]></title>
            <link>https://medium.com/design-bootcamp/rizen-framework-prompt-engineering-2d260b872521?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d260b872521</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[language-model]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Mon, 26 Feb 2024 11:00:36 GMT</pubDate>
            <atom:updated>2024-02-26T22:17:53.319Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re constantly seeking ways to improve our efficiency and unlock new possibilities. Entering the world of Large Language Models (LLMs) — such as ChatGPT or Gemini, revolutionized our design processes. But how do we effectively communicate with these Generative AIs to get the most out of them?</p><p>The answer lies in the <strong>RIZEN Framework</strong>, a structured approach to crafting prompts that guide LLMs toward creating exceptional UX deliverables. Let’s dive deeper into each step of RIZEN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*grqrZbWFbs2GCHoFwqCc6Q.jpeg" /></figure><h4><strong>R — Role</strong></h4><p>Imagine your LLM as a skilled collaborator — a UX researcher, UI copywriter, or even a usability testing facilitator. By defining the <strong>role</strong> you need, you set the stage for the LLM to assume the appropriate expertise and produce relevant outputs.</p><p>For example, if you’re designing a new onboarding process, you might prompt your LLM: <strong>“Act as a UX researcher and conduct an in-depth analysis of user pain points during the current onboarding experience.”</strong> This role sets the tone for the LLM to focus on gathering user insights and identifying areas for improvement.</p><h4><strong>I — Instructions</strong></h4><p>Think of this step as writing a <strong>clear and concise design brief</strong>. Provide specific instructions on the desired deliverable, just like you would for any other team member.</p><p>For instance, instead of a vague request like “Help me design a better landing page,” instruct your LLM:<strong> “Generate three landing page concept variations for our new productivity app, targeting busy professionals aged 25–35.”</strong> This ensures the LLM understands the specific goal, target audience, and desired number of outputs.</p><h4><strong>S — Steps</strong></h4><p>Break down the task into <strong>actionable steps</strong>, providing the LLM with a roadmap to follow. Think of it as guiding your assistant step-by-step through the design process.</p><p>For instance, when building a persona, your prompt could be: <strong>“Create a detailed user persona for our primary user group, tech-savvy professionals aged 25–35. Include information on their demographics, motivations, frustrations, and goals.”</strong> This helps the LLM structure the persona by providing specific details to focus on.</p><h4><strong>E — End Goal</strong></h4><p>Clearly define the <strong>purpose and target audience</strong> of the LLM’s output. This ensures the generated content aligns perfectly with your project’s vision.</p><p>For example, while designing a user flow for a mobile app, you might state: <strong>“This user flow should cater to first-time users and guide them through the app’s core functionalities seamlessly and intuitively.”</strong> This sets a clear goal for the user flow and aligns the LLM’s efforts with the desired user experience.</p><h4><strong>N — Narrowing</strong></h4><p>Just like any design project, provide <strong>constraints and specific guidelines</strong> to refine the LLM’s output. This helps ensure the results are consistent and meet your design standards.</p><p>For instance, when creating a user interface mockup, you might specify: <strong>“Use a minimalist design aesthetic with high-contrast colors. Maintain consistency with our existing design system and prioritize a mobile-first approach.”</strong> These guidelines ensure the LLM generates a UI that aligns with your overall brand and design language.</p><h3>Let’s go through it ones again</h3><p><strong>R — Role</strong></p><ul><li>Define the AI’s <strong>role</strong> based on the task at hand. Examples:</li><li>“Act as a UX researcher…”</li><li>“Act as a UI copywriter…”</li><li>“Act as a usability testing facilitator…”</li></ul><p><strong>I — Instructions</strong></p><ul><li>Give the AI <strong>clear instructions</strong> on the desired deliverable. Think of it like writing a design brief:</li><li>“Create a user flow for our new onboarding process…”</li></ul><p><strong>S — Steps</strong></p><ul><li>Outline the <strong>process</strong> you’d follow as a UX designer. Provide a structured pathway for the AI:</li><li>“Start by identifying key user pain points, then map out decision points and potential interactions. Include alternative paths for error states.”</li></ul><p><strong>E — End Goal</strong></p><ul><li>State the <strong>purpose and target audience</strong> of the deliverable. This aligns the AI’s output with your project’s vision:</li><li>“This persona should represent our primary user segment: tech-savvy professionals aged 25–35 interested in productivity tools.”</li></ul><p><strong>N — Narrowing</strong></p><ul><li>Set <strong>constraints or style guides</strong>. This helps refine the AI’s output:</li><li>“Limit the user flow to a maximum of 5 steps.”</li><li>“Use friendly and conversational language for the UI copy.”</li><li>“Adhere to our existing design system for visual elements.”</li></ul><h3><strong>Example</strong></h3><p><strong>Designing a Landing Page</strong></p><p>Let’s say you want a compelling landing page concept. Your RIZEN prompt might look like this:</p><ul><li><strong>Role:</strong> Act as a UI/UX designer specializing in landing pages.</li><li><strong>Instructions:</strong> Generate a landing page concept for our new time-tracking app.</li><li><strong>Steps:</strong> Start with a bold headline and value proposition. Include a clear call to action, social proof, and visuals aligning with our brand.</li><li><strong>End Goal:</strong> Target busy professionals looking to streamline their workdays.</li><li><strong>Narrowing:</strong> Use a minimalist aesthetic. Prioritize mobile-first design.</li></ul><p><strong>Benefits of RIZEN for UX</strong></p><ul><li><strong>Rapid Ideation:</strong> Generate multiple concepts or variations quickly.</li><li><strong>Streamlined Persona Development:</strong> Get rich data points for building user personas.</li><li><strong>Efficient Copywriting:</strong> Create user-centric copy for interfaces and marketing materials.</li><li><strong>Scalable User Testing:</strong> Design AI-powered usability test scenarios.</li></ul><p><strong>Remember:</strong> The RIZEN framework is customizable! Adapt it to various UX tasks and experiment to discover the best ways to collaborate with your AI design assistant. Experiment, adapt, and explore different prompt variations to see what works best for your specific needs and the capabilities of your chosen LLM.</p><p><strong>Ready to take your design process to the next level?</strong> Start incorporating the RIZEN framework into your workflow and witness the transformative power of AI in UX.</p><p>Want to explore more ways to leverage AI for a smoother, smarter design process? Follow me on LinkedIn for additional tips and tricks: <a href="https://am.linkedin.com/in/khatchadour">https://am.linkedin.com/in/khatchadour</a></p><p>Let’s unlock the full potential of AI and revolutionize the way we design!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d260b872521" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/rizen-framework-prompt-engineering-2d260b872521">RIZEN Framework: Prompt engineering</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mystery Box Mania: UX Lessons from the Surprise Shopping Phenomenon]]></title>
            <link>https://medium.com/design-bootcamp/mystery-box-mania-ux-lessons-from-the-surprise-shopping-phenomenon-3356db114e0d?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/3356db114e0d</guid>
            <category><![CDATA[shopping]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mystery]]></category>
            <category><![CDATA[mystery-box]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Fri, 29 Dec 2023 11:37:51 GMT</pubDate>
            <atom:updated>2023-12-30T13:44:34.316Z</atom:updated>
            <content:encoded><![CDATA[<p>Mystery boxes have become a popular online shopping phenomenon, offering a thrill of the unknown and the potential for rare finds. But have you ever stopped to think about the user experience (UX) behind these surprise packages?</p><p>In this article, we’ll delve into the world of mystery boxes, analyzing their UX strengths and weaknesses on websites, and exploring potential ways to enhance the experience for both sellers and buyers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uo4ZRp3vqLRvo9Vf" /></figure><p><strong>The core appeal of mystery boxes lies in their inherent uncertainty. </strong>Buyers gamble on the contents, driven by the excitement of potentially snagging valuable items or completing coveted collections. This element of surprise taps into our natural curiosity and desire for reward, creating a unique and often addictive shopping experience.</p><h4>Website UX Challenges</h4><p>While the allure of mystery boxes is undeniable, their website UX often presents challenges:</p><ul><li><strong>Information asymmetry<br></strong>Buyers lack crucial information about the potential contents, making it difficult to assess value and manage expectations.</li><li><strong>Unfulfilled desires</strong><br>The element of chance can lead to disappointment, especially when buyers receive items they dislike or have no use for.</li><li><strong>Limited customization</strong><br>Most mystery boxes offer little to no control over the contents, which can alienate buyers with specific preferences.</li></ul><h4>UX Design Strategies for Improvement</h4><p>Here are some ways to improve the UX of mystery boxes on websites:</p><ul><li><strong>Transparency and trust</strong><br>Provide detailed information about the range of possible items, their rarity, and potential value ranges. This builds trust and helps buyers manage expectations.</li><li><strong>Curated options</strong><br>Offer themed or categorized mystery boxes catering to specific interests or fandoms. This allows buyers to tailor their experience and increase the likelihood of receiving desired items.</li><li><strong>Customization elements</strong><br>Introduce limited customization options, such as choosing the item category or brand preference. This empowers buyers and enhances the feeling of control.</li><li><strong>Post-purchase engagement</strong><br>Create a community around mystery boxes. Encourage buyers to share their experiences, unboxings, and collections. This fosters engagement and loyalty.</li><li><strong>Leverage gamification</strong><br>Implement reward systems based on purchases or unboxings. This adds an element of fun and incentivizes repeat purchases.</li></ul><h4>Beyond Traditional Mystery Boxes</h4><p>The concept of surprise and discovery can extend beyond physical products. Consider these alternative approaches:</p><p><strong>Digital mystery boxes</strong><br>Offer curated bundles of digital content like music, movies, or ebooks.</p><p><strong>Subscription mystery boxes</strong><br>Deliver regular surprises with themed or personalized deliveries.</p><p><strong>Experience mystery boxes</strong><br>Provide access to exclusive events, workshops, or activities.</p><h4>So,</h4><p>Mystery boxes present a unique opportunity for engaging and interactive online shopping experiences. By addressing UX challenges and implementing creative strategies, sellers can foster trust, excitement, and brand loyalty amongst their customers. Remember, the key lies in balancing the thrill of the unknown with a sense of control and value for your buyers.</p><p>Share your thoughts on mystery box UX in the comments below! <br>Have you had positive or negative experiences? <br>What features would make them more appealing to you?</p><p>Let’s start a conversation about how to elevate the mystery box experience for everyone involved.</p><blockquote>Also follow me on Linkedin: <a href="https://www.linkedin.com/in/khatchadour/">https://www.linkedin.com/in/khatchadour/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3356db114e0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/mystery-box-mania-ux-lessons-from-the-surprise-shopping-phenomenon-3356db114e0d">Mystery Box Mania: UX Lessons from the Surprise Shopping Phenomenon</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measuring the Heartbeat of UX: How Google’s HEART Framework Keeps Users Pulse-Racing]]></title>
            <link>https://medium.com/design-bootcamp/measuring-the-heartbeat-of-ux-how-googles-heart-framework-keeps-users-pulse-racing-4d21dd89d44a?source=rss-952bf1f4616------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d21dd89d44a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[measure]]></category>
            <dc:creator><![CDATA[Khatchadour Israelyan]]></dc:creator>
            <pubDate>Mon, 25 Dec 2023 07:25:19 GMT</pubDate>
            <atom:updated>2024-01-04T13:24:08.226Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine crafting a beautiful, intuitive interface, only to discover users bouncing off faster than a pinball off a tilted table. Ouch. In the world of UX design, good intentions aren’t enough. We need data-driven insights to understand what truly resonates with users and keeps them coming back for more. This is where Google’s HEART framework steps in, offering a simple yet powerful lens to measure the health of your user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vzdNS9aLdUMUwfQ-7VGL7Q.png" /></figure><h4>What is the HEART Framework?</h4><p>Think of HEART as a stethoscope for your product. Each letter represents a crucial metric that taps into the core of user experience:</p><p><strong>Happiness: <br></strong>How satisfied are users with your product? Think surveys, NPS scores, and user reviews.</p><p><strong>Engagement: <br></strong>Are users actively interacting with your product? Track metrics like session duration, feature usage, and click-through rates.</p><p><strong>Adoption:<br></strong>How many users are actively using your product? Monitor sign-up rates, active user numbers, and feature adoption statistics.</p><p><strong>Retention:<br></strong> Are users sticking around? Analyze churn rates, time to first engagement, and repeat usage patterns.</p><p><strong>Task success:<br></strong> Are users achieving their goals with ease? Measure error rates, completion times, and user feedback on specific tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SWmiqoWeKgnXtwkugFjOXQ.png" /><figcaption>Example of HEART</figcaption></figure><h4>Why Use HEART?</h4><p>HEART’s beauty lies in its simplicity and holistic approach. Unlike siloed vanity metrics, it provides a comprehensive picture of how users experience your product across the entire lifecycle. This allows you to:</p><p><strong>Identify strengths and weaknesses:<br></strong> Pinpoint areas where your product shines and areas needing improvement.</p><p><strong>Prioritize design decisions: <br></strong>Focus your efforts on metrics that matter most to your users and business goals.</p><p><strong>Track progress and measure impact: </strong><br>Quantify the effectiveness of your UX design decisions.</p><p><strong>Tell a compelling story: </strong><br>Communicate the value of UX to stakeholders with clear, data-driven insights.</p><h4>Putting HEART into Practice</h4><p>Implementing HEART effectively requires more than just slapping metrics on a dashboard. Here are some tips:</p><p><strong>Set clear goals and objectives: </strong><br>Align your HEART metrics with your overall product goals and user needs.</p><p><strong>Choose the right metrics:</strong> <br>Not all HEART metrics are relevant for every product. Pick the ones that resonate most with your specific context.</p><p><strong>Go beyond the numbers: <br></strong>Qualitative research like user interviews and usability testing can provide valuable context to quantitative data.</p><p><strong>Share and iterate:<br></strong> Communicate your findings with stakeholders and use them to inform continuous improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6SjR-D7It_zMgAeOQ084Q.jpeg" /><figcaption>Template to build HEART</figcaption></figure><p>Remember, HEART is not a one-size-fits-all solution. It’s a flexible framework that you can adapt to your specific needs. By measuring the right metrics and interpreting them thoughtfully, you can gain valuable insights into your users’ hearts and minds, ultimately crafting delightful experiences that keep them coming back for more.</p><p>So, put on your stethoscope, listen to the beat of your product, and let HEART guide you toward a healthier, happier user experience.</p><p><strong>Bonus Tip: </strong>Check out Google’s “HEART framework: Choosing the right metrics for your product” article for deeper insights and practical examples.</p><blockquote><em>Also follow me on Linkedin: </em><a href="https://www.linkedin.com/in/khatchadour/"><em>https://www.linkedin.com/in/khatchadour/</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d21dd89d44a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/measuring-the-heartbeat-of-ux-how-googles-heart-framework-keeps-users-pulse-racing-4d21dd89d44a">Measuring the Heartbeat of UX: How Google’s HEART Framework Keeps Users Pulse-Racing</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>