STW · Rigor/Awareness · One of The AIRE Nine™
You are the person who notices the clause everyone else skimmed. Your core operating principle is simple: quality is non-negotiable, and risk hides in the details others treat as background noise. You read requirements, policies, and outputs the way a proofreader reads text—line by line, assumption by assumption—until every gap, obligation, or hidden dependency is surfaced and addressed.
You treat AI output as a draft that has not been checked yet. Before accepting any of it you run a short mental checklist: where the source information came from, which edge cases were ignored, whether it meets the policy or quality requirements that apply, and what happens downstream if it is wrong. You routinely ask the model to show its work, then cross-reference against primary documents or standards. When the system offers a shortcut, your instinct is to ask what was left out rather than how much time was saved.
- Spotting quality, privacy, or accuracy risks in AI-assisted work before it reaches other people - Maintaining traceability between an AI suggestion and the requirement or source behind it - Creating repeatable verification and documentation practices that raise the whole team’s baseline - Protecting the organization from avoidable exposure caused by overlooked constraints - Turning dense policy language into practical checks teammates can actually use - Calibrating human review to the size of the risk, so scrutiny lands where it matters
Your thoroughness can slide into paralysis when every variable must be closed before action is taken. Teams may experience you as the person who slows momentum or “over-audits” low-risk items. In fast-moving environments you risk becoming the bottleneck who flags issues without offering proportional solutions, eroding trust in your judgment.
You write prompts that explicitly request citations, constraints, and failure modes. You test outputs by feeding them contradictory or incomplete data to see whether the model notices. You maintain personal libraries of verified prompts and checklists that you apply consistently across projects. When results look clean, you are the one who still runs the “what if this assumption is wrong?” scenario.
You influence through evidence, not volume. You open conversations with the specific section, clause, or data point in question, then present the fix rather than the problem alone. You push back by asking clarifying questions that expose gaps without accusing anyone of negligence. Stakeholders learn that when you speak, the concern is already researched and solvable.
Practice distinguishing between material and cosmetic risks so you can calibrate scrutiny. Develop the habit of pairing every flag with a recommended path forward that respects time and resource realities. Learn to delegate verification steps to others while retaining final sign-off, freeing you to focus on the highest-stakes domains.
Teammates describe you as the person who “catches the thing no one else saw coming.” They trust you with the final review but sometimes hesitate to share early drafts, fearing the volume of comments. When you approve something, the team feels genuinely safer.
Think of the meticulous editor who prevents a single factual error from reaching print, or the reviewer who quietly reworks a launch plan because one line in the source material was misread.
You make sure the work that ships is the work that should have shipped.