key-risk-indicator
Key risk indicator (KRI) for risk management and business strategy
Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (8.9%) to scientific vocabulary
Repository
Key risk indicator (KRI) for risk management and business strategy
Basic Info
- Host: GitHub
- Owner: joelparkerhenderson
- Default Branch: main
- Size: 25.4 KB
Statistics
- Stars: 28
- Watchers: 2
- Forks: 6
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
Key Risk Indicator (KRI)

A key risk indicator (KRI) is a measure used in management to indicate how risky an activity is. This page is summary excerpts from Wikipedia / Key risk indicator.
Contents:
- What is a KRI?
- What are KRI examples?
- What is the best KRI?
- How can a KRI help?
- What makes a good KRI?
- How to handle KRI?
- Links
What is a KRI?
A key risk indicator (KRI) is a measure used in management to indicate how risky an activity is.
Key risk indicators are metrics used by organizations to provide an early signal of increasing risk exposures in various areas of the enterprise. It differs from a key performance indicator (KPI) in that the latter is meant as a measure of how well something is being done while the former is an indicator of the possibility of future adverse impact.
KRI give an early warning to identify potential event that may harm continuity of the activity/project.
KRIs are a mainstay of operational risk analysis.
What are KRI examples?
Key risk indicators for finance:
letters of intent (LOI) such as unbooked dollar value ($)
value at risk (VaR) such as investment dollar value ($)
Key risk indicators for marketing:
customer complaints (CC) such as incident count (#) for previous N days
net detractor score (NDS) such as measured per user cohort
Key risk indicators for operations:
unplanned unavailability (UU) such as incident count (#) for previous N days
mean time to recovery (MTTR) such as for the previous N incidents
Key risk indicators for queues, pipelines, funnels, processes, etc:
σ: dropout rate
ε: error ratio
What is the best KRI?
Organizations have different sizes and environment.
So every enterprise should choose its own KRI, taking into account the following steps:
Consider the different stakeholders of the organization
Make a balanced selection of risk indicators, covering performance indicators, lead indicators and trends
Ensure that the selected indicators drill down to the root cause of the events
Choose high relevant and high probability of predicting important risks: high business impact, easy to measure, high correlation with the risk, and sensitivity.
Determine thresholds and triggers for the set of KRI's
Locate and fold in data sources that contribute or feed data into KRI triggers
Determine notification methods, recipients, and action or response sequences
How can a KRI help?
The constant measure of KRI can bring the following benefits to the organization:
Provide an early warning: a proactive action can take place
Provide a backward looking view on risk events, so lesson can be learned by the past
Provide an indication that the risk appetite and tolerance are reached
Provide real time actionable intelligence to decision makers and risk managers
What makes a good KRI?
Qualities of good key risk indicators:
Ability to measure the right thing (e.g., supports the decisions that need to be made)
Quantifiable (e.g., damages in dollars of profit loss)
Capability to be measured precisely and accurately
Ability to be validated against ground truth, and confidence level one has in the assertions made within the framework of the metric
How to handle KRI?
Management selects a risk response strategy for specific risks identified and analyzed, which may include:
Avoidance: exiting the activities giving rise to risk
Reduction: taking action to reduce the likelihood or impact related to the risk
Alternative Actions: deciding and considering other feasible steps to minimize risks
Share or Insure: transferring or sharing a portion of the risk, to finance it
Accept: no action is taken, due to a cost/benefit decision
Monitoring is typically performed by management as part of its internal control activities, such as review of analytical reports or management committee meetings with relevant experts, to understand how the risk response strategy is working and whether the objectives are being achieved.
Links
Wikipedia:
Owner
- Name: Joel Parker Henderson
- Login: joelparkerhenderson
- Kind: user
- Location: California
- Website: http://www.joelparkerhenderson.com
- Repositories: 319
- Profile: https://github.com/joelparkerhenderson
Software developer. Technology consultant. Creator of GitAlias.com, NumCommand.com, SixArm.com, and many open source projects.
Citation (CITATION.cff)
cff-version: 1.2.0
title: Key Risk Indicator (KRI)
message: >-
If you use this work and you want to cite it,
then you can use the metadata from this file.
type: software
authors:
- given-names: Joel Parker
family-names: Henderson
email: joel@joelparkerhenderson.com
affiliation: joelparkerhenderson.com
orcid: 'https://orcid.org/0009-0000-4681-282X'
identifiers:
- type: url
value: 'https://github.com/joelparkerhenderson/key-risk-indicator/'
description: Key Risk Indicator (KRI)
repository-code: 'https://github.com/joelparkerhenderson/key-risk-indicator/'
abstract: >-
Key Risk Indicator (KRI)
license: See license file
GitHub Events
Total
- Watch event: 2
- Push event: 1
- Fork event: 1
Last Year
- Watch event: 2
- Push event: 1
- Fork event: 1
Committers
Last synced: 11 months ago
Top Committers
| Name | Commits | |
|---|---|---|
| Joel Parker Henderson | j****l@j****m | 13 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 11 months ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0