AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

interview-mapper

Use when coding or making sense of one interview transcript (customer, JTBD, expert, usability, exit). Extracts verbatim-grounded nuggets with extract_nuggets.py, verifies quotes with verify_quotes.py and checks conclusions hold across reruns with consensus.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--interview-mapper at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 63

templates/change-readiness.md

Lens: Change Readiness (stakeholder)

When: interview with a stakeholder/employee BEFORE a specific transformation/reorganization — goal is to map the political landscape around a decision that hasn't been made yet or is being rolled out. Difference from org-mapping-vmdi: that one is a snapshot of the current state of the system as a whole; this one is targeted at ONE upcoming change, the coalitions for/against it, and the hidden interests around it. Difference from expert: that one assesses domain expertise regardless of personal stance; here, stance and personal interest are the main subject. Coding unit: a statement of position on a specific change with a quote + separately — the presumed hidden interest (not what is said formally, but what is lost/gained personally). Collection discipline: keep "what is said publicly" and "what can be inferred about personal interest" explicitly separate (the latter is interpretation, not fact — flag as hypothesis).

Layer 1 — operational (facts + quote + line)

  • R1 Stated position on the change — for / against / neutral, in the respondent's own words.
  • R2 Official reason for the position — what they name as justification (efficiency, risks, organizational values).
  • R3 Who else is for and against, per the respondent — names/roles named by the respondent, and which side they place them on.
  • R4 Past experience with similar changes — how similar transformations went in this organization before, per the respondent's memory — success/failure and why.
  • R5 Conditions for support — what would need to happen for the respondent to move from neutral/opponent to active supporter.
  • R6 Expected personal losses/gains for the respondent — what the respondent themselves names as a possible personal gain/loss (authority, status, workload, budget).
  • R7 Channel of influence — through whom/what the respondent usually pushes their position in the organization (meetings, informal conversations, memos).

Layer 2 — analytical (conclusion + quote; CAPS) — to council

  • A1 Public position vs hidden interest — where the official justification (R2) may be masking a personal interest (R6) — interpretation, flag as HYPOTHESIS, not fact. (unstable — latent)
  • A2 Coalition map — (assembled after several interviews) clusters "for" / "against" / "wait-and-see", based on overlapping R3 mentions across respondents.
  • A3 Influence strength — how much the respondent can actually affect the outcome, judging by channel (R7) and role, not just by how loud their position is.
  • A4 Conditional support (R5) — specificity — a concrete, measurable condition vs a vague deflection ("if it's all done fairly") — a vague condition often signals hidden disagreement that no compromise will resolve.
  • A5 Risk of repeating a past failure — does the current situation match the pattern of a failed change from R4.
  • A6 Key insight — 1 sentence: on change [X], the respondent holds position [Y], the likely real interest is [hypothesis Z], influence strength is [high/low], risk is [W].

Forcing questions

What will personally change for you if this happens? Who in the organization will be happy about this, and who won't, and why? Has something similar happened before — how did it turn out? What would need to happen for you to support this 100%? How do you usually push your position here?

Scope and ethics

This is the only lens where the interviewer deliberately builds a political map of people — handle A1/A2 with maximum care: hypotheses about hidden interest MUST NOT be shared with respondents without anonymization, and they must not become the sole basis for personnel decisions without independent human verification.