Managing UX Design Projects

Managing remote UX teams at top tech companies like Dropbox and Google has given me unique insights. Here are some best practices to overcome common challenges. - Virtual Design Critiques: Host regular design critique sessions via video conferencing. These allow for real-time feedback and ensure all team members stay aligned and engaged. - Leverage Digital Whiteboarding: Utilize tools like Miro or Mural for collaborative brainstorming and sketching sessions. These digital whiteboards can simulate the in-person experience and foster creativity among remote team members. - Conduct Virtual Usability Testing: Schedule remote usability testing sessions with real users using platforms like UserTesting or Lookback. This allows your team to gather valuable feedback and iterate on designs without needing in-person interactions. - Implement Design Pairing: Pair designers to work together on tasks via screen sharing and collaborative tools. This practice, similar to pair programming in software development, enhances problem-solving and skill-sharing among team members. - Encourage Creative Breaks: Schedule regular creative breaks where team members can share inspiration, personal projects, or recent design trends. This keeps the team engaged and inspired, even when working remotely. What strategies have you found effective for managing remote UX teams?

I used to wonder how to make my UX work more impactful. I saw designers getting astonishing results for their clients/stakeholders so I knew it was possible. I just didn’t know how to actually do it. I knew the standard processes and tools. So I thought I should hit my stakeholders over the head with how they’re doing it wrong and be the guy always fighting for users. That should do the trick, right? Wrong. Turns out I needed to: → Listen more → Follow my gut → Break the rules That’s when things started clicking. I pieced this together a long time ago in the tech world. Now I apply it to client projects. And it works... We’ve helped our clients: → 3.5x their conversion (eCommerce) → Oversubscribe their A round by 55% (health tech) → Rack up 8 awards for innovation (education) Here’s exactly how we did it: 1. Understand goals and constraints: - How is success measured? - What time pressure exists? - What have they already tried? - What are the biggest challenges? - Who are their customers or users? - What unique assets or data do they have? Literally everything depends on this. Asking the right questions upfront means better insights, better design recommendations, and better collaboration. 2. Audit the current product: - Review every screen, state, and flow - Gather screencaps and recordings - Identify opportunities, risks, problems Step 1 was the big picture. This is about details. Experience, intuition, and judgement matter here. 3. Make recommendations: - Prioritize by impact - Call attention to the top 3 issues - Present findings clearly. We use slides. Show what's happening with the current product—and how to transform it. 4. Agree on priorities, timelines, and process: - What’s the most important thing to do next? - How will we execute the work? Too many designers get caught up on "right" process. Right depends on context. There are lots of ways to succeed. 5. Execute the work: - Research, design, prototyping, testing - Every decision or finding gets tied to goals or risks AI is speeding this part up. It's a wild time. 6. Communicate & collaborate throughout: - Design is a team sport—we win together - The whole team knows what’s happening, and why - Nobody's left guessing Pro tip: Clarity is a gift designers are well positioned to give product teams. Capture roadmap, process, and status in a single visual to do this. Not sure how? DM me. 7. Ship product: “Everyone has a plan until they get punched in the face”—Mike Tyson. Things get real when they're put in front of users. Do that fast, but not so fast that you don’t get a good signal from the market. – I love helping clients succeed. Over time, I found these traits help: Teamwork Pragmatism Bias for action Lightheartedness Commitment to quality Find your own way. Break the rules when needed. Stay focused on impact. That’s what makes the work meaningful—and what makes for truly successful products (and design careers).

🚀 I Stopped Designing Alone. I Started Designing With AI. And honestly? It changed my entire UX process. Over the past few months, I’ve been integrating AI Figma plugins directly into my real-world client projects,not as shortcuts, but as thinking partners. Here’s how I actually use them in real projects 👇 1. UX Pilot: My Rapid Prototyping Engine When I receive a PRD or rough client requirements, I don’t jump straight into polished UI. I prompt UX Pilot to: • Generate quick wireframes • Create possible user flows • Explore multiple layout structures This helps me validate direction in hours instead of days. I never ship AI output directly, I refine it with business logic and user behavior insights. 2. Clueify: My Pre-User-Test Check Before showing designs to stakeholders, I run an AI usability audit. It helps me analyze: • Visual hierarchy • CTA focus • Cognitive overload • Attention flow It’s like doing a “silent usability test” before real users ever see it. 3. Stark: Accessibility Is Not Optional Real-world products serve real people. I use Stark to: • Check contrast ratios • Simulate visual impairments • Ensure WCAG compliance Accessibility isn’t a feature. It’s responsibility. 4. Octopus.do: I Structure Before Screens In large projects (especially SaaS dashboards), structure matters more than UI. Before designing anything, I: • Map the entire sitemap • Validate navigation depth • Align user journeys Because messy structure = messy experience. 5. Magician: Fast Ideation Mode When brainstorming: • Placeholder content • Icon ideas • Micro-interactions • Empty states Magician speeds up exploration so I can focus on strategy. 6. MagiCopy: UX Writing That Converts Good UI means nothing without clear communication. I use it to: • Generate button variations • Test tone (friendly vs professional) • Improve clarity Then I humanize it with brand voice. 7. Uizard: From Sketch to Prototype Sometimes clients send hand-drawn ideas. Instead of rebuilding from scratch: I convert sketches → editable wireframes → interactive prototypes. Faster iteration. Faster validation. 💡 My Personal Approach AI doesn’t replace UX thinking. It accelerates it. In real projects, I follow this rule: - AI for speed. - Human for strategy. - Users for validation. The result? • Faster delivery • Better alignment with stakeholders • More time spent on problem-solving • Less time on repetitive tasks And most importantly, better user experiences. If you’re a designer still afraid AI will replace you… It won’t. But designers who use AI effectively? They will replace those who don’t. Let’s build smarter. 💜 Whats your way of design? Comment below👇 UX Pilot AI Clueify #UXDesign #UIDesign #Figma #AIinDesign #ProductDesign #UXResearch #DesignProcess #Accessibility #SaaSDesign #UserExperience #DesignThinking #Prototyping #UXWriting #FutureOfDesign #designtools #uiux

Find the shape of your design decision. Fix the constraint, then scale the problem space. Most teams argue about design because they don’t know what kind of UX problem they’re in. Once you can read the UX metric stack, the next decision becomes obvious. In many of my work sessions with customers, we’re trying to make a call using constraints and UX metrics to understand where users actually are. These meetings can be groups of five to ten people, and there’s rarely time for deep analysis. Teams often need orientation to ideate. Not a full answer, but clarity on what the design signals mean and how to move forward. Iteration can always come later. In the moment, people want to know: what does this tell us, and what should we do next? Over time, I started noticing a pattern in how I frame design decisions and recommendations. With a small set of UX metrics in a stack, you can orient a team in about 30 seconds. You can quickly see which problems matter most. This is where design leverage starts. You cannot earn trust if people are not clear on what you are presenting to them. I often sit at the front end of fast, million dollar decisions at ZURB that compound over the life of an initiative. These decisions tend to fall into the same few shapes. Think of UX metrics as four layers that sit on top of each other. 1. Clarity Do people understand what this is and what to do next? 2. Ability Can they do it quickly and without mistakes? 3. Confidence Do they feel safe, in control, and willing to continue? 4. Commitment Do they come back, adopt it, recommend it, and rely on it? Here are the four common shapes of design problems. These patterns show up again and again. Each one tells you what kind of problem you actually have. → Confusion Trap Clarity is low. Everything above it becomes noisy or misleading. Users are not oriented. They guess, hesitate, and click around. The job here is to fix comprehension before touching polish, new features, or conversion tactics. →  Friction Wall Clarity is solid, but ability is low. Time is high, errors increase, and drop-offs appear. Users get it, they just cannot do it. The move is to remove steps, simplify flows, reduce cognitive load, tighten IA, and improve affordances. → Trust Gap Clarity and ability look fine, but confidence is low. Doubt, anxiety, perceived risk. The experience works, but it does not feel safe. This is common in fintech, healthcare, and AI. Teams need to focus on building reassurance. Transparency, guardrails, explanations, error prevention, and clear feedback about what happens next. → Adoption Leak The top of the stack is healthy, but commitment is weak. The design works, but there is no habit. The move is to focus on the value loop. Activation timing, defaults, reminders, integrations, onboarding sequence, and ongoing use cases. Finding the shape of your decision helps orient everyone on a team. You fix the lowest broken layer…and everything above it gets easier!

I’ve led significant products and successfully brought them to the finish line. Every time I take on a massive product, the first thing I do is plan for the pre-launch and post-launch activities. I brainstorm with product, UX, engineering, and QA teams to list all the different areas, milestones, risks, and dependencies. When building a new product or introducing significant enhancements, there are hundreds of things to track and align to ensure a timely launch and avoid getting stuck in an endless development cycle. Remember, coding-related activities contribute only 30% to a product's success. The remaining 70% comes from ideation, planning, communication, and adoption. Here are some of the crucial activities I focus on when I start working on a product launch: 1. Visualize the Go-Live Understand this: at this stage, most teams don’t even have a running product or final mockups yet. But we do have a high-level understanding of what it will look like. So, we start by imagining the change already in the hands of our users. Imagine the go-live day and map out every activity that comes to mind. This includes: - Product is live for consumers - Stakeholders are communicated with - A go-live support center is established - Customers and support teams are well-educated and informed Think about users, - What are they feeling? - What are they missing? - What questions do they have? - What challenges are they facing? - What do we wish we had done differently? We ensure that our entire team—engineering, product, support, marketing—knows how to support and communicate with both internal and external users about the new changes. 2. Visualize the Pre-Go-Live Map out every activity leading up to go-live. What needs to happen right before go-live? This includes: - Coding is completed - Extensive testing is conducted - Preparation for deployment - Production infrastructure is configured - Education, training, and pre-go-live communication 3. Create a Master List These brainstorming sessions result in a master list of activities—from initial development to launch. This list ensures we cover every critical step, such as: - UX design - Development - In-sprint testing - DevOps activities - Regression testing Additionally, it includes activities related to: - Risk management - Dependencies - Communication - Education & training Remember to balance the big picture with the details. We use JIRA to plan and track our day-to-day work. It’s invaluable for tracking details, but it can also be overwhelming. That’s why we need a high-level view with milestones, dependencies, and potential risks. This top-down planning approach—working backward from the launch to where we are today—has transformed how I manage and deliver big initiatives, and it can do the same for you. What approach do you follow when planning a significant initiative? Let’s discuss.

83% of ALL software projects fail. Here's our 3-step playbook that guarantees our clients are part of the 17%: In 2020, Standish Group (global IT research firm) reported: - 1 in 2 software projects are delayed, over budget, or fail to meet expectations - 1 in 3 software projects go through a complete rewrite Why do so many projects fail? - Developer-Only Teams: Narrow expertise creates one-dimensional solutions - No Documentation: Limits progress and future support - Agile Chaos: Lack of planning causes poor execution At Incepteo (my AI & digital advisory firm), we ensure our clients succeed by calling the 'architects' before the 'builders.' Here's what this looks like in practice: 1) Assemble a team of 'architects' Before our team starts building anything, I assemble a team or architects to design the solution based on the client's requirements: - CTO for strategy & implementation - Solution Architect for structural design - UX Designer for user interface and experience - Business Analyst to align solutions with business goals With this team, we: 2) Conduct a detailed discovery & design workshop We use this workshop to understand the client's: - Organizational Journey: History, goals and challenges - Customer Journey: Needs and motivations - Branding Journey: Identity & tone of voice Using this information, we: - Build a 'mood board' consisting of good ideas - Turn the best ones into low and high fidelity designs - Take feedback to a pixel level Once design and process flows are finalized, we: 3) Hand off the design to the 'builders' Builders (developers) take the designs and documentation and turn them into reality. Our development team includes the following roles: - Project Manager: to manage timeline, budget, and scope - Lead Developer: to ensure code meets the project's requirements - Frontend & Backend Developers: to code the software's UI and internals - Quality Tester: to ensure the software meets project requirements and is free of defects This process ensures that we: - Create clear, focused work packages (instead of the entire project as 1 unit) - Never face delays, budget constraints, or unmet expectations - Never need to re-code or re-write — Don't let your project become another statistic. Bring in the architects to design before letting the builders execute. And, if you're looking for a team of experts to bring your project to life – send me a direct message with your requirements and I'll personally see if we can help. Let's make your project one of the 17% that succeed 🙂

If there’s one pain point I’ve seen designers and researchers at every company I’ve ever worked at, consulted with, or advised struggle with: it’s lack of alignment on the capacity & priority of UX Design & Research work. Some of the struggles come from designers who expect to do the “full UX process” (whatever that means) on every project. Other designers have anxiety letting developers implement anything they’ve designed without first usability testing their work. Even more common is a lack of alignment with Product Management on the level of research & design effort a particular project should justify. Often, this is because no actual capacity planning for UX work takes place. Effort, Estimates, Roadmaps, and Capacity are all terms most commonly assigned to engineering work. Commitments are made, and planning is done for the delivery phase only. Often, it’s not so much that teams don’t want to include UX in their estimates. They often just don’t know how. Most companies don’t have a standard framework for level setting across the board around Design & Research Effort. So I created this framework to: ✅ Enable better capacity planning ✅ Set realistic expectations with partners on the kind of UX activities that can realistically be expected in the timeframe ✅ Help UX team determine level of discovery, iteration, and execution ✅ Empower UX team to spend more time on projects where they can add the most value. It’s been extremely helpful for us. Hoping it can help you too. #Leadership #CapacityPlanning #UXDesign #UserResearch

How do you accelerate product definition with a PM and UX Designer? 🤔 The key to speeding up product definition when a Product Manager (PM) and a UX Designer work closely is to foster a true team dynamic. This means embracing a divide-and-conquer mentality while ensuring mutual agreement on the scope and goals of what you're building. Consider this: everyone should know their role, but collaboration is where magic happens. Product Managers bring in the business perspective, what fits the business, what customers need, and are in tune with users. UX Designers offer insights into user desires and design usability, making the product appealing and intuitive. Together, with developers ensuring technical feasibility, they form a triad crucial in bringing an idea to life. One pitfall to avoid is creating silos. Don’t let the PM write requirements only to toss them over a fence to the UX Designer. Instead, work in lockstep. The process of defining the product should be as collaborative as possible, leveraging each person's expertise. This minimizes handoffs, reduces miscommunication, and ultimately accelerates the journey from concept to reality. When efficiency feels elusive, it might be due to stage gates or late involvement of team members. Involve your UX Designer from the start, prototyping and mapping workflows early. This keeps everyone aligned and contributes to a seamless and swift product definition process. In essence, it's about more than just having multiple roles; it’s about the synergy between those roles. The closer and more integrated the team, the faster and more effectively they can operate. Got a burning question about product management? Reach out at dearmelissa(dot)com!