Department Playbooks — Knowledge Check

[
  {
    "question": "A sales rep pastes a competitor comparison into the Sales Project and asks Claude to explain why your product is better. What is the main risk?",
    "options": [
      "Claude will refuse to answer because it involves competitors",
      "Claude may generate claims that are inaccurate or unsupportable, creating reputational or legal risk",
      "Claude does not have access to competitor product information",
      "The output will always be too long to use in an email"
    ],
    "answer": 1,
    "explanation": "Claude will generate a comparison, but it can fabricate or exaggerate claims. The Sales Project system prompt should explicitly prohibit making claims about competitors. All competitive messaging should come from approved materials."
  },
  {
    "question": "An HR manager wants to use Claude to draft redundancy letters. What is the most important thing to include in the HR Project system prompt?",
    "options": [
      "A list of all employees who may be affected",
      "A requirement that every output is labelled as a draft requiring HR and legal review",
      "Instructions to use formal legal terminology throughout",
      "A connection to the company HR information system"
    ],
    "answer": 1,
    "explanation": "Redundancy letters have legal effect. The system prompt must make clear that all outputs are drafts requiring review — never final documents. This protects both the company and the employees involved."
  },
  {
    "question": "A colleague proposes one shared Claude Project for the whole company — Sales, HR, Legal, and Finance all in the same Project. What would you advise?",
    "options": [
      "This is the most efficient approach and reduces admin overhead",
      "It works well if the system prompt is kept very short and generic",
      "Separate Projects per team consistently outperform a general shared Project because system prompt specificity drives output quality",
      "This is not possible — Claude only supports one Project per organisation"
    ],
    "answer": 2,
    "explanation": "A general system prompt produces generic outputs. Sales, HR, Legal, and Finance have completely different audiences, tones, constraints, and use cases. One Project per team produces dramatically better results."
  },
  {
    "question": "A legal team member pastes an NDA into Claude and asks if it is safe to sign. What is the correct response?",
    "options": [
      "Claude can accurately determine whether an NDA is safe to sign",
      "Claude can only review NDAs under 5,000 words",
      "Claude can summarise the NDA and flag unusual clauses, but cannot determine whether it is safe to sign — that requires qualified legal review",
      "Claude should refuse to process legal documents entirely"
    ],
    "answer": 2,
    "explanation": "Claude is useful for a first-pass scan and plain-English summary, but cannot provide legal advice or make a determination about whether a contract should be signed. All outputs must be reviewed by a qualified lawyer."
  },
  {
    "question": "What is the single most effective technique for improving the quality of board reports written with Claude?",
    "options": [
      "Ask Claude to write longer reports",
      "Specify the audience explicitly — for example, experienced board members who will read this in 5 minutes",
      "Remove the system prompt so Claude has no constraints",
      "Use Claude only for the metrics table, not the narrative"
    ],
    "answer": 1,
    "explanation": "Specifying the audience shapes structure, tone, length, and vocabulary. The audience instruction changes what Claude produces more than almost any other single variable."
  },
  {
    "question": "What is the quality bar for a saved prompt in the department prompt library?",
    "options": [
      "The output must require no editing before use",
      "A team member can paste in their content and get a usable output in under 2 minutes with minor edits",
      "The prompt must be under 100 words",
      "The output must match the system prompt instructions exactly"
    ],
    "answer": 1,
    "explanation": "The goal is not zero editing — that would make outputs sound robotic. The goal is that a team member can go from raw material to something usable in under 2 minutes. Minor editing to match their voice is expected and desirable."
  }
]