Overt integrity tests: origins, purpose, and a narrower proposal

Research context

Official OPM guidance distinguishes overt, clear-purpose integrity questions from less explicit personality-based approaches. The integrity-test literature includes employment prediction research, but findings about existing instruments do not validate a new questionnaire. MIO deliberately avoids questions about criminal records, drug use, and private misconduct histories.

Machiavelli development analysis

An assessment called integrity creates a serious interpretive burden. Readers may hear an assurance about honesty, while the questions actually ask whether someone remembers explaining a delay or checking permission. The proposed MIO begins with that gap. It treats integrity orientation as a set of ordinary practices that a person can describe, examine, and improve. The name does not authorize a verdict on someone’s character. An attractive report would be misleading if it quietly converted a limited self-description into a promise that its owner can be trusted in every circumstance.

The historical distinction between direct-purpose and indirect-purpose testing is useful for designing a transparent participant experience. A person should understand why a question about correcting a mistaken impression appears in the questionnaire. There is no hidden interpretation that turns an answer about equipment into an allegation about theft. The proposed introduction would explain the six domains, the recent-work reference period, and the intended audience before asking for consent. Participants would be invited to consider routine professional, volunteer, or project settings rather than disclose intimate events.

Consider two people who both endorse making commitments carefully. One works with stable deadlines and has authority to renegotiate. The other receives changing instructions and cannot easily refuse extra work. Their answers may look similar, yet the conditions supporting those answers differ substantially. MIO therefore treats the report as a prompt for a contextual example. A useful reflection asks what was promised, which dependency changed, who was informed, and what happened next. It does not infer a hidden moral essence from agreement with an appealing sentence.

The original design also separates a habit from its possible benefits. Clear disclosure might make collaboration easier, but that possibility is a rationale for research, not an established product outcome. The development version should never say that its scores predict theft, prevent fraud, or certify trustworthy employees. A safer report describes what the participant endorsed and suggests an optional experiment, such as naming uncertainty in one weekly update. Whether the experiment improves understanding must be checked in the setting where it is used.

This scope makes several exclusions necessary to the scientific definition itself. There is no criminal-history scale, no lie-detector function, no employability label, and no pass mark. Questions about resource stewardship concern permissions and care, while questions about concern raising acknowledge that a safe route may be unavailable. Users should be able to pause rather than invent a confident answer. The first release is consequently a documented proposal for adult reflection, with research tasks remaining before anyone could support broader claims about measurement or practical value.