01 Are the steps, inputs, outputs, and exceptions for important workflows documented? Workflow clarity · Think about work that crosses people, teams, or systems.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
02 Does each important workflow have a clear owner and measurable outcome? Workflow clarity · An owner can resolve ambiguity and accept or reject changes.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
03 Can the systems involved in important workflows exchange information through supported connections? Systems connectivity · Include built-in integrations, supported interfaces, and managed file exchange.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
04 Is the authoritative system clear for each important business record? Systems connectivity · Examples include the trusted source for customer, order, employee, or financial records.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
05 Is the information used by important workflows accurate, complete, and timely enough for the decisions it supports? Data readiness · Consider missing values, duplicates, stale records, and reconciliation work.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
06 Are data definitions, owners, and handling expectations understood? Data readiness · People should know what a field means, who can change it, and how it should be protected.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
07 Are identities, roles, and access reviewed before systems can perform privileged work? Identity and security · Access should match job responsibility and be removable when responsibility changes.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
08 Can integrations use minimum-necessary, separately managed credentials? Identity and security · Avoid shared personal credentials and broad, permanent access.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
09 Are approval requirements based on the risk and reversibility of an action? Governance and approvals · Low-risk work and consequential decisions should not share one blanket rule.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
10 Can the business explain what happened, who authorized it, and whether the result was validated? Governance and approvals · Consider evidence, logs, independent checks, and recovery records.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
11 Do workflow changes have an accountable sponsor and participation from the people who do the work? Operational change readiness · A sponsor can clear obstacles; participants can expose the real operating constraints.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
12 Can the organization train, support, measure, and adjust a changed workflow? Operational change readiness · Include feedback, exception support, adoption measures, and rollback planning.
Established and consistently used Established with minor gaps Partly established Informal or inconsistent Not in place Unknown Not applicable
