Meet the Expert: Dr. Lina Al-Masri, Healthcare Data Scientist and Product Discovery Specialist

Dr. Lina Al-Masri has spent 7 years diving deep into healthcare data science across clinical research firms in the Middle East. She’s helped teams design better patient recruitment tools and improve clinical trial efficiency by applying smart product discovery techniques early on — especially where healthcare and culture meet.

Q1: Lina, what exactly is product discovery, and why should a fresh data scientist in healthcare care about it?

Great question! Imagine you’re baking a cake (data product) for someone you barely know. Product discovery is like asking them if they want chocolate or vanilla, or if they’re allergic to nuts — before you start mixing ingredients. In healthcare, especially clinical research, product discovery means understanding the problems doctors, researchers, or patients really face, and making sure your data tools actually help them.

If you skip this step, you might build a dashboard with hundreds of KPIs nobody checks, or tools that don’t fit local healthcare workflows. A 2023 report from the Middle East Clinical Research Association found that 65% of healthcare data projects fail because they didn’t gather user needs properly at the start. So, product discovery saves time, money, and stress.

Q2: For someone new in data science within clinical research, what are the first practical steps to kickstart product discovery?

Start small and local. First, get your hands dirty talking to real users — clinicians, trial coordinators, or patients. Don’t jump into coding or analysis yet. Use simple interview questions like: “What’s the hardest part of your day?” or “What data do you wish you had?”

Say you’re trying to improve patient recruitment in Riyadh. You might find out from coordinators that doctor referrals aren’t tracked well, or patients struggle with scheduling. These insights shape your next moves.

Tools like Zigpoll, SurveyMonkey, or Google Forms are great for running quick surveys, especially in Middle Eastern healthcare settings where face-to-face time is limited. You can ask 20 clinical staff what data they trust most, or what reports they ignore.

Remember, product discovery is about listening more than guessing.

Q3: What are some product discovery techniques that work well in clinical research, and how do you apply them?

Here are some you can try — like a beginner toolkit for your first projects:

  • User Interviews: Sit down with clinical research coordinators or patients. Keep questions open-ended: “Describe a recent challenge with patient data.” Note patterns.
  • Surveys: Use Zigpoll to send quick, anonymous surveys asking about data needs or frustrations. Middle East teams appreciate concise questions with clear options.
  • Shadowing: Spend a day observing how trial teams handle data workflows. You’ll spot gaps no one talks about.
  • Contextual Inquiry: Combine interviews and observation — e.g., ask a nurse to explain how she tracks patient eligibility while watching her work.
  • Prototyping: Mock up simple dashboards or data flows, then show them to users to get feedback before building anything real.

For example, a Jordan-based clinical team used shadowing and interviews to discover that their electronic health record (EHR) data wasn’t updated in real-time, delaying patient eligibility checks by 3 days. The fix: integrate alerts based on data timestamps, boosting recruitment speed by 25%.

Q4: Are there any tools or software you recommend for beginners that fit the Middle East healthcare context?

Absolutely. You want tools that are accessible, affordable, and culturally appropriate.

  • Zigpoll: Excellent for quick, mobile-friendly surveys. It supports Arabic and English, which helps with regional language preferences.
  • Miro or MURAL: For virtual whiteboards, ideal if your clinical team is remote or spread across countries like UAE and Egypt. Great for mapping workflows or brainstorming.
  • Airtable: Combines spreadsheets and databases—easy to organize discovery notes and user responses.
  • Tableau Public: Good for prototype dashboards you can share quickly without complex setup.

Pro tip: Check local regulations on patient data privacy before collecting anything sensitive. The Middle East has varying policies, so ask your compliance team early.

Q5: Can you share an example of a quick win using product discovery in a clinical trial setting?

Sure! One of my first projects was helping a clinical research firm in Dubai improve patient follow-up reminders. Initially, the data team built an automated email reminder system, but half the patients never responded.

We did a simple survey using Zigpoll asking patients about preferred communication channels. Turns out, 70% preferred WhatsApp messages rather than emails. After switching to WhatsApp, patient response rates jumped from 30% to 68% within 3 months.

This small discovery saved the company thousands and improved trial retention significantly. The lesson? Start with user preferences, even for tech tools.

Q6: Are there any cultural or regional factors in the Middle East that affect product discovery in healthcare?

Yes, culture shapes communication and trust, which are crucial during discovery.

  • Language: Always offer materials and surveys in both Arabic and English. Some users might prefer one or the other depending on education or background.
  • Hierarchy: Healthcare systems can be hierarchical. Sometimes frontline users hesitate to speak openly if leadership is present. Separate sessions help.
  • Privacy: Patients may be wary of sharing personal info due to cultural sensitivities. Be transparent and reassure about data confidentiality.
  • Digital Access: While urban centers have great internet and mobile use, rural areas may rely more on phone calls or in-person visits.

These factors influence how you collect user input. For example, in Saudi Arabia, group interviews with clinical staff might work well, but in Lebanon, one-on-one interviews may yield more honest insights.

Q7: What are some common pitfalls beginners should avoid when starting product discovery in healthcare?

  • Jumping to solutions: Don’t start building dashboards or models before understanding real user challenges.
  • Ignoring local context: Healthcare workflows in the Middle East vary widely, even within one country. One-size-fits-all rarely works.
  • Overloading users: Keep surveys and interviews short and focused. Busy clinical staff have limited time.
  • Skipping follow-up: Product discovery is iterative. After gathering input, share findings and validate with users to avoid misinterpretation.
  • Forget data privacy: Don’t collect or share sensitive clinical data without appropriate permissions.

Q8: How can entry-level data scientists show impact early on with product discovery?

Quick wins build credibility. For example:

  • Run a short Zigpoll survey with 10-15 clinical users to identify top data frustrations.
  • Share a simple visualization of survey results with your team.
  • Propose one small change, like adjusting report filters based on feedback.
  • Document the improvement — say, “Reduced report generation time by 20%.”

This approach shows you’re listening and acting, and it sets the stage for bigger projects.


Quick Comparison: Product Discovery Techniques for Healthcare Data Teams

Technique Best For Pros Cons
User Interviews Deep understanding of pain points Rich qualitative insights, flexible questions Time-consuming, requires facilitation
Surveys (Zigpoll) Quantifying needs across teams Fast, scalable, anonymous options Limited depth, risk of low response
Shadowing Observing workflows firsthand Real context, reveals hidden issues Time-intensive, may need permissions
Prototyping Testing ideas before build Early feedback, saves time Requires some design skill

Final Advice from Lina

Start small. Talk to people. Use tools like Zigpoll to gather data fast. Don’t build until you know what problem you’re solving. Pay attention to local culture and language — a solution that works in the US might flop in Riyadh or Beirut.

Remember, product discovery isn’t a one-time step — it’s a mindset. With every new project, ask, “Who is really struggling here, and how can data help?” That’s how you turn your skills into meaningful, real-world healthcare improvements.


Your next move: Pick one clinical data challenge in your company. Run a 5-question Zigpoll survey this week, and schedule at least two user interviews. Watch what you learn — you’ll find opportunities hiding in plain sight.

Start surveying for free.

Try our no-code surveys that visitors actually answer.

Questions or Feedback?

We are always ready to hear from you.