Strengths Mapping from Lived Experience

By Better Wise

From Values to Evidence

In Lesson 1.2 you named the values that act as your filter: the non-negotiables you use to judge whether work is meaningful. Values tell you what you will not trade away. Strengths tell you what you can actually do, repeatedly, with proof. This lesson builds the bridge between the two, so that when you eventually write a bio or a portfolio, every claim has a receipt behind it.

By the end of this lesson you can:

• Define a strength precisely, and separate it from a skill, a trait, and a compliment
• Climb the evidence ladder from a raw experience to a repeatable capability
• Fill a strengths map with five columns: capability, experience, evidence, energy, values
• Test a capability across contexts and rank your evidence by strength

Anatomy of a Strength

Most people describe strengths with adjectives. "I'm passionate." "I'm detail-oriented." "I'm a people person." These are claims, not strengths. Here is the working definition this course uses:

Note: A strength is a repeatable capability that you can demonstrate with evidence and would willingly do again. All three parts are required.

The trait and the skill are not useless. They are raw material. The strength is what happens when a skill meets real situations often enough that you can point at proof.

The Evidence Ladder

Vague experiences become credible strengths by climbing four rungs. Do not skip the middle.

flowchart TD
    A["1. Moment<br/>The raw event"] --> B["2. Action<br/>What you actually did"]
    B --> C["3. Capability<br/>The repeating verb"]
    C --> D["4. Evidence<br/>Artifact, number, outcome"]

Weak version: "I helped organize a community event." Climbed version: Moment: a 60-person neighborhood repair café lost its volunteer coordinator three weeks out. Action: rebuilt the shift schedule in a shared sheet, called 14 volunteers, reassigned six roles. Capability: coordinate logistics under time pressure. Evidence: event ran with all 12 stations staffed; two volunteers reused the schedule template for the next event.

Notice that rung 3 is a verb phrase, not an adjective. Verbs travel. Adjectives don't.

Practice: Climb One Rung at a Time

Pick one concrete moment from the past twelve months (work, volunteering, family, a side project). Write it at rung 1, then climb.

Guidance for checking your answer: Rung 2 is correct only if it answers "what did I do," not "what did the team do." Rung 3 should be readable in a job description. Rung 4 fails if it contains only your own opinion, because evidence must be verifiable by someone else.

Building Your Strengths Map

Your map is a table you will keep editing for the rest of the course. Five columns, one row per capability.

Two things about this table matter more than they look. The Energy column records whether you would willingly repeat the work. A capability you are good at but dread is a skill you can rent out, not a strength you want to build an identity on. The Values column keeps you honest: if a row serves no value you named in 1.2, ask why it is on the map.

Aim for five to seven rows. Fewer than five usually means you stopped climbing too early.

Practice: Draft Three Rows

Fill three rows using the ladder from the previous section. For each, force yourself to write something in the Evidence column that a stranger could verify.

Guidance: If a row's evidence reads "people said I was good at it," you have a testimonial without a source. Convert it: who said it, in what setting, and what changed because of your work? If you genuinely cannot find evidence for a capability, either find the proof or demote the row to "developing."

Testing for Patterns and Weak Evidence

One instance is an anecdote. Three instances across different settings is a pattern. Run the cross-context test: does this capability show up at work, in a community or volunteer role, and in a personal project? Capabilities that survive all three are the ones you can claim with confidence.

Rank your evidence roughly like this, strongest first:

1. Artifacts and measured outcomes (a document, a number, a shipped thing)
2. Named outcomes with a witness or recipient
3. Specific repeatable process you can describe step by step
4. Memory of a general impression

Two inflation traps to avoid, because they are the exact habits that turn a credible brand into performative self-promotion:

• Adjective stacking. "Passionate, driven, dynamic" tells a reader nothing they can check.
• Borrowed scale. "We grew revenue 40%" when your contribution was one meeting. Say what you did, and let the honest scope carry more weight than the inflated one.

Field Notes From Doing This With Real People

• Write the evidence column before the capability column. Starting with the label invites you to invent a self-image, then hunt for proof.
• Keep "I" sentences in your raw notes even if the final portfolio uses different framing. Ambiguity is where exaggeration hides.
• A strength with low energy is legitimate data. Many people discover that their most credentialed skill is the one they least want to lead with.
• If you cannot name a single artifact for a capability, that capability is still forming. Label it "developing" and revisit it after your capstone.
• Do not outsource the map to a tool before you have written it by hand. Critique comes later; authorship comes first.

Where This Leaves You

Your strengths map now converts lived experience into verifiable capability, and the evidence ladder keeps every claim anchored to something real. Your values tell you which rows you want to lead with; your evidence tells you which ones you can defend.

Front: What three parts make something a strength rather than a trait? Back: A repeatable capability, demonstrable evidence, and willingness to do it again.

Front: Strength or trait: "I'm detail-oriented"? Back: A trait or claim. It becomes a strength only when tied to repeated action and proof.

Front: What are the four rungs of the evidence ladder, in order? Back: Moment, Action, Capability, Evidence.

Front: How should the Capability rung be phrased? Back: As a verb phrase that could appear in a job description, not as an adjective.

Front: Why is "I helped organize an event" a weak strengths statement? Back: It names a vague activity with no personal action, repeating capability, or verifiable outcome.

Front: Which evidence type ranks strongest? Back: Artifacts and measured outcomes, because someone else can verify them.

Front: What does the cross-context test check? Back: Whether a capability shows up in at least three different settings, such as work, community, and personal.

Front: What does the Energy column on a strengths map record? Back: Whether you would willingly repeat that work, scored roughly 1 to 5.

Front: What is the inflation trap called "borrowed scale"? Back: Claiming a team-level outcome as your own when your contribution was small.

Front: Why is adjective stacking a problem in strengths claims? Back: Adjectives like passionate or driven give a reader nothing they can check.

Front: How many rows should a working strengths map have? Back: Roughly five to seven, with fewer usually meaning you stopped climbing too early.

Front: What should you do with a capability that has no evidence yet? Back: Label it developing and revisit it later, rather than inflating the claim.

Check your recall of the core vocabulary:

A strength requires a repeatable _____, _____, and the willingness to do it again. The evidence ladder runs from Moment to _____, then Capability, then Evidence. The _____ test asks whether a capability appears in at least three different settings. A capability you perform well but dread repeating should be marked with low _____ on your map.

Next up is the Module 1 checkpoint, where you will assemble your values list and strengths map into one identity foundation you can defend line by line.