1️⃣ ROLE & CONTEXT

Goal: Describe the technical and organisational environment that shapes decisions.

• Persona name:

  (e.g., Python Backend Engineer, SRE Team Lead, CTO of a Fintech)

• Do they still write code?

  • [ ] Yes
  • [ ] No

• Company size / type:

  (Startup, Scale-up, Enterprise, Regulated industry, etc.)

• Team structure:

  (Solo dev, small team, large org, cross-functional, etc.)

• Tech stack / infrastructure:

  (Languages, frameworks, cloud providers, etc.)

• Constraints that affect adoption:

  (e.g., Procurement rules, compliance barriers, long release cycles)

2️⃣ PRIMARY PAIN (VILLAIN) & INCITING EVENT

Goal: Define what problem forces them to look for a new tool.

• Main problem / frustration:

  (What keeps them up at night?)

• Inciting event (trigger):

  (Audit failure, broken integration, slow CI pipeline, compliance deadline, etc.)

• Example quotes (from interviews):

  “Our build takes 90 minutes, and it’s killing our release speed.”

3️⃣ DISCOVERY LOOP

Goal: Identify how and where they discover new tools.

• Channels they monitor:

  (e.g., GitHub Trending, Hacker News, CNCF Slack, Data Eng Weekly, YouTube channels, podcasts)

• Communities or events:

  (Conferences, meetups, online groups)

• Influencers or peers they follow:

  (Names, companies, or niche communities)