財務チームパフォーマンス指標
Executive Summary
| KPI | Health | Status |
|---|---|---|
| Recurring revenue variance ex-JV | Confidential |
|
| Expense variance excluding CR | Confidential |
|
| Billing variance | Confidential |
|
| Days to financial close | Confidential |
|
| \% of journal entries automated | Confidential |
|
| On-Boarding CSAT | Okay |
|
| Deliver Annualized Savings | Confidential |
|
| Accounting Efficiency (FY23 Plan) | Confidential |
|
| Data Monthly Active Users (FY23 Plan) | Okay |
|
Key Performance Indicators
Recurring revenue variance ex-JV
Variance Actual to Forecast of recurring revenue, excluding joint ventures. This metric falls under “Accurate and reliable financial forecast” umbrella.
Target: This KPI cannot be public Health:Confidential
- Confidential
Expense variance excluding CR
Variance Actual to Forecast of expense, excluding CR (CR = “Consolidated Results” includes financials from consolidated entities, including Ji Hu JV majority-owned subsidiary). This metric falls under “Accurate and reliable financial forecast” umbrella.
Target: This KPI cannot be public Health:Confidential
- Confidential
Billing variance
Variance Actual to Forecast of billing.
Target: This KPI cannot be public Health:Confidential
- Confidential
Days to financial close
Days taken to close financial books.
Target: This KPI cannot be public Health:Confidential
- Confidential
% of journal entries automated
Percentage of accounting journal entries that are automated.
Target: This KPI cannot be public Health:Confidential
- Confidential
On-Boarding CSAT
Customer Satisfaction for the onboarding process.
Target: Health:Okay
- Above target
Deliver Annualized Savings
Amount of annualized savings in $.
Target: This KPI cannot be public Health:Confidential
- Confidential
Accounting Efficiency (FY23 Plan)
Efficiency of accounting processes in %.
Target: This KPI cannot be public Health:Confidential
- Confidential
Data Monthly Active Users (FY23 Plan)
Number of monthly active users using Sisense and Snowflake.
Target: 1000 This KPI cannot be public Health:Okay
- Above target
Legends
Health
| Value | Level | Meaning |
|---|---|---|
| 3 | Okay | The KPI is at an acceptable level compared to the threshold |
| 2 | Attention | This is a blip, or we’re going to watch it, or we just need to enact a proven intervention |
| 1 | Problem | We'll prioritize our efforts here |
| -1 | Confidential | Metric & metric health are confidential |
| 0 | Unknown | Unknown |
How pages like this work
Data
The heart of pages like this are Performance Indicators data files which are YAML files. Each - denotes a dictionary of values for a new (K)PI. The current elements (or data properties) are:
| Property | Type | Description |
|---|---|---|
name | Required | String value of the name of the (K)PI. For Product PIs, product hierarchy should be separate from name by " - " (Ex. {Stage Name}:{Group Name} - {PI Type} - {PI Name} |
base_path | Required | Relative path to the performance indicator page that this (K)PI should live on |
definition | Required | refer to Parts of a KPI |
parent | Optional | should be used when a (K)PI is a subset of another PI. For example, we might care about Hiring vs Plan at the company level. The child would be the division and department levels, which would have the parent flag. |
target | Required | The target or cap for the (K)PI. Please use Unknown until we reach maturity level 2 if this is not yet defined. For GMAU, the target should be quarterly. |
org | Required | the organizational grouping (Ex: Engineering Function or Development Department). For Product Sections, ensure you have the word section (Ex : Dev Section) |
section | Optional | the product section (Ex: dev) as defined in sections.yml |
stage | Optional | the product stage (Ex: release) as defined in stages.yml |
group | Optional | the product group (Ex: progressive_delivery) as defined in stages.yml |
category | Optional | the product group (Ex: feature_flags) as defined in categories.yml |
is_key | Required | boolean value (true/false) that indicates if it is a (key) performance indicator |
health | Required | indicates the (K)PI health and reasons as nested attributes. This should be updated monthly before Key Reviews by the DRI. |
health.level | Optional | indicates a value between 0 and 3 (inclusive) to represent the health of the (K)PI. This should be updated monthly before Key Reviews by the DRI. |
health.reasons | Optional | indicates the reasons behind the health level. This should be updated monthly before Key Reviews by the DRI. Should be an array (indented lines starting with dashes) even if you only have one reason. |
urls | Optional | list of urls associated with the (K)PI. Should be an array (indented lines starting with dashes) even if you only have one url |
funnel | Optional | indicates there is a handbook link for a description of the funnel for this PI. Should be a URL |
public | Optional | boolean flag that can be set to false where a (K)PI does not meet the public guidelines. |
pi_type | Optional | indicates the Product PI type (Ex: AMAU, GMAU, SMAU, Group PPI) |
product_analytics_type | Optional | indicates if the metric is available on SaaS, SM (self-managed), or Both. |
is_primary | Optional | boolean flag that indicates if this is the Primary PI for the Product Group. |
implementation | Optional | indicates the implementation status and reasons as nested attributes. This should be updated monthly before Key Reviews by the DRI. |
implementation.status | Optional | indicates the Implementation Status status. This should be updated monthly before Key Reviews by the DRI. |
implementation.reasons | Optional | indicates the reasons behind the implementation status. This should be updated monthly before Key Reviews by the DRI. Should be an array (indented lines starting with dashes) even if you only have one reason. |
lessons | Optional | indicates lessons learned from a K(PI) as a nested attribute. This should be updated monthly before Key Reviews by the DRI. |
lessons.learned | Optional | learned is an attribute that can be nested under lessonsand indicates lessons learned from a K(PI). This should be updated monthly before Key Reviews by the DRI. Should be an array (indented lines starting with dashes) even if you only have one lesson learned |
monthly_focus | Optional | indicates monthly focus goals from a K(PI) as a nested attribute. This should be updated monthly before Key Reviews by the DRI. |
monthly_focus.goals | Optional | indicates monthly focus goals from a K(PI). This should be updated monthly before Key Reviews by the DRI. Should be an array (indented lines starting with dashes) even if you only have one goal |
metric_name | Optional | indicates the name of the metric in Self-Managed implemenation. The SaaS representation of the Self-Managed implementation should use the same name. |
