<?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 Cynthia Caxton on Medium]]></title>
        <description><![CDATA[Stories by Cynthia Caxton on Medium]]></description>
        <link>https://medium.com/@cynthiacaxton?source=rss-a22eb3fc0820------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QuUP5HhV41GzoPoQDGfKMg@2x.jpeg</url>
            <title>Stories by Cynthia Caxton on Medium</title>
            <link>https://medium.com/@cynthiacaxton?source=rss-a22eb3fc0820------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:11:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cynthiacaxton/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 Subjectivity of UX, Don’t Judge a Book by Its Broken Button.]]></title>
            <link>https://medium.com/@cynthiacaxton/the-subjectivity-of-ux-dont-judge-a-book-by-its-broken-button-7cf1374d142c?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cf1374d142c</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 08:14:02 GMT</pubDate>
            <atom:updated>2025-09-23T08:14:31.502Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Subjectivity of UX, Don’t Judge a Product by Its Broken Button.</h3><p>We’ve all been there, you open an app or website, something doesn’t feel right, and the first instinct is: <em>“Wow, this is a bad product.”</em><br>But pause for a second. Is the product bad, or did <em>your</em> experience with it simply not work out as expected?</p><p>This distinction matters. User experience (UX) is subjective; it’s how <em>you</em> perceive and interact with a product. And while one bad interaction can feel defining, it doesn’t always reflect the product’s overall quality or usefulness for others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xjJYOjnrieRInJzd" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.linkedin.com%2Fpulse%2Funderstanding-user-needs-heart-great-ux-design-nayyer-abbas-6i8of&amp;psig=AOvVaw1dkBvbvox1YZJ5eB_OyqsY&amp;ust=1758700529503000&amp;source=images&amp;cd=vfe&amp;opi=89978449&amp;ved=0CBkQjhxqFwoTCOiU65607o8DFQAAAAAdAAAAABA6">Image source</a></figcaption></figure><h3>The Subjectivity of UX</h3><p>The Subjectivity of UX is the idea that user experience is an individual, personal journey shaped by a user’s emotions, perceptions, prior knowledge, and unique circumstances. This makes UX distinct for every person and makes it difficult to measure uniformly.</p><p>Yes, we can measure objective aspects of design, things like load time, error rates, or task completion. But a user’s <em>overall satisfaction, feelings, and opinions</em> are subjective. They depend on personal identity, expectations, and context.</p><p><strong>So, what makes UX subjective?</strong></p><p>1. <strong>Individual Differences</strong>: Each user brings a unique background, including age, culture, past experiences, and preferences, that influences how they interpret and interact with a product or service. A teenager might navigate TikTok with ease, while their parent feels lost within minutes. Both are using the same product, but their backgrounds and digital fluency change the experience.</p><p><strong>2. Emotions and Perceptions</strong>: User experience isn’t just about functional performance; it includes the emotional, psychological, and perceptual responses to a product. A travel app that crashes before checkout doesn’t just cause frustration; it creates anxiety about missed deals. UX is never just functional; it’s emotional.</p><p><strong>3. Personal Context</strong>: A user’s beliefs, tastes, feelings, and even their physical or mental state can affect their experience, making it highly contextual and personal. A productivity app might feel empowering when you’re well-rested, but it can be overwhelming when you’re already stressed. Your context reshapes your perception.</p><p><strong>4. Holistic Relationship</strong>: UX is the ongoing relationship between a person and a product, not just what you do, but how you feel and what you think while doing it.</p><h4>How, Where, and What: Separating the Design from the Product</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DQ8jImsroM1WRAU5.png" /><figcaption><a href="https://miro.medium.com/v2/resize:fit:3840/1*r40wS6q1iklSynszHWDcbg.png">Image Source</a></figcaption></figure><blockquote>Our brains are wired to make quick judgments. When we encounter friction, our emotional brain (the limbic system) often overrides our logical brain. The frustration is real and valid, but it’s primarily a response to the interface and the interaction flow , not necessarily the core value of the product itself.<br> — — The Psychology of Frustration</blockquote><ul><li><strong>How did it fail?</strong> Did it fail because the feature you needed was missing (a product problem), or because you couldn’t find the feature that was there (a UX problem)? The “how” is often about navigation, clarity, and feedback.</li><li><strong>Where did the friction occur?</strong> Was it during the sign-up process? In the checkout flow? Pinpointing the “where” helps identify a specific design flaw in a particular user journey, rather than condemning the entire product.</li><li><strong>What was the core value?</strong> Ask yourself: “If I could magically bypass this frustrating step, would the end result be valuable?” If the answer is yes, you’ve identified a UX problem blocking a good product.</li></ul><p>This framework isn’t just for analysis; it’s a guide for different roles in the digital ecosystem:</p><ul><li><strong>For users:</strong> Before labelling a product as “bad,” take a moment to ask: <em>was it the design, my expectations, or my context that created the friction?</em> Perhaps you were in a hurry, or your prior experience with similar products set a different pattern. This reflective approach turns frustration into valuable, articulate feedback.</li><li><strong>For designers:</strong> This underscores the critical need to test with diverse user groups. A design that works perfectly in your bubble (with your expertise, tech-savviness, and stable Wi-Fi) might fail for someone with different abilities, older technology, or in a low-connectivity context. Empathy is the cornerstone of good UX.</li><li><strong>For businesses:</strong> Understand that every product won’t please everyone. Good UX is about strategic balance, not universal perfection. It’s about prioritizing the core journeys for your primary audience while minimizing friction for others. Investing in UX is about removing the biggest roadblocks to value, not paving every single possible path.</li></ul><p>Great UX isn’t about creating a flawless masterpiece on the first try. It’s a continuous process of research, testing, iteration, and improvement. The app you found confusing today might have been perfect for its initial target audience, and the company might be actively working on a redesign based on feedback from users just like you.</p><p>So, the next time you have a bad experience, pause and analyze it. Instead of saying “This product is bad,” try to articulate <em>what</em> was bad: “The checkout process has too many steps,” or “The menu labeling is unclear.” This shift in perspective not only makes you a more savvy consumer but also, if you choose to share it, provides incredibly valuable feedback to the people working to make that product better.</p><p>Thanks for reading this far. let’s stay connected, Cheers!<br><em>Follow for more Articles and videos via </em><a href="https://www.youtube.com/@cynthiacaxton"><em>YouTube</em></a><em>, </em><a href="https://www.linkedin.com/in/cynthia-caxton/"><em>LinkedIn</em></a><em> &amp; </em><a href="https://www.instagram.com/cynthiacaxton/"><em>Instagram</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cf1374d142c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Retrospective, A Tool For Team Growth]]></title>
            <link>https://medium.com/@cynthiacaxton/product-retrospective-a-tool-for-team-growth-c1f255d1ce24?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1f255d1ce24</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Thu, 03 Oct 2024 17:21:20 GMT</pubDate>
            <atom:updated>2024-10-03T17:21:20.875Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve worked in a team for a while, you’ve probably been part of a retrospective but if you haven’t conducted one yet or feel like they’re just another meeting to tick off, then allow me to shed light on how retrospectives can be a game-changing tool for your product teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yBRXoZiRCnARUA32.png" /></figure><p>From the perspective of a Product Manager, we’re always pushing to move forward new features, better user experience, and create more impact. But there’s one key process that helps us learn, grow, and improve as a team; <strong><em>The Product Retrospective</em></strong>. So, how can you run a retrospective that makes a difference? Let’s break it down.</p><h3>What is a Product Retrospective and why is it important?</h3><p>A retrospective is essentially a reflection session with your team, usually held at the end of a sprint, release, or project. It’s a time to look back and assess what went well, what didn’t, and how you can improve for the future.</p><p>You might be thinking, “Why can’t we just move on to the next thing?” Well, skipping a retrospective is like racing in a car for miles without checking your fuel gauge, temperature incase of overheating, or whether you’re even driving in the right direction. You might finish the race, but you’ll be missing out on critical insights that could make the next race smoother.</p><p>Retrospectives give you the chance to:</p><ul><li><strong>Learn from mistakes</strong>: Address problems before they grow.</li><li><strong>Celebrate successes</strong>: Recognize what’s working and keep doing it.</li><li><strong>Improve team collaboration</strong>: Build a culture of openness and continuous improvement.</li></ul><h3>How to Conduct an Effective Product Retrospective</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OJVJM59vJGP9SJx0.jpg" /></figure><p>There is no one-size-fits-all when it comes to conducting a retrospect, there are various approaches and templates you can use for this but let’s break it down into five simple and essential steps:</p><h3>1. Set the Stage</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I_ogymPOmyvN8AGd.png" /></figure><p>Create a space where everyone feels comfortable sharing their thoughts. Make it clear that this is not a blame game. It’s about <strong>learning and improving together</strong>. Set a collaborative tone by asking an icebreaker question like, “What’s one thing you’re proud of this sprint?”</p><h3>2. Gather Data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VkWro2cwbpTLoW3l.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fmedium.com%2Fhike-one-digital-product-design%2Feffective-yet-fun-retrospectives-336f6d40a65b&amp;psig=AOvVaw3et2EWkPW3LLyC0riHTSkm&amp;ust=1727526147339000&amp;source=images&amp;cd=vfe&amp;opi=89978449&amp;ved=0CBcQjhxqFwoTCPjpm8WO44gDFQAAAAAdAAAAABAE">Source</a></figcaption></figure><p>Now, let’s dive into the facts. Ask the team what went well and what didn’t. I like to use the “<strong>Start, Stop, Continue</strong>” method here:</p><ul><li><strong>Start</strong>: What should we start doing?</li><li><strong>Stop</strong>: What’s not working that we should stop?</li><li><strong>Continue</strong>: What’s working well that we should keep doing?</li></ul><p>You’d be surprised how much the right questions can change the outcome of your retrospective. You can also use another method as shown below;</p><ul><li><strong>What went well?</strong> (Celebrate the wins, no matter how small!)</li><li><strong>What didn’t go well?</strong> (Be constructive, not critical.)</li><li><strong>What can we improve?</strong> (Focus on actionable changes.)</li></ul><p>These questions keep the conversation balanced between positivity and areas for growth. Use a virtual whiteboard or sticky notes to jot down everyone’s feedback. It’s important to encourage <strong>all voices, </strong>even the quieter ones.</p><h3>3. Dig Deeper into Root Causes to Generate Insights</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j3KylhtZrcBT43fP.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fconceptboard.com%2Fblog%2Fproblem-solving-using-5-whys%2F&amp;psig=AOvVaw3I_dHOEs31SO8EhKCdyD2i&amp;ust=1727527613627000&amp;source=images&amp;cd=vfe&amp;opi=89978449&amp;ved=0CBQQjRxqFwoTCIjNroGU44gDFQAAAAAdAAAAABAZ">Image Source</a></figcaption></figure><p>It’s not enough to list out what happened, you need to understand <strong>why</strong> it happened. It’s easy to say, “We missed the deadline,” <em>but why</em>? The real value of a retrospective comes from digging into the root causes of what went wrong. Was it a lack of clarity on the goals? Miscommunication? An unexpected blocker?</p><p>Use techniques like the <strong>“5 Whys”</strong> to drill down and identify the core issue. For example:</p><ul><li>We missed the deadline. Why?</li><li>The feature took longer than expected. Why?</li><li>We didn’t scope it properly. Why?…</li></ul><p>Focus on uncovering the root cause of both the good and the bad. Once you find the root cause, you can work on preventing similar issues next time, this is where you’ll find your real growth opportunities.</p><h3>4. Create Actionable Items</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/0*pqm14LtJ-i5UN6BZ.png" /></figure><p>Reflection without action is just a conversation. Retrospectives only work if they lead to <strong>actionable steps</strong>. For each insight, define a concrete action that is specific, achievable, and can be assigned to someone on the team. That way, you ensure improvements happen, instead of just talking about them.</p><p>For example:</p><ol><li>If you identified communication issues, an action item could be <strong>“Implement daily standups”</strong> or <strong>“Create clearer documentation”</strong> for future projects.</li><li>If you struggled with feature scope, try <strong>“Break down larger features into smaller, manageable tasks.”</strong></li><li>If we’ve been missing deadlines because of vague user stories the action could be<strong> “The PM will work with the team to create more detailed stories by the next sprint.”</strong></li></ol><p>The goal is to walk out of the retrospective with a game plan for improvement.</p><h3>5. Close on a Positive Note</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/0*dIXxRBysVY6IPbvZ.png" /><figcaption>Image Source</figcaption></figure><p>Wrap up the retrospective on a positive note. It’s easy to focus on what went wrong, but don’t forget to <strong>celebrate </strong>your wins or give <strong>kudos</strong> to your team members for their openness and hard work.</p><p>A Product Retrospective isn’t just a meeting, it’s an opportunity. Done right, it can help your team improve processes, communication, and product quality. The best part? It fosters a culture of continuous learning and growth, which is exactly what we want as Product Professionals.</p><p>So, the next time you wrap up a sprint or project, don’t skip the retrospective. Trust me, the insights you gain will be well worth the hour you invest!</p><p>Thanks for reading this far. let’s stay connected, Cheers!<br><em>Follow for more Articles and videos via </em><a href="https://www.youtube.com/@cynthiacaxton"><em>YouTube</em></a><em>, </em><a href="https://www.linkedin.com/in/cynthia-caxton/"><em>LinkedIn</em></a><em> &amp; </em><a href="https://www.instagram.com/cynthiacaxton/"><em>Instagram</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1f255d1ce24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Conduct User Research For Product Success]]></title>
            <link>https://medium.com/@cynthiacaxton/how-to-conduct-user-research-for-product-success-465f9fe5126d?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/465f9fe5126d</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Fri, 27 Sep 2024 15:02:28 GMT</pubDate>
            <atom:updated>2024-09-27T15:02:28.120Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s face it, guessing what your users want is a risky game. As Product Professionals, we can’t afford to make decisions based on hunches or personal preferences. That’s where <strong>user research</strong> comes in.</p><p>User research is our secret weapon. It’s the key to understanding who our users are, what they need, and how they experience our product. The more we know, the better we can build products that actually <em>solve problems</em>. So, how do you, as a Product manager, designer etc, go about conducting user research? Let’s break it down:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HkJiUS4180CwupqH" /></figure><h3>1. Start with a Clear Goal</h3><p>Before you even begin reaching out to users, you need to ask yourself: <em>What am I trying to learn?</em> Am I trying to validate a new feature? Understand a pain point? Improve the onboarding flow?</p><p>The SMART framework can serve as a tool to help you define your research goal upfront, and let that guide the rest of the process. When you have a clear question in mind, you’ll know what kind of data you need to collect.</p><h3>2. Choose the Right Method</h3><p>User research isn’t one-size-fits-all. There are several methods you can use, and the right one depends on what you’re trying to learn. Some options include:</p><ul><li><strong>User interviews:</strong> These are great for gathering qualitative insights and understanding the “why” behind user behaviour. Ask open-ended questions, and let the conversation flow.</li><li><strong>Surveys:</strong> If you need quick, quantitative feedback from a larger group of users, a survey is your best friend. Just keep it short and sweet.</li><li><strong>Usability testing:</strong> Watch how users interact with your product in real-time. You’ll be surprised at the things you learn by observing them.</li><li><strong>Analytics:</strong> Dive into your product’s data to identify patterns in user behaviour. This can complement qualitative insights and give you the bigger picture.</li></ul><h3>3. Recruit the Right Participants</h3><p>Who should you talk to? The best people to interview are the ones who use your product regularly or the ones who should be using it but aren’t. Reach out to power users, new users, and even those who’ve churned. Each group has unique insights that can help you build a more well-rounded picture of your user base.</p><h3>4. Ask the Right Questions</h3><p>This is where things get tricky. Asking the right questions is the heart of good user research. You want to dig deep but not lead users to answers. A few tips:</p><ul><li><strong>Keep questions open-ended.</strong> Instead of asking “Do you like this feature?” try “How do you feel about this feature?”</li><li><strong>Focus on user experience, not product features.</strong> Avoid asking “What do you think about this button?” and instead, try “What were you expecting to happen next?”</li><li><strong>Ask follow-up questions.</strong> Sometimes the most valuable insights come when you dive deeper into their initial answers.</li></ul><h3>5. Listen Without Bias</h3><p>Here’s a hard truth; sometimes, user feedback isn’t what you want to hear. But as a Product Professional, you need to leave your ego at the door. Listen openly, and don’t try to guide the conversation toward the outcome you’re hoping for. If users are struggling with a feature you love, that’s an opportunity to make improvements.</p><h3>6. Synthesize Your Findings</h3><p>Once you’ve gathered your data, it’s time to make sense of it all. Look for patterns, common pain points, and unexpected insights. Don’t just summarize, <strong><em>Synthesize</em></strong>. What does the feedback mean for your product? How does it align with your roadmap? And most importantly, how can it inform your next steps?</p><h3>7. Share the Insights</h3><p>User research doesn’t belong to you alone. Share your findings with your team, this could be your developers, designers, marketers, and even stakeholders. Visuals like user journey maps or persona sketches can help bring the data to life and make the insights easier to digest. Everyone should be on the same page about what users need and how your product can serve them better.</p><h3>8. Take Action</h3><p>User research is only useful if you act on it. Once you’ve identified the key takeaways, incorporate them into your product strategy. Prioritize changes that will have the biggest impact on user experience, and communicate those updates to your users. Show them that their feedback leads to real improvements, it builds trust and loyalty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z8k7AMWrOWPqtXFj.jpg" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.liveabout.com%2Fanalyze-qualitative-research-findings-with-code-book-2296911&amp;psig=AOvVaw2BkrV4aQy7qHTK3-323kga&amp;ust=1727526471442000&amp;source=images&amp;cd=vfe&amp;opi=89978449&amp;ved=0CBcQjhxqFwoTCLDFmfOP44gDFQAAAAAdAAAAABAJ">Image source</a></figcaption></figure><p>Conducting user research isn’t just a checkbox in the product development process, it is a continuous practice. Users evolve, and so should your understanding of them. The more you invest in understanding your users, the better equipped you’ll be to build products that solve real problems, delight customers, and drive success.</p><p><strong><em>So, don’t guess. Get out there, talk to your users, and let their insights guide your product decisions.</em></strong></p><p>Thanks for reading this far. let’s stay connected, Cheers!<br><em>Follow for more Articles and videos via </em><a href="https://www.youtube.com/@cynthiacaxton"><em>YouTube</em></a><em>, </em><a href="https://www.linkedin.com/in/cynthia-caxton/"><em>LinkedIn</em></a><em> &amp; </em><a href="https://www.instagram.com/cynthiacaxton/"><em>Instagram</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=465f9fe5126d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Acing Your Next UX interview]]></title>
            <link>https://medium.com/@cynthiacaxton/acing-your-next-ux-interview-4038ed5860cc?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/4038ed5860cc</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 10:15:28 GMT</pubDate>
            <atom:updated>2023-12-03T10:15:28.324Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Whether you’re a seasoned UXer or just starting out in the exciting world of User Experience and product design, the path to landing that dream position often involves a series of interviews. While the specifics may vary for each company and organization, each stage of the process serves as a checkpoint to assess your skills, experiences, and alignment with the company’s culture. I will talk about some of these stages, highlight key questions to be aware of, and offer tips to help you excel in each one.</p><blockquote>Every interview process is an opportunity to showcase your value and quality of work. Don&#39;t forget, it&#39;s a two-way street!</blockquote><h3>Getting through the door, the phone screening interview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4aUiQhQD7a_FQXh5WNJng@2x.jpeg" /></figure><p>So, you’ve submitted your application, and now it’s time for the first hurdle, the phone screening interview. Lasting for about 10–20 minutes, this chat with the recruiter or HR rep aims to lay the groundwork. Expect questions about your availability, salary expectations, basic information verification, and what you know about the company.</p><p>In this part, you want to be clear and concise. Show genuine interest in the company’s mission. It will demonstrate to whoever you are on call with, that you are prepared and have done your research.</p><h3>The one with the hiring manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tsFSaxWM5f4sZjIgx9K2Ew@2x.jpeg" /></figure><p>Now, you’re onto the next level, the hiring manager interview, a 30-minute dive into your design process, tools, and teamwork dynamics. be ready for some in-depth questions like:</p><ul><li>Tell me about a time when you faced pushback from stakeholders.</li><li>Describe a situation where you encountered a problem without an immediate solution.</li><li>Share details about a project you’re proud of and why.</li></ul><p>Always use real examples, if you haven’t been in those situations acknowledge it and explain how you would handle them hypothetically by saying something around “But if I was faced with this type of situation this is how I am likely to handle it” This approach will help you avoid the risk of appearing uninformed. Additionally, be transparent about challenges, and emphasize your problem-solving skills.</p><h3>It’s your time to shine, portfolio presentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*z62wJ2GbFQElC73JVGSTPg@2x.jpeg" /></figure><p>You are in the spotlight now! You’ll be asked to present your portfolio to the technical team in a 45-minute to 1-hour session. you might want to set aside the traditional website portfolio, I would advise using a slide presentation instead because it’s time to wow your audience.</p><p>Tell a story, focusing on projects that capture the skills that are most needed for the job you are interviewing for.</p><p>During your presentation, key points to shine a light on would include your role and how you engaged with stakeholders, your research and problem identification techniques, alignment with business goals, your design process, your solution, and how you measured success.</p><h3>Taking up a challenge, could be whiteboard or take home</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DN1Opb_6Ki9d3ZP3fWbuCA@2x.jpeg" /></figure><p>I will speak mainly on the whiteboard challenge because this requires you to be physically or virtually present. It is a pivotal moment, you’ve probably got one hour tops to showcase your design thinking and problem-solving skills. You should expect a real-world or hypothetical problem.</p><p>Piece of advice; speak your thoughts out loud to demonstrate your collaboration skills, ask questions if need be, try clarifying key points like user demographics, pain points, contextual factors, contribution to business goals, design constraints, and how you’ll measure success.</p><h3>Culture fit assessment, are we a match?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*pKp_0YrKHH8vN22Npw0bQA@2x.jpeg" /></figure><p>After all the back-and-forth of replying to emails, joining interview meetings, and not knowing if you would get to the next phase or not, the final stretch is the culture fit interview, which typically lasts about 30 minutes. During this interview, the focus is on aligning with the company’s values. In my opinion, this is a two-way street, where both parties should ensure that their goals align and that compromises are not one-sided. At this stage, some interviewers might even include a personality test like the DISC assessment but you should expect questions like:</p><ul><li>Do you prefer working alone, with a partner, or with a team?</li><li>What management style suits you best?</li><li>Any favorite team-building activities?</li></ul><p>Be genuine, and if the company’s culture resonates with you or does not, express it. It’s a two-way street!</p><p>Remember, each interview stage is a chance to showcase your unique skills and experiences, navigating the UX interview process successfully requires a holistic approach that combines technical proficiency, effective communication, and cultural alignment. By understanding the nuances of each stage, you can prepare and strategically position yourself by showcasing your skills and experiences to leave a lasting impression on potential employers.</p><p>Stay confident, be yourself, and let your passion for UX shine through.<br>Cheers!</p><p>I have made a video you can watch in <a href="https://www.instagram.com/reel/ComeBE4jBnP/?utm_source=ig_web_copy_link&amp;igshid=MzRlODBiNWFlZA==">parts 1</a> and <a href="https://www.instagram.com/reel/Co4awnrDzxe/?utm_source=ig_web_copy_link&amp;igshid=MzRlODBiNWFlZA==">2</a>.</p><p>Thanks for reading this far. let’s stay connected, Cheers!<br><em>Follow for more Articles and videos via </em><a href="https://www.linkedin.com/in/cynthia-caxton/"><em>LinkedIn</em></a><em> &amp; </em><a href="https://www.instagram.com/cynthiacaxton/"><em>Instagram</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4038ed5860cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Impact of Crafting a Strategic UX Problem Statement]]></title>
            <link>https://medium.com/@cynthiacaxton/the-impact-of-crafting-a-strategic-ux-problem-statement-5885656d9f5b?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/5885656d9f5b</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[problem-statement]]></category>
            <category><![CDATA[strategic-thinking]]></category>
            <category><![CDATA[define-problem-statement]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Sat, 18 Nov 2023 19:06:27 GMT</pubDate>
            <atom:updated>2023-11-18T19:06:27.866Z</atom:updated>
            <content:encoded><![CDATA[<p>User experience (UX) design is an intricate dance between creativity and strategy, where designers strive to create products that not only dazzle visually but also seamlessly integrate into users’ lives. At the heart of this dance lies a seemingly simple yet profoundly impactful step — crafting a UX problem statement. In this article, I will be unravelling why this seemingly straightforward task holds the key to unlocking strategic success in UX design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wmzCHcu93pfBzi1z.png" /></figure><p><strong><em>Design Thinking as a Strategic Framework</em></strong></p><p>Before delving into the impact of a strategically crafted UX problem statement, it’s essential to understand the overarching framework in which it operates — <strong>design thinking</strong>. Design thinking is not just a methodology; it’s a mindset that places the end user at the centre of the design process. By embracing empathy, ideation, and iteration, design thinking fosters a collaborative and user-focused approach to problem-solving.</p><blockquote>The problem statement emerges as the guiding star within this framework, directing the design team toward meaningful solutions.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M3Zq3n2hzjjcKgwE.jpg" /></figure><p><strong><em>The Importance of a Problem Statement</em></strong></p><p>A problem statement serves as the lighthouse that prevents the design process from drifting aimlessly. Its importance cannot be overstated, it defines the boundaries, sets the scope, and clarifies the objectives of a design project. Without a well-defined problem statement, designers risk creating solutions for nonexistent problems or, conversely, missing the mark entirely.</p><p>It aligns the entire team with a shared understanding of the challenge at hand. It is the foundation upon which the entire design thinking process is built, fostering collaboration, guiding decision-making, and ultimately determining the success of a project. By clearly articulating the problem, designers lay the groundwork for strategic thinking, ensuring that every subsequent step is purposeful and user-centred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D2Xt1xAcw8sCCsXv.JPG" /></figure><p><strong><em>A Methodical Approach To Crafting Problem Statements</em></strong></p><p>Coming up with a strategic problem statement is an art in itself, demanding a methodical approach that combines analytical thinking with empathy for the end user. Here’s a step-by-step guide to formulating a problem statement that not only identifies the challenge but also sets the stage for strategic design:</p><ul><li><strong>Understand User Needs:</strong> Start by immersing yourself in the world of your users. Conduct user research, surveys, and interviews to gain deep insights into their behaviours, preferences, and pain points. A strategic problem statement is rooted in a profound understanding of the people you’re designing for.</li><li><strong>Define the Problem Scope:</strong> Clearly delineate the boundaries of the problem. Avoid broad or vague statements that can lead to confusion. A problem statement is focused and specific, providing a clear direction for the design team.</li><li><strong>Identify the Root Cause:</strong> Go beyond surface-level issues and dig into the root cause of the problem. Understanding why a problem exists is crucial for devising strategic solutions. This step ensures that your efforts are not just addressing symptoms but are genuinely transformative, a great way to do this is by using the 5whys technique by Sakichi Toyoda<strong>.</strong></li><li><strong>Consider Business Goals:</strong> Align the problem statement with the broader objectives of the business. A problem statement not only addresses user needs but also supports the overall goals and vision of the organization. This alignment ensures that the design solution is not only user-centric but also strategically valuable.</li><li><strong>Involve Stakeholders:</strong> Collaborate with key stakeholders to gather diverse perspectives. Every problem statement is enriched by input from different departments and disciplines. By involving stakeholders early in the process, you foster a sense of collective ownership and alignment.</li><li><strong>Craft with Precision and Clarity:</strong> The language you use matters. Craft the problem statement with precision and clarity, avoid jargon and ambiguous terms. A strategic problem statement is a communication tool that should resonate with everyone involved in the project, from designers to executives.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rcz_T6PXFmht1J3e.jpeg" /></figure><p><strong><em>The Fruits of a Thoughtful Problem Statement</em></strong></p><p>A meticulously crafted problem statement isn’t just a starting point; it’s a catalyst for a cascade of positive outcomes in the UX design journey. These outcomes signal that the design process is not only effective but strategically aligned with broader objectives.</p><p><strong>Precision in Design Decisions: </strong>The problem statement acts as a filter, guiding designers to make precise decisions that directly address the identified challenge. This precision minimizes the risk of design drift, ensuring each choice contributes strategically to the overall solution.</p><p><strong>Efficient Resource Allocation: </strong>By clearly outlining the problem, a strategic statement aids resource allocation. Design teams can focus on solving identified issues, avoiding unnecessary detours that might dilute the strategic impact of the project.</p><p><strong>Measurable Success Metrics: </strong>Strategic problem statements help establish measurable success metrics, whether it’s increased engagement, enhanced usability, or improved conversion rates. These metrics become benchmarks for evaluating the effectiveness of the design solution.</p><p><strong>Enhanced Stakeholder Buy-In: </strong>A thoughtfully crafted problem statement is a persuasive tool for gaining stakeholder buy-in. When stakeholders grasp the strategic importance of the identified problem, they are more likely to support the design process, fostering smoother project execution and increasing the chances of product success.</p><p><strong>Seamless User Adoption: </strong>Ultimately, the true measure of strategic success in UX design is the seamless adoption of the final product by end users. A problem statement capturing user needs paves the way for solutions resonating with the audience, ensuring the design strategy aligns strategically with the goal of user satisfaction.</p><p>The impact of crafting a UX problem statement cannot be overstated. As the guiding force within the design thinking framework, a well-defined problem statement serves as a blueprint, directing designers with precision and purpose. Its power lies in its ability to foster user-centred strategies, align multidisciplinary teams, and drive iterative refinement. Beyond the initial stages, a strategically crafted problem statement unlocks a series of positive outcomes that are beneficial both to the users and the business. It is not merely a theoretical exercise but a practical tool that transforms the design process into a strategic journey, leading to solutions that not only dazzle aesthetically but strategically fulfil user needs and expectations.</p><p>Thanks for reading this far. let&#39;s stay connected, Cheers!<br><em>Follow for more Articles and videos via </em><a href="https://www.linkedin.com/in/cynthia-caxton/"><em>LinkedIn</em></a><em> &amp; </em><a href="https://www.instagram.com/cynthiacaxton/"><em>Instagram</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5885656d9f5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FORTOE]]></title>
            <link>https://medium.com/@cynthiacaxton/fortoe-f61294e75a97?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/f61294e75a97</guid>
            <category><![CDATA[ux-ui-product-designer]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 08:32:09 GMT</pubDate>
            <atom:updated>2020-07-29T08:43:56.853Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNnYwJSlyeUuKTMBBz5DBQ.png" /></figure><p><strong><em>A UX Case Study</em></strong></p><h4>Overview</h4><p>Fortoe is a web photo repository where photographers and other content creators can upload license-free images and videos for others to use freely.</p><h4>The Challenge</h4><p>Create a site with diversity, and one that allows the user to download images in bulk. Users should be able to make an open request for photos on the website.</p><h4>Approach</h4><p>A survey was carried out to reach out to our Target users and balance these data with the companies Goals.</p><h4>Outcome</h4><p>A web repository site that allows Photographers to upload images and videos and enhance the user experience by enabling bulk download and open request.</p><h4>Length of Project</h4><p>3 weeks (Speculative Project)</p><h4>Role</h4><p>In a team of Six, I played the role of the Lead UX/UI Designer</p><h4><strong>RESEARCH</strong></h4><p>During the research phase, we sought to understand what our users look for in licensed free photo repository websites, what they think about having a portfolio on a web repository site and generally, how they would like a bulk download feature. We also needed to understand the needs and pain points of our target user so as to better understand how they feel and create a solution for that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eGhkCOHZks47XvoqJ_uwKA.jpeg" /></figure><p><strong>Secondary Research: Competitive Analysis</strong></p><p>A competitive analysis was performed to understand the strengths, weaknesses, similarities, and differences between competitor of a photo repository website.</p><p>Our competitive analysis produced the following insights:</p><p>Findings</p><ul><li>Limited Uploads: Most of the competitors offer limited uploads for content and the content is reviewed before it is published, this will help in image/video control</li><li>Stats: Stats on how the images are doing are sent to the creative</li><li>Social Features: Only a few offer the means for content creators to communicate on their platform, it appears to be a feature that is not expected by users but will be appreciated when it is made available.</li><li>Bulk Downloads: Most of the research competitors do not offer a feature for their users to be able to download images in bulk, these are pain points that need to be resolved.</li><li>Diversity: Diversity in our researched competitors is at its minimum, users tend to get frustrated when they search through images and not find a particle image because they (the competitors) do not avail to their users with contents that are diverse.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrcmJv0L1Px1kGThcb6JZg.jpeg" /></figure><p><strong>Personas Creation</strong></p><p>We created personas that reflected the data we had collected through our user research. Getting a sense of the general target audience helped us deliberate about a licensed free photo repository would appeal to different demographics with varying needs.</p><p>Afterwards, we used all of the qualitative data gathered during the research process to create Dan Usman, a user persona. Dan is a 32-year-old self-employed young man who lives in Lagos. He mostly spends his time on the road, he enjoys travelling and spends a lot of time on social media. He likes to show the world his exploring lifestyle so he posts mostly on his social media handles and photo repository web sites. We also created a second persona for Anna steel who is a 27-year-old Doctor who lives in the federal capital territory Abuja. Because of her busy schedule, she seldom goes for social activities. As an introverted person, she spends most of her lone time reading articles online and surfing the Internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rcmLl3gRCT2ffiQwEyL24A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0fxVSZDYtX5IJi1J4dbcPA.png" /></figure><p><strong>Deductions</strong></p><p>From our primary/ secondary research and Personas, we deduced from it, insights and needs we had generated. First, we identify their needs and pain points that define our design challenges. Secondly, we restructured these challenges into possible solutions archived through brainstorming. Below are our deductions;</p><ul><li>Primarily value picture/video quality above all</li><li>Users rely heavily on stock sites for their workflow</li><li>They need more access to racially diverse photos and images during a search</li><li>Users can only endure a download time of less than a minute.</li><li>Users would like to have a social connecting feature incorporated into the product such as liking and commenting on photos</li><li>Users would like the open request feature incorporated into the website.</li><li>Users show high interest in the Bulk Download feature.</li></ul><p>When Users decides to use this product as a portfolio site, they would be interested and considerate of the following;</p><ul><li>Sufficient space.</li><li>A simple and easy to use interface.</li><li>A significant social media footprint with the product for more exposure.</li><li>Significant client poll and,</li><li>Access to job opportunities.</li></ul><h3>Business and User Goals</h3><p>To find a happy medium where users and stakeholders will be happy, we reflected on the business goals, user goals, and technical considerations. The moment we found a common ground, we decided what product features were necessary for the prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*xqq8XlgkRQVYi0yI-EE2og.png" /></figure><h4>INFORMATION ARCHITECTURE.</h4><p>A high-level list of web features was created to further define and guide the vision for the product. We created a site map of a licensed free web photo repository that incorporated Our design goals.</p><h4>Wireframes</h4><p>We began the process of wireframing with sketches of several of the main screens for the web site. During this process, we thought of possible ways the layers and contents will be structured to satisfy user and business goals in a feasible way. Our wireframe sketch became a guide to our digital wireframe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eduMK22fIkXHW_SeFnO2xg.png" /></figure><p><strong>High-Fidelity Design:</strong></p><p>We created a high-fidelity prototype of the Web repository site using Figma. I created a UI requirements document to outline all of the features and elements I wanted to incorporate into the design. <a href="https://www.figma.com/file/HJnzOKSck1tZVDoAiEViSQ/Group-3-FORTOE?node-id=326%3A2343">Click here</a> to view my high fidelity design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*rwkaGdGZjE5S5VwZPaz4hw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WODWtZyqaszZeWT3n743A.png" /></figure><h4>Visual Design</h4><p>I created a UI Kit, this kit consists of all components and UI patterns used in the designing of this website. I created the logo for the client and as well as other features such as buttons and new icons I had created for the social feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iwhe6o3FOkQS4zGcsQ71pA.png" /></figure><p>As all recommendations, user goals and business goals have been incorporated into the design and prototype, usability testing would be carried out continuously to help determine whether the feature is more quintessential.</p><p>Thank you for your time, let’s talk more on <a href="https://twitter.com/CCAnna6">Twitter</a>, <a href="https://www.instagram.com/anastesiacaxton/">Instagram</a> or <a href="https://www.linkedin.com/in/cynthia-caxton-779a75196/">LinkedIn</a></p><h4><strong>Cheers ❣</strong></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f61294e75a97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 4weeks Journey As A UX/UI Design Student.]]></title>
            <link>https://medium.com/@cynthiacaxton/my-4weeks-journey-as-a-ux-ui-design-student-72dba3a01b25?source=rss-a22eb3fc0820------2</link>
            <guid isPermaLink="false">https://medium.com/p/72dba3a01b25</guid>
            <category><![CDATA[journey]]></category>
            <category><![CDATA[ux-ui-product-designer]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Cynthia Caxton]]></dc:creator>
            <pubDate>Fri, 26 Jun 2020 20:15:52 GMT</pubDate>
            <atom:updated>2020-06-30T20:18:55.523Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week One.</h3><p>The story I am about to share with all of you is an amazing one, I have mostly written about fiction and nothing related to a true-life story but today, I won’t just be writing about a true-life story, I will be writing about my Four weeks Journey as a UI/UX student.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*luSHmxj_roUot7Qy4AZw6A.gif" /></figure><p>It all began two months into the Corona Virus outbreak in Nigeria, I live in the Federal Capital Territory, Abuja. A two-week lockdown was imposed in the country, I was bored out of my mind, I have been trying a lot of things out of late, although, I work from home, it just kept getting more and more unbearably boring so I decided to apply for freelance writing gig on Fiverr. I filled all the necessary information and at the part where I get to choose what category of writing I will be open to, I saw UX WRITING. I stopped for a minute and I thought; how have I never come across this UX writing? so as expected, I went on google, wrecked the whole place, and turned it upside down looking for everything I can find about that category of writing.</p><p>I was partly disappointed because I didn’t get what I wanted, I kept seeing UX design, UI design, UI/UX design I even saw articles about this type of writing but I wasn’t just satisfied with the result, I was new to all these and I needed something less in my face, and I thought, maybe I didn’t use the right keywords so I gave up my search, went on Youtube and I was almost drowned with the sea of information I was choking on. (there is literally nothing you won’t find on the internet😌 )</p><p>what I did next was put on a life jacket and swim carefully through them. I confided in two of my very close friend about my interest in UX writing, <a href="https://www.linkedin.com/in/olusi-oluwaseun-1aa74498">Oluwaseun</a>, and <a href="https://www.instagram.com/ms_ikea/?hl=en">Ikeade</a>. Oluwaseun sent me links to online courses, I pick from one of those links (<a href="https://uxwritinghub.com/">UX Writing Hub</a>) I registered and started the course, I was curious and wanted to learn everything at once but unfortunately for me, I had to hold my reins because I had to wait for a new module to be uploaded before I can proceed.</p><blockquote><em>Want to read this story later? Save it in </em><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=noteworthy&amp;utm_content=eid7"><em>Journal</em></a><em>.</em></blockquote><p>Some days later I was sent another link, this one was different, it was a 3 days online class for UI/UX design. I never had any intention of learning design but what is there to lose? I registered and began the class. The Tutor for the 3 days online course began with UX design and to my amazement, I was hooked. I listened, took notes, and did more research.</p><p>The second and third day was purely UI design. that was where I knew design wasn’t just a cup of cake. As a young lady that I am, with no ARTISTRY background, no prior education on design, I was completely lost with a paintbrush in hand, staring at the Canvas. on the last day, I was able to design a two-screen app which I was totally in love with. I told everyone that cared to listen that I was an amazing designer, they complimented my design and told me I was doing great. little did I know that that app design I was so in love with would break my heart if a true critic should see it. yeah, it was that bad and even I knew it.</p><blockquote><em>Don’t just show your design to anyone, be open to professional criticism.</em></blockquote><h3>Week Two</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o5eHErA0TgTpuXv7fJB-bg.png" /></figure><p>In the second week, I practiced more and was able to come up with two designs. At that time, I don’t know what I would call the first design, but I did design a two-screen app and a three-screen banking app I called ZOKO (Named after the son of Fire Lord Ozai In Avatar😂). That design sure looked like flames.</p><p>At week two I didn’t know much about User Experience, I just designed ideas without much thought but I was about to know everything I needed to about User Experience. On 22 May, <a href="https://www.linkedin.com/in/olusi-oluwaseun-1aa74498">Oluwaseun</a> sent an electronic flier of a UX/UI design class and his caption said;</p><p>“I think you should register for this”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6Cn3J7vV9JrXwheLTbKtA.jpeg" /></figure><p>in my mind I screamed; I think I should too! I sent an Email stating my interest in the class, I got a reply from them with well-listed criteria needed for me to be part of the class, it wasn’t so demanding at all. A few days later I was asked to choose a day I would like for a Video interview. I did choose Friday, and guess what? the call came when I just woke up from my siesta! imagine how I would look on that video call ( I was more nervous about the interview though 😂). I was asked a few questions about myself if I had any prior education/skills in design which my answer was obviously no, I was also asked about my Goals for the class and what time would be preferable for me to take my classes. when all had been said and done, I waited for June 1st. At this stage I was crawling, so eager to take my first baby steps into UX/UI design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*4kal5zYn7P0hEpg6tTMJ7A.jpeg" /></figure><p>June 1st ( Drum rolls ) I woke up so excited, I woke up with a specific purpose in mind; UX/UI design. I had the whole day to get prepared, the classes begin by 7 PM and ends by 9 PM ( So they said 😎 ). I needed an uninterrupted supply of WiFi, I had a 3g MiFi but I knew since 2018 that it was of no use, but I couldn’t bring myself to dispose of it, the product design was so beautiful I could just keep it as an Artifact ( see why UX/UI is essential? ).</p><p>while I waited for time to do its thing, I got bored and decided to go out, My friend had set an alarm for me on her phone, it rang at 6:45 pm she looked at me and said, we will be home soon and if we are not, you can always join the class on my phone. ( what more can you ask for in a friend 🥰 ) 10 minutes later, we were home. I rushed to my room and turned on my laptop, a link was sent both to my Email and on Telegram. At exactly 7 pm, I was approved to join the class! (phew I barely made it). there where unfamiliar Names (all cameras were turned off) the Tutor introduced himself as Mr. Pelumi Adeyemi and gave us hints on what the class will be like clearly stating we all have graces of three strikes;</p><ul><li>you get a strike when you are beyond the 15minutes grace time.</li><li>when you don’t do your assignments.</li><li>when you disrespect another member of the class.</li></ul><p>with that been said, we started with UX design (the first week was for UX design) he spoke about the difference between UX and UI design, the roles of a UX designer, etc. at the end of the class, we were all given an assignment. the said assignment was to explain to a 10-year-old what UX/UI design is. I wondered why he would give such an assignment, I was expecting a whole load of assignment and I get this? Come on 😂.</p><p>Maybe you should take some seconds to think about that assignment too. At a later time, I understood why he gave us that assignment because UX design is not just all designing, you have to understand and empathize with users, know what they want, why they want it and how to continuously make them want it even more.</p><p>Day two, we spent the first 30 minutes going through the assignments, believe me, my assignment wasn’t 10/10 it was more like 4/10 but He always starts by giving good compliments on your work before he criticizes the hell out of it. His level of encouragement though, very comforting.</p><p>There was this lady that her answer to the assignment was so good that even I, a beginner, understood the main concepts of UX/UI design by just reading through her answers. it was so thorough and well perceived.</p><p>After the assignment reviews, the class was divided into four groups. I was in group 3 and I was made the group leader, I had an instant surge of panic. what do I know about being a group leader? absolutely nothing! I hated working in a group, I wasn’t a people person but who cares.</p><blockquote><em>As a designer, there will always come a time where your people relation skills will be required. learn it now, use it later.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOq-SP6pm78m9E9ivnbadQ.jpeg" /></figure><p>So as the team leader, I was tasked with creating a group on Telegram and a Figma Page. we all proceeded with our assignment it was really interesting, I had nice people in my group so the first step with them was easy. For the whole week, everyone was busy with doing with UX design for their project, and believe me it was awesome! why? because I had to learn every process myself, share my findings with my group member, get professional criticism from my Tutor (you won’t believe the number of class works and assignments he gives us😂). Now that I think about it, the feeling is heavenly. might I mention that for my UX class, projects by <a href="https://www.niyawatkins.com/about-1">Niya Watkins</a> were really helpful, Her Projects guided me through my user experience class and in writing my case study.</p><h3>Week Three.</h3><p>It was now time for User interface design and as expected, more than half the class was excited about it. Our Tutor, Mr. Pelumi Adeyemi already created a page for the class on Figma, so we were already invited to the page.</p><p>we started with wireframes, Typography, and colors, then high fidelity design, believe me, it’s way cooler than it sounds but the process was nerve-wracking. I am more of a black and white kind of person so choosing color was an issue for me but not anymore, thanks to our design class Superhero (Mr. Pelumi), who told us everything we needed to know about Colours and links to color guide sites. He was always there for the rescue.</p><p>At this point, I was head over heels interested in UX/UI design. No day would go by without assignment, no day. I felt disciplined, I wanted to do more by completing does assignment which I did, 90% of the time.</p><p>The third week was the most demanding, I went for a medical check and found out among other things that I had nerve stress (on my head) while taking my medication, I tried as much as possible to rest during the day time and then get ready for my classes by night. it was on this same week that our personal projects were assigned to us, which means I have my personal project, group project and the never-ending series of assignment to worry about and the doctor said;</p><p>“Don’t stress, try to rest as much as possible.”</p><p>but with a tutor who would always encourage you to do better, work at your pace but hurry up, I was able to work on my assignments and group work. Although I had issues with black outs of the time in week three, I had my pen and paper to write things I am likely to forget afterward.</p><h3>Week Four.</h3><p>We all knew this was our last week in the class, we began to pack up our bags. we were solely working on our design skills, replicating websites and mobile applications, I would spend 4 hours replicating a three-screened app but as time passed, I became familiar with shortcuts and plugins, those two save a lot of time, I can testify. on day 14 and 15 of our class, I felt so attached, I didn’t want the class to come to an end, we were so good together! On the last day, we mostly talked about ourselves, opportunities in UX/UI design, and for the first time, we got to see each other’s faces!</p><p>It was a beautiful feeling and deep down I felt satisfied. In tech, I have looked for an area to be an expert in, I have tried; HTML, CSS, JavaScript, Python, and IoT but none stuck I found out recently that I easily lose interest in stuff and for me to have gone 30 days without thinking of giving up or using my health as an excuse to lag, I believe there is more to learn and a whole lot more to give to the world with my skills.</p><p>At first, UX/UI design was just something I was curious about, a field I was yet to explore, now it is a Career part I am willing to venture into, I am really looking to see what the future holds, and in so doing I have started working on building up a portfolio because I will be open to any form of opportunities (internship, junior roles, and collaboration). In the nearest future. Thanks to <a href="https://www.linkedin.com/in/olusi-oluwaseun-1aa74498">Oluwaseun</a> who will always tell me;</p><blockquote><em>Keep trying till you find the one that sticks</em></blockquote><p>I have found UX/UI design. A big thanks to <a href="https://www.instagram.com/ms_ikea/?hl=en">Ikeade</a> who pushes me to do more and would always remind me to take my pills (I often get lost when am working or doing my assignments) she will tell me to believe in myself . to every member of Design class 2.0 every one of you was a healthy competition ( you won’t believe how good some of those guys are!) To Mr. Pelumi, I must say, you are the best Tutor I have ever had, you listen to your students, guide them and encourage them to keep doing better, little wonder how you are an Outstanding UX/UI designer.</p><figure><img alt="A concept I came up with for a social media app I call Pineapple." src="https://cdn-images-1.medium.com/max/1024/1*iOCTP5w3m0HgSpx0ys8JQw.png" /></figure><blockquote><strong>A concept I came up with for a social media app I call Pineapple.</strong></blockquote><p>To you reading this, it has been really great sharing my journey with you, whatever field or carrier part you want to venture into, there is no such thing as its too late when it comes to learning, keep trying till you find the one that sticks.</p><p>📝 Save this story in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://usejournal.com/newsletter/noteworthy-in-tech/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72dba3a01b25" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>