15 questions measuring five psychological barriers that may be constraining your Tech Passioning engine — the beliefs, fears, and patterns that prevent entrepreneurs from developing full technological conviction and spreading that conviction to their teams.
Before We Start
Enter your details to receive your TP Psychological Barrier score and a personalized interpretation.
By continuing, you agree to receive your diagnostic results and information about CBT Coaching for entrepreneurs from PreneurDomain. Unsubscribe anytime.
Question 1 of 15 — Technology Identity Anxiety
When someone describes you as “a tech person” or “technical,” your internal reaction is:
That feels accurate — technology is a core part of who I am
Mostly accurate, though I wouldn’t call myself deeply technical
Somewhat uncomfortable — I use technology but don’t fully identify with it
Noticeably uncomfortable — I feel like a fraud when described that way
Strongly uncomfortable — I actively resist being labeled as “technical”
Question 2 of 15 — Technology Identity Anxiety
When a technology conversation becomes complex or highly technical, I:
Lean in — complexity energizes me even if I need to learn
Engage comfortably and ask clarifying questions
Feel my attention drifting and tend to defer to the “technical people”
Feel anxious and often stay quiet to avoid revealing what I don’t know
Actively avoid or exit such conversations whenever possible
Question 3 of 15 — Technology Identity Anxiety
My belief about my capacity to understand and lead technology decisions is:
Strong — I can understand any technology given enough context and effort
Generally positive — I’m comfortable with most technology discussions
Mixed — I can handle some areas but feel genuinely out of my depth in others
Limited — I believe technology understanding requires an innate aptitude I don’t have
Deeply fixed — I’ve accepted that technology is simply not my strength and never will be
Question 4 of 15 — Techno-Imposter Syndrome
When making a technology-related decision for my venture, I typically feel:
Confident — I trust my judgment even on technical matters
Mostly confident, with occasional self-doubt on highly technical decisions
Uncertain — I often wonder if someone more technical should be making this call
Anxious — I frequently worry that others will discover I don’t truly understand the technology
Paralyzed — I avoid making technology decisions because I fear making a mistake that exposes my lack of expertise
Question 5 of 15 — Techno-Imposter Syndrome
When investors, partners, or team members ask me deep technical questions about my product or platform:
I engage enthusiastically — technical Q&A is where I shine
I answer comfortably and acknowledge when I need to follow up
I deflect to team members when possible to avoid revealing gaps
I feel a spike of anxiety and rehearse answers to avoid appearing uninformed
I dread these moments and sometimes avoid situations where technical questions are likely
Question 6 of 15 — Techno-Imposter Syndrome
Despite any evidence of my competence (revenue, users, team trust), the thought “I’m not really qualified to lead this technology” occurs to me:
Never or almost never — I feel qualified and evidence confirms it
Occasionally during moments of high stress or uncertainty
Regularly — at least once a week this thought surfaces
Frequently — it’s a persistent background narrative
Constantly — it shapes most of my decisions about when and whether to engage technically
Question 7 of 15 — Vision Communication Avoidance
When I have the opportunity to share my bold technological vision with my team, investors, or partners:
I share passionately and openly — expressing my conviction comes naturally
I share effectively, though I sometimes hold back the most ambitious parts
I tend to use safe, corporate language instead of expressing my genuine excitement
I frequently downplay my vision because I fear being seen as naive or unrealistic
I almost never share the full depth of my technological conviction with others
Question 8 of 15 — Vision Communication Avoidance
My fear about expressing passionate technological conviction publicly (to teams, audiences, or stakeholders) is:
Minimal — I’m comfortable being seen as passionate and technologically driven
Low — some mild discomfort but I push through easily
Moderate — I worry about being perceived as “too intense” or unrealistic
Significant — the fear of judgment or rejection meaningfully constrains what I say
Intense — expressing genuine technological passion feels deeply vulnerable and I avoid it
Question 9 of 15 — Vision Communication Avoidance
When my team or stakeholders respond with skepticism to my technology-driven ideas, I:
Double down with evidence and enthusiasm — skepticism energizes me
Engage with the skepticism constructively while maintaining my position
Partially retreat — I soften my position to reduce conflict
Significantly retreat — I question my own conviction when others doubt it
Completely withdraw — skepticism confirms my fear that the vision is unrealistic
Question 10 of 15 — Perfectionism-Driven Evangelism Paralysis
My willingness to passionately promote my technology/product BEFORE it is fully polished is:
High — I share the vision and excitement from day one, imperfections and all
Good — I share early with appropriate caveats about work in progress
Hesitant — I wait until at least the core features are working before sharing with conviction
Reluctant — I need significant completion before I feel comfortable evangelizing
Blocked — I cannot share with genuine passion until the product meets my quality standards
Question 11 of 15 — Perfectionism-Driven Evangelism Paralysis
The thought “it’s not ready yet” has prevented me from sharing my technological vision with potential team members, partners, or customers:
Never or rarely — I share regardless of readiness level
Occasionally — but I recognize and push past the hesitation
Sometimes — it has delayed important conversations by weeks
Frequently — it has delayed important conversations by months
Persistently — I am currently holding back from sharing because the product isn’t “ready”
Question 12 of 15 — Perfectionism-Driven Evangelism Paralysis
My standard for “ready to share” when it comes to my technology vision or product is:
Minimum viable — if the concept is clear, I’m sharing it
Functional — core value proposition demonstrable, even if rough
Solid — major features working, most bugs resolved
Polished — I need a professional-quality presentation of the technology
Near-perfect — I rarely feel the technology is ready enough to represent my vision
Question 13 of 15 — Passion Hoarding
When it comes to sharing ownership of the technological vision with team members:
I actively encourage others to champion the tech vision — more evangelists means more momentum
I share willingly and enjoy seeing team members develop their own passionate relationship with the technology
I share the vision but feel uncomfortable when others interpret or represent it differently than I would
I hold the vision tightly — I worry that others will dilute or misrepresent it
The technological vision feels inseparable from my identity — sharing it feels like losing a part of myself
Question 14 of 15 — Passion Hoarding
My willingness to delegate technology-related decisions to capable team members is:
High — I delegate confidently and trust my team’s technical judgment
Good — I delegate most decisions but retain oversight on strategic tech choices
Moderate — I delegate reluctantly and often second-guess or reverse decisions
Low — I need to be involved in most technology decisions or I feel anxious
Very low — I cannot release technology decisions without significant distress
Question 15 of 15 — Passion Hoarding
The thought “if I share this vision completely, they won’t need me anymore” resonates with me:
Not at all — the team succeeding without me on every decision is the goal
Slightly — a small part of me worries, but I recognize it as irrational
Moderately — this fear influences some of my sharing/delegation decisions
Significantly — this is a real concern that constrains how much I share
Strongly — my value to the venture feels tied to being the sole holder of the technological vision