
Written Communication
Turn repeated explanations into clear async docs and stronger leadership communication using curated Lenny’s Podcast guest patterns.
Overview
Written Communication is a journey-wide agent skill that helps solo builders scale impact by turning recurring verbal explanations into clear asynchronous documents and stronger leadership messaging.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill written-communicationWhat is this skill?
- Curated insights from 38 Lenny’s Podcast guests with 61 documented mentions
- Codify explanations repeated in one-on-ones into 30-minute docs others read async
- Treat communication as the job: artifacts and verbalizations must land with the audience
- Use metaphors so readers connect the final dot themselves
- Multimodality and extreme ownership of whether the message was received
- 38 guests
- 61 mentions
Adoption & trust: 1.4k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You repeat the same strategy in every one-on-one and still hear confusion because nothing durable exists for people to read on their own time.
Who is it for?
Solo founders and indie PMs who are the bottleneck for context and need Lenny-style communication habits without a comms team.
Skip if: Purely visual brand systems with no narrative component, or situations where a legal-approved template already forbids informal docs.
When should I use this skill?
User needs help writing memos, scaling 1:1 explanations into docs, or improving leadership and async communication quality.
What do I get? / Deliverables
You publish concise, metaphor-friendly docs and messages that teammates and stakeholders can absorb without another live explanation from you.
- Async strategy or process document
- Clearer stakeholder update or narrative draft
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Draft a positioning memo after hearing the same investor question three times.
Replace a looping scope chat with a short spec others comment on async.
Shape a launch narrative that uses metaphor so readers connect the last strategic dot.
Write lifecycle emails that assume the reader never attended your live walkthrough.
How it compares
Use this insight library for leadership writing habits, not as a Figma or code review automation skill.
Common Questions / FAQ
Who is written-communication for?
Solo builders and small-team leads who write specs, updates, and strategy docs and want podcast-grade communication tactics in the agent.
When should I use written-communication?
At idea when researching positioning narratives; at validate when scoping async specs; at build and ship for plans and reviews; at launch and grow for distribution writing; at operate for incident and process memos.
Is written-communication safe to install?
Review the Security Audits panel on this Prism page; the skill is text guidance compiled from public podcast insights with no special system access.
SKILL.md
READMESKILL.md - Written Communication
# Written Communication - All Guest Insights *38 guests, 61 mentions* --- ## Alex Komoroske *Alex Komoroske* > "Maybe in 10 different one-on-ones with people on the team, I had to explain to them a strategic thing that we were doing... Well, you know what? That should probably be a document, right? If the same idea worked for 10 different people... now I'll write that document in 30 minutes and now I have it as a memorialized thing that other people can read on their own time without having to involve me." **Insight:** Scale your impact by identifying recurring verbal explanations and codifying them into asynchronous documentation. **Tactical advice:** - Identify patterns in 1:1 conversations and turn successful explanations into permanent docs. - Use metaphors to connect 'nine of the ten dots,' inviting the reader to engage and connect the final dot themselves. *Timestamp: 00:08:58* ## Boz *Boz* > "Communication is the job... it is exclusively done through the creation of artifacts or verbalizations that affect other humans. That is all there is." **Insight:** Leadership is fundamentally a communication task; if your ideas don't break through or aren't understood, you haven't done the job. **Tactical advice:** - Take extreme ownership of whether your message was successfully received by the audience. - Understand that silence and the absence of check-ins are also forms of communication. *Timestamp: 00:51:40* --- > "One is multimodality... I will give an all-hands and then write a post with the content of the all-hands, because different people are going to respond differently to these modalities." **Insight:** Using multiple channels and repeating key messages ensures that information is absorbed by diverse audiences. **Tactical advice:** - Repeat key points using different metaphors and modalities (verbal, written, visual). - Address the audience's fears and concerns at the very beginning to establish trust in your premise. *Timestamp: 00:56:46* ## Brandon Chu *Brandon Chu* > "It was the writing process itself that actually allowed me to solidify those mental models and those frameworks in my mind. And so I wasn't ahead of the game in any way. It was just I think I really wanted to disambiguate the chaos in my mind about what my job was." **Insight:** Writing is primarily a tool for the author to achieve clarity and refine mental models, with communication being a secondary benefit. **Tactical advice:** - Use writing to 'release' ideas from your mind and clear space for new thinking - Invest significant time (e.g., 40 hours) into editing and refining core ideas - Share raw, early thoughts with others to test how your internal narrative resonates externally *Timestamp: 27:21* ## Christina Wodtke *Christina Wodtke* > "They were like, "What's your confidence level on your key results? What did you do last week? And what are you doing next week?" And the last week, next week is great because it allows you to start noting down what stops you from getting shit done." **Insight:** Weekly status updates should focus on confidence levels and blockers to facilitate cross-team learning and support. **Tactical advice:** - Send weekly status updates (via email or Slack) including confidence levels (1-10) for each KR. - List 'P1' priorities for the next week and reflect on why previous priorities weren't met. *Timestamp: 00:48:13* ## Claire Hughes Johnson *Claire Hughes Johnson* > "Whenever I do write something down, I'm glad I did. So I probably do more crystallizing by writing than I would admit." **Insight:** Writing serves as a primary tool for clarifying and crystallizing complex thoughts and strategies. **Tactical advice:** - Use the act of writing to force clarity on topics you think you already understand *Timestamp: 00:06:20* --- > "Having really smart communication practices is something that I think a lot of companies don't invest in early... Do you have a newsletter? Do you have founders d