Sample Tip Archive

Browse recent daily tips on leadership, communication, and strategy before joining the list.

← Back to home
Clear filters
Day 188 Relationship Building Share →
Use the Champion Equation. A champion is not someone who likes your demo. A champion is someone with pain, influence, and a reason to spend political capital for change. 1. Pain: What problem do they personally feel? 2. Power: Whose opinion do they shape internally? 3. Personal win: How does solving this make their job, status, or team better? 4. Proof: What evidence can they use when you’re not in the room? No personal win, no real champion. 🎯 Try this today: Pick one “champion” in your pipeline and fill in the four parts. If one is blank, ask about it on your next call.
Day 138 Relationship Building Share →
Use the “Answer-First Brief” when writing to senior leaders. Barbara Minto’s Pyramid Principle applies: don’t make busy people climb your logic ladder—hand them the answer, then the reasons. 1. Answer: Lead with the recommendation or conclusion. “We should delay launch by two weeks.” 2. Why: Give 2–3 reasons, not a data dump. “Payment failure rate is 11%, support scripts aren’t ready, and rollback risk is high.” 3. Risk: Name the trade-off honestly. “Delay costs us one campaign slot but protects customer trust.” 4. Ask: State the decision needed. “Approve revised launch date by Friday.” 🎯 Try this today: Rewrite one email or slide so the first sentence is the answer, not the background.
Day 114 Relationship Building Share →
3R Ladder — a 3-line update that spotlights you without sounding like bragging 1. Result: State the concrete win with a metric (“Shipped self-serve checkout—cut sign-up time 42 s”). 2. Relevance: Tie it to a priority leadership cares about (“Speeds ARR growth target and bumps trial-to-paid”). 3. Recognition: Share credit (“Big assist from Mia on UX tests”). Post the note where decision-makers lurk (team Slack, weekly digest). You prove impact, show strategic awareness, and build goodwill—all in 30 words. 🎯 Try this today: Draft a 3R update for your latest deliverable and drop it in the team channel before lunch—stop editing at 3 sentences, hit send.
Day 106 Relationship Building Share →
3×3 Ping — the 3-line, 3-minute note that keeps your network warm 1. Callback: Lead with one concrete thing you last discussed (“Your point about trimming QA cycles stuck with me.”) 2. Value drop: Offer a nugget that helps them—link, stat, intro (“Saw this case study where a 2-step checklist cut defects 18 %.”) 3. Open door: End with a no-pressure invite (“Happy to swap notes if useful—grab 15 min whenever.”) Three pings a week and your name stays synonymous with usefulness, not small talk. 🎯 Try this today: DM one colleague you haven’t spoken to in a month using the 3×3 Ping—see how quickly the thread revives.
Day 104 Relationship Building Share →
Most execs skim only slide titles—if yours say “Pipeline” or “Roadmap,” you’ve wasted the one line they notice. Turn each title into a takeaway sentence: “Pipeline up 18 %—new SMB tier drives half the lift.” The story now travels even if Wi-Fi dies. 🎯 Try this today: Open your next deck, rewrite the first three slide titles into 10-word headlines that state the result or decision—no lone nouns, full sentences only.
Day 95 Relationship Building Share →
C.R.I.S.P. Brief — package any exec update in 5 laser lines 1. Conclusion: open with the headline metric or decision (“Churn down 2.1 % in 30 days”). 2. Reason: why leadership should care right now (revenue, risk, brand hit). 3. Insight: the one fact that explains the movement (“90 % of saves came from the new onboarding video”). 4. Step: the concrete next move you’re driving (“Rolling the video to Enterprise accounts next”). 5. Permission: the specific ask or green light needed (“Need $8k for pro voice-over, decide by Friday”). Executives scan top to bottom; this gives them the movie trailer, not the blooper reel. 🎯 Try this today: Draft your next status email in the C.R.I.S.P. sequence—trim to 100 words, hit send, and clock how fast replies come back with a clear “yes” or “no.”
Day 71 Relationship Building Share →
N.O.T.E. Recap — the 4-line follow-up execs love 1. Net outcome: the single sentence on what got decided or delivered. 2. Ownership: who’s got the ball, bold their name. 3. Timeline: the exact date the next milestone lands. 4. Escalation need: one line on any blocker the leader must clear. Four bullets, no narrative. Reads in 15 seconds, saves a week of “wait, who’s doing what?” threads. 🎯 Try this today: After your next meeting, draft a N.O.T.E. Recap in Slack or email and hit send before anyone leaves the room.
Day 46 Relationship Building Share →
Seal the deal before the room even hears the pitch. Land one respected ally in advance and lead with their endorsement: “I walked Maya (Head of Ops) through this; she’s ready to lend two analysts.” Cialdini’s social proof flips listeners from “Is this safe?” to “Looks like we’re already doing it.” 🎯 Try this today: For your next ask, DM the most trusted stakeholder, give them a 60-second preview, and secure permission to cite their support—then open your meeting or email with that line.
Day 42 Relationship Building Share →
S.I.N.G. Update — the 4-bullet note that spotlights your work without sounding like a show-off 1. Success: a one-line headline of what landed (“Launched self-serve FAQ”). 2. Impact: the concrete win (-30% support tickets in 48 hrs). 3. Next: where you’re driving it next (“A/B test new search tags by Friday”). 4. Gratitude: tag at least one collaborator (↔ Cialdini’s reciprocity pays forward). Post these four lines in Slack, email, or stand-up; leaders see results, the team sees momentum, and you bank goodwill by sharing credit. 🎯 Try this today: Draft a S.I.N.G. update for the work you touched today and drop it in your project channel before you log off.
Day 36 Relationship Building Share →
T.R.A.C.K. Update — a 5-bullet status snapshot leaders can scan in 10 seconds 1. Target: restate the goal (“Ship v2 by Oct 1 to catch holiday demand”). 2. Result: current metric (“Dev 80% complete, QA 60%”). 3. Assessment: ahead/on/behind—one word or traffic light (“Amber—4 days late”). 4. Correction: what you’re already doing (“Pulling one engineer from v1 maintenance”). 5. Key Ask: what you need from them, by when (“Need overtime budget approved by Friday”). 🎯 Try this today: Craft your next project update using T-R-A-C-K and send it—five bullets, no prose.