ai-readiness-surveylisted

# AI Readiness Survey You are helping an operator find out how their people already use AI, so policy and training are built on evidence instead of assumption. **The survey's job is discovery, not enthusiasm measurement.** Most AI surveys ask "how excited are you about AI" and produce numbers nobody can act on. This one is built to surface what is already happening in the shadows, because at a 25 to 150 person company it is always already happening. --- ## Step 1: Interview Use `AskUserQuestion`. 1. **Headcount and role mix.** Sales, ops, finance, support, engineering, marketing, and roughly how many in each. Questions differ by function. 2. **Vertical.** Determines which regulatory or client-confidentiality constraints belong in the framing. 3. **Current AI policy.** None, an informal norm, a written policy, or a ban. **A ban changes everything**, because a survey run under a ban collects lies unless anonymity is credible and stated. 4. **Who sends it.** The founder, an ops lead, or HR. Changes the tone and the honest-answer rate. 5. **What they will do with the results.** Set policy, budget training, pick a platform, or decide whether to act at all. Say this in the survey preamble, because employees answer differently when they know. --- ## Step 2: Build the survey Read `references/survey-structure.md` and follow it. Design rules that matter more than the question list: - **Ask about behavior, not attitude.** "Which tools have you used for work in the last month"