Conquering Enterprise Design Challenges with Limited Domain Knowledge
As a UX or product designer, you’re likely to face complex problems in niche industries that require specialized knowledge. When designing product features for highly specialized use cases in domains where you have limited experience, it can be especially challenging. I’ve encountered this challenge firsthand while designing features in the data security and cybersecurity space. However, I’ve developed strategies over time that have helped me deliver great designs with confidence. In this article, I’ll share four of these strategies that can help you tackle any complex problem, even if you lack domain experience.
Use metaphors to develop a high-level mental model
Before jumping into design, talk to subject matter experts (SMEs) in your team and try to build a solid understanding of the product and its various use cases. Often these conversations would introduce you to technical concepts and jargon you have never encountered before. Now one can either spend hours and get into the weeds of these concepts to understand the product better, or just use metaphors to build a high-level mental model. I prefer the latter. Ask the SME whether the concept they are talking about is similar to another concept you’re already familiar with. For example, “Is the Oracle DB folder hierarchy similar to the MacOS folder hierarchy?”
The mental model you develop doesn’t necessarily have to make complete technical sense, but it’s just a tool to build a clearer picture of the product in your head and move forward with confidence.
Start with a raw user flow
Create a raw user flow based on your initial conversations with the stakeholders. The flow doesn’t have to include fancy flow charts like you see in design portfolios but could very well be a simple list in your Notes app. Writing thoughts down can help you find an initial direction to pursue, improve how you convey your thoughts to the team, and help discover missing links that the team may not have recognized earlier.
Don’t wait for all the answers before starting to design
When starting a new project, product designers tend to have a bunch of questions. A lot of the time designers get bogged down by a few unclear requirements and don’t start designing unless they have answers to all their questions. Although the intention is good, sometimes even the major stakeholders including product managers (PMs), SMEs, and design managers might not have a clear answer.
Instead of waiting for total clarity, I believe taking a proactive approach is more productive. Try making some assumptions and creating an initial high-level exploration and sharing it with stakeholders (this could be sketches or low or high-fidelity mocks). Creating these initial explorations hasn’t only helped me become more decisive but has also helped the stakeholders get clarity — by assessing my assumptions and evaluating the technical feasibility of the designs — to answer previously unanswered questions.
You are the designer
While it’s important to listen to the guidance of product managers and SMEs, it’s also important to remember that you are the designer. Don’t rely too heavily on your technical partners for design input. Use your design expertise to come up with an intuitive solution. Question and critique suggestions from PMs and SMEs, get to the root of the problem and use your design skills to create effective solutions.
In conclusion, these strategies can help you overcome the challenges of designing complex solutions in niche industries, even when you have limited domain knowledge. By building a solid mental model, starting with a raw user flow, taking a proactive approach to design, and using your design expertise, you can create effective solutions that meet the needs of your users.
