Guides
Executive presence vs leadership presence: a 90-day test
Test executive presence against leadership presence over 90 days: three countable behaviors, a peer group and an evidence log a promotion panel can check.
What to take away
- A 90-day log turns "she has presence" into dated, countable evidence.
- Track three behaviorscomposure, priority clarity and follow-through.
- Compare yourself with peers in similar roles, scope and review windows.
- Keep direct observations apart from impressions, and note the context of each.
- Team-level scores are context for a panel, not proof of one leader's effect.
- Build leadership presence first. It survives a change of employer.
Three behaviors you can count
Composure is the time you take to return to the agenda after a direct challenge. Record elapsed seconds and restarts for each observed challenge. Use repeated observations rather than a single moment, because one tense meeting says little about a whole quarter.
Priority clarity is whether three people on your team can name the same top two goals without checking with you first. Ask them separately and write the answers down as given. Matching answers are evidence; scattered answers show where the next meeting needs work.
Follow-through is the share of commitments you close on the date you named. Track it in a shared log rather than in memory, so a panel can check each date. For wider measures of influence, the leadership influence metrics give more to compare.
Polish gets you read. Decisions get you followed.
The five-step test over one quarter
Each step produces something a panel can read: a baseline, a definition, a log, a peer comparison and a review. Run them in order, and do not skip the baseline, because it shows what you can already document.
Five-step evidence test
- Name three behaviors to test
- Attach one countable indicator each
- Collect 90 days of existing data
- Compare with two same-level peers
- Keep what moved, repeat next cycle
- Set the window and baseline.Choose a 90-day period and note what evidence you already have for composure, priority clarity and follow-through. State the decision the evidence will inform, such as a development plan or promotion discussion.
- Define what you will observe.For composure, record the time to return to the agenda and any restarts after a direct challenge. For priority clarity, ask three team members to name the same top two goals. For follow-through, record commitments due and whether each closed on the date named. Do not invent a pass/fail threshold.
- Collect evidence as it happens.Log dated examples from panel notes, 360 feedback, calendar data, performance reviews, engagement scores and exit interviews where available. Separate direct observations from impressions, and note the context for each example.
- Compare with relevant peers.Use people with similar roles and scope, the same review window and the same definitions of each behavior. Treat the comparison as context, not a ranking against people whose responsibilities or evidence differ.
- Review the pattern.Look across the baseline and the 90-day record. Stronger evidence of in-room composure without clearer team priorities or follow-through supports executive presence more than leadership presence; evidence of both supports both. Pick a behavior to improve and repeat the review next quarter, without applying an arbitrary score.
What a panel sees against what a team shows
A panel sees one meeting; a team shows its work across quarters. Evidence from the first is quick to collect and easy to over-read. Evidence from the second takes longer but says more about leadership presence, which is why the test mixes both.
Executive presence, as the log measures it, is what a room sees: composure under challenge. Leadership presence is what a team shows: shared priorities and commitments closed on the date named. The two can come apart, which is why the log tracks both kinds of behavior.
Executive vs leadership presence signals
Executive presence
- Where it shows
- Boardroom, client pitch
- Time to observe
- One meeting
- Common proxy
- Speaking time, polish
- Evidence to collect
- Panel notes, 360 feedback
- Failure mode
- Confident but vague
Leadership presence
- Where it shows
- Team output, retention
- Time to observe
- One to two quarters
- Common proxy
- Priority clarity, coaching
- Evidence to collect
- Calendar data, engagement scores
- Failure mode
- Well liked but invisible
Each source answers a different question, and each has a limit you should write beside it. The executive and leadership presence comparison covers the definitions, so this table only sorts the evidence.
| Evidence source | What it can show | What it cannot show |
|---|---|---|
| Panel notes | How you answered a challenge in one meeting | How the team performs in week six |
| 360 feedback | How colleagues describe your conduct | Why a result occurred |
| Calendar data | Where your time and meetings went | Whether decisions held |
| Engagement scores | Whether people speak up and recommend the team | One leader's individual effect |
| Exit interviews | Why people chose to leave | Whether the leader caused it alone |
Example: a regional sales director
A regional sales director wanted a vice president title. Her sponsor described strong executive presence, but the promotion panel asked for evidence of leadership presence. She had a reputation and no record.
She ran the test for one quarter. Composure held. Priority clarity did not. Her eight direct reports named five different top goals.
She fixed one meeting, published two goals, and repeated the survey. The panel saw the shift in the next cycle.
Presence checklist for a promotion panel
A panel can use five questions to decide whether a presence claim counts as evidence. Each question can be answered from the log, which keeps the discussion on what happened rather than on how someone came across.
Promotion panel presence checklist
- Three written behaviors with countable indicators
- Ninety days of data from existing systems
- One peer comparison at same level
- Two examples of team acting without you
- One plan for lowest-scoring behavior
- Observed behavior:Does the evidence describe a specific response to challenge, clear priorities or follow-through, rather than a general impression of polish?
- Date and context:Is each example tied to a situation and review period so panel members can assess what happened?
- Team priority clarity:Can three team members independently name the same top two goals without checking with the leader?
- Commitment record:Does the evidence show which commitments were due and which closed on the date named?
- Corroboration and limits:Do multiple relevant sources support the conclusion, and does the panel distinguish team-level results from proof of one leader's effect?
Evidence your organization already keeps
Performance reviews and rating scales usually capture leadership effectiveness, and the OPM performance management resources describe how federal agencies structure those records.
Engagement surveys are another source. Employee engagement scores can indicate whether people speak up and recommend the team; treat them as team-level context, not proof of an individual leader's effect.
Use the sources that are available and relevant, and record what each can and cannot show. A calendar entry or survey score alone does not establish why a result occurred.
One log entry per observation
Keep a presence evidence log with one entry for each observation. Each entry holds the same fields, so a panel can read ten entries as quickly as one and see the pattern across the quarter.
Field / What to write
- Date
- The day the behavior was observed
- Behavior
- Composure, priority clarity or follow-through
- Situation
- The meeting, challenge or commitment involved
- Evidence source
- Panel notes, 360 feedback, calendar data or another record
- Observed result
- Elapsed seconds and restarts, or commitments due against closed
- Context
- What else was happening that could explain the result
- Follow-up
- The one behavior to change before the next review
Signals that imitate presence
Speaking first is not presence. It is a habit that panels sometimes mistake for command. Volume is not influence either: a leader who talks in every meeting can still leave the team without a decision.
Titles are not evidence. A director title changes how a room greets you, not how your team performs in week six. The log exists to keep such signals out of the record and put observed behavior in.
