
Sign up to save your podcasts
Or


Your platform is live, workflows are active, and training completion rates look great on paper. So why is the compliance team still the only group logging in six months later?
In this episode of Let's Talk IRM, Jada Porter and Meesh dig into the difference between deployment (getting the system running) and adoption (getting people to understand why their input matters). If your control owners finish attestations in under two minutes just to check a box, look at how the program was designed for change before you schedule more training.
We talk through moving away from one-size-fits-all training toward targeted adoption paths for each type of user.
In this episode:
• Deployment vs. adoption: why high training metrics can hide low platform engagement.
• Three platform signals of an adoption gap: completion times under two minutes, little status variance, and few or no issue records (or issues that close almost as soon as they open).
• Designing for three user personas: what control owners, risk owners and executive reviewers need to see and understand.
• A lean program: getting 50 non-technical control owners working in the platform with no training budget.
• Reframing the "no": why a failed attestation is useful data, and how issue workflows close the loop.
• One action for this week: the question to ask your fastest control owner.
Timestamps:
00:00 The core problem: deployment vs. adoption
00:40 Introduction to Let's Talk IRM
00:56 Why 100% training completion can still mean low adoption
01:41 Reading the gap in platform data
02:05 Signal 1: attestation completion times (the two-minute problem)
03:15 Signal 2: little status and implementation variance
04:12 Signal 3: issue logging cadence and handling
06:12 Community Q&A: 94% training completion, but still the only user
06:54 Diagnosing the hand-off: presentation slides vs. real understanding
09:02 Starting with the direct conversation: "What does this task mean?"
10:33 The design gap: who are we training?
11:27 Persona 1: the control owner (finding tasks, evaluation and downstream impact)
12:56 Persona 2: the risk owner (accept vs. mitigate context)
14:26 Persona 3: the executive reviewer (15-minute decision dashboards)
16:14 Community Q&A: getting 50 non-GRC users functional with no budget
16:43 Persona-based documentation: the why before the how
19:53 Why comprehensive training drives user avoidance
20:28 Empathizing with the move from spreadsheets to ServiceNow
22:04 Session 1 focus: navigating workspaces and finding tasks
23:36 Session 2 focus: real evaluation vs. form-filling
24:45 Session 3 focus: downstream impacts and data feedback loops
25:58 Community Q&A: what changes behavior when emails and helper text fail?
26:43 Removing the stigma: a failed attestation gives you data
29:55 Using ServiceNow issue workflows to close the loop
30:46 Final takeaway: one question to ask your fastest control owner
31:56 Wrap-up, SaaSCE Boutique resources and outro
Resources:
Join the waitlist for IRM for GRC Practitioners: https://www.thesaasceboutique.com/course#waitlist
Get IRM study notes with every new episode: https://www.thesaasceboutique.com/newsletter
Connect with Jada on LinkedIn: https://www.linkedin.com/in/jadaporter
Connect with Meesh on LinkedIn: https://www.linkedin.com/in/meesh-miller/
Subscribe to Let's Talk IRM wherever you listen: https://letstalkirm.transistor.fm/subscribe
#ServiceNowCommunity #IntegratedRiskManagement #GRC #ChangeManagement #RiskManagement #Compliance #LetsTalkIRM
Picture the moment right after go-live. The implementation partner has signed off. The platform is live. The dashboards are populating. And somewhere in that room, the executive sponsor is mentally filing this under done and moving on to the next initiative. That is what this episode is about.
A successful implementation and a working program are two different outcomes. In Episode 9 of Let's Talk IRM, Jada Porter and moderator Meesh work through four community questions from practitioners navigating the post-go-live gap in real time.
In this episode:
Community Questions Answered in This Episode:
Timestamp | Chapter Title
0:00 | Hook — Picture the Moment Right After Go-Live
0:57 | Segment 1: Implementation Success Is Not Program Success
1:30 | How to Tell Whether Stakeholders Are Genuinely Engaged vs Completing Tasks
3:18 | What Engaged Looks Like in Day-to-Day Platform Behavior
4:10 | Community Question 1: Six Months Post Go-Live and Nothing Feels Like It’s Working
5:40 | The Culture Gap Behind Check-the-Box Attestation Behavior
7:08 | Segment 2: What Executive Disengagement Actually Costs the Program
7:40 | Whose Responsibility Is It to Build the Governance Model?
8:30 | Why GRC Is Not Just a Cybersecurity Problem
9:50 | Can the Implementation Partner Own It, or Must It Be Internal?
10:30 | IRM as a Cultural Change, Not a Tool Purchase
12:00 | Community Question 2: Executive Sponsor Has Checked Out — How Do I Re-Engage?
13:00 | Setting Governance Expectations Before Go-Live
15:10 | What Happens When You Cannot Get the Sponsor Re-Engaged
15:58 | Segment 3: The Governance Design Nobody Delivers
16:40 | The Four Elements: Risk Appetite, Escalation Model, Executive Cadence, Named Owner
17:38 | Risk Appetite Decision Model — Named Authorities at Every Threshold
18:40 | Escalation Model — Named Humans with Defined Response Times
19:30 | Executive Review Cadence — Decisions Not Dashboards
20:00 | Named Governance Owner Post-Implementation — Why This Is the Heaviest Element
21:05 | Community Question 3: Will Dynamic User Assignment Solve the Ownership Problem?
22:05 | What the Platform Can and Cannot Do Without a Governance Foundation
23:00 | Community Question 4: How Do You Prevent Decentralized Ownership from Becoming Chaotic?
24:47 | The Governance Model as the Firewall Against IRM Fragmentation
26:15 | Segment 4: What Genuine Executive Engagement Actually Looks Like
27:00 | The Behavioral Signal — Pointed Questions vs Baseline Questions
28:30 | How to Tell Whether Someone Has Actually Been Working in the System
29:30 | Community Question 5: If the Platform Assigns the Right Person, How Do You Know the Roles Were Defined Correctly?
30:20 | CMDB Alignment as the Telltale Sign of Role Definition Health
31:57 | Closing Question: The One Thing to Add to Every Governance Design Before Departure
34:24 | End
Connect + Resources:
Website: thesaasceboutique.com
Article 9 (companion reading): Re-Engineering the Post-Go-Live Slump: Moving IRM from Live to Governed — thesaasceboutique.com/blog
Connect with Jada on LinkedIn: linkedin.com/in/jadaporter
Connect with Meesh on LinkedIn: linkedin.com/in/michelle-m-65a4b9a7
Subscribe so you don’t miss Episode 10.
#ServiceNow #IRM #GRC #ServiceNowIRM #LetsTalkIRM #IRMPractitioner #Governance #RiskManagement #ServiceNowGRC #GRCPodcast #PostGoLive #IRM Planning #ExecutiveEngagement #TheSaaSCEBoutique #RiskOwnership #GRCImplementation #ServiceNowCommunity #ContinuousMonitoring #IRMGovernance #GRCGovernance
In Episode 8 of Let's Talk IRM, Jada Porter and moderator Meesh work through five real questions from IRM practitioners navigating risk ownership gaps in their ServiceNow programs. Jada covers the earliest platform signals that ownership was configured before the organizational conversation happened, why defaulting to the CISO as the enterprise risk owner is a governance vulnerability, how scenario-based questions surface the actual risk owner faster than abstract definitions, and what it costs a program long-term when the implementation team fills the ownership vacuum to meet a deadline. The episode closes with a framework-to-controls walkthrough using an access control example and one concrete action every practitioner can take this week.
Who Actually Owns Risk in Your IRM Program?
The risk register shows owners. The owner field has a name in it. And that person has never once made a deliberate decision about the risk they are listed as owning.
That is not a platform problem. The platform did exactly what it was configured to do. It is a governance design problem.
In Episode 8 of Let's Talk IRM, Jada Porter sits down with moderator Meesh to unpack the most common post-go-live failure in ServiceNow IRM programs: risk ownership that exists on paper and nowhere else. Together they work through five community questions from practitioners who are navigating this problem in real time.
In this episode:
Community Questions Answered in This Episode:
Connect + Resources:
Website: thesaasceboutique.com
Article 6 (companion reading): Why Executive Engagement Is the Variable Nobody Plans For — thesaasceboutique.com/blog
Connect with Jada: linkedin.com/in/jadaporter
Connect with Meesh: linkedin.com/in/michelle-m-65a4b9a7
Subscribe so you don't miss Episode 9.
#ServiceNow #IRM #GRC #RiskOwnership #LetsTalkIRM #IRMPractitioner #ServiceNowIRM #Governance #GRCPodcast #TheSaaSCEBoutique
This episode explores how to differentiate between genuine system gaps and knowledge gaps that lead to unnecessary customizations. The discussion emphasizes the importance of understanding customer needs, the risks of customizing baselines, and strategic approaches to IRM implementation within ServiceNow.
Main Topics Covered:
In this episode:
This episode explores the critical aspects of planning and stakeholder alignment in ServiceNow IRM implementations. Featuring expert insights, it emphasizes the importance of strategic preparation, ownership, and organizational discipline for successful risk management.
Key Topics
Chapters
00:00 Introduction to IRM Planning and Goals
02:06 Why Planning Often Traces Back to Resources and Stakeholders
04:07 Technical vs. Project Management Planning in IRM
06:09 Aligning Business Processes with IRM Capabilities
07:56 The Importance of Clear Ownership and Stakeholder Communication
09:46 Building a Realistic and Phased IRM Implementation Roadmap
12:08 Assessing and Improving Your CMDB for IRM Success
14:05 Evolving Documentation and Regulatory Changes
16:04 Minimum Viable CMDB Thresholds for IRM
17:50 Trust and Gaps in the CMDB and Their Impact
19:57 Granularity in IRM: Going Beyond the Basics
21:50 Stakeholder Ownership and User Adoption Challenges
24:01 Effective Communication and Ownership in IRM Projects
25:58 ServiceNow vs. Practitioner Responsibilities in Readiness
27:58 The Role of Readiness Checklists and Organizational Strategy
29:51 Key Takeaways for Successful IRM Implementation
32:13 Final Tips for Planning and Execution in IRM
34:00 Using Now Create as a Starting Point
34:58 Next Steps: Managing Scope and Roadblocks
36:11 Closing Remarks and Resources for IRM Enthusiasts
Are you struggling with user adoption and process alignment during your IRM implementations? In this episode of Let's Talk IRM, certified IRM practitioners Elay and Jada dive into the core differences between transforming existing processes and merely transferring them into new tools, particularly within ServiceNow IRM.
Key topics covered:
Timestamps: 00:00 - Introduction: Why many IRM projects fail despite investing heavily
00:28 - The critical question: Are we transforming or just transferring processes?
1:26 - Elay's expertise: Insights from numerous IRM implementations
2:25 - Why spreadsheets often outperform complex GRC platforms
3:20 - Signs early in a project that indicate a need for transformation
4:03 - How to identify a team's readiness to change during initial sessions
5:26 - Understanding the "crawl walk run" approach for IRM adoption
6:41 - Managing client expectations when demo-proof features don’t match real needs
7:37 - The impact of client resistance and how to handle it effectively
9:36 - When to automate and transform versus work with existing dashboards
10:41 - Navigating client resistance when they want to recreate their old workflows
11:36 - The importance of configuring at the right level: front-end vs. data model
13:58 - Accepting that sometimes you must lose battles for long-term wins
15:02 - When re-implementation is necessary: assessing the extent of the "lift and shift"
16:30 - Rebuilding vs. working around: making strategic decisions based on pain points
18:39 - Balancing user adoption with maintaining data integrity over the long term
20:11 - Protecting the process flow and data model during phased rollouts
22:08 - The importance of leadership support in successful IRM adoption
23:09 - Is lift and shift ever justified? Elay’s perspective on organizational readiness
24:26 - The role of executive buy-in in preventing half-baked IRM projects
25:31 - Practical considerations: matching implementation approach to organizational culture
26:44 - Closing remarks: The value of ongoing conversations around IRM best practices
The Critical Role of Business Understanding Before ServiceNow IRM Implementation
Are you about to implement ServiceNow's IRM application? This episode exposes common pitfalls organizations face when rushing into tool deployment without fully understanding their business processes. Learn from real-world stories why IRM success begins with business insights.
In this episode:
Why IRM begins before the tool is even purchased
The dangers of skipping business process analysis
Common implementation pitfalls based on field stories
How organizational complexity impacts IRM projects
Strategies for aligning IRM with actual business operations
The importance of stakeholder engagement and clear ownership
Risks of unnecessary customizations and performance issues
Key questions to ask before and during IRM implementation
Timestamps:
00:00 - Why organizations are unprepared for ServiceNow IRM success
00:50 - How to determine the ideal order for IRM product implementation
02:05 - The importance of understanding your business operations first
03:24 - Challenges with entity scoping without clear business context
04:11 - The risks of jumping into IRM without aligning to business needs
06:39 - Handling immature processes and manual workflows in IRM projects
08:43 - How language barriers and unexperienced teams impact implementation
11:21 - Why organizations fail despite large investments in IRM tools
12:37 - The pitfalls of customizing out-of-the-box modules
15:43 - Performance issues and cross-functional silos in IRM deployments
18:22 - Upgrade difficulties and the risk of over-customization
20:47 - The importance of clear ownership and stakeholder involvement
24:36 - Final takeaway: IRM starts with business, not technology
Have you been through an IRM implementation that went sideways — or one that went exactly right because your team did the business work first? Jada wants to hear from you. This podcast is built on real stories from real practitioners.
Send your story: Connect with Jada on LinkedIn (https://www.linkedin.com/in/jadaporter/) or send to [email protected]
Follow Let's Talk IRM for new episodes and IRM practitioner content.
Summary
In this episode, Jada Porter explains Integrated Risk Management (IRM), clarifying its meaning and importance in organizations. She discusses common misconceptions about IRM, emphasizing that it is not merely a tool or a checkbox exercise, but a comprehensive process that integrates various aspects of risk management. Jada outlines a four-part framework for successful IRM implementation, focusing on data, process, framework, and reporting integration, and encourages organizations to adopt a holistic approach to risk management.
Takeaways
The purpose of this episode is to explain what IRM is.
IRM stands for Integrated Risk Management.
IRM is not just a tool or a checkbox exercise.
Understanding IRM is crucial for successful implementation.
There are multiple meanings for IRM in different contexts.
A lack of understanding of IRM can lead to complications.
IRM involves integrating risk and compliance processes.
Successful IRM requires strong business and leadership input.
Four types of integration in IRM are essential for success.
Meeting users where they are is key to effective IRM.
Summary
In this episode, Jada introduces her podcast focused on integrated risk management, sharing her passion for the subject and her desire to bridge the gap between business needs and technology solutions. With over a decade of experience in IT and security, Jada aims to create a platform for real discussions about the human side of risk management, moving beyond technical how-tos to address the challenges practitioners face in aligning business goals with technology. She emphasizes the importance of understanding stakeholder dynamics and the mindset required for successful implementation of integrated risk management strategies.
Jada outlines her vision for the podcast, targeting GRC practitioners, technology teams, and anyone involved in risk management who may feel disconnected from the tools they are using. She expresses her hope that the conversations will resonate with listeners, providing insights and support for navigating the complexities of integrated risk management. By fostering an open dialogue, Jada aims to create a community where practitioners can share their experiences and learn from one another, ultimately enhancing their understanding and execution of risk management practices.
From the publisher's feed