# The PVI Model
Executive summary
The PVI model, popularized by Harvey Coleman, distinguishes Performance—the quality and value of contribution; Visibility—whether relevant people can see and understand that contribution; and Image—the expectations and reputation created by repeated behavior and communication. The model is a career heuristic, not a validated formula or permission for impression manipulation. The PVI model is useful when Performance, Visibility, and Image are treated as an integrity chain: create valuable results, make evidence accessible to legitimate stakeholders, and build a reputation consistent with conduct; visibility cannot compensate for weak work, and invisible contribution should not remain structurally unrewarded. The managerial task is to turn the concept into an evidence system: clarify the decision, expose assumptions, observe outcomes, compare alternatives, and revise action when results disagree. This chapter treats the method as a disciplined operating capability rather than a workshop artifact. It integrates theory, implementation, measurement, failure analysis, ethics, and a field exercise so a reader can use the model while respecting its limits.[s1][s2][s3][s4][s5][s6]
Learning objectives
By the end of this lesson, you will be able to:
- Diagnose when PVI model can materially improve a business decision.
- Design a defensible evidence and implementation process rather than a presentation-only exercise.
- Select leading, lagging, economic, and quality measures that reveal whether the intervention works.
- Identify analytical, organizational, and ethical failure modes before they cause stakeholder harm.
- Translate an insight into a time-bounded test with ownership, thresholds, and a learning loop.
Foundations: what the concept means
The PVI model, popularized by Harvey Coleman, distinguishes Performance—the quality and value of contribution; Visibility—whether relevant people can see and understand that contribution; and Image—the expectations and reputation created by repeated behavior and communication. The model is a career heuristic, not a validated formula or permission for impression manipulation.
Foundation 1
Identity and career behavior emerge through interaction among values, capability, relationships, opportunity, institutions, incentives, health, and repeated action; a framework should organize inquiry rather than define worth. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 2
Credible development uses observable contribution, plural feedback, applied experiments, and real stakeholder outcomes. Confidence, visibility, prestige, and narrative coherence are insufficient evidence by themselves. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 3
Relationships can provide challenge, information, access, support, and sponsorship, but power, conflict, reciprocity, confidentiality, and dependency require explicit boundaries. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 4
Sustainable progress preserves ethics, health, recovery, accessibility, financial realism, and option value; individual action cannot erase structural exclusion or institutional responsibility. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
The literature provides complementary rather than interchangeable lenses.[s1][s2][s3][s4][s5][s6] A rigorous practitioner uses those lenses to sharpen observation and decision quality, not to borrow academic authority for a conclusion already chosen. Definitions, samples, methods, and boundary conditions should travel with every important claim.
A decision-ready operating framework
A useful framework must specify inputs, transformation, outputs, ownership, and feedback. The following five-stage system creates that chain while leaving room for the method to be adapted to category, organization, and evidence quality.
1. Perform
Define perform through purpose, stakeholder, values, boundaries, constraints, and the next real decision. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Evidence
Investigate evidence using work evidence, contrasting perspectives, market or organizational context, and a credible alternative explanation. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Visibility
Practice visibility in a bounded real situation with feedback, support, privacy, and a stop or escalation rule. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Reputation
Make reputation credible through outcomes, artifacts, reciprocal relationships, and transparent limits rather than claims alone. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Calibrate
Review calibrate for contribution, learning, fairness, wellbeing, unintended effects, and changed conditions; revise without identity shame. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
This animated pvi model evidence pathway shows an animated pathway connects perform, evidence, visibility, reputation, calibrate through responsible practice and review. The sequence remains fully understandable when motion is disabled.
The stages are iterative. New evidence may change the original question, expose a missing stakeholder, or show that an apparently attractive option is infeasible. Governance should allow the team to return to an earlier stage without describing learning as failure.
Worked example: A composite infrastructure engineer overlooked for promotion
Situation
Critical reliability work remained invisible, while a colleague’s polished updates received credit; the engineer was advised simply to promote himself more. The case is hypothetical and composite; it illustrates a reasoning process rather than reporting facts about any real organization. Management agreed to separate observations, interpretations, choices, and measured outcomes so hindsight could not erase uncertainty.
Case movement 1
The person defined the desired outcome and constraints, separated self-story from evidence, and named stakeholders, authority, resources, privacy, and non-negotiable protections. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 2
Field evidence and structured conversations revealed conflicting expectations, missing capability, system barriers, and an alternative to the initial personal explanation. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 3
A small real-world experiment paired one behavior change with one enabling system or relationship change and defined support, feedback, and fallback. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 4
Measurement covered credible contribution, quality, learning, reputation or relationship effect, wellbeing, fairness, and unintended consequences. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 5
The review retained supported changes, corrected harm and structural barriers, documented boundaries, and sought regulated professional advice where the decision exceeded the lesson’s scope. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Interpretation
The case matters because action followed the diagnosed mechanism, not the fashionable label. It also preserved a comparison and a boundary statement. A result in one setting changed the next decision; it did not become a universal law.
90-Day Action Plan
Implementation needs an executive sponsor, a working owner, protected access to evidence, and explicit decision dates. The plan below can be compressed for a small reversible choice or expanded for a regulated, capital-intensive, or high-harm decision.
1. Days 1–14: define the developmental decision
Name outcome, stakeholders, baseline, values, constraints, authority, evidence, privacy, and conditions that would disconfirm the initial story. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Days 15–30: gather field evidence
Review artifacts and outcomes; interview contrasting practitioners or stakeholders; map capability, incentives, access, relationships, and structural barriers. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Days 31–45: design a bounded practice
Choose one behavior and one enabling system or relationship change, with feedback, support, boundaries, safeguards, and stop rules. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Days 46–70: test in real work
Produce a useful artifact or decision, collect plural feedback, and measure outcome, quality, fairness, wellbeing, and unintended effects. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Days 71–90: review and stage
Document learning, correct harm, strengthen relationships and options, obtain qualified advice where required, and set the next evidence-based decision date. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The plan should connect with Developing mutual understanding and trust, How Good Are Your Project Management Skills?, SMART Goals, Managing Your Career, How to Be a Good Role Model, What Is Personal Branding? and the Strategy learning hub. These links are complementary tools, not substitutes for the evidence required by this decision. At day ninety, write a one-page decision record covering the original premise, evidence obtained, decision taken, result, unresolved risk, and next review.
Measurement and review
Measurement should serve learning and accountability. Establish a baseline, define the unit and denominator, segment outcomes where averages can conceal harm, and choose a review interval that matches how quickly the underlying mechanism can change.
1. Evidence
Observable contribution, artifacts, outcomes, feedback sources, uncertainty, and contrary cases. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Capability and behavior
Skill demonstrated, judgment, reliability, ethical conduct, transfer, and correction across contexts. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Relationships
Trust, reciprocity, access, diversity, boundaries, conflicts, sponsorship, and dependency. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Opportunity and value
Stakeholder result, job quality, economics, future options, and distribution of benefit or burden. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Sustainability
Health, recovery, workload, privacy, accessibility, inclusion, and ability to continue without heroics. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The second infographic keeps personal action, credible contribution, relationships, structural conditions, safeguards, and review connected so development cannot collapse into image management or dependency.
Avoid a dashboard in which every number rises when activity rises. Include outcome, quality, economic, and counter-metrics. Predefine a threshold that triggers investigation or stopping, and retain qualitative evidence that explains why the number moved.
Failure modes and corrective action
The most dangerous errors are often organizational rather than technical: incentives reward certainty, a senior sponsor prefers one explanation, or presentation deadlines arrive before evidence. Treat the following patterns as control failures with observable warning signs.
1. Identity performance
A polished story outruns evidence. Build credible work. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Prestige proxy
Status substitutes for fit or contribution. Inspect real conditions. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Single relationship
One gatekeeper controls development. Build a network. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Individualization
Structural barriers become self-improvement. Address systems. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Boundary erosion
Availability and disclosure become expected. Contract limits. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
Run a pre-mortem before launch and an after-action review after the first decision cycle. Record near misses, not only visible failures. A healthy team can say that an attractive hypothesis was not supported and redirect resources without reputational punishment.
Ethics, limits, and responsible use
Business usefulness does not excuse deception, avoidable harm, or unsupported inference. The method should be proportionate to the decision and reviewed more carefully when it affects employment, credit, health, safety, privacy, or access to essential services.
Responsibility 1
People must not be pressured into personal disclosure, emotional performance, unpaid work, endorsement, or access through exploitative relationships. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 2
Career, reputation, health, and relationship data require privacy, legitimate purpose, access control, and a route to correction. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 3
Discrimination, disability, class, caste, caregiving, migration, geography, and power shape opportunity and should be addressed explicitly. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 4
Retirement, compensation, legal, tax, fiduciary, immigration, health, and investment decisions require current qualified professional advice. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Limits should be written into the decision record: population, context, time, method, uncertainty, and the conditions under which the conclusion should be revisited. Do not imply individualized legal, medical, financial, or employment advice.
Practice Checklist and Laboratory
Implementation Checklist
- [ ] The audience, decision, accountable owner, and intended value are explicit.
- [ ] Material claims have traceable evidence, sources, limits, and correction ownership.
- [ ] The plan includes a baseline, comparison, primary outcome, cost, and stakeholder counter-metric.
- [ ] Consent, privacy, accessibility, safety, legal, and platform obligations have been reviewed.
- [ ] Stop, escalation, remedy, and after-action review rules are documented before launch.
Complete the exercises with a live but reversible decision. Preserve artifacts so another reviewer can inspect how you moved from evidence to recommendation.
Exercise 1
Write a one-page PVI model hypothesis with outcome, evidence, stakeholders, constraints, and the result that would change your mind. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 2
Collect three concrete perspectives, including one contrary or less powerful voice; ask about actual behavior, risks, access, and advice they distrust. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 3
Design a two-week practice that creates a work artifact, feedback, relationship evidence, and an observable outcome with privacy and stop rules. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 4
Complete the checklist and create a decision record covering action, evidence, fairness, wellbeing, limits, and next review. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Finish with a decision memo: “We believed… We observed… We now infer… We will test… We will stop or revise if…” This format makes uncertainty actionable and creates an organizational memory stronger than a polished retrospective.
Key takeaways
- Use PVI model as an evidence-led practice, not an identity claim. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Ground narrative and visibility in real contribution. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Build plural reciprocal relationships with boundaries. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Pair individual practice with enabling system change. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Protect ethics, privacy, inclusion, health, and option value. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Review outcomes and revise when reality disagrees. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
Mastery means choosing the method for the decision it can improve, using evidence at the level it supports, and changing course when the world contradicts the model.
References and further reading
The sources below establish the conceptual and methodological foundation. Publication details and locators have been retained so editors can verify every material attribution before publication.
[s1] Harvey J. Coleman. “Empowering Yourself.” 1996. https://search.worldcat.org/title/36916708
[s2] Robert P. Vecchio. “Impression Management in Organizations.” 1998. https://search.worldcat.org/title/39485173
[s3] Tony Simons. “Behavioral Integrity.” 2002. https://doi.org/10.1287/orsc.13.1.18.543
[s4] Robert K. Merton. “The Matthew Effect in Science.” 1968. https://doi.org/10.1126/science.159.3810.56
[s5] Zachary A. M. Blickle et al.. “Predicting Workplace Reputation.” 2011. https://doi.org/10.1037/a0022672
[s6] Mark S. Granovetter. “The Strength of Weak Ties.” 1973. https://doi.org/10.1086/225469
