interview-guides
Interview Guides for Consulting Engagements
Interviews are the primary tool for understanding organizational reality. They reveal what actually happens (vs. what's supposed to happen), uncover pain points and workarounds, surface political dynamics, and build relationships with key stakeholders. Good interviews are disciplined and structured; poor interviews are rambling, biased, and generate unreliable insights. This skill covers designing, conducting, and synthesizing interviews.
Interview Types
Discovery/Diagnostic Interviews
Purpose: Understand current state, identify pain points, establish baseline understanding Duration: 45-60 minutes Frequency: 20-30 interviews across organization Who to interview: Cross-functional representatives—finance, operations, IT, customers, suppliers, frontline staff Question style: Open-ended, exploratory, hypothesis-generating Output: Pain point inventory, process understanding, organizational dynamics, hypothesis validation
Use when: Starting an engagement, need to understand lay of the land, validate scoping assumptions
Validation Interviews
Purpose: Test hypotheses, validate preliminary findings, pressure-test recommendations Duration: 30-45 minutes
More from lauraflorentin/skills-marketplace
multi-agent-collaboration
A structural pattern where multiple specialized agents communicate and coordinate to solve a problem that is too complex for a single agent. Use when user asks to "build a multi-agent system", "agents working together", "agent collaboration", or mentions team of agents, distributed agents, or swarm.
23reflection
A recursive pattern where an agent evaluates and critiques its own output to iteratively improve quality and catch errors. Use when user asks to "add self-reflection", "agent introspection", "self-critique", or mentions self-evaluation, meta-cognition, or quality self-assessment.
18human-in-the-loop
A hybrid pattern where the system pauses execution to request human approval, input, or disambiguation before proceeding with critical actions. Use when user asks to "add human approval", "require human review", "human-in-the-loop", or mentions approval workflows, human oversight, or escalation.
17planning
A high-level cognitive pattern where an agent formulates a structured sequence of actions (a plan) before executing any of them, ensuring goal-directed behavior. Use when user asks to "add planning to my agent", "task planning", "agent planning", or mentions plan generation, plan execution, or step-by-step planning.
14parallelization
A concurrency pattern where multiple agent tasks are executed at the same time to speed up processing or gather diverse perspectives. Use when user asks to "run agents in parallel", "parallelize tasks", "concurrent execution", or mentions parallel processing, fan-out, or batch execution.
13routing
A control flow pattern where a central component classifies an input request and directs it to the most appropriate specialized agent or tool. Use when user asks to "route between agents", "agent routing", "task dispatch", or mentions classifier routing, intent detection, or agent selection.
12