WHYME!
How Why Me! works

The three pillars · Strategic Initiatives

Strategic Initiatives

What you helped lead.

Make your contribution clear: the challenge, your role, the decisions and the progress. Show the work behind the job title.

Show the work behind your achievements

A list of responsibilities can hide the work that mattered. Describing a specific initiative helps someone understand the scope of a challenge and your contribution within a team.

What belongs here

  • Projects or initiatives you led or meaningfully contributed to, with an accurate role and timeframe.
  • The problem, scope, collaboration and decisions that explain what you actually did.
  • Progress and related outcomes, including work still underway; avoid taking credit for the whole team's result.

How to use it in Why Me!

  1. Step 1. Open Edit Profile and select Strategic Initiatives. Add a title, your contribution, a concise description and relevant dates.

  2. Step 2. Explain scope, collaborators and decisions in the description. Add related outcomes when you have something meaningful to report.

  3. Step 3. Choose whether the entry is public. Optional HTTPS supporting references stay private by default. When relevant, attach a claim to a Perspective invitation so the reviewer can choose whether to provide context.

Context from someone who was there

An attached initiative claim is separate from the reviewer's broader Perspective. In the invitation process, they can describe their familiarity, your contribution and whether the stated outcome is consistent with their experience—or skip it if they cannot assess it.

Only eligible, consented corroboration of the unchanged claim can appear alongside a published Perspective. This adds firsthand context; it does not independently validate a retention percentage, establish causation or certify the whole project.

The power of firsthand context

What this can look like

Fictional examples for illustration—not real profiles, reviews or product-verified claims.

Cross-functional process rollout

Coordinated a shared customer handoff checklist with Sales and Support. Gathered requirements, piloted the process with two teams and revised it using their feedback.

Fictional example · contribution and scope are self-reported; no company-wide transformation claim.

Retention improvement initiative

Contributed to an onboarding improvement effort by identifying recurring support questions and helping revise the first-month check-ins.

Fictional example · a contributor can describe their part without claiming sole ownership of retention.

How it evolves over time

Start with the challenge and your role. Update the description as decisions are made and the work develops. Add results when they are known, with dates and context rather than retroactively turning every project into a success story.

Grow your professional story

Privacy and verification

Your initiative description is self-reported. A consenting reviewer may corroborate familiarity or contribution; that is not an audit of the project or independent verification of its numbers. Keep confidential client, employer and colleague information out of public descriptions and references.

New profiles start private. Review your visibility choices before sharing.

How verification works