Show communication, teamwork, organization, or judgment through a specific action rather than a bare trait label.
Harvard recommends specific, active, fact-based language. It does not claim that a fixed formula guarantees an interview.
A practical method
- Select one trait that appears in the target posting.
- Recall a specific work, school, volunteer, or project situation where you used it.
- Name the people or process involved and your observable action.
- State the outcome or deliverable, using numbers only if supported by records.
- Place the example near the relevant experience rather than listing a string of adjectives.
Worked example: from first attempt to usable result
- Task: Show communication, teamwork, organization, or judgment through a specific action rather than a bare trait label.
- First output/attempt: “Excellent communicator and team player.”
- Mistake/weakness: The claim asks the reader to accept a trait without showing the situation or behavior.
- Human correction: Choose a real moment when the skill changed a handoff, decision, or outcome; describe the audience, action, and resulting artifact or decision.
- Quality check: Could a former teammate recognize the behavior? Can you explain what you personally did and what changed? Remove outcome claims you cannot verify. Illustrative soft-skill check: 1 teammate confirmed the behavior description while correcting the candidate’s attribution.
- Final usable result: Coordinated a weekly handoff between support and billing teams by documenting unresolved cases and assigning an owner for each follow-up.
- Resume bullet: Illustrative resume bullet (use only if true): “Documented cross-team case handoffs and clarified individual ownership of follow-up actions.”
A beginner exercise you can complete today
For one soft skill, write a short situation-action-result note and ask a collaborator whether it fairly describes your contribution. Retain the note and revise the bullet if they identify missing context.
Pass check: Keep the posting, one finished behavior-based bullet, the source of the example, and a collaborator’s feedback. Pass when the line names what you did and its context without private details; if no measurable outcome is available, name a verifiable handoff or deliverable instead.
Frequently asked questions
Should I list “team player”?
Only if space and context justify it; a specific example of coordinating or contributing usually shows more.
Can I use feedback as evidence?
Yes, when accurately attributed and not confidential. Still explain the behavior the feedback refers to.
Decisions that change the approach
Soft skills become readable when a line shows behavior. “Communicated well” says little; “summarized a late shipment, named the unresolved question, and handed the case to the right team” shows what communication did. Choose a skill that matters to the vacancy and then find a moment with an observable action.
| Situation | What to inspect | Next decision |
|---|---|---|
| Communication | What information did you make usable? | Name audience, message, and next action. |
| Teamwork | What did you coordinate or contribute? | Separate your work from the group outcome. |
| Organization | What did you track and how? | Identify process and deliverable, not personality. |
Do not label yourself “empathetic” to disclose private customer stories, or claim leadership when you only attended a meeting. A safe example can be anonymized and still specific: clarify the task and your behavior without names, account details, or protected information. For a measurable result, use a source; otherwise describe the handoff, decision, or artifact.
Communication and judgment need different evidence
For a customer-facing role, “communicated well” is too broad. A specific example might be: “Clarified a customer’s billing question, summarized the unresolved issue, and routed it to the billing team with the relevant account context.” This shows communication behavior and the process it supported; it does not claim customer satisfaction improved unless a source demonstrates that result.
For a judgment example, show the decision boundary: “Flagged a mismatch between the order record and the customer’s request, paused the handoff, and asked a supervisor to confirm the correct charge.” This demonstrates careful escalation, not authority to change billing policy. Ask a collaborator whether your description fairly represents your contribution. If the only evidence is a private customer record, write a sanitized description or choose another example; do not expose identifying details to prove a soft skill.
A useful next step
Use this to check that each behavior claim stays factual. the resume-mistakes checklist. Use this when your strongest behavior example came from a project. the project-resume guide.
Select a behavior that matches the job, then show it in context
Soft skills are broad labels for observable behaviors. For a customer-facing role, “listened and clarified the request before escalating” is more meaningful than “empathetic.” For coordination, “kept owners and due dates visible across a handoff” shows the work behind “organized.” For judgment, explain the relevant constraint and how you chose a next step without revealing confidential customer or coworker details. For collaboration, identify your contribution and the shared result separately.
Choose one soft skill from the vacancy and look for a specific moment when it mattered. Ask a former teammate what behavior they remember, but verify the description yourself. A manager’s praise is not a substitute for an action; “praised for communication” becomes useful only when you can explain what message, audience, and outcome it refers to. When no evidence exists, omit the adjective or build a future example through a volunteer or project setting.
Expected rewrite: turn “great communicator” into a line that names the situation and behavior, such as “Summarized unresolved billing questions at shift handoff and identified the next owner for each case.” Keep that wording only if it accurately describes your work. A reader should be able to ask a follow-up and receive a factual explanation, not a second adjective.
Soft skills should complement—not crowd out—technical evidence. If every bullet says “collaborated,” the resume may conceal the actual work. Use one or two examples that show the behavior and let the remaining space explain methods, tools, outcomes, or responsibilities. This produces a more balanced account and gives an interviewer a meaningful story to explore.
A final practical boundary
Choose the verb that makes the behavior visible: clarified, summarized, coordinated, resolved, documented, prioritized, or escalated. Then check whether the sentence explains the recipient or process and what changed. “Collaborated with colleagues” is too broad by itself; “coordinated the billing handoff and recorded the next owner” gives a reader something to picture. Do not borrow a teammate’s result as your own. If the shared result matters, state your role in the group effort.
If you cannot support a soft skill, leave it out or find a real example
Suppose a posting values problem solving. A bullet that says “Excellent problem solver” does not show a decision. If the candidate has no work example, do not force the trait into the skills list. They can instead describe a supervised project or a clearly labeled practice exercise, or wait until they have a verifiable example. In a resume, “developing” is not a substitute for proof; describe training under training and demonstrated behavior under experience.
| Weak line | Revised line (illustrative; use only if true) | Verify before using | Evidence to retain |
|---|---|---|---|
| “Great communicator and team player.” | “Coordinated the customer-to-billing handoff, recorded the unresolved issue and next owner, and used a checklist reviewed by the team lead.” | Did the candidate create or use the checklist? Can the lead confirm the assigned role? Do not claim fewer repeat contacts without a record. | An anonymized checklist, date/role note, and supervisor feedback. Remove customer identifiers. |
| “Strong problem solver.” | “Compared two inventory reports, flagged duplicate item codes, and documented the correction for the next shift.” | Can the candidate show the comparison or explain how the duplicate was confirmed? | A redacted example or private process note, not confidential employer data. |
If no legitimate evidence exists yet, omit the trait rather than borrowing another person's result. A short public-data practice sample can demonstrate how you approached a defined problem, but it does not prove paid-work experience or employer-wide impact.
Sources
- Harvard College Guide to Creating a Strong Resume — Harvard recommends specific, active, fact-based resume language, tailoring to a position, clear organization, and checking how a PDF converts. Checked 2026-10-17.
- University of Michigan University Career Center: Resume Resources — Michigan recommends consistent scannable formatting, reverse chronology within sections, tailored experience, and bullets that add what/how/why or impact; its one-page suggestion is specifically for most undergraduates. Checked 2026-10-17.
- UC Berkeley Career Engagement: Resumes — Berkeley recommends matching resume evidence to required and preferred qualifications and focusing on results, transferable skills, and targeted accomplishments; its one-page advice is specifically for students. Checked 2026-10-17.