A Disagreement on Principles, Not on Skills  🔗 **Source:** [A Disagreement on Principles, Not on Skills](https://www.youtube.com/watch?v=aogfHvcVGTE) > [!note]+ Document Notes > --- > tags: [ai-adoption, organizational-change, workforce-management, mandates, dissent, trail-of-bits] > author: unattributed clip (Trail of Bits — speaker presents as company leadership) > source: YouTube short-form clip > reference: https://www.youtube.com/watch?v=aogfHvcVGTE > date created: 2026-07-31 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > [!note] Clip context > > One of at least six short clips from the same Trail of Bits talk on AI adoption inside a security > > firm. Siblings in this batch: *Give Your Agents a Performance Review*, *A 7-day Cooldown on Every > > Dependency*, *The CEO Goes First*, *All of It's Becoming Due at the Same Time*, *The Machine > > Doesn't Cook for You*. This is the clip where the adoption programme's enforcement is described. > # 🏷️ Title > A Disagreement on Principles, Not on Skills — Trail of Bits clip on AI-adoption non-engagement > # 🧭 Table of Contents > 1. Summary > 2. Main Content / Notes > 3. References > 4. Paraphrase > 5. Newsletter > 6. Action Items > 7. Hypotheses > 8. Methodology > 9. Questions > 10. Future Research > 11. Implications > 12. Learning Styles Assessment > 13. Accessibility Assessment > 14. DEIB Assessment > 15. Logical Validity > 16. DARVO Analysis > 17. Conclusion > 18. Refactor Appendix > 19. Template Library > # 🔗 References > - An internal **four-or-five-level adoption maturity scale** (levels 0–3 referenced; the scale itself is defined in the parent talk, not this clip) > - The company's **HR team**, named as a participant in the process > - No external framework, study, or policy document is cited > # 📝 Summary > **What happened.** A ~60-second passage describing how the company handled employees who did not adopt AI tooling. Levels 1–3 are treated as a skill gap needing time. **Level 0 — "not engaged" — is reclassified as a values disagreement**, escalated with HR, and some of those people left the company. > **Why it matters.** This is the enforcement mechanism behind the adoption programme the other five clips describe, and it is stated plainly rather than euphemised. It is also the clip that makes the set's other content read differently — "give your agents a performance review" lands differently once you know the humans were getting one too. > **Stakeholders.** Employees at organizations mandating AI adoption; managers designing such programmes; anyone weighing a company's stated position on AI dissent. > **Risks.** The reclassification is doing enormous work. It converts *a technical judgement about tool suitability* into *a loyalty question*, which removes the possibility of principled, informed disagreement. Notably, the two examples given of level-0 behaviour are not refusal to try — they are holding a *position* ("dismisses AI as hype," "refuses to use AI for security work"). > **Bottom line.** An unusually candid account of how an AI mandate was enforced, valuable precisely because it does not soften what happened — and worth reading critically rather than as a template. > # 📖 Main Content > ## 🗒️ Notes > **[00:00:00] The skill/principle split.** The clip's entire structure rests on one classification: > > [!quote] > > Levels 1, 2, and 3 are a skill issue. Just means you haven't spent enough time with the tool to get good at it. > Those people get patience — "you need more time to experiment," "more time to play." No consequence attaches. > **Level 0 is treated categorically differently.** Not as less skill, but as opposition: > > [!quote] > > If you're in level zero though, if you're not engaged, that means you're fighting back against the company. It means that uh, you are you have not adopted the vision and the direction that the company is now going in. > **The two named examples deserve close attention**, because they define what "not engaged" means in practice: > > [!quote] > > if you dismiss AI as hype, if you refuse to use AI for security work. This is a disagreement on principles, not on skills. > The first is an *opinion about the technology's value*. The second is a *professional judgement about its suitability for a specific domain* — and that domain is the company's actual business. Neither is described as refusing to attempt the tools. Both are positions a competent security engineer might hold on evidence, and the framework classifies holding them as opposition to the company. > **[00:00:31] The consequence.** > > [!quote] > > So, for people that were stuck in the not engaged category, we had hard conversations with our HR team, and uh, there were people that left the company uh, because they were um, stuck at that stage. > The verbal hesitancy here ("uh," "um") is the most pronounced in the clip, and sits exactly on the sentence describing departures. Whether that signals discomfort or ordinary disfluency is not determinable from a transcript, and shouldn't be over-read — but it is where the fluency breaks. > Note also the passive construction: people "left the company" because they "were stuck at that stage." Agency is attributed to the employee's position rather than to the decision made about them. > **The contrast is the point.** Skill gaps get time and encouragement. Principled disagreement gets HR. That asymmetry is the policy. > # 📚 References > Primary sources preferred: the full parent talk (which defines the maturity scale this clip references but does not explain); Trail of Bits' public writing on their AI adoption programme; research on technology-mandate outcomes and voluntary turnover; and the substantial literature on dissent as a signal in engineering organizations — none of which the clip engages. > # 🗣️ Paraphrase > The company sorted employees by how far they had got with AI tooling. > Most stages were treated as a matter of practice. If you had used the tools a little and were not yet good with them, you needed more hours, and that was fine. > The bottom stage was treated as something else entirely. Someone who was not engaging at all was understood to be resisting the company's direction rather than lacking practice. > Two behaviours were given as examples: saying AI is hype, and declining to use it for security work. > Those cases went to HR as difficult conversations, and some of the people involved ended up leaving. > The distinction the speaker draws is between not being able to and not agreeing to — and only the second had consequences. > # 📰 Newsletter > **When "not engaged" gets reclassified as disloyalty** > Here is the clearest description I have seen of how an AI mandate actually gets enforced, from a security company's leadership, stated without euphemism. > They graded staff on AI adoption. Levels 1 through 3 — *a skill issue. Just means you haven't spent enough time with the tool.* Those people got time and encouragement. Fine, and genuinely humane. > Level 0, "not engaged," got a different category: *that means you're fighting back against the company… you have not adopted the vision and the direction the company is now going in.* Hard conversations with HR followed, and some of those people left. > The part worth sitting with is what counted as level 0. Two examples are given: **dismissing AI as hype**, and **refusing to use AI for security work**. > Neither is "wouldn't try the tool." Both are *positions*. And the second is a professional judgement about tool suitability in the domain the company actually sells into — precisely the kind of call you hire senior security engineers to make. The framework converts that judgement into a values problem. > That's the move to watch for, and it isn't unique to AI: **a technical disagreement reclassified as a loyalty question stops being answerable with evidence.** Once "I don't think this is reliable enough for security work" is heard as "you're fighting the company," there is no finding that could settle it. The engineer who was right for good reasons and the engineer who was merely obstinate are now in the same bucket. > Worth noting the flip side honestly: an organization genuinely does need to be able to change direction, and a person who wil Levels 1, 2, and 3 are a skill issue. Just means you haven't spent enough time with the tool to get good at it. You know, if you're capable, means that you just had a few hours of experience. Um, and you need more time to experiment to get to level two. If you're in level zero though, if you're not engaged, that means you're fighting back against the company. It means that uh, you are you have not adopted the vision and the direction that the company is now going in. Uh, if you dismiss AI as hype, if you refuse to use AI for security work. This is a disagreement on principles, not on skills. So, for people that were stuck in the not engaged category, we had hard conversations with our HR team, and uh, there were people that left the company uh, because they were um, stuck at that stage. Uh, but for anybody that's at level 1, 2, or 3, we just treat this as like, "Okay, you know, you need more time to play.", A Disagreement on Principles, Not on Skills, YouTube, 01kywpajsmrdsa6m0qmda653p0.