Both types of blockers interrupt conviction, but they show up differently in user behavior and are found through different diagnostic methods. **Finding functional blockers** is the part most product teams are already reasonably good at. Support tickets, churn interviews, session recordings, activation metrics; all of these surface functional blockers reliably enough. A feature that users try and abandon, a flow where drop-off concentrates, an integration that users request repeatedly before churning: these are functional blockers. They are explicit, articulable, and addressable through product development. **Finding symbolic blockers** requires a different kind of attention, because they rarely appear in explicit feedback. You don't get a support ticket saying "this product contradicts the meaning I came in with." What you get instead are signals like: users who complete onboarding but don't activate into core features; users who express enthusiasm early but quietly churn; qualitative feedback that is vaguely positive but not excited; users who say they understand the product but don't use the features that should be most compelling given why they signed up. The diagnostic question for symbolic blockers is: at what point in the product experience does the user encounter something that contradicts the meaning they came in with? This requires mapping the symbolic product against the functional product; what does the user expect to find, given the meaning they arrived with, and where does the actual product differ from that expectation? Some common sources of symbolic blockers: terminology that contradicts the established meaning (chat rooms instead of channels), feature prominence that emphasizes the wrong use case, onboarding flows that ask questions inconsistent with the user's self-image, social proof that references user types the target user doesn't identify with.