Personal operating-system review

The diagnostic goal

Use the personal operating-system review to locate the specific conditions behind this question: Do a leader's routines, information flows, decisions, and relationships support effective work? The working view makes priorities, calendar, and information visible so discussion can move from general opinion to a specific action or decision.

When to run it

Run the personal operating-system review before a consequential review or change in personal leadership, when symptoms are visible but the underlying condition is still unclear. Repeat it when the evidence for priorities, calendar, and information changes, rather than on a calendar alone.

What it tests

The personal operating-system review is an evidence-based review that keeps healthy, watch, gap, and unknown states visibly distinct. Its core working elements are priorities, calendar, information, and decisions. Those elements belong together because each changes how the others should be interpreted or acted on.

Diagnostic dimensions

Priorities

Capture priorities only at the level needed to answer: Do a leader's routines, information flows, decisions, and relationships support effective work? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the personal operating-system review, connect this entry to calendar so the relationship can be reviewed rather than inferred.

Calendar

Capture calendar only at the level needed to answer: Do a leader's routines, information flows, decisions, and relationships support effective work? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the personal operating-system review, connect this entry to information so the relationship can be reviewed rather than inferred.

Information

Capture information only at the level needed to answer: Do a leader's routines, information flows, decisions, and relationships support effective work? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the personal operating-system review, connect this entry to decisions so the relationship can be reviewed rather than inferred.

Decisions

Name the decision, the person or body with final authority, the date, and the rationale that should remain visible later. Within the personal operating-system review, connect this entry to meetings so the relationship can be reviewed rather than inferred.

Meetings

Define the intended output, required preparation, decision roles, time allocation, and record created at close. Within the personal operating-system review, connect this entry to relationships so the relationship can be reviewed rather than inferred.

Relationships

Describe what each side provides, when it is needed, how readiness is confirmed, and where unresolved issues escalate. Within the personal operating-system review, connect this entry to recovery so the relationship can be reviewed rather than inferred.

Recovery

Capture recovery only at the level needed to answer: Do a leader's routines, information flows, decisions, and relationships support effective work? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the personal operating-system review, connect this entry to experiments so the relationship can be reviewed rather than inferred.

Experiments

Capture experiments only at the level needed to answer: Do a leader's routines, information flows, decisions, and relationships support effective work? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the personal operating-system review, connect this entry to recovery so the relationship can be reviewed rather than inferred.