Fleurs de colza dans le sud-ouest de la Chine

Creating a course can be overwhelming. Luckily, AI can make it 10x easier: Quick context: Over the past few weeks, I had to create 4 different modules for a new cohort I was running. Each module needed to be very in-depth & comprehensive (3-5k words each). And I had a tight deadline to finish them. Luckily, I found a way to use AI to streamline the whole process (without sacrificing quality). Let’s break it down: Step 1: Outline your module The best thing you can do before you start creating your course module: Outline it. That will give you clarity over the direction you’re going before you even start writing. Now, what does “outlining” mean exactly? For me, I means: 1/ Clarifying the overarching structure & sections of the piece. 2/ Brain-dumping some initial ideas for what could potentially go inside each section. Now, I typically do my outlines manually because I feel good about doing that without the AI’s help. But if you’re new to creating big, long-form pieces like this, you can definitely get AI to help you with this too. Step 2: Clarifying the outline (with AI) After I have the v1 of my outline, I share it with my AI tool (Claude) so it can: ? Analyze it ? Look for potential gaps ? Suggest potential tweaks or additions This is super helpful because even though I am the “expert,” there’s usually things I forget or overlook. So this is a great & very easy way to identify those blindspots. Now, after reviewing & implementing some of the AI’s suggestions, I create my final outline & move onto the next step: Step #3: Drafting your module (with AI) With my outline finalized, I then ask Claude to help me start drafting my module. Now, this is probably one of the most nuanced steps in the process. Because if you don’t do a good job with your prompting here, the quality of the output will suffer - a lot. So, here’s a few things I do to avoid that: First, I share with Claude any pieces of content I have on this topic. That way, it can use them as a starting point. Second, I also prompt Claude to ask me any necessary clarifying questions. The goal is to make sure it has access to all the specific knowledge & context it needs to draft the module without hallucinating. Lastly, I share a few of my best pieces of writing so it can mimic my writing style & voice. Then, once Claude is done making the first draft, I move onto the final step: Step 4: Editing the draft At this point, I usually just move Claude’s draft to a Notion doc so I can make all the final edits. (But you can explain the changes you’d like to make to your AI, and have it execute them.) Either way, this step is crucial. Because no matter how great your outline & your prompts were, the draft will never be perfect. And that’s OK. The goal is not to create a “perfect” draft. The goal is to have the AI do 80% of the heavy lifting so you can just fill in the gaps at the end. Anyway - hope this was helpful. Have any follow-up questions? Lmk below.

How the military writes emails: I served in the Navy. And I learned a few tactics that changed how I approach email at work. The secret? Let's call it military precision. In the military, precision isn't just about the drill. It's about how folks communicate: Everything from mission briefings to day-to-day emails. Here's the breakdown: - BLUF: Bottom Line Up Front ? Always start with your main point. - Start emails with action-oriented subject lines ? e.g., "INFO: Q4 Sales Report" or "REVIEW: Client Proposal Due 12/15" - Use Active voice and BE direct ? "The team completed the project" is leagues better than "The project was completed by the team" - Follow the 1 idea per paragraph rule ? (It really forces you to be clear and concise) - Use bullet points where possible ? The bullet points aren't just a layout choice. They force you to be concise. Here's the result: Faster responses. Quicker decision-making. Clearer communication. This approach wasn't just about being formal. It's about getting things done. Whether it's a military mission or a corporate task... Clear and decisive communication wins the day, every time. Try it and see what difference it makes. What’s your take on effective email communication? Any protocols that give consistent results? ? Repost to help folks in your network email with military precision. ? Follow Kabir Sehgal for daily tips on growth, productivity, & building your portfolio career.

I meet B2B companies in the streaming media space every day....all up and down the supply chain. And more often than I'd like, I get lost when I'm getting pitched. I find it that a lot of companies (for whatever reason, probably several, and I can think of a few) overcomplicate their product marketing. Overly technical info, buzzwords, high-level speak that sometimes makes me feel like an idiot for not fully grasping what a company does within the first 5 minutes. My approach at 43Twenty for the past 6 years is to align a brand narrative around 3 things - these are non-negotiable. 1. Why does this matter? If you drop a buzzword, be sure to immediately follow it up with why it matters. Btw, why it matters to a CEO and CFO could be completely different. A CEO does not care about about "no code". But they might care that your product can empower non-technical people across various departments to quickly and effectively build applications. And the CFO might care that this could "significantly reduce expenses by 80%" Tie "why it matters" to a business outcome or a persona's pain point. Make "the why" relatable. Evoke emotion. 2. Explain it to a 5th grader Maybe I'm wrong here, but I don't whether you win or lose a contract is going to be based on how overly technical you sound. Obviously, most of you are tech companies and you need to talk to the CTO...but if the rest of the C-Suite has no flipping clue what you're talking about, that's a problem. And more often than not, it's someone technical that's holding the wallet. Your content's gotta resonate with everyone. What I do is make sure that a 5th grader can understand what a company does. Btw, two people that are amazing a simplifying complicated things in easy to grasp terms are Alan Wolk Jason Thibeault. 3. Use Cases I will admit that I learn via use cases. Don't tell me in adjectives and shiny buzzwords what your company does. Tell me, with a use case, how you help someone solve a problem. If you can't talk about your customers, that's fine. Anonymize the use cases. Somepeople learn better this way. At least I do and I'm sure there's more weirdos just like me. I apply these principals over at The Streaming Wars and BIG OL' KUDOS to the team for their coverage of Gracenote's launch of Data Hub and its 2024 State of Play Report. They didn't just say "Gracenote did this, announced that, here's the quote from the press release" I challenged them to explain what the heck Data Hub is in a way that a 5th grader could understand -- or maybe just so I could understand it ??♂? After all, what's the point of PR and reaching the a masses if not everybody is grasping the message or what it actually means? Btw, there's a 4th thing.... 4. Explain how you're different. I continually get feedback from media companies (your buyers) that they can't tell the difference between one solution provider from another. (Welp, I just hit the character limit on this post) ?? you

Don't try to sound smart. Try to be useful. 3 years ago, I deleted my most "impressive" newsletter. 2,000 words. Multiple frameworks. Industry jargon everywhere. 14 drafts. It felt "professional." It felt "high-level." It felt wrong. That week, a CEO guest spoke to me before our podcast: "You know why I listen to your show? Because you make things simple." Then she paused. "But your newsletter... sometimes I need a dictionary." That changed everything. I opened my analytics that night. The pattern was clear: My "smartest" content performed worst. My simplest advice spread fastest. I had been: ? Writing to impress peers ? Stacking jargon on jargon ? Trying to sound "intellectual" ? Hiding behind complexity So I started over. New rules: 1. Write like I talk 2. No words I wouldn't use at dinner 3. Every piece needs a clear "do this" Example: Before: "Contemporary market dynamics necessitate strategic pivots in content optimization." After: "Test what works. Double down on what people love." That decision? It built my entire business: ? The podcast grew exponentially ? The newsletter became my main lead generator ? Sponsorship deals rolled in ? Speaking opportunities opened up Best feedback I get: "Used your advice. Landed the client." "Finally, someone who makes this simple." "Implemented this today. It worked." The truth about expertise: ? Rookies hide behind jargon ? Veterans embrace simplicity ? Masters focus on impact This philosophy drives everything: ? How I write ? How I speak ? How I teach ? How I coach Because here's what I learned: Value beats vocabulary. Always. 3 questions before publishing: 1. Would my mom get this? 2. Can someone use this today? 3. Did I remove all the fluff? Remember: Your audience's success is your scorecard. Not your vocabulary. Today? That decision to choose simplicity over sophistication was worth millions. But more importantly: It actually helped people. // Agree? Simple or complex content - which actually helps you more? Share below. #ContentCreation #Podcasting #Writing #ValueFirst

Year to date, I've published 379 posts to Linkedin, garnering 2.2M impressions, 20k likes, 10k comments and 843 shares. I write all of my own posts. I've asked the Databox marketing team to ghost write things for me, but I end up rewriting them quite a bit. (It's still helpful to get their drafts since the quotes, video/images and data they gather, as well as ideas for angles saves me a lot of time.) Recently, Heather Adams, our new VP Marketing asked Nevena Rudan, our market research analyst to try ghost writing specific posts for me. As one of her first moves, she fed in my most successful posts into ChatGPT and asked it to create a list of guidelines for her. ChatGPT *almost* nailed it. (See below. I made a few tweaks.) 1?? Start with a Bold or Contrarian Hook: Begin your post by challenging prevailing industry norms or popular opinions to capture attention. This approach sets the stage for a compelling narrative that invites readers to rethink established ideas. 2?? Establish Authority Early: Mention your relevant experience, accomplishments, or results early in the post. This builds trust and credibility with your audience, making your arguments more persuasive. 3?? Incorporate Data and Real-World Examples: Use quantitative data, research findings, and real-world examples to substantiate your claims. This not only supports your narrative but also illustrates the practical implications and successes of your points vividly. 4?? Offer Practical Solutions: Present actionable solutions and alternatives after discussing problems or challenges. This approach not only adds value but positions you as a thought leader who not only identifies issues but also proposes effective solutions. 5?? Optimize Formatting for Engagement: → Use bullet points to break down complex information into digestible pieces. → Ask questions in posts to get readers thinking and commenting → Include concise summaries or takeaways at the end of sections to encapsulate key messages and aid in retention. 6?? Authoritative but conversational tone: → Authoritative & Insightful: Write in a direct, knowledgeable manner that reflects deep industry understanding and offers nuanced analyses of complex issues. → Conversational & Approachable: Maintain a conversational tone that makes even the most complex or technical ideas accessible and engaging for a broad audience. → Forward-Thinking & Strategic: Focus on future-proofing strategies & adapting to tech advancements, which showcases a strategic mindset & a proactive approach to industry changes. When I speak with other business owners and executives who want to leverage Linkedin better to market and prospect, I often try to explain these things to them. But, I've never sat down to write out a full guide. It's taken me time & repetitions to be able to write this way. It's not easy, but I wouldn't do it any other way -- whether I'm getting help from my team or ChatGPT. Hope this helps someone else.

The best learning during my time at Amazon was improving my writing. Here is my list of how to edit your writing to improve it and how to get an idea down on paper in the first place. TL;DR craft compelling documents by anticipating reader needs, addressing potential questions, and clearly articulating the desired outcome. This will take time and a lot of editing. Make your writing better, editing tips: A. Use data and logic to lead the reader to a conclusion. Using adverb and adjective is less effective. B. Eliminate weasel words C. Use readable scores to get data on how readable your doc is now and improve it D. Use read-a-loud extension or read it out loud yourself E. Edit words that don't add value. Look for repetitive language. Don't tax your reader with big words How to crafting an idea in writing: 1. Start with bullet list of what your thinking about 2. Start by writing with limited edits. Sleep on it and then edit like crazy. 3. Know your reader and write for them. 4. Write down FAQ to the end of a doc that you think your reader will have. If you can, you should answer these in your writing but it's not always possible.? 5. Take ownership not ask for ownership. If you are asking for ownership or asking the reader to force someone to do something you are doing it wrong.??? 6. Ask why 5 times on customer facing questions to get to the detail why this is important 7. Think in 3s. How would you explain this with a 3 word (The Title), 3 sentences (TLDR), 3 paragraphs (a 1 page page overview), 3 pages (longer form with more detail). 8. Bonus: add some long term thinking topics to your doc. If the reader is excited about what you are writing about, give them more and think big about the future. 9. Close with what decision you need help from the reader 10. Finally writing a couple page document should take a week(s) not days or hours to complete.

In the past 10 years, I’ve reviewed 100s of design docs. Here’s how to write review-ready design docs in 3 simple steps. 1/ Start with a skeleton, write these: ? Metadata (Title, authors, status, date, reviewers, approvers) ? Context and background ? Problem statement ? Summary or tl;dr (Optional) ? Proposed solution details with tradeoffs and selection rationale? ? Other alternatives considered ? Failure modes of the proposed solution ? Open Questions ? References (Optional) 2/ After the skeleton, fill in the content under these headings. -If there are sub-sections, add sub-headings.? -Provide examples and sample calculations. -Use bullet points and lists wherever applicable -Include architectural diagrams, graphs and tables. 3/ If the document is large, put a summary after the problem statement. Start with the skeleton, take it one step at a time, and before you know it, you are done! Remember, a good design doc: -helps understand design decisions and implementation details -helps in identifying potential issues and challenges early? -gives a clear understanding of the architecture -serves as a reference doc during the project While you write and review, make sure your work follows these guidelines. I know writing detailed docs doesn’t come naturally when you’re focused on problem solving. But it’s an essential skill you have to learn to level up. just follow a simple procedure, practice and you’ll get the hang of it. – P.S: Check out additional writing tips in the comments below ↓

?? Have you ever tried to communicate a complex tech issue, only to be greeted with puzzled looks? What if I told you that the key to clear communication might just be in your garage? Communicating complex concepts in understandable terms is no small feat. Here are some tactics that have significantly helped me: 1. Recognize and empathize ??: Imagine your car's engine is acting up. The mechanic says it'll take two weeks for a fix, involving a transmission overhaul, timing belt replacement, and fuel injection recalibration. Sound complicated? That's exactly how your audience feels when they encounter technical jargon. Acknowledge this! 2. Analogies are your friend ??: Find common ground in a domain familiar to both you and your audience. Use this shared understanding as a foundation to explain the technical challenge at hand. 3. Destination over journey ??: Focus on the what (the outcome) and why (the benefits), not the how (the technical process). It's the results that matter most to your audience. 4. Foster a dialogue ???: Encourage questions and create an atmosphere where non-technical stakeholders feel comfortable to engage. Their inquiries can also help you refine your communication approach. 5. Visual aids are invaluable ??: Diagrams, flowcharts, and other visuals can make complex ideas more accessible and easier to grasp. #leadership #communication

How founders think technical content works: 1. Explain every feature 2. Use all the industry terms 3. Show how innovative we are 4. Target "technical decision makers" Versus how technical content *actually* works: A DoD drone startup taught me this the hard way. They were 22-year-olds building defense tech. But we wrote like we were selling to Fortune 500. Technical buyers focus on: 1. Specific use cases they relate to 2. Plain language about complex problems 3. Proof you understand their world 4. How you solve their exact pain point Your technical content doesn't need more jargon. It needs more clarity. Examples from working with 100+ technical founders: The best performing content: - Focuses on one specific problem - Uses customer language (not marketing speak) - Shows deep understanding of their workflow - Makes complex things simple The worst performing content: - Tries to sound smart - Stuffs in technical buzzwords - Focuses on features over problems - Makes simple things complex Technical content doesn't need to be about proving how smart you are it should prove you understand their world Want more insights on creating content for technical products? Follow me for weekly tips

Structured writing isn't just for technical writers ... its for anyone who deals with content at scale, including educators. In my recent work developing virtual exchange courses between American and Polish students, I discovered that creating consistent learning materials across cultural contexts mirrors the challenges technical writers face when documenting software for global audiences. Both roles require systematic approaches that maintain quality across diverse contexts. When I started using structured frameworks for my course materials I found I could rapidly adapt content while maintaining pedagogical effectiveness. Here's the systematic approach that evolved: 1?? Content Pattern Analysis I examined my most successful assignments, identifying recurring elements that consistently engaged students. This revealed core components—learning objectives, cultural context bridges, and assessment criteria—that could be systematized. 2?? Framework Development These patterns informed a structured framework where each assignment component became a reusable block that can be adapted for different cultural contexts: ? Learning objectives ? Background information ? Rationale ? Instructions ? Criteria 3?? Implementation and Testing I began small, converting one successful assignment into this structured format. Testing revealed that what worked for American business writing students also resonated with Polish students when properly structured. This systematic approach transformed what initially seemed like a daunting cross-cultural challenge into a scalable content operation. Bonus ... I can now use these assets to build more content for other contexts using AI.