To understand project ownership, ask what the candidate personally decided, delivered, and remained accountable for. A team outcome or a prominent project name does not by itself establish an individual's role.
Break a project into responsibilities
Start with a candidate's description, then trace one decision through the work. Ask who defined the scope, who completed the task, who approved it, and who handled a problem. Use the same core inquiry for candidates being assessed against the same requirement.
| Dimension | Useful follow-up |
|---|---|
| Contribution | Which deliverable did you produce yourself? |
| Decision authority | What could you change without approval? |
| Collaboration | Which parts belonged to other people? |
| Accountability | Who was responsible when the deadline moved? |
These questions form an original screening aid. They are not a validated assessment instrument or a scoring model.
Keep participation and leadership distinct
Fictional example: a candidate attended a software migration's steering meetings and prepared status reports. The initial note says “led enterprise migration.” A follow-up establishes that the program manager controlled budget and delivery, while the candidate owned reporting quality.
The revised evidence should credit that work accurately: “Owned weekly migration reporting and presented risks to the steering group.” If the open role requires program ownership, the record should show that broader responsibility was not established in this example.
Do not equate a title with authority. A lead may coach colleagues without managing them; a manager may coordinate work without owning the budget. The useful detail is the decision or responsibility the role requires.
Ask for an example that can be discussed
Candidates may be unable to share confidential project details. Invite a description of their actions and process without requesting proprietary material. If the available example cannot establish a requirement, mark that limitation and decide how an appropriate later assessment can address it.
Avoid filling the gap from a company description. Working at an organization known for a particular technology does not prove the candidate used it.
Write the evidence for the next reviewer
OPM describes structured interviews around job-related competencies and consistent questions. Use your agreed role criteria to decide which responsibilities matter, then attach the candidate's example to those criteria.
The screening template can hold the evidence; the client write-up should carry only the relevant, reviewed claims. Keep any unresolved ownership question visible rather than making the summary sound more senior than the evidence supports.