<?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 Solomon Eberechukwu Obika on Medium]]></title>
        <description><![CDATA[Stories by Solomon Eberechukwu Obika on Medium]]></description>
        <link>https://medium.com/@obikasolomon?source=rss-45b02f3c0ffe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NffDh1X7zwmckLrA66Qg1w.jpeg</url>
            <title>Stories by Solomon Eberechukwu Obika on Medium</title>
            <link>https://medium.com/@obikasolomon?source=rss-45b02f3c0ffe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:13:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@obikasolomon/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[How Listening Without Leading Shapes Better UX]]></title>
            <link>https://medium.com/@obikasolomon/how-listening-without-leading-shapes-better-ux-290544e1a190?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/290544e1a190</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[devcareerxcoursera]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 07:20:11 GMT</pubDate>
            <atom:updated>2026-11-21T07:20:11.116Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ys3Uy9wlze7mQuQG4iDjAQ.jpeg" /><figcaption>Photo by Christina Morillo: <a href="https://www.pexels.com/photo/man-wearing-blue-dress-shirt-facing-whiteboard-1181343/">https://www.pexels.com/photo/man-wearing-blue-dress-shirt-facing-whiteboard-1181343/</a></figcaption></figure><p>While studying <strong>Empathize, Define, and Ideate</strong> in the Google UX Design Certificate, a few core practices have shaped how I think about problem solving:</p><ol><li><strong>Run ethical, neutral interviews:</strong> Set specific research goals and define target participant traits such as age, gender, and location, including checking direct competitors to learn more about who they reach. Use open-ended, non-leading, neutral questions, and always ask permission before recording the interview session. These people will serve as your research sample, which is a small group of people representing your target audience.</li><li><strong>Don’t rely on just one persona:</strong> A user persona gives an overview of user interviews, but meeting the needs of varied target users takes more than one persona and clear, actionable goals on how to solve them.</li><li><strong>Separate problem statements from hypotheses:</strong> A problem statement describes a user need that the product must address, and its insights explain <em>why</em> the user needs that solution. A hypothesis statement on the other hand is your best educated guess on how to address that need, supported by a clear value proposition.</li><li><strong>Look for gaps and generate lots of ideas:</strong> Competitive audits examine competitors’ strengths, weaknesses, and gaps such as things they are not doing across design, product features, customization options, or accessibility. And this can be shared in a written report or slideshow presentation with a summary of key points. To arrive at the right idea, generate plenty of ideas first using these two methods: <br><strong>a) How Might We (HMW) questions:</strong> This involves asking questions about how a problem/challenge can be solved and then taking notes of the ideas that come up. When doing this, keep drafts broad rather than too specific, be creative, and write down as many ideas as possible without leaving anything out. <br>b) <strong>Crazy Eights (rapid sketching):</strong> Crazy Eights is a rapid sketching method used during the ideation phase to help designers move through ideas quickly. The goal is to generate 8 ideas in 8 minutes by spending just 1 minute on each idea. This fast pace pushes you to explore plenty of possibilities so you can arrive at the right solution rather than getting stuck overthinking.</li></ol><p>5. <strong>Know when to step back or research deeper:</strong> Stepping away from your usual workspace such as physically leaving the desk, room, or screen setup where you normally work or study, moving to a quieter spot, taking a short walk, or changing your surroundings could give your mind a mental reset so fresh ideas can flow more easily. For strong design solutions, you also need to understand business needs and market gaps. If you run into roadblocks while coming up with ideas, pause and check whether you need more research and data before moving forward.</p><p>Conclusion<br>Great UX doesn’t happen by accident, it is the result of intentional empathy, disciplined problem framing, and fearless ideation. When we take the time to listen without leading, look beyond a single persona, and explore a wide range of ideas before committing to one, we build products that solve real human problems. As I continue my UX journey, these foundational habits serve as a reminder that the strongest designs always start with curiosity and genuine respect for the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=290544e1a190" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Design Sprints Transform Product Strategy and Team Collaboration]]></title>
            <link>https://medium.com/@obikasolomon/how-design-sprints-transform-product-strategy-and-team-collaboration-10053769af49?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/10053769af49</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[dev-careers]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 07:02:52 GMT</pubDate>
            <atom:updated>2026-10-24T07:02:52.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IcFNKBclB6HVnuVAo7Ht6w.jpeg" /><figcaption>Photo by ThisIsEngineering: <a href="https://www.pexels.com/photo/engineers-designing-app-3912478/">https://www.pexels.com/photo/engineers-designing-app-3912478/</a></figcaption></figure><p>As I document my path through the Google UX Design Professional Certificate, I have learned that product success relies on rapid validation, structured collaboration, and deep empathy. While broader frameworks like Design Thinking provide long-term vision, teams often need a faster way to turn complex challenges into testable solutions.</p><p>That is where the <strong>Design Sprint</strong> comes in. This is a focused, week-long design task developed by Jake Knapp at Google Ventures, to be used by a cross-functional team to rapidly improve a product and validate ideas before committing significant resources.</p><h4>The 5 Phases of a Design Sprint</h4><p>A Design Sprint comprise of a five-phase workflow: <strong>Understand</strong>, <strong>Ideate</strong>, <strong>Decide</strong>, <strong>Prototype</strong>, and <strong>Test</strong>.</p><ul><li><strong>Understand Phase:</strong> The process begins by bringing together a diverse group of cross-functional team members — including project managers, customer relationship managers (CRMs), engineers, marketers, and designers. By incorporating different backgrounds from across the company, the team uncovers domain expertise, aligns on business goals, and establishes a shared understanding of the core user problem.</li><li><strong>Ideate Phase:</strong> With a defined challenge, individual team members explore a wide array of potential design solutions. Rather than rushing to final graphics, the team brainstorms, sketches, and thinks through various wireframe ideas to visualize potential product flows.</li><li><strong>Decide Phase:</strong> After exploring multiple possibilities, the team reviews the proposed concepts, critiques trade-offs, and selects the single design solution best suited to solve the user’s primary challenge.</li><li><strong>Prototype Phase:</strong> The chosen concept moves into rapid development. Designers and builders transform the initial wireframes into a high-fidelity interactive prototype that looks, feels, and functions realistically enough to simulate a true user experience.</li><li><strong>Test Phase:</strong> The sprint concludes by putting the high-fidelity prototype directly into the hands of real target users. By observing actual user interactions and gathering direct feedback, the team validates assumptions and monitors the process in real time.</li></ul><p>To set a design sprint up for success, preparation is critical. Essential items for a successful sprint environment include comprehensive design sprint briefs, board stickers, user research insights, clear sprint rules, comfortable chairs, snacks, direct access to domain experts, and a structured post-sprint planning roadmap.</p><h4>Refining Strategy Through the Retrospective</h4><p>A Design Sprint does not end when testing wraps up. To maximize value, the UX design team conducts a <strong>Design Sprint Retrospective</strong> which is a critical feedback session designed to critique the sprint process itself.</p><p>To ensure actionable insights and prevent groupthink, every participant is encouraged to speak honestly. The team openly re-evaluates proposed ideas, analyzing why certain directions were chosen and why others were discarded, all done in a collaborative space where no one’s ideas are ridiculed.</p><p>During a retrospective, team members reflect on fundamental questions like:</p><ul><li>Did we conduct enough research prior to execution?</li><li>Did we deeply understand the user and their specific challenges?</li><li>Did our final prototype actually solve their problem?</li></ul><h4>Conclusion</h4><p>Design Sprints bridge the gap between creative strategy and practical execution. By uniting cross-functional teams around rapid prototyping, continuous feedback, and constructive retrospectives, we ensure that digital products remain grounded in real human needs.</p><p>Are you using Design Sprints or structured retrospectives in your team’s workflow? How do you keep team members aligned when solving complex user problems?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10053769af49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for Real Impact the Power of the 5-Step Design Thinking Process]]></title>
            <link>https://medium.com/@obikasolomon/designing-for-real-impact-the-power-of-the-5-step-design-thinking-process-657e5ff87889?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/657e5ff87889</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[devcareerxcoursera]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 04:17:22 GMT</pubDate>
            <atom:updated>2026-10-24T04:17:22.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D7S6gdgF-QXaQYCm" /><figcaption>Photo by <a href="https://unsplash.com/@uxindo?utm_source=medium&amp;utm_medium=referral">UX Indonesia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever used a digital product that left you feeling confused or frustrated? Often, products fail not because of poor visual design, but because they were built without a deep understanding of the user.</p><p>As an entry-level UX designer documenting my journey through the Google UX Design Professional Certificate, I have learned that great design starts with empathy. At the core of every user-centric product is <strong>Design Thinking</strong> — a UX framework used to create solutions that take into full cognizance the users’ needs and solve their real-world problems.</p><p>While many picture design as a linear path, Design Thinking is an iterative, cyclical process. Feedback continually feeds back into the loop to refine the product experience.</p><p>Here is a breakdown of the 5 key phases of the Design Thinking framework:</p><ol><li><strong>Empathy: </strong>Before attempting to build a solution, you must step into the shoes of the end user. In this initial phase, you conduct research, observe environments, and listen to target audiences to uncover their true frustrations, motivations, and pain points.</li><li><strong>Define</strong>: Once research insights are gathered, it is time to narrow down your focus. In the Define stage, you synthesize qualitative and quantitative data to pinpoint the exact problem of the user you want to solve. Crafting a clear, user-focused problem statement ensures your team remains aligned on who you are building for and why.</li><li><strong>Ideate</strong>: With a defined problem statement, creativity takes center stage. Ideation is about generating a wide range of innovative design concepts. Rather than settling on the first idea, designers explore diverse angles and systematically choose the solution that best addresses the user’s core challenge.</li><li><strong>Prototype</strong>: This phase moves concepts from abstract ideas into tangible forms. Here, designers build information architecture (IA), sitemaps, sketches, wireframes, and low-to-high fidelity interactive prototypes to bring the proposed product solution to life. Prototypes serve as early, cost-effective models to test functionality before development begins.</li><li><strong>Test</strong>: A design is only as good as its real-world usability. In the testing phase, real users interact with the product while designers monitor their interactions, take note of confusion points, and gather direct feedback.</li></ol><h4>Conclusion</h4><p>Just like any effective user experience design framework, Design Thinking is not a one-and-done checklist. Rather, it is a continuous and cyclical process. Testing often uncovers new user insights that send designers back to refine prototypes or even re-evaluate core problem definitions. By keeping human needs at the center of every iteration, we ensure that technology remains an empowering solution rather than a barrier.</p><p>Are you currently using Design Thinking in your daily product or design workflows? Which stage do you find the most rewarding? Let’s connect and share insights in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=657e5ff87889" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why User-Centered Design is Everyone’s Business]]></title>
            <link>https://medium.com/@obikasolomon/why-user-centered-design-is-everyones-business-9e01efa03738?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e01efa03738</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[devcareerxcoursera]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 03:49:24 GMT</pubDate>
            <atom:updated>2026-10-15T03:49:24.887Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KywMEeGTVlap6f4t2ZP0vQ.jpeg" /><figcaption>Photo by Isaac Mitchell: <a href="https://www.pexels.com/photo/white-signs-on-a-wall-14367788/">https://www.pexels.com/photo/white-signs-on-a-wall-14367788/</a></figcaption></figure><p>Have you ever opened an app or visited a website and felt like it was built specifically for you? Every seamless button tap, clean layout, and intuitive flow feels almost like magic. But as I dive deeper into the Google UX Design Professional Certificate, I’m realizing that great products are never built by accident. They come to life through a deliberate framework called <strong>User-Centered Design (UCD)</strong> which is an approach where we put the user front and center in the design process, ensuring their needs, frustrations, and goals are deeply considered at every single turn.</p><h3>The 4-Step User-Centered Design Process</h3><p>To turn empathy into action, UCD relies on a structured, four-step lifecycle that guides us from an abstract thought to a validated solution. They include:</p><ol><li><strong>Understand: </strong>This foundational stage is all about building empathy. Before writing a single line of code or sketching a wireframe, we must immerse ourselves in the user’s world. We conduct user interviews, observe behaviors, and uncover pain points. As builders, this phase stops us from building solutions for problems that do not actually exist.</li><li><strong>Specify: </strong>Once we collect qualitative and quantitative insights from our research, we synthesize the data to specify the core problem. Here, we define who our user is, what they are trying to achieve, and what obstacles are standing in their way. Crafting clear problem statements and user personas in this phase ensures our entire team stays aligned on what we are trying to solve.</li><li><strong>Design: </strong>With a clear problem defined, we move into creative execution. This is where designers brainstorm layout options, sketch low-fidelity wireframes, map user flows, and build interactive prototypes. Software builders and product teams look closely at this stage to visualize how features will translate into actual architecture, ensuring the product looks, feels, and functions seamlessly.</li><li><strong>Evaluate: </strong>The design process does not end when a prototype is built. In the evaluation phase, we put our designs directly into the hands of real users through usability studies. We watch how they interact with the product, note where they get confused, and gather critical feedback. This evaluation naturally exposes gaps in our assumptions, paving the way for us to iterate and refine.</li></ol><p>As we evaluate our prototypes and look closely at how different people interact with our platforms, we quickly realize that a standard, one-size-fits-all product often leaves vulnerable groups behind. This is why knowing the three design methodologies is vital in order to produce more tailor-made product/service that caters to the challenges of our target user.</p><h3>3 Design Approaches: Universal, Inclusive, and Equity-Focused</h3><p>It is very important to note that these approaches or methodologies are not just unique to digital product designers but also to anybody who is involved in delivering, building, or producing something that others will use such as building construction, policy, or a learning framework.</p><p>Moving beyond basic usability, how we approach our target audience defines how far our digital products can truly reach. Modern product development requires us to adopt intentional frameworks that account for human diversity:</p><ul><li><strong>Universal Design:</strong> Universal design focuses on creating a single, standardized solution that can be used by everyone to the greatest extent possible, without needing specialized adaptations. Universal design aims for a broad single solution for all users irrespective of their background.</li><li><strong>Inclusive Design: </strong>Inclusive design broadens our scope by taking cognizance of people from different backgrounds, ages, genders, classes, races, and life experiences throughout the design process. It acknowledges that human diversity is multi-dimensional and ensures that diverse perspectives actively shape how we build a product.</li><li><strong>Equity-Focused Design: </strong>Equity-focused design takes inclusion a step further by focusing specifically on frequently underrepresented users such as those who are historically marginalized or usually left out of mainstream product creation. Instead of treating accessibility as an afterthought, equity-focused design intentionally centers these communities from day one, ensuring they are fully catered to in the experience and can achieve equal access and outcomes.</li></ul><p>User-centered design is a commitment to empathy, equity, and human connection. By using the four-step UCD process and applying thoughtful design approaches, we can build digital spaces that welcome, respect, and empower people. As digital and non-digital product users, builders, and creators, we have the power to shape technology, infrastructure, and policy that doesn’t just function but truly serves humanity.</p><p>How are you integrating inclusive and equity-focused practices into your current product workflows or job?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e01efa03738" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 5-Step Journey Behind Every Product You Love]]></title>
            <link>https://medium.com/@obikasolomon/the-5-step-journey-behind-every-product-you-love-ea163271139d?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea163271139d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[dev-careers]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 02:52:23 GMT</pubDate>
            <atom:updated>2026-10-12T02:52:23.202Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Yx_cBrrY6SyneEckKyRjA.jpeg" /><figcaption>Photo by RDNE Stock project: <a href="https://www.pexels.com/photo/green-and-yellow-pencil-on-white-paper-7947648/">https://www.pexels.com/photo/green-and-yellow-pencil-on-white-paper-7947648/</a></figcaption></figure><p>Every great product starts as a simple thought before transforming into a tool that solves real user problems. As I dive into the Google UX Design Professional Certificate, I am learning that the Product Development Life Cycle (PDLC) is a core framework guiding this transformation. It is also very important to note that this framework is an iterative process.</p><p>The PDLC encompasses five key stages, they include:</p><ol><li><strong>Brainstorm:</strong> As a first line of action, the designers and team members generate a wide variety of creative ideas and potential concepts to solve a specific user problem. This discovery phase relies on early research and collaboration to explore possibilities without premature judgment.</li><li><strong>Define: </strong>Here, the team narrows down the broad ideas collected during brainstorming to focus on core concepts and establish a clear problem statement, hypothesis statement, and goal statement. This stage sets a solid project scope by figuring out exactly who the product is for and what features it needs.</li><li><strong>Design:</strong> In this stage the UX designers translate user insights and requirements into tangible assets like wireframes, storyboards, and interactive prototypes. The primary focus is on shaping how the product will look, feel, and function for the end user.</li><li><strong>Test: </strong>Finished prototypes are put directly into the hands of real users to evaluate overall usability and uncover potential friction points. The team carefully analyzes this feedback to refine and iterate on the product before it goes live.</li><li><strong>Launch: </strong>Finally, the finished version of the product is officially shared and released to the public. Marketing strategies roll out alongside this release to build awareness and transition the concept into a real-world tool.</li></ol><h4><strong>Conclusion</strong></h4><p>Mastering the PDLC is essential for any entry-level UX designer. It provides a clear roadmap to bridge the gap between creative concepts and impactful, real-world solutions.</p><p>What stage of the PDLC do you find most exciting? Let’s connect in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea163271139d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Different UX Roles Come Together to Build Great Products]]></title>
            <link>https://medium.com/@obikasolomon/how-different-ux-roles-come-together-to-build-great-products-b9a5bfa2609e?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9a5bfa2609e</guid>
            <category><![CDATA[dev-careers]]></category>
            <category><![CDATA[user-needs]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[cross-functional-teams]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 06:34:44 GMT</pubDate>
            <atom:updated>2026-10-08T06:34:44.867Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8ryxixPF7lVkkWvj" /><figcaption>Photo by <a href="https://unsplash.com/@alanaprilio?utm_source=medium&amp;utm_medium=referral">Alan Aprilio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>UX Designers work with a variety of other professionals in the development of a product. This is important in order to build high-quality products that meets users’ needs. These people are called cross-functional UX professionals.</p><h4>Who is a cross-functional professional?</h4><p>This is a somebody who has a broad range of knowledge in several professional domains and who also works alongside the UX designer to achieve a shared goal in a project. It is also someone who is a specialist that works in an interdisciplinary team to deliver project deliverables independently.</p><h3>Examples of cross-functional UX professionals</h3><p>There are several people who are usually involved in the user experience design of a product. Some of them are:</p><p><strong>1. Product Lead: </strong>This professional bridges the gap between user needs, business strategy, and technical viability. They synthesize input from designers, engineers, and marketers to define the overarching product vision and roadmap. They also ensure the cross-functional team delivers a product that provides genuine value while achieving key business metrics.</p><p><strong>2. UX Researcher: </strong>The UX Researcher acts as the voice of the user by investigating user behaviors, motivations, and pain points. Through qualitative interviews, usability testing, and quantitative analytics, they transform raw user data into actionable insights for the entire team. They role ensures that product, design, and engineering teams build solutions grounded in real user needs rather than assumptions.</p><p><strong>3. UX Writer: </strong>This person can also be called a content designer, they craft the microcopy and product language that guides users seamlessly through digital interfaces. They ensure that buttons, error messages, and onboarding flows are clear, concise, and intentional by aligning brand tone with user intent and turning complex interactions into intuitive, human-centered conversations.</p><p><strong>4. Brand Designer: </strong>The Brand Designer makes sure that the product’s identity both visually and emotionally is consistent across every user touchpoint. Working closely with UX designers and marketers, they make sure the user journey feels cohesive whether a customer is viewing an ad, visiting the website, or using the app.</p><p><strong>5. UX Engineer: </strong>The UX Engineer sits directly at the intersection of design and front-end software development. They translate high-fidelity design concepts into functional and realistic prototypes. By speaking both design and engineering languages, they advocate for technical feasibility early in the design process while preserving design integrity in the final codebase.</p><h3>Conclusion</h3><p>At the end of the day, building extraordinary digital products isn’t a solo mission, it takes a village of diverse minds speaking a shared language of taste, knowledge, experience, and skill to bring a product idea to fruition with experiences that users genuinely love and remember.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9a5bfa2609e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The User Experience and 4 Qualities of a Good Product]]></title>
            <link>https://medium.com/@obikasolomon/the-user-experience-and-4-qualities-of-a-good-product-26b2a65159d8?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/26b2a65159d8</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[dev-careers]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 16:15:08 GMT</pubDate>
            <atom:updated>2026-09-20T16:15:08.934Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I12bcpSa9uCik384" /><figcaption>Photo by <a href="https://unsplash.com/@jonathanborba?utm_source=medium&amp;utm_medium=referral">Jonathan Borba</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A few weeks ago, I began the Google UX Design professional certificate course on Coursera under the auspices of DevCareer. And so far, I’m grateful for the added wealth of knowledge I’ve amassed which I intend to share weekly on this platform. <br>One of things I learned is the origin of the term user experience and the characteristics of a good product.</p><p>The term UX means User Experience. This term was first coined in the 1990s by cognitive psychologist, Don Norman. This refers to how a person (the user) feels about his or her interaction/experience with a product whether physical or digital.</p><h3>4 Qualities of a Good Product</h3><p>In order to design products that meets a vast array of your intended users’ needs, the product should have the following qualities:</p><p><strong>1. Usefulness</strong>: This refers to the ability of a product to solve user problems. People want to use products that help them solve their problems. Therefore, product designers need to answer the question: “how useful is this product?” and “how would this product help users solve their problem?”.</p><p><strong>2. Equitable</strong>: This is when a product is designed with the inclusivity in mind. It is when a product is designed to meet the needs of those who are usually been excluded in the design process. Here, the designer takes into consideration people from diverse background, race, gender, ability, and ethnicity.</p><p><strong>3. Enjoyable</strong>: Users enjoy products that are appealing to use. This serves as a boost for their continued patronage of that product. When an app or website has a good visual design and interactivity, users enjoy using it and as such they are more likely to recommend it to others.</p><p><strong>4. Usable</strong>: When a product is usable it means it can function properly and is easy to use. However, the lack of this leads to an increase in the bounce rate of users which means they will leave even before completing their intended goal of using the product.</p><h3>Conclusion</h3><p>Good design is marked by thoughtfulness and a commitment to good user experience. As UX designers, we should help users avoid mishaps and roadblocks by incorporating the four qualities of a good product when designing. This ensures that we’re putting users front and center.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26b2a65159d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 FASTEST WAYS TO BECOME A WEB DEVELOPER]]></title>
            <link>https://medium.com/@obikasolomon/3-fastest-ways-to-become-a-web-developer-fd77386853cb?source=rss-45b02f3c0ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd77386853cb</guid>
            <category><![CDATA[learn-web-development]]></category>
            <category><![CDATA[become-web-developer]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[become-web-developer-fast]]></category>
            <dc:creator><![CDATA[Solomon Eberechukwu Obika]]></dc:creator>
            <pubDate>Mon, 16 Aug 2021 14:00:13 GMT</pubDate>
            <atom:updated>2021-09-11T14:37:52.489Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A lady using a laptop with a book and a pen" src="https://cdn-images-1.medium.com/max/640/0*ZS-MXleQsLyp0Zmj" /></figure><p>Learning web development can be a rewarding and intimidating process at the same time.</p><p>It is a skill that will pay a great dividend in an individual’s professional journey, hence it requires a great amount of hard work and learning.</p><p>This also means that there is a need for proper assimilation of this invaluable and high-demand skill making it dreadful prone and discouraging if the learner isn’t properly set on the right track.</p><p>This article is one that I can surely relate to because it doesn’t just talk about the fastest ways to become a developer but it brings the solution to the depression that I have gone through.</p><p>So, if you are going through a tough time learning this skill, feeling depressed as a result of your learning pace, and comparing your progress to others.</p><p>If you’re in any of these boats, one piece of advice, <strong><em>keep reading</em></strong>. 😁</p><h4>WEB DEVELOPMENT</h4><p>Web development is the process of building web applications that run on the web. These are usually applications that can be viewed and interacted with by users.</p><p>Web development is made up of three parts commonly called <strong><em>stacks, </em></strong>namely:</p><ul><li>Front-end development</li><li>Backend development</li><li>Full-stack development</li></ul><p>These three stacks are the different ways of looking at web development and they are independent career paths that you can pursue as an aspiring web developer.</p><p>It will take quite some time to expatiate on them. Well, good thing I’m not running away.</p><blockquote>Front-end developer</blockquote><p>This is a person who learned the client-side aspect of web development. He/she is concerned with building web applications that the client (the user through the browser) can see. They focus more on the appearance of the website concentrating on things like colors, typography, positioning, etc</p><p>The main technologies that frontend developers use in their work are:</p><ul><li>HTML(HYPERTEXT MARKUP LANGUAGE)</li><li>CSS (CASCADING STYLE SHEET)</li><li>JAVASCRIPT</li></ul><p>They also use additional tools that make development much easier called frameworks and libraries. These include;</p><ul><li>VUE</li><li>REACT</li><li>ANGULAR</li><li>BOOTSTRAP</li><li>TAILWIND</li><li>NODE.JS</li></ul><blockquote>Backend developer</blockquote><p>The guy who builds the interactive side of web applications and who brings functionality to the designed website is called the backend developer.</p><p>These developers make it possible for a user to send information via a form, and the developer can receive the input coming from the respective user and therefore can make use of that information.</p><p>Simply put, a backend developer makes the client and application interaction completely possible, else the web development process isn’t complete.</p><p>This set of professionals have the basic knowledge of:</p><ul><li>HTML</li><li>CSS</li></ul><p>However, they are expected to have fundamental knowledge and work constantly with most of the following:</p><ul><li>JAVASCRIPT</li><li>NODE.JS</li><li>EXPRESS.JS</li><li>MONGOOSE</li><li>PHP</li><li>MySQL</li></ul><p>In some cases, for those using python programming, they would use Django as a framework for backend development.</p><blockquote>Full Stack developer</blockquote><p>This web developer can be described as the best of both worlds.</p><p>He/she has professional knowledge of both the frontend and backend development knowing and using most of all the web application technologies common to a web developer.</p><p>Having gone through the three stacks of a web developer, we are now ready to delve into the ways of learning how to become a web developer quickly.</p><h4>1. Building Project</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*K28VO9KTmDdhxr1u" /></figure><p>I know this is a strategy that you probably must have heard before because of how popular it is in the software engineering industry. Nonetheless, it is an effective way to learn web development fast because as you go through the process of building projects you begin to see firsthand how things work and how they are being applied.</p><p>As you build projects often you begin to realize what works and what doesn’t.</p><p>So get projects and start building. This is will help to ensure that you get the hands-on experience of the web development process fast. Some of the importance of building projects are:</p><ul><li><strong>Growing a strong and better portfolio</strong></li></ul><p>The more you build projects the better you build projects and inadvertently, you create a wide pool of portfolios that you can show to your prospective clients and recruiters so that you can land the job you want. Also, it is professionally important to create a portfolio with series of projects to show your credibility.</p><ul><li><strong>Learning fast</strong></li></ul><p>Learning web development fast is the reason why you are here and so it will be relieving to know that the more you build projects the faster you learn web development.</p><ul><li><strong>Experience</strong></li></ul><p>If you don’t have experience with a craft you cannot deliver an excellent job. Without experience, you won’t have the confidence to apply and take on available jobs. With a series of projects to your name, it becomes evident that you have a track record of work and the quality required to take on a gig.</p><ul><li><strong>Confidence</strong></li></ul><p>Confidence is one important thing that you will gain when you build projects. That feeling of accomplishment when you complete a project will make you believe in yourself more and with that positive feeling, it becomes easier to be a web developer fast.</p><p>Here are some web development projects for you to have fun with:</p><ul><li>Todo list App</li><li>Personal portfolio</li><li>Product Landing Page</li><li>Form page</li><li>Documentation page</li><li>Calculator</li><li>Games</li><li>A humanitarian project you’re passionate about</li><li>Tribute page</li></ul><h4>2. Teaching others</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*CjKD1wSprFZCYBCf" /></figure><p>It is quite true that when you teach what you learn you find more insights with regards to what you are learning.</p><p>I have found out that as you teach others what you know it is possible to encounter problems that could challenge the level of your assimilation which determines how and whether you can help solve the problem.</p><p>Check out this <a href="http://dx.doi.org/10.1080/14703297.2016.1156011">article about teaching to learn</a> which would also give you some more insights into the concept of teaching what you’ve learned.</p><p>Let’s go over some benefits of teaching others, be it a peer, siblings, students what you learn in web development:</p><ul><li><strong>Increase level of communication</strong></li></ul><p>Communication is an important soft skill in the tech industry, especially in the software development space. Thus, having this skill is vital. As you explain to others what you know, you try to find ways you could explain it better, therefore, improving your level of communication.</p><p>One last thing, you gain more confidence because you are giving out something the other person knows little about.</p><ul><li><strong>Increase knowledge</strong></li></ul><p>A famous French moralist and essayist, Joseph Joubert puts it this way, “To teach is to learn twice”.</p><p>This means as you teach others you relearn gaining better insights and at the same time finding efficient ways to explain what you teach.</p><h4>3. Practice</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*n1orXj3BUTq-hLPy" /></figure><p>Practice is an activity that will never be erased from the process of learning anything worth learning especially coding. It is already a cliche to say that the more you practice the better you become.</p><p>Practice is just like exercise, the more you practice the stronger your mental, intellectual and coding muscles become.</p><p>While this activity is needed, you might be asking how you should go about it.</p><p>Truth is, you should practice building things… yeah, projects.</p><p>Sites like:</p><ul><li><a href="https://www.frontendmentor.io/">frontend mentor</a></li><li><a href="https://www.freecodecamp.org/">Freecodecamp</a></li><li><a href="http://codepen.io/">Codepen</a></li><li><a href="https://www.w3schools.com/">W3schools</a></li></ul><p>These websites provide you with mockups or a coding environment you can build projects on and share with others.</p><h4>Conclusion</h4><p>Now that you have seen the 3 fastest ways to become a web developer, it will be of great benefit to you if you try these strategies out for yourself.</p><p>Becoming a web developer is not an easy task but by building different projects, teaching/sharing your knowledge with others, and finally by practicing you will become a web developer fast.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd77386853cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>