UX Gaps

 Missing out on the EdTech opportunity hit harder than you expected. The work would have been a good fit, and you were ready, but the lack of testimonials stopped things before they could even get started. You realized that waiting for opportunities to quietly land in your inbox wasn’t enough—you needed to be intentional. You reached out to your network, sharing that you were open to freelance work focused on EdTech and mobile projects. You followed up with people you trusted, showed up to meetings with clarity about what you were looking for, and positioned yourself to be seen. A few weeks later, it worked. A stakeholder at a local community college contacted you. They were preparing for the upcoming semester and adding a new industry track. They needed updates to their mobile app, new courses added, and a simple onboarding flow for students. Their internal designer, who usually handled these projects, was on vacation, and the timeline was tight. You didn’t know the stakeholder ...

 It’s been a couple of weeks since you wrapped up that project with the other designer. You’re back to sharing insights in UX communities, and staying active in your monthly meetup—just keeping the momentum going and putting your work out there. Then, out of the blue, a message lands in your inbox. A small ed-tech startup noticed something you commented on and wants to see if you can help with a project. It’s exciting—you weren’t looking for work—but there’s a catch: they want social proof . A testimonial from a previous client. You freeze. You’ve done real freelance projects, but you’ve never asked for testimonials. Everything in your portfolio looks like practice work or personal experiments. Without social proof, you know the client likely won’t move forward. You reach out to one or two of your friends from the UX meetup, hoping someone might be able to help. Only one of them responds: “Hey, thanks for reaching out! You’re a really great person, and we always have such interes...

That realization stayed with you longer than you expected. You had been so excited about working with another designer—someone in your niche whose work you genuinely admired. You imagined an equal partnership, a flow of ideas, a chance to learn from someone more experienced. But the reality wore you down. Instead of the dialogue and shared effort you hoped for, you found yourself taking on the tasks no one else wanted. Your ideas were dismissed before they were even considered. The project itself aligned with your skills, but the experience left you drained, frustrated, and far from what you had envisioned. As you reflect on it now, one question keeps resurfacing: Are you the kind of designer others would choose to work with? The answer isn’t obvious. You realize now that, even though you're new, showing that you take your work seriously and contribute thoughtfully is what makes others want to collaborate with you. During that project, you didn’t assert yourself when things felt un...

 With a clearer understanding of the gaps in your skills, you start taking a closer look at the people you've met in your weekly networking group over the past few months. You’ve built a sense of who you connect with, who’s approachable, and who you could genuinely see yourself working with. You dive a little deeper—checking LinkedIn profiles, browsing portfolios, and trying to get a feel for who might be a good fit for future projects. You reach out to a developer who seems promising. You explain your situation honestly: your strengths, the areas where you could use support, and the types of projects you might bring them into. They’re open but cautious. No promises yet—just the beginning of a possible collaborative relationship. While that’s unfolding, an email pops up in your inbox. A short freelance request from a UX designer in one of your online communities. It’s a small ed-tech project, right in your wheelhouse, and the chance to collaborate is exciting. The first week goes...

Two days after delivering the final handoff for your barter project, the excitement is still buzzing, but so is the overwhelm. Your client is ecstatic about their new website. They promised referrals and a glowing testimonial for your portfolio. You finally take a deep breath and sit with everything that’s just happened. It was a small, low-stakes project, yet it felt full of pressure. Delayed responses, tiny scope changes, and unexpected requests stretched your timeline and tested your communication skills. Looking back, you realize that every quick addition did more than extend the hours. It nudged the entire project schedule for both you and the client. You hadn’t paused to address those changes in the moment. Now that you see it clearly, even the smallest add-on should have been a signal to stop and talk — a simple conversation confirming that any additions, big or small, would shift the timeline and potentially the deliverables. Only after alignment should you have even considered...

It’s been a few months since you started showing up to UX meetups, and things are finally starting to pick up. One day, a friend of a colleague reaches out, connecting you with a small business that needs a website. You open the email, excited. They’re just getting started and can’t quite afford a full-rate project, but the work aligns perfectly with your niche. You see an opportunity for a strategic barter — a partial discount in exchange for a testimonial or referral. You hop on a call to learn more. You ask about their business goals and deadlines and try to get a sense of how involved they want to be. Pulling from your pricing guide, you make sure that even a discounted project still feels fair. You sign the contract, set your plan, and get to work. Then reality hits. Unlike your boot camp days, no mentor is checking your progress or confirming your decisions. Every unexpected client request or small mistake triggers self-doubt. Did you communicate clearly enough? Did you scope t...

The new business cards arrived last week — thick matte paper, clean typography, and your latest title: EdTech App Designer. It feels good. You’ve reworked your portfolio, aligned all your social media, and even updated your email signature. Everything finally fits the story you’ve been building — your brand, your niche, your vision. This week, you’re at your monthly designer meetup, showing off your new cards and talking about your focus in EdTech app design with friends and colleagues. Everyone’s impressed — and for the first time, you feel like your hard work is starting to pay off. But as the conversation continues, reality hits in the form of questions you’re not prepared to answer. “So, what do you charge for a typical project?” “Do you have a contract template you use?” “How do clients usually pay you — upfront or in phases?” You smile, trying to sound confident — but inside, there’s a flicker of panic. Because while you finally look like a business, you realize you don’t quite ...

After weeks of reflection and research, you finally feel confident about where you want to focus your freelance career: EdTech app design. It's a space that excites you, connects with your strengths, and builds naturally from the projects you already have. But once the excitement settles, it hits you. Deciding your niche was only the first step. If you want clients to see you as an EdTech designer, everything you show and say about yourself has to support that story. Refining Your Portfolio You start with your portfolio. The EdTech app you designed during your bootcamp instantly feels like the anchor, a project that fits exactly where you're heading. But as you read through the case study, you notice that it mostly focuses on final designs, not the reasoning behind them. You go back in and refine the story, explaining why you made certain design decisions, how your research informed the direction, and what outcomes your design led to. You want potential clients to understand no...

It’s been a few months since you decided to go out on your own as a UX designer. You’ve updated your LinkedIn headline — UX Designer, Product Designer — built your portfolio, and started applying for small freelance projects. You’ve joined a few UX meetups, maybe even jumped into an online community or two, hoping to connect with other designers. You’re doing everything you’re supposed to. You’re networking, getting your name out there, and following all the advice about how to get started. And then, at one of those meetups, it happens. You’re standing in a small circle of designers, chatting about tools, projects, and career paths. Most of them work full-time at companies. One’s a UX researcher in healthcare, another designs enterprise dashboards, and another is deep into usability testing for e-commerce. Eventually, someone turns to you and says, “ Oh, you’re freelancing now? That’s awesome. What kind of UX designer are you?” You freeze for a second. You know you do UX — but wha...

After finishing a UX design bootcamp, a new designer is eager to get their career started. They’ve been networking, attending meetups, sharing work online, and even landed interviews. But nothing has felt like the right fit yet. So instead of waiting for the perfect opportunity, they decide to try freelancing. The thinking is simple: “Why wait for a company to hire me when I can start working on my own projects right now?” They tell friends and family they’re available for freelance work, and a few opportunities come up. Maybe it’s a local store downtown that needs a website redesign, and they barter services — “ I’ll design your website if you help me with something in return.” Or maybe a cousin needs a simple portfolio site. These early projects are valuable. They provide practice, portfolio pieces, and confidence. But they’re not real client work. There’s no legal agreement, no formal contract, no defined scope. If something goes wrong, the stakes are low. That’s part of the probl...

 It’s your first week as a junior UX designer on a small, tight-knit product team — one lead designer, one mid-level designer, and two developers. You’re excited to finally put your skills into practice and contribute to real work. Your first project focuses on improving a section of the company website that’s been struggling with performance. After your first stakeholder meeting, you receive a detailed summary document packed with business metrics: conversion rates, drop-off points, and profitability trends. You scroll through it, trying to make sense of everything. The language is full of business jargon — meaningful, but disconnected from the world of users. Unpacking the Jargon You take the document to the mid-level designer, who’s experienced with the product and can help translate the metrics into actionable insights. Together, you review the spreadsheet. They explain: “When stakeholders talk about conversion rates, they mean how many users complete key actions — like si...