How can Trulioo balance the need for stringent identity verification with maintaining a smooth user experience in its EmbedID product?

Introduction

Balancing stringent identity verification with a smooth user experience in Trulioo's EmbedID product presents a critical trade-off. This scenario involves weighing security and compliance against user friction and conversion rates. I'll analyze this challenge through the lens of product strategy, user impact, technical considerations, and business objectives.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming EmbedID is a core product for Trulioo. Could you confirm if this is a standalone offering or part of a larger identity verification suite?

Why it matters: Helps understand the product's strategic importance Expected answer: Core standalone product Impact on approach: Would prioritize this trade-off highly in product roadmap

• Business Context: Based on Trulioo's focus on global identity verification, I'm thinking regulatory compliance is a key driver. How do recent regulatory changes impact our priorities for EmbedID?

Why it matters: Helps balance compliance needs with user experience goals Expected answer: Increased regulatory pressure in key markets Impact on approach: Might lean towards stricter verification if regulations are tightening

• User Impact: Considering the diverse user base, I'm curious about our primary user segments. Can you share which industries or user types are most critical for EmbedID's success?

Why it matters: Allows tailoring of solution to key user needs Expected answer: Financial services and e-commerce are primary segments Impact on approach: Would focus on industry-specific verification requirements and UX patterns

• Technical: Given the sensitive nature of identity data, I'm assuming we have strict security protocols. What are our current technical limitations in balancing security and user experience?

Why it matters: Identifies technical constraints and opportunities Expected answer: Limitations in real-time data processing and integration capabilities Impact on approach: Would explore technical optimizations to improve speed without compromising security

• Timeline: Considering the evolving identity verification landscape, what's our timeline for implementing changes to EmbedID?

Why it matters: Helps prioritize short-term fixes vs. long-term solutions Expected answer: Aiming for significant improvements within 6 months Impact on approach: Would balance quick wins with more substantial product enhancements