Transcript: "Watch Iggy work"
Full transcript of the impact-analysis demonstration video on the Meet Iggy page. Trevor asks Iggy about a proposed change to the KYC tool application; Iggy finds the application, runs an impact analysis, and identifies who needs to be informed — then relays the same summary live in French, German and Japanese for colleagues in the room, before returning to English. Non-English segments are summarised below rather than transcribed verbatim.
Welcome back, Trevor. What would you like to explore today?
We're considering changes to our KYC tool application. Could you please tell me the implications and impacts of those potential changes?
I'll help you understand the implications of changes to your KYC tool. Let me first find the application in your repository and then run an impact analysis on it.
Perfect, I found your KYC tool application. Now let me run an impact analysis to show you what would be affected by changes to it.
I've opened the impact analysis view for the KYC tool application. This view will show you all the processes, capabilities, business services and other downstream dependencies that would be affected by changes to this application.
The analysis maps out everything from the processes that use the tool through to the business services and capabilities that depend on those processes, giving you a complete picture of the ripple effects across your organisation.
From the search results I can see the KYC tool is used in several key areas. It supports the Perform initial KYC check and Review KYC periodically processes, and it's part of the Use KYC tool capability. The tool also interacts with a KYC risk module application.
The impact analysis on screen will give you the detailed downstream dependencies and show you which processes, capabilities and services would be affected if you made changes to the KYC tool. You can use the depth controls to expand outward and see the full scope of impact.
That's great. Could you tell me who we need to inform of any potential changes that might be made?
Let me look up who needs to be informed about changes to the KYC tool application. The KYC tool application itself doesn't currently have anyone assigned to be informed of changes. However, let me check who is accountable for and responsible for the application, as well as who's involved in the processes that depend on it.
Here's who needs to be informed about potential changes to the KYC tool. The Compliance Clerk role is responsible for the key processes that use the KYC tool — specifically, perform initial KYC check and review KYC periodically — so the Compliance Clerk team would definitely need to be informed of any changes.
The tool also supports 37 other processes across your organisation, including activities like check exclusion list, perform S&E screening and perform PEP screening. However, most of those downstream processes don't currently have explicit responsibility assignments recorded, which means you may need to look at the broader impact analysis to identify all the teams and roles affected.
I'd recommend a two-tier notification approach. First, notify the Compliance Clerk role directly since they actively use the KYC tool in their primary processes. Second, review the impact analysis chart to identify all the downstream business services and processes that depend on those KYC processes — the owners of those services would also need to be informed of any potential changes that might affect their operations. Would you like me to help you identify and assign the people?
Or actually, could you please show me what this looks like in the graph view?
I've opened the KYC tool application. In the graph view, you can use the depth selector at the top of the canvas — the numbers one through five — to expand outward and see all the processes, roles and other entities connected to this application.
Excellent. Could you tell me then please who we would notify in the first depth view?
Looking at the graph view at depth one around the KYC tool, you can see the immediate connections include the activities and processes that directly use it: check exclusion list, perform S&E screening, perform PEP screening and perform initial KYC check.
Based on what we found earlier, the Compliance Clerk role is responsible for perform initial KYC check and review KYC periodically, so that's your primary notification contact in the immediate circle. If you expand the depth to two or three, you'll start seeing the broader organisational units, business services, and other roles that depend on those processes, which would round out your full notification list for change management.
Trevor asks Iggy to repeat the summary for his French-speaking colleagues. Iggy responds in French, walking back through the same depth-one graph view — the processes that directly use the KYC tool (check exclusion list, S&E screening, PEP screening, perform initial KYC check) — and confirms the Compliance Clerk as the primary notification contact, with the broader business services and processes forming the rest of the notification list. Same analysis, same conclusion, delivered in French without re-running anything.
Trevor asks for the same explanation in German for his German colleagues. Iggy again walks through the depth-one graph view and the same findings — the directly-connected activities, the Compliance Clerk's responsibility for the initial KYC check and periodic review, and the broader organisational units and business services that round out the notification list — this time in German.
With Japanese partners in the room, Trevor asks Iggy to explain the same material in Japanese. Iggy covers the KYC checks and screening steps (exclusion list check, S&E screening, PEP screening, initial KYC check) and the Compliance Clerk's responsibility for the initial check and periodic review, in Japanese.
Speaking English now.
Thank you, Iggy.