Leadership asks you to prove the docs team's value. What's the most credible way to measure impact?
- A. Total number of pages published this quarter
- B. Reduction in related support tickets, task success rates, and time-to-first-success for users ✓
- C. Word count and how many features are 'covered'
- D. How many internal stakeholders praised the docs
Correct answer: B. Outcome metrics like deflected tickets and user success tie docs to business value, unlike vanity output counts.
You want to overhaul a legacy docs system, but you have no authority over the teams whose content it affects. How do you drive the change?
- A. Wait until you're given formal authority to mandate it
- B. Build a coalition with data, a pilot showing results, and allies among team leads ✓
- C. Redo it all yourself quietly and present it as done
- D. Escalate to the CEO to force compliance
Correct answer: B. Influence without authority comes from evidence, small proven wins, and coalition-building, not mandates or unilateral action.
You suspect the docs are hurting adoption but you only have subjective complaints. How do you build a real case?
- A. Trust the complaints and start rewriting immediately
- B. Instrument the docs — search analytics, page drop-off, ticket tags, and user testing — to locate the real failures ✓
- C. Survey the docs team for their opinions
- D. Compare page counts against a competitor
Correct answer: B. Turning anecdotes into an evidence-based diagnosis lets you fix the actual failure points rather than guess.
A powerful stakeholder wants a large, low-value doc set built for a pet project, pulling you off high-impact work. How do you handle it?
- A. Comply fully to keep the relationship smooth
- B. Make the trade-off visible with data and propose a scoped-down version or a priority decision from a neutral owner ✓
- C. Refuse outright and tell them it's not worth it
- D. Do it quietly while letting the important work slip
Correct answer: B. Surfacing the opportunity cost and forcing an explicit prioritization protects impact without a purely political fight.
You're setting docs strategy for a fast-growing product. What should anchor the strategy?
- A. Covering every feature the product has ever shipped
- B. The highest-impact user journeys and the business outcomes docs can move ✓
- C. Matching whatever the biggest competitor documents
- D. Maximizing the volume of content for SEO
Correct answer: B. Strategy should focus finite resources on the journeys and outcomes that matter most, not exhaustive or imitative coverage.
An SME repeatedly signs off on drafts without really reading them, and errors slip through. How do you fix the review process?
- A. Stop asking that SME to review anything
- B. Make review low-effort and targeted — ask specific technical questions or have them verify by running the steps ✓
- C. Publish without review to save everyone time
- D. Escalate the SME to their manager for not doing their job
Correct answer: B. Rubber-stamp reviews improve when you lower the effort and ask precise, verifiable questions rather than 'please review this.'
Two teams own overlapping features and each wants 'their' terminology in the shared docs, confusing users. As the senior writer, what do you do?
- A. Let each team use its own terms in its own sections
- B. Facilitate a decision on one controlled vocabulary based on what's clearest for users, and document the rationale ✓
- C. Alternate between the two terms to be fair
- D. Escalate and let a VP pick a term at random
Correct answer: B. A senior writer resolves terminology conflicts by driving to a single user-centered standard, using neutral facilitation and rationale.
Your docs score well on internal reviews but users still struggle. What does this most likely mean?
- A. Users aren't the target audience after all
- B. Your internal quality proxies don't match real user success — validate with actual users ✓
- C. The docs need more internal reviewers
- D. The product is simply too complex to document
Correct answer: B. A gap between internal quality signals and user outcomes means you're measuring the wrong thing and must test with real users.
You're asked to cut the docs budget and automate more. How do you approach it strategically?
- A. Resist all automation to protect writer headcount
- B. Identify what automation genuinely helps (generation, checks) versus what still needs human judgment, and redeploy writers to high-value work ✓
- C. Automate everything and reduce writers to editors
- D. Refuse and argue docs can't be measured
Correct answer: B. Mature strategy separates the mechanical work automation handles well from the judgment work humans must do, then reallocates accordingly.
A long-tenured writer on your team resists any new structure or standards. How do you handle it?
- A. Overrule them and impose the standards by authority
- B. Understand their concerns, involve them in shaping the standards, and show evidence the change helps readers ✓
- C. Route around them and let them keep their old ways
- D. Document their resistance for their performance review
Correct answer: B. Durable change with a resistant peer comes from listening, co-ownership, and evidence, not authority or avoidance.
You have to decide whether to invest in a docs-as-code toolchain migration that will slow output for a quarter. How do you make the call?
- A. Avoid it — never sacrifice short-term output
- B. Weigh the long-term gains (versioning, review, scale) against the short-term cost and get stakeholder buy-in on the trade-off ✓
- C. Do it immediately because modern tooling is always better
- D. Let engineering decide since it's a tooling question
Correct answer: B. Senior judgment weighs long-term leverage against short-term cost transparently and secures buy-in, rather than reflexively optimizing either horizon.
Support tickets are dropping but you can't tell if your new docs caused it. How do you establish the connection?
- A. Claim credit since the timing lines up
- B. Correlate ticket categories with specific doc changes, and where possible test changes against a control or baseline ✓
- C. Assume other factors and don't claim anything
- D. Ask support to guess how much the docs helped
Correct answer: B. Attributing impact responsibly requires linking specific changes to specific ticket categories and controlling for confounds, not timing alone.
A major release is coming with breaking changes, and multiple teams disagree on what users need to be told. How do you lead the docs effort?
- A. Wait for the teams to align before doing anything
- B. Drive a migration-focused narrative centered on what users must do, and use it to force the teams to converge ✓
- C. Document every team's view separately
- D. Publish only after everything is perfectly settled, even if that's post-launch
Correct answer: B. For breaking changes, leading with the user's required actions both serves readers and becomes the forcing function to align teams.
You realize a whole category of docs no one reads is consuming maintenance effort. What's the best move?
- A. Keep maintaining it in case someone needs it someday
- B. Analyze usage and either deprecate/archive it or investigate why it's unused, freeing effort for high-value work ✓
- C. Delete it immediately without checking
- D. Leave it unmaintained but published
Correct answer: B. Retiring or fixing unread content based on usage data reclaims capacity, whereas hoarding or blind deletion both carry avoidable cost.
A director wants a flashy new docs redesign; your data says the real problem is content accuracy, not design. How do you respond?
- A. Do the redesign since the director requested it
- B. Present the evidence that accuracy is the bottleneck and propose fixing that first, offering design as a later phase ✓
- C. Do the redesign but secretly fix accuracy too
- D. Refuse the redesign and only fix accuracy
Correct answer: B. Redirecting a HiPPO toward the evidence-backed real problem, while acknowledging their goal, serves users without a needless standoff.
You're building a content model to scale docs across many products. What principle should guide it most?
- A. Let each product team invent its own structure freely
- B. Define reusable, task-based content types and standards that stay consistent while allowing product-specific detail ✓
- C. Force every product into one rigid identical template
- D. Prioritize whatever structure is easiest to build first
Correct answer: B. Scalable content models balance shared, task-based standards for consistency with enough flexibility for genuine product differences.
Your best writer is producing accurate docs that quietly ignore the style guide and confuse the broader set. How do you address it?
- A. Ignore it because their accuracy is excellent
- B. Discuss the reader-consistency cost of going off-standard and align on why the shared standard exists ✓
- C. Publicly correct their work as an example
- D. Rewrite their docs yourself after they submit them
Correct answer: B. Even strong individual work must serve the whole system's consistency, and the fix is a direct conversation about the reader-level cost.
You want docs to become a strategic asset, not just a cost center. What's the strongest positioning?
- A. Emphasize how many pages the team produces
- B. Tie docs to measurable outcomes like activation, retention, deflected support, and sales enablement ✓
- C. Argue that docs are simply the right thing to do
- D. Benchmark purely against competitor doc volume
Correct answer: B. Positioning docs against business outcomes stakeholders care about is what elevates them from cost center to strategic asset.
A cross-functional debate erupts over whether to document an internal workaround for a known bug. What's the wisest approach?
- A. Never document workarounds; they make the product look bad
- B. Weigh user harm from silence against risk, and if it helps users, document it clearly with context and a path to the real fix ✓
- C. Document the workaround with no mention of the bug
- D. Wait until engineering fixes the bug, however long that takes
Correct answer: B. When a workaround genuinely reduces user harm, transparent documentation with context serves readers better than protecting appearances or waiting indefinitely.
You must choose where to invest to raise overall documentation quality across a large org. What gives the best leverage?
- A. Personally editing as many individual pages as possible
- B. Investing in systems — standards, templates, review processes, and enablement — that raise everyone's output ✓
- C. Hiring more writers to cover more surface area
- D. Mandating a single tool everyone must use
Correct answer: B. At org scale, leverage comes from systems and enablement that lift every contributor, not from a senior writer's individual page-by-page effort.