<?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 Mubaraq Somuyiwa on Medium]]></title>
        <description><![CDATA[Stories by Mubaraq Somuyiwa on Medium]]></description>
        <link>https://medium.com/@mubaraqsomuyiwa?source=rss-f1a22ebe5bdc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NgslOSXQSobZGOtrBBApWQ.png</url>
            <title>Stories by Mubaraq Somuyiwa on Medium</title>
            <link>https://medium.com/@mubaraqsomuyiwa?source=rss-f1a22ebe5bdc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:18:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mubaraqsomuyiwa/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[Don’t Tell Me How to Design: Striking the Right Balance When Feedback Feels Undermining]]></title>
            <link>https://medium.com/design-bootcamp/dont-tell-me-how-to-design-striking-the-right-balance-when-feedback-feels-undermining-c634f83a00a5?source=rss-f1a22ebe5bdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c634f83a00a5</guid>
            <category><![CDATA[constructive-feedback]]></category>
            <category><![CDATA[workplace-dynamics]]></category>
            <category><![CDATA[creative-confidence]]></category>
            <category><![CDATA[handling-criticism]]></category>
            <category><![CDATA[feedback-handling]]></category>
            <dc:creator><![CDATA[Mubaraq Somuyiwa]]></dc:creator>
            <pubDate>Sun, 01 Dec 2024 13:40:27 GMT</pubDate>
            <atom:updated>2024-12-03T03:36:05.891Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>Don’t tell me how to design: striking the right balance when feedback feels undermining</em></strong></h3><figure><img alt="A simple chat bubble icon with three dots symbolises communication and the idea that most issues with poor feedback can be resolved through open, clear dialogue." src="https://cdn-images-1.medium.com/max/1024/1*IqytjX72CmAx9WOx4Rm3gg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lunarts?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Volodymyr Hryshchenko</a> on <a href="https://unsplash.com/photos/three-crumpled-yellow-papers-on-green-surface-surrounded-by-yellow-lined-papers-V5vqWC9gyEU?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>It happens in a flash — you’re in a team meeting, and suddenly, feedback hits like a gut punch. You’ve poured hours, maybe days, even weeks, into this project, but one comment cuts through your confidence. Instead of insights or improvements, it feels like someone’s questioning your skills. Your mind spins — self-doubt, frustration, and even anger start to brew. For sanity, one question lingers: How do you handle feedback that feels more like a critique of our abilities than constructive help? Knowing that it is bound to happen in other scenarios (a different company, a different role, a different team size)</p><p>We all encounter feedback that hits the wrong nerve, especially when it comes from colleagues outside our expertise. Whether it’s a project manager micromanaging details you already nailed or a developer critiquing your design choices, the impact can linger, feeding self-doubt and frustration. If left unchecked, these moments can build up, leading to stress, strained relationships, and even burnout. Without the right approach, these moments can spiral, eroding your confidence and motivation.</p><p>Here’s a step-by-step approach to not only survive but thrive in environments where feedback can sometimes feel more like a test than a tool.</p><h4><strong>1. Feel It, Don’t Dismiss It</strong></h4><p>The first step might seem counterintuitive: don’t bottle it up. Allow yourself to feel the hurt. If you need to, vent to a friend or confidant who listens without judgment. Processing your emotions helps you move past them, giving you the clarity to respond instead of react. In emotionally charged moments, making snap decisions can lead to impulsive actions that may complicate things further.</p><h4><strong>2. Decode the Intent</strong></h4><p>Now, dig deeper. Try to see the feedback from the other person’s perspective. Was the intent to solve a problem, hit a deadline, or improve a process? Often, feedback that feels abrasive is simply a case of poor delivery, emotional intelligence, or poor communication skills rather than malice. Picture a scenario: a well-meaning but blunt project manager suggests a change that disrupts your flow but is purely focused on overcoming a blocker. While the phrasing stings, the intent might be to make the product better or to clear a roadblock. Shifting focus from tone to intent, allows you to address the content, not the delivery.</p><h4><strong>3. Reclaim Your Expertise</strong></h4><p>When working cross-functionally, owning your space is essential. Establish yourself as a go-to for your area of expertise by responding to feedback confidently and quickly. Instead of letting insecurities fester, staying proactive in your role reinforces that you are the professional in your space. Silence can be misinterpreted as weakness, while a clear, confident response underscores your role as a professional. Lack of response or delayed input can send mixed signals, while timely, thoughtful engagement solidifies your authority.</p><h4><strong>4. Talk to an Ally in Leadership</strong></h4><p>Engage with a trusted mentor, manager, or someone in authority who can offer an objective perspective. Having a second opinion — especially from someone neutral, with a broader view — often sheds new light on the situation. Sometimes, the best insights come from a fresh set of eyes, and having a trusted ally helps validate your feelings and also bring up potential areas for process improvement, and make feedback exchanges more respectful across the team without escalating the conflict.</p><h4><strong>5. Set the Stage for Feedback on Your Terms</strong></h4><p>Instead of waiting for offhand comments in a crowded meeting, be proactive. Schedule regular check-ins to discuss progress, outline what’s helpful to cover, and steer the conversation toward objective improvements. When you take control of feedback, it’s less likely to catch you off guard or feel personal, and it enables a more productive, focused dialogue. This strategy can prevent unfiltered, offhand feedback that strays into personal territory.</p><blockquote>We all can learn to give constructive feedback. Here is a plug-and-play sample to start with</blockquote><blockquote>“Acknowledge effort: [recognise the positive aspects of their work]. Areas for improvement: [mention the areas that need attention]. Moving forward, [offer a suggestion or recommendation for improvement]. Keep up the good work, and I’m confident you’ll make great progress!”</blockquote><h4><strong>6. Foster Inclusion and Collaboration</strong></h4><p>Building rapport with colleagues helps establish trust, reducing the likelihood of hurtful feedback. Engaging others early on in your projects — seeking their input, pov, and gauging feasibility — fosters collaboration. People who feel included are more likely to offer balanced, constructive feedback that benefits everyone involved, as they know the thought process that brought about the solution making them open to be proactive and consider alternative approaches in their feedback rather than lash out.</p><h4><strong>7. Data, Your Silent Advocate</strong></h4><p>Let your work speak for itself through measurable outcomes. Data brings objectivity to conversations that might otherwise be clouded by opinion. When you can back up your methods with hard numbers, your responses are grounded in results, reducing friction and establishing you as an invaluable decision-maker.</p><h4><strong>Encourage Team-Building “Lunch and Learns” (Bonus Tip for Organizations)</strong></h4><p>“Lunch and Learn” sessions — casual presentations on any work-related topic — provide a relaxed setting for feedback. These sessions foster understanding across departments, letting everyone share ideas and insights without the pressures of formal feedback. When feedback flows freely and positively, individuals are more likely to feel understood, respected, and part of the bigger picture.</p><h3><strong>TL;DR</strong></h3><p>Workplace feedback dynamics are complex but remember: while feedback is vital to personal and professional growth, not all of it needs to be taken to heart. By setting boundaries, owning your expertise, and embracing proactive communication, you can keep the feedback from derailing your confidence and instead use it as a tool to advance your career on your terms. After all, thriving in your role means mastering not just the craft, but the art of handling critique.</p><h4><strong>PS</strong></h4><p>Now and then, you might cross paths with someone whose feedback feels less like collaboration and more like confrontation. Maybe they’re blunt, or maybe it’s something deeper — a clash of egos or values. It’s tempting to label them a saboteur outright but resist the urge. Pause — is it possible to build a bridge instead of burning one? Sometimes what looks like animosity is just a failure to communicate. But when all efforts fall flat, remember this: their bias isn’t your burden — it’s just noise.</p><p>Appreciation to <a href="https://medium.com/u/97074f6e4f64">Bryan Anoruo</a> and <a href="https://medium.com/u/e3504ad9100a">Roberto Aiello</a> for their guidance on such a delicate topic, it was of immense value.</p><p>That’s it for today, thanks for reading.</p><p>Did you find this article helpful? I look forward to your thoughts in the comments.</p><p>Don’t want to miss out on any future helpful articles? Then be sure to <a href="https://medium.com/@mubaraqsomuyiwa">follow </a>and <a href="https://medium.com/@mubaraqsomuyiwa/subscribe">subscribe</a>.</p><p>Do you have a suggestion, leave a comment and I will follow up soon :)</p><p>I can’t wait to see you in the following article I’m thinking of calling it “<strong>Speed or Substance: What Truly Matters When Building an MVP?</strong>” — Thoughts?</p><p>Till then, Ciao 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c634f83a00a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/dont-tell-me-how-to-design-striking-the-right-balance-when-feedback-feels-undermining-c634f83a00a5">Don’t Tell Me How to Design: Striking the Right Balance When Feedback Feels Undermining</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Users’ Needs Are Overrated: A Case for Business-First Design]]></title>
            <link>https://medium.com/design-bootcamp/users-needs-are-overrated-a-case-for-business-first-design-aee3d78ecd5c?source=rss-f1a22ebe5bdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/aee3d78ecd5c</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Mubaraq Somuyiwa]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 00:34:29 GMT</pubDate>
            <atom:updated>2024-11-30T23:53:34.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="User needs matter, but they aren’t everything. True product success comes from balancing design, development, strategy, and marketing — not prioritizing one over the others." src="https://cdn-images-1.medium.com/max/1024/1*g3QuZtPbyLyzhIBLzj-pGw.jpeg" /><figcaption>Image by <a href="https://www.freepik.com/free-photo/business-financial-accounting-concept-with-wooden-blocks-side-view_9426556.htm#fromView=search&amp;page=1&amp;position=48&amp;uuid=545eab1d-4974-45f3-ba25-73a1cdca47d4">Freepik</a></figcaption></figure><p>In today’s digital landscape, UX designers champion user needs, tirelessly crafting experiences meant to engage and delight. What if we’ve been getting it wrong all along? What if prioritizing users is only one part of the bigger picture? In the grand scheme of product success, could balancing business goals with user satisfaction be the true path to innovation and growth?</p><h4>The Trap of Over-Prioritizing Users</h4><p>Meeting user expectations is crucial, but over-focusing on them can create inefficiencies.<a href="https://medium.com/design-bootcamp/dichotomy-of-talking-to-users-fundamental-of-user-research-2a0698109c0d#:~:text=Many%20even%20beyond,users%E2%80%9D.%20%E2%80%94%20Jakob%20Nielsen"> Users, after all, don’t always know what they want</a>. Research shows a disconnect between what users say and how they actually behave.</p><p>Catering to every demand can lead to an overwhelming list of features — many of which may not be beneficial for the business. The result? A bloated product that fails to align with the company’s growth strategy. While user satisfaction is important, the question we must ask is: At what cost to the business?</p><h4>Data-Driven Design: A Smarter Approach</h4><p>This is where data steps in. Instead of focusing solely on what users say, a business-first approach embraces the patterns revealed through data. Research data offers a window into real user behavior, allowing businesses to prioritize the most common and high-impact needs. These insights drive the creation of a Minimum Viable Product (MVP) — a streamlined version of the product that meets core user needs while staying aligned with business goals.</p><p>The MVP strategy allows for faster market entry. Instead of building an exhaustive product based on every user whim, the MVP delivers value to users without overextending resources. Once the MVP is in the hands of users, feedback becomes the guiding star for further improvements. This iterative process — launching, gathering insights, and refining — ensures continuous evolution while keeping the product grounded in both user needs and business objectives.</p><blockquote>However, product is just one of the tools that makes a business sustainable. Development, marketing, strategy, and delivery are equally important.</blockquote><p>Over-focusing on users while neglecting these other arms of the business can be detrimental. Once a clear user pattern is identified, it must be balanced with development and delivery to shape an MVP. The strategy and delivery teams should also think about how the product will launch and effectively reach the target audience through marketing. Only by integrating these different facets of the business can a product succeed. Continuous feedback can then guide further iterations, ensuring that the product remains grounded in both user needs and business objectives.</p><h4>Balancing Business Goals with User Needs</h4><p>Business success lies in finding the sweet spot where user needs support business growth, not hinder it. By focusing too much on users, businesses risk becoming reactive, endlessly chasing user desires that may not align with growth strategies. On the flip side, prioritizing only business goals can lead to products that fail to resonate with users. The key is balance.</p><p>A business-first design approach acknowledges that user needs and business goals can, and should, coexist. It is not a matter of raising one above the other but of recognizing that both play a role in product success. This balance is essential for long-term success. The trick is in how they interact, finding the overlap where the needs of the user and the goals of the business support each other.</p><h4>The Power of Continuous Iteration</h4><p>The difference in a business-first approach is the ability to keep pushing forward, even when user requests introduce uncertainties. By allowing business goals to drive design decisions, the development process becomes more coordinated, reducing redundancies that arise from catering to endless user demands.</p><p>The difference in a business-first approach is the ability to keep pushing forward, even when user requests introduce uncertainties. When business goals drive design decisions, the development process becomes more coordinated, reducing redundancies that arise from catering to endless user demands.</p><blockquote><em>So, when next you find yourself in disagreement with developers over UI development or the behavior within certain user flows, always make your case pro-business — focusing on how best to get your solution to users without compromising usability or sacrificing business goals.</em></blockquote><p>This iterative process — driven by data and feedback — ensures that both user satisfaction and business growth remain priorities. Scalable, sustainable growth is possible when design choices are aligned with business goals, driving continuous innovation.</p><h4>TL;DR - Building for Today and Tomorrow</h4><p>In the end, user needs are important, but they’re not everything. The real value lies in aligning these needs with a solid business strategy. When done right, this balance allows companies to not only meet current market demands but exceed them — creating a product that delights users and propels the business toward long-term success.</p><p>By adopting a business-first approach, companies can build a foundation for growth that’s both innovative and sustainable. The secret lies in finding the perfect overlap where user satisfaction supports business growth.</p><p>That’s it for today, thanks for reading! I look forward to your thoughts in the comments, and I’ll see you in the next article.</p><p>If you need anything, you can reach me on <a href="https://www.linkedin.com/in/mubaraqsomuyiwa/">LinkedIn</a> :)</p><p>Did you find this article helpful? Awesome! 😍</p><p>Don’t want to miss out on any future helpful articles? Then be sure to <a href="https://medium.com/@mubaraqsomuyiwa">follow </a>and <a href="https://medium.com/@mubaraqsomuyiwa/subscribe">subscribe </a>to the e-mail list.</p><p>And if you enjoyed reading this article, please give it a clap 👏 to let me know! Your feedback means the world to me.</p><p>Thank you for reading! I can’t wait to see you in the following article I’m thinking of calling it “<strong>Devs telling you how to design: Navigating pushback in collaborative teams</strong>”</p><p>Till then, Ciao 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aee3d78ecd5c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/users-needs-are-overrated-a-case-for-business-first-design-aee3d78ecd5c">Users’ Needs Are Overrated: A Case for Business-First Design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech Careers Unmasked: The Good, The Bad, and The Ugly Truth]]></title>
            <link>https://medium.com/design-bootcamp/tech-careers-unmasked-the-good-the-bad-and-the-ugly-truth-ba13c4fc02c0?source=rss-f1a22ebe5bdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba13c4fc02c0</guid>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[rejection-letter]]></category>
            <category><![CDATA[tech-career]]></category>
            <category><![CDATA[entry-level-jobs]]></category>
            <category><![CDATA[resilience]]></category>
            <dc:creator><![CDATA[Mubaraq Somuyiwa]]></dc:creator>
            <pubDate>Sat, 25 Mar 2023 06:25:30 GMT</pubDate>
            <atom:updated>2024-11-30T23:55:15.644Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RyMBDxhZ6g7Y6yfGU6mwVA.jpeg" /><figcaption><a href="https://www.freepik.com/free-photo/exhausted-woman-employee-working-project_5890230.htm#query=frustrations&amp;position=18&amp;from_view=search&amp;track=sph">Image by pch.vector</a></figcaption></figure><p>We must have noticed the growing trend of people transitioning to tech careers. Many are attracted to the tech industry because of the freedom and flexibility it offers, including lucrative compensation and the ability to work from anywhere. Additionally, the peace that comes with working in tech can be appealing to some. It’s no surprise that there have been various campaigns encouraging more people to consider tech careers, and I believe we will continue to see more of these campaigns in the future.</p><p>Although the tech industry has many attractive features, I have noticed that some challenges and obstacles are often left unaddressed in the tech industry. Especially in campaigns, these initiatives are aimed at promoting diversity and inclusion in the tech industry and encouraging people from all backgrounds to pursue careers in technology. These campaigns take various forms, such as coding education initiatives, workforce development initiatives, and diversity and inclusion initiatives.</p><p>While it is certainly tempting to believe that tech careers are the perfect solution to all our career woes, we must be realistic and acknowledge that there are still many obstacles to overcome. These can include things like career growth blockers, the trend of mass layoffs, unending rejection emails, entry-level roadblocks, productivity issues, work-life balance concerns, boot camp scams, startup fraud, and more. Therefore, while tech careers may be appealing, it’s important to approach them with a realistic and well-informed mindset. By acknowledging these challenges and taking steps to address them, we can help ensure that the tech industry remains a viable and fulfilling career choice for years to come.</p><p>Drawing on my encounters, I wish to explore the effects of rejection emails during the job hunt. It’s important to recognize that everyone has, and will have, their fair share of rejections. Rejection emails are notifications that a job application has been unsuccessful, and they can be difficult to receive. Rejection emails can be a result of factors like lack of qualifications, lack of open positions, being overqualified, poor resumes, timing, location constraints, and other reasons. It’s crucial not to take rejection emails personally and instead use them as an opportunity to improve your job search strategy. Rejection emails can be discouraging, and it’s natural to feel disappointed when they arrive. However, it’s important to remember that rejection is a normal part of the job search process and know that it doesn’t define your worth as a professional. By using rejection as an opportunity to learn, I have been able to improve my application and interview skills, and I can increase my chances of success in the future.</p><p>There are several steps you can take to move forward, such as seeking feedback, networking, and continuing to apply for jobs that match your qualifications and interests. By learning from rejection emails and using them as motivation to improve, you can increase your chances of landing your dream job.</p><p><em>As I sat in my dimly lit home office, staring at the email inbox on my computer screen, I couldn’t help but feel a pang of disappointment with each rejection email I received. It seemed like all my hard work and effort had gone unnoticed, and my enthusiasm for work was waning. Despite knowing that rejection was a natural part of the job search process, it still stung.</em></p><p><em>But I refused to let the rejection emails get the best of me. Instead, I decided to take a break from my usual routine and live in the present moment for a day. I went for a walk in the park, savoured my favourite foods, and did some activities that brought me joy. It was a refreshing break that allowed me to recharge my batteries and recenter my focus.</em></p><p><em>The next day, I got back to work with renewed vigour. I began by connecting with recruiters and analyzing the reasons behind the rejections. I sought out mentors through Adplist, a platform that had been a lifesaver for me, and listened intently to their advice. It was during one such conversation with a product hiring manager that I had a breakthrough — I realized that I needed to create a website portfolio to showcase my work, personality and skills.</em></p><p><em>Looking back, I realized that those rejection emails had prepared me for a bigger stage. They helped me build resilience, hone my skills, and develop a deeper understanding of what I wanted from my career. And as I looked towards the future, I felt confident in my ability to shape it in a way that aligned with my goals and aspirations.”</em></p><p>There are a variety of reasons why you receive multiple rejection emails. Some of the most common include: <br> <strong>Lack of qualifications:</strong> One of the most apparent reasons for rejection is not having the necessary qualifications for the job. Not every job is a good fit for every candidate. Even if you have the necessary qualifications, it may not be enough to stand out from the competition. It’s important to tailor your resume and cover letter to match the requirements listed in the job posting.</p><p><strong>Location:</strong> Based on my personal experience, I’ve come to realize that the location of a job plays a critical role in the job search process. It’s important to understand the nature of the job, as it can determine whether the job is based in a physical office, fully remote, or a hybrid of both. When applying for remote jobs, I have found it helpful to consider the time difference between my location and the company’s office or headquarters and look for roles that have overlapping hours with my time zone to enable easy communication between teams. By having a clear understanding of the nature of the job, I am better able to tailor my application and increase my chances of success.</p><p>For physical roles, the location of the job may be too far away from where you live, making it impossible for you to commute daily.<br> For hybrid roles, the location of a job can be a major constraint for many job seekers, especially in the current remote work environment. Even though the option to work from home has become more prevalent, many companies still prefer to have their employees work in a physical office location. This can limit the job opportunities for those who live in different regions or who are looking for a job in a different city. <br> On the other hand, if you’re open to remote work, it can greatly increase your job opportunities and open up new career possibilities. Many companies are now offering remote work as a permanent option, and others are open to hiring remote workers temporarily. It’s important to remember that even though remote work can provide more flexibility and freedom, it also comes with its own challenges such as isolation, communication barriers and self-discipline. Therefore, it’s important to ensure that remote work aligns with your personal and professional goals.<br> <br> In conclusion, location can be a major constraint for job seekers, but with the rise of remote work, it’s possible to find job opportunities regardless of location. It’s essential to be open to remote work and be aware of the pros and cons that come with it.</p><p><strong>Lack of experience:</strong> Even if you have the qualifications, a lack of experience in a specific field can make it difficult to stand out from other applicants. Consider gaining relevant experience through internships, volunteer work, or side projects.<br> <br> <strong>Poor application materials:</strong> A poorly written resume, cover letter, or application can make it easy for hiring managers to reject a candidate. Make sure to proofread and have someone else review your materials before submitting them.</p><p><strong>Unclear career goals:</strong> Employers want to see that an applicant has a clear career path and that the job they’re applying for aligns with their goals. Be sure to research the company and position beforehand, and tailor your application materials to show how the job fits into your career plans.</p><p><strong>Competition:</strong> There’s often a lot of competition for any given job, and even if you’re a strong candidate, you may not be the best fit for the position. Don’t be discouraged, and keep applying for other opportunities.<br> <br> <strong>Overqualified:</strong> On the other hand, you may be overqualified for the job. This means that the employer may feel that you would be too expensive or that you would quickly become bored in the role.</p><p><strong>Timing:</strong> Sometimes, the company may not have any open positions when you apply, but they keep your application on file for future reference.</p><p>I had<em> an interesting conversation with my mentor and friend, Chris, towards the end of last year. Chris is a product designer and hiring manager for a top firm, and his experience has given him insight into the challenges people face when trying to enter the tech industry. One key issue that Chris highlighted was the difficulty that individuals from underrepresented regions have in gaining entry.</em></p><p><em>According to Chris, HR departments use a variety of metrics and tools to filter out a large number of applicants. For example, even if a position is advertised as 100% remote, HR may use parameters such as “right to work in the job location” and “in need of visa sponsorship now or in the future” to eliminate over 50% of applicants. As a result, many well-qualified people are unable to gain a foothold in the industry and receive nothing more than an automated rejection email.</em></p><p><em>For those who pass this initial screening, the next challenge is the applicant tracking system (ATS), which is an HR tool designed to make hiring more efficient but can be a pain for applicants. The ATS typically does a CV-to-job description match, and most HR departments require a minimum CV/job match percentage, often as high as 90%, for an application to move forward. Those who fail to meet this requirement are automatically rejected.</em></p><p><em>Assuming an applicant makes it past the ATS, they will then need to complete various skills and personality assessments. Only a fortunate few who perform well on these tests will have the opportunity for their portfolios to be reviewed. </em><strong><em>Chris was quite frank in stating that no recruiter spends more than a minute reviewing a portfolio/resume, as they have a lot of them piled up and waiting to be reviewed.</em></strong><em> The final step in the process is to meet with hiring managers, who are often the key decision-makers. The process can be unique for different employers</em></p><p><em>Chris suggested that one way for underrepresented groups to increase their chances of success in the tech industry would be to apply for positions closer to their location. For Africa, Chris suggested particularly South Africa, which is known as Africa’s tech capital. Additionally, he advised applying to countries with overlapping time zones, as this makes it easier for remote teams to interact during working hours. Finally, he recommended applying to smaller companies, as their recruiting process is often less tedious and more flexible than larger enterprises.</em></p><p><em>Overall, my conversation with Chris was informative and enlightening. Although, entering the tech industry can be challenging, but by following Chris’s advice, I am optimistic that I can increase my chances of success</em>, and so can you.</p><p><strong>Remember, rejection is not the end of the road, it’s the start of a new journey towards finding the right opportunity. Keep pushing and don’t give up, and you’ll find the perfect job for you.</strong></p><p>That’s it for today, thanks for reading! and I will see you in the next article</p><p>If you need anything, you can reach me on <a href="https://www.linkedin.com/in/mubaraqsomuyiwa/">LinkedIn</a> ;)</p><p>Did you find this article helpful? Awesome! 😍</p><p>Don’t want to miss out on any future helpful articles? Then be sure to <a href="https://medium.com/@mubaraqsomuyiwa">follow </a>and <a href="https://medium.com/@mubaraqsomuyiwa/subscribe">subscribe</a> to the e-mail list.</p><p>And if you enjoyed reading this article, please give it a clap 👏 to let me know! Your feedback means the world to me.</p><p>Thank you for reading! I can’t wait to see you in the following article I’m thinking of calling it “Job Security is Never Secure,” we never can tell, but …</p><p>Till then, Ciao 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba13c4fc02c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/tech-careers-unmasked-the-good-the-bad-and-the-ugly-truth-ba13c4fc02c0">Tech Careers Unmasked: The Good, The Bad, and The Ugly Truth</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dichotomy of talking to users: Fundamental of User Research]]></title>
            <link>https://medium.com/design-bootcamp/dichotomy-of-talking-to-users-fundamental-of-user-research-2a0698109c0d?source=rss-f1a22ebe5bdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a0698109c0d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[behavioural-design]]></category>
            <dc:creator><![CDATA[Mubaraq Somuyiwa]]></dc:creator>
            <pubDate>Sat, 16 Apr 2022 10:03:02 GMT</pubDate>
            <atom:updated>2022-09-19T05:16:05.146Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>The dichotomy of talking to users: a fundamental of user research</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1DnKZSNjraC33dE-ZzUdg.png" /><figcaption>Interviews, surveys, qualitative and quantitative research and others are forms of User Research</figcaption></figure><p>As a product designer, the most basic principle is to create a product that is easy to use and needs no manual to handle. To achieve this feat, one needs to be in the position of the user, this concept birthed the behavioural design study we call user experience design (UED). <a href="https://en.wikipedia.org/wiki/User_experience_design">Design decisions in UX design are driven by research, data analysis, and test results rather than aesthetic preferences and opinions. Unlike user interface design, which focuses solely on the design of a computer interface, UX design encompasses all aspects of a user’s perceived experience with a product or website, such as its usability, usefulness, desirability, brand perception, and overall performance.</a></p><p>There are a series of user experience research methods that can be applied to a project you are working on which include qualitative vs. quantitative research, attitudinal vs. behavioural research, generative vs evaluation research, remote usability testing, diary studies, card sorting, surveys, and interviews and others. Selecting a method will depend on a series of options, selecting one doesn’t render others useless, you can as well select a couple to work on a particular project as well</p><blockquote><a href="https://medium.com/u/fb258fde54c1">Nannearl LeKesia Brown</a> says <a href="https://maze.co/guides/ux-research/ux-research-methods/">The method I choose would need to be able to get me answers to the research questions I have, but I also must take into account the project timeline, budget, and the amount of synthesis required for that method versus another one. <br>Make sure you understand where you are in the UX design process. Once you clarify that, having a good idea of the different methods you can use and when they’re best applied throughout the design process will help you identify what might yield the most helpful results within the constraints under which you’re working.</a></blockquote><p>It is also important to be skilled in user research as there are principles, techniques and methods of questioning a user, a few of which include</p><ul><li>Never ask leading questions</li><li>There are no right or wrong questions</li><li>The first solution to a problem isn’t the best, always look forward to optimal solution. This <a href="https://medium.com/u/a25a101a5693">Erik D. Kennedy</a> often refers to as <em>satisficing</em></li></ul><figure><img alt="Dichotomy of talking to users: Fundamentals of user research" src="https://cdn-images-1.medium.com/max/1024/1*YG1-d3K_DDvLQDrugALsrA.png" /></figure><p>There lies confusion in some user research principles, which need clarity. Let’s discuss the dichotomy of talking to users!</p><figure><img alt="“Never ask a user what they want. Do not listen to a user”" src="https://cdn-images-1.medium.com/max/1024/1*YoW3vUXexPu6EqXoAy8v1Q.png" /></figure><p>Many even beyond design agree with the principle of not listening to user opinions.</p><blockquote>“The first rule of user research: never ask anyone what they want” — Erika Hall<br> “If I had asked my customers what they want, they would have said a faster horse” — Henry Ford (allegedly)<br> “First rule of usability design? Don’t listen to users”. — Jakob Nielsen</blockquote><figure><img alt="“Users are always wrong but not dumb! Do not take design advice from a user”" src="https://cdn-images-1.medium.com/max/1024/1*QdpG_b1mZvonk9jGZJrsbA.png" /></figure><p>Users will help you figure out facts that you won’t discover yourself or will take you a long time to discover. Users help you make better products but they are not helpful if you listen to them, isn’t that confusing enough? Enough with the dichotomies, let’s take a look at what they mean and how to make an effective user research off them</p><figure><img alt="“Read between the lines of what users say, find out the reason why they are saying it”" src="https://cdn-images-1.medium.com/max/1024/1*ViZKMfpnNPrc4ftz-2jKiQ.png" /></figure><figure><img alt="Users do not express the difficulty they experience with a product. It could be because they do not want to hurt your feelings or some other reasons highlighted below" src="https://cdn-images-1.medium.com/max/1024/1*aJl1shurD1bCjWffLv5aXw.png" /></figure><p>Being human makes us have social interactions and this ensures we are being thoughtful about our comments and actions towards others, social feelings such as sympathy, empathy, and politeness amongst others can restrain users from making candid comments about the tested products. But assuring users that, their honest opinion is the only way of correcting user errors and making the product usable Ensuring them that, it won’t hurt your feelings but help you get better with your designs. <br>Let&#39;s take a look at what users are wrong about and how to handle such situations</p><figure><img alt="users are always wrong about the following: their desogn suggestions, their skills, how good the design is and their behaviour" src="https://cdn-images-1.medium.com/max/1024/1*6zgn5qv2nO80L_8lf-wdSA.png" /></figure><p>Simple variations to the design will solve the users’ problems, the goal is to be able to see beyond the statements users make while skillfully interpreting what users say and figuring out why they made such a suggestion. Remember not to ask leading questions as you do this.</p><figure><img alt="Elaborating how users are wrong about their design suggestions" src="https://cdn-images-1.medium.com/max/1024/1*cTht33wXh-8iR4ocgMmBgg.png" /></figure><p>In a quest to solve a usability problem, users can make a suggestion that is considered a bad design idea, but they believe is the best way out, as they often do not see beyond the problem they are faced with and they do not know the full context of the design. As a designer knows fully well that adjusting the opacity, varying the contrast, increasing the size of a certain element, adding an extra layer or changing the typography used can solve a visibility problem rather than a “move/delete the button suggestion” made by the user during an interview session</p><figure><img alt="Elaborating how users are wrong about their own skills" src="https://cdn-images-1.medium.com/max/1024/1*zYO4nIna1UWqjySZ0F-7Dg.png" /></figure><p>Users often doubt their skills and blame themselves when they find it difficult to use a product, this happens mostly with older users. They believe you have an awesome design and they are just bad at using computers which frustrates them. In such situations tell them the design is faulty and not their skills. Designing a better interface will fix the users’ complaints, remember not to give in to the first solution that comes to mind (principle of satisficing)</p><figure><img alt="Elaborating how users are wrong about how good the design is" src="https://cdn-images-1.medium.com/max/1024/1*xl0N83bGoJ5Do78hpwZi4Q.png" /></figure><p>I can’t overemphasize the need to guarantee users that their candour won’t hurt you but rather help fix the errors in the design. Also ensure you avoid settling for general comments such as: “the design is nice and simple, I like it”, “this is nice”, and so on. Encourage users to express how they feel about the product.</p><figure><img alt="Elaborating how users are wrong about their own behaviour" src="https://cdn-images-1.medium.com/max/1024/1*Y77jPUFY_TeIX8kBbtB9iQ.png" /></figure><p>Ask a user if they love the ‘new card and wallet feature’ that helps them manage their finance and simplify payments. Users will go on to say how lovely the feature is, talking about its advantages and use case. The moment you go ahead to ask them to try it out for a full experience and you start noticing reluctance. The reluctance is the action to watch out for, it is the truth about how they feel and how they will most likely behave in a live scenario with the product. <br> If you follow the actions rather than the words, you’ll find out that there will be a convergence of actions, a pattern will form from the multiple responses you get, and then proceed to solve the issue. This and many more are the actions we need to observe and take note of, not the beautiful words put out there.</p><p>If a user tells you frankly “it looks great but not something I will try out” or “exclaims in surprise for finding out that his expectations are what just happened”, these are typical examples of candour and emotions that matter, as the user already told you what exactly he’ll do, nonetheless, find out the reasons for the action. As for emotions, it is not possible to conceal true emotions and we can often tell when an emotion is not genuine. Imagine a user expressing emotions in a one-on-one interview or a live video meeting, you can always tell the difference.</p><p>This concludes “The dichotomies of talking to users”. Remember to clap, share and comment, if this was a great read, let’s also have your thoughts about dichotomies you know of in the comment section.</p><p>Appreciation and recognition to <a href="https://medium.com/u/a25a101a5693">Erik D. Kennedy</a> and other resources used.</p><p>Stay tuned as I bring forward more topics on #talksaboutdesign</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a0698109c0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/dichotomy-of-talking-to-users-fundamental-of-user-research-2a0698109c0d">Dichotomy of talking to users: Fundamental of User Research</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX FOR EDUCATIONAL WEBSITE]]></title>
            <link>https://medium.com/@mubaraqsomuyiwa/ux-for-educational-website-3036155612e0?source=rss-f1a22ebe5bdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/3036155612e0</guid>
            <category><![CDATA[side-hustle]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mubaraq Somuyiwa]]></dc:creator>
            <pubDate>Sat, 27 Nov 2021 10:07:30 GMT</pubDate>
            <atom:updated>2021-11-27T10:07:30.904Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Opp05X-sCm1Dbl6NoBxjZA.jpeg" /></figure><p><strong>CAPSTONE WEEK 2 PROJECT- UX for an Educational Website</strong></p><p>The only constant thing in business is a competition they say, and website project planning is destined for failure without proper competitive analysis.</p><p>It’s our Second Capstone project (Capstone project 2) at SideHustle Internship. Our area of focus as a team is the academic sector, a university of agriculture to be precise and as a creative agency, we are tasked with improving its website and making it easier for its users to navigate. After all, what is an institution without a functional website in this age of technological literacy?</p><p>As a team, we have come to understand from our various lessons on the SideHustle Internship that there are important steps to be taken when you have a project on your hands. The designed product is not the first step and if you leapfrog over these steps, the end-product may leave much to be desired.</p><p>Understanding the goals of our client and the would-be users of the product which we believe are the very first steps in any UI/UX project and to this end, we identified some business goals of the University and the users which include both intending, new and returning students and staff.</p><p>Our identified Business Goals are:</p><p>i. to increase awareness about the University, and improve its perception among members of the public.</p><p>ii. to attract more students by having a functional and aesthetically pleasing website.</p><p>Our Identified Student-User Goals are:</p><p>i. to have ample information on the chosen course of study and the requirements to study at the University.</p><p>ii. to have a university website that has most if not all of all the processes required for my stay in school on it without having to do them physically.</p><p>iii. To have a school website that makes payment of school fees easier and faster.</p><p>Our Identified Lecturer-User Goals are:</p><p>i. To have a functional platform to upload course materials.</p><p>ii. To have a platform for easy publication of test and exam scores.</p><p>Our identified Visitor-Goals are:</p><p>i. To be able to gather information about the university with ease.</p><p>ii. To easily locate various places in the University.</p><p>You can click on the link below to see the graphical representation of the goals enumerated above.</p><p><a href="https://www.figma.com/file/ndReWkoxazGSAtXBsKuQAz/Untitled?node-id=5%3A93">https://www.figma.com/file/ndReWkoxazGSAtXBsKuQAz/Untitled?node-id=5%3A93</a></p><p>The identification of the goals was very instrumental to the creation of User Personas. User Personas are semi-fictional characters that represent the larger target users for the product. The personas created have some of the goals enumerated above. It helped us have a graphic understanding of the persons we are creating this product for and empathize with some of their frustrations and need. Click on the links below to the User Personas we created:</p><p><a href="https://www.figma.com/file/TXAH5PN2r6fN9w9okvyH6h/User-Persona?node-id=0%3A1">https://www.figma.com/file/TXAH5PN2r6fN9w9okvyH6h/User-Persona?node-id=0%3A1</a></p><p><a href="https://www.figma.com/file/c8YJ5oUGf1QCn53Ftr32mz/User?node-id=1%3A58">https://www.figma.com/file/c8YJ5oUGf1QCn53Ftr32mz/User?node-id=1%3A58</a></p><p>Having determined the goals of every concerned party, we brainstormed and thought up the type of content and pages that should be on a university’s website and more importantly, a university of agriculture. We carried out detailed research on our competition using their websites. The competition was narrowed down to the four existing Federal Universities of Agriculture in Nigeria namely, Federal University of Agriculture, Abeokuta; Federal University of Agriculture, Markurdi; the Michael Okpara University of Agriculture and the Federal University of Agriculture, Zuru.</p><p>We were able to do a comparison of the content and pages of this website. Below is a picture of some of our findings. From the brainstorming sessions, we decided that our educational website will have the following pages; Homepage, About Us, Colleges, Student portal which will have for undergraduates and postgraduate, staff portal, undergraduate studies, postgraduate studies, international studies among others. Each of these pages has specific content. For instance, the undergraduate studies will show prospective students what studying in this university is like, the course duration, type of learning environment. It will have a search bar to search for the available courses at the University.</p><p>We took our research further by categorizing our content appropriately. This is called card sorting. We labelled the contents we identified for a functional website and put them into the appropriate pages they should be found. In getting our card, we used FIGJAM on Figma. Card sorting can also be done manually. You can click on this: <a href="https://www.figma.com/file/zDWjSnIrGtQUSJEjtyhQ6S/Card-sorting?node-id=0%3A1">https://www.figma.com/file/zDWjSnIrGtQUSJEjtyhQ6S/Card-sorting?node-id=0%3A1</a> to see our card-sorting.</p><p>Upon aligning our content with their respective pages, it was time for us to have a blueprint and layout of our website, that is, a sitemap. This step is very pivotal to the look of the website and it was a much-needed learning experience for us. In designing our sitemap, we used primarily the information from our card sorting. Click on the link below to see our sitemap. <a href="https://www.figma.com/file/s1MGteZXtKe45QvGRSsFZK/Sitemap%2C-Group-24?node-id=6%3A955">https://www.figma.com/file/s1MGteZXtKe45QvGRSsFZK/Sitemap%2C-Group-24?node-id=6%3A955</a></p><p>In all, this project was a learning curve for our team and we were able to finally have a hands-on experience of all our lessons. It gave us the similitude of being UI/UX Designers working on a live project. We will only get better from here.</p><p>We welcome your comments, observations and questions on any of what we have mentioned.<br> <a href="https://medium.com/u/f41b5d8ca29b">FOLORUNSO JEREMIAH</a> @OMONIJO ABIODUN</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3036155612e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>