A tailored course, built for your situation
Influence in Technical Decision-Making with NIST AI RMF
Turn AI governance expertise into peer-level authority on system design and implementation choices
The situation this course is for
Strong engineers often see risks early but get overruled or ignored in design phases. Without structured influence, even the best insights stay reactive.
Who this is for
Senior data and AI engineers who are expected to contribute to governance but lack formal authority
Who this is not for
Entry-level practitioners, managers looking for team-wide compliance tools, or executives seeking board-level narratives
What you walk away with
- Lead design reviews with structured, framework-aligned reasoning
- Position yourself as the go-to person for NIST AI RMF interpretation
- Deflect misaligned implementations using pre-built response templates
- Build credibility across teams without formal authority
- Anticipate upstream decisions and insert input proactively
The 12 modules (with all 144 chapters)
- Defining influence in engineering contexts
- Examples from AI infrastructure teams
- The role of NIST AI RMF as a neutral standard
- How peers accept input from non-leaders
- Identifying high-leverage decision points
- Mapping influence pathways in your org
- Common mistakes that reduce credibility
- Building trust before you need it
- Using frameworks to depersonalize feedback
- Positioning input as enablers, not blockers
- The timing of early vs late input
- Creating visibility without overstepping
- Overview of NIST AI RMF core functions
- Mapping roles to engineering workflows
- Governance vs implementation responsibilities
- How mapping supports influence
- Using taxonomy to clarify scope
- Translating principles to code-level checks
- Integrating risk categories into design docs
- Linking decisions to accountability
- Documenting assumptions systematically
- Versioning control for framework use
- Cross-referencing with data lineage
- Maintaining alignment over time
- Reading project specs for triggers
- Flagging high-risk patterns early
- Pre-building common response templates
- Using NIST AI RMF to justify intervention
- Knowing when to escalate vs advise
- Aligning with data stewards preemptively
- Mapping data flows to risk domains
- Assessing model purpose and impact
- Identifying unsafe deployment paths
- Documenting assumptions for traceability
- Creating reusable risk assessments
- Scaling input across projects
- Starting with shared goals
- Using NIST AI RMF language objectively
- Avoiding blame in feedback
- Structuring comments around risk domains
- Referencing precedent from other teams
- Phrasing trade-offs neutrally
- Linking to compliance expectations
- Highlighting operational impact
- Offering alternatives, not just objections
- Using data to support claims
- Tying recommendations to uptime
- Balancing innovation and risk
- Capturing what works in governance
- Designing reusable checklists
- Template for risk assessment input
- Standard wording for common issues
- Versioning and change tracking
- Integrating with ticketing systems
- Sharing playbooks with peers
- Onboarding others to your approach
- Measuring influence over time
- Adapting to new frameworks
- Updating based on audit findings
- Scaling beyond individual projects
- Recognising valid counterpoints
- Differentiating ego from risk
- Asking clarifying questions
- Using NIST AI RMF as common ground
- Acknowledging constraints fairly
- Focusing on outcomes, not ownership
- Escalating disagreements constructively
- Documenting decisions and rationale
- Avoiding adversarial tone
- Staying collaborative under pressure
- Knowing when to stand firm
- Preserving relationships after debate
- Evaluating vendor AI claims
- Mapping features to risk domains
- Asking the right due diligence questions
- Using NIST AI RMF in RFPs
- Benchmarking against peer tools
- Identifying hidden limitations
- Documenting vendor risk profiles
- Aligning with security teams
- Negotiating controls pre-contract
- Building internal scorecards
- Tracking vendor compliance changes
- Planning for exit paths
- Identifying gaps in current policies
- Proposing updates based on incidents
- Using NIST AI RMF to justify changes
- Gathering peer input systematically
- Drafting policy language clearly
- Aligning with legal and compliance
- Testing policy feasibility
- Running small-scale pilots
- Measuring adoption and impact
- Revising based on feedback
- Documenting exceptions and waivers
- Archiving outdated versions
- Setting workshop goals
- Selecting participants strategically
- Preparing NIST AI RMF materials
- Facilitating without authority
- Managing dominant voices
- Capturing decisions visibly
- Linking outcomes to roadmap
- Following up on action items
- Measuring workshop effectiveness
- Repeating with new teams
- Scaling facilitation skills
- Creating workshop templates
- Tracking prevented incidents
- Quantifying time saved in rework
- Capturing peer testimonials
- Linking input to system stability
- Creating summary reports
- Sharing wins without self-promotion
- Aligning with performance goals
- Requesting feedback on input
- Building a portfolio of contributions
- Positioning for leadership roles
- Mentoring others in influence
- Extending reach across orgs
- Updating playbooks regularly
- Tracking framework changes
- Staying ahead of industry shifts
- Reconnecting with stakeholders
- Avoiding influence fatigue
- Rotating responsibilities fairly
- Onboarding successors
- Recognising diminishing returns
- Re-evaluating high-touch processes
- Automating routine input
- Focusing on next-level risks
- Scaling impact through systems
- Choosing a live project to apply to
- Running a pre-mortem using NIST AI RMF
- Drafting influence strategy
- Engaging stakeholders proactively
- Hosting a mock design review
- Incorporating feedback
- Finalising documentation
- Measuring outcome success
- Sharing lessons learned
- Updating personal playbook
- Planning for next cycle
- Celebrating peer recognition
How this maps to your situation
- Before a major AI system design review
- When reviewing vendor proposals for AI tools
- After a policy gap is exposed in production
- When building internal governance playbooks
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed for working professionals to complete at their own pace over 6-8 weeks.
How this compares to the alternatives
Unlike generic AI ethics courses, this program focuses specifically on how engineers can exert influence in real design decisions using the NIST AI RMF as a leverage tool, without needing managerial authority.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.