Writing Clear Instructions for Projects

Found this 1980 ad about writing clearly. 65 years later, it's still the best writing advice I've ever seen: 1) Know exactly what you want to say before you start Most people start writing and figure it out as they go. That's why most writing sucks. Thompson says outline first, write second. Revolutionary concept, apparently. 2) Start where your readers are, not where you are Don't assume people know what you know. Meet them at their level of understanding, then bring them along. Most "experts" write for other experts and wonder why nobody gets it. 3) Use familiar word combinations Thompson's example: A scientist wrote "The biota exhibited a one hundred percent mortality response." Translation: "All the fish died." Stop trying to sound smart. Start trying to be clear. 4) Arrange your points logically Put the most important stuff first. Then the next most important. Then the least important. Seems obvious, but most people do it backwards. 5) Use "first-degree" words Thompson says some words bring immediate images to mind. Others need to be "translated" through first-degree words before you see them. "Precipitation" => "Rain" "Utilize" => "Use" "Facilitate" => "Help" 6) Cut the jargon Thompson warns against words and phrases "known only to people with specific knowledge or interests." If your mom wouldn't understand it, rewrite it. 7) Think like your reader, not like yourself Thompson asks: "Do they detract from clarity?" Most writers ask: "Do I sound professional?" Wrong question. TAKEAWAY: This ad is from 1960. The internet didn't exist. Social media wasn't even a concept. But the principles of clear communication haven't changed. Most people still can't write clearly because they're trying to impress instead of express.

STOP asking ChatGPT to "make it better". Here's how to better prompt it instead: ☑ Clearly Identify the Issue Rather than a vague “make it better,” specify the exact element that needs change. For example: "Rewrite the second paragraph so it includes three concrete examples of our product’s benefits. The tone must be formal and persuasive. Remove any informal language or redundant phrases." ☑ Divide the Task into Discrete Steps Break the overall revision into a sequence of manageable tasks. For example: "Go through my instructions, step by step. – Step 1: Summarize it in one sentence. – Step 2: Identify two specific weaknesses. – Step 3: Rewrite the text to address these weaknesses, incorporating specific data or examples." ☑ Specify the Format and Level of Detail Define exactly how the final output should look. For example: "Provide the final revised text as a numbered list where each item contains 2–3 sentences. Each item must include at least one statistical fact or concrete example, and the overall response should not exceed 250 words." ☑ Request a Chain-of-Thought Explanation Ask the model to detail its reasoning process before giving the final output. For example: "Before providing the final revised text, explain your reasoning step-by-step. Identify which parts need improvement and how your changes will enhance clarity and professionalism. Then, present the final revised version." ☑ Conditional Instructions to Enforce Compliance Add if/then conditions to ensure all requirements are met. For example: "If the revised text does not include at least two concrete examples, then add a sentence with a real-world statistic. Otherwise, finalize the response as is." ☑ Consolidate All Instructions into One Prompt Integrate all the detailed instructions into a single, comprehensive prompt. For example: "First, identify the section of the text that needs improvement and explain why it is lacking. Next, summarize the current text in one sentence and list two specific weaknesses. Then, rewrite the text to address these weaknesses, ensuring the revised version includes three concrete examples, uses a formal and persuasive tone, and is structured as a numbered list with each item containing 2–3 sentences. Each list item must include at least one statistical fact or example, and the overall response must be no longer than 250 words. Before providing the final text, explain your reasoning step-by-step. If the revised text does not include at least two concrete examples, add an additional sentence with a real-world statistic." ___ Why This Works People never give enough context. And once ChatGPT answers, they never correct it enough. Think about it like an intern. Deep prompting is all about precision: give clear instructions, context & the right corrections. PS: Don't forget to use the new o3-mini model. It's crushing any other one. Yes – even DeepSeek.

I can’t stop thinking about this. If you invest in your people from day 1, they’ll invest their talents in your company tenfold. It sounds obvious, but I’ve seen firsthand how often this gets missed. I joined companies and startups with zero training: - no documentation - unclear processes - no real onboarding I was expected to figure it out as I went, and honestly, it was brutal 😭 So here’s what *actually* sets people up for success: —— 1️⃣ What does a new hire need to know but feels awkward asking? Think back to your first 30 days. ↳ How do things actually work here? ↳ Where do I go for answers? ↳ What mistakes should I avoid early on? If the answers live only in someone’s head, that’s the gap. ✅ Document anything you explain more than once. —— 2️⃣ Where are people guessing instead of being guided? When training doesn’t exist, people improvise. ↳ Clicking the wrong thing ↳ Following outdated steps ↳ Copying work that isn’t quite right That’s how errors and rework happen. Tools like Tango make this easy by turning workflows into step-by-step guides. ✅ Record one common task this week and turn it into a reusable guide. —— 3️⃣ What tribal knowledge needs to be documented? You know it’s a systems problem when there are: ↳ Constant pings ↳ Repeating the same answers ↳ Little time for deep work ✅ Have your strongest team member document one core process they own. —— 4️⃣ Are you onboarding people or overwhelming them? More information doesn’t mean better onboarding. People need: ↳ Clear priorities ↳ Time to practice ↳ Space to build confidence ✅ Use a simple 30-60-90 day framework for all new hires —— 5️⃣ Are expectations clear or just assumed? When expectations are vague: ↳ People second-guess themselves ↳ Feedback comes too late ↳ Performance feels personal instead of fixable ✅ Check in early and often and schedule 20-minute check-ins with your manager or onboarding buddy in the first 8 weeks. —— When you give people the right tools, training, and support, you get: → Faster onboarding → More consistent processes → Fewer mistakes and support tickets → Happier, more confident employees 💙 You can’t expect people to thrive without setting them up properly. Set people up to win and they will 🫶 Do you agree? #TangoPartner

✍️ Golden Rules For UX Writing. With practical guidelines on how to avoid confusion and help people understand better ↓ ✅ Always write with respect, for people as smart as you. ✅ Write mobile-first: short, plain language, bite-sized chunks. ✅ Decide what to say, then find the shortest way to say it. 🚫 Avoid long buttons: use 2–4 words, max. 25 characters. 🚫 Avoid long links: at least 8 chars, max. 8 words (55 chars). ✅ Use sentence case by default, Title Case only for headings. ✅ Use progress anchors for long forms: “Next: Payment details”. 🚫 Don’t use placeholders as replacement for labels or hints. 🚫 Don’t hide critical details or guidelines behind a tooltip. 🚫 Don’t hide frequently used filters/nav behind a button. ✅ Front-load keywords in headings and text summary. ✅ Make people hunt for destructive buttons to avoid mistakes. ✅ Leave room for translation. Expect your text to grow by 40%. 🚫 Avoid more than 20 words/sentence, 50 words/paragraph. 🚫 Never mix 2+ type treatments (color, bold, indents, italic). Good writing is an incredible opportunity. Not only to help people get work done faster and with confidence, but also to build a strong and lasting relationships. To be charming when users get started. To help without a fuss when things go wrong. To show respect and sincerity, but also understanding and care when it’s needed. One little technique that has helped me is to imagine a real person speaking to the customer before I choose words to communicate something to them. I think about how they speak — from voice and tone to speed and intonation. How casual or formal they are dressed. What their personality is. And, most importantly, what traits, values, beliefs and principles they uphold. A product then needs to match that personality, and adapt tone based on user’s context. Once we have it, we write down all the questions users might have. We re-arrange them in order of importance and severity. We decide what to say, and find the shortest way to say it. And then we test, by reading out a piece of content loud. And if it doesn’t sound right, it doesn’t read right either. ✤ Content Design in Design Systems Atlassian: https://lnkd.in/eGpzQqm4 Amplitude: https://lnkd.in/eaB85T7n 👍 DHL: https://lnkd.in/eF494fkT 👍 Duolingo: https://lnkd.in/egCSX9At Girlguiding: https://lnkd.in/eZ8zMyC3 👍 Gov.uk: https://lnkd.in/ekRadXad Intuit: https://lnkd.in/eGyBUrZ2 👍 JSTOR: https://lnkd.in/eAnyrtcu 👍 MetLife: https://lnkd.in/evVE8sqf Progressive’s: https://lnkd.in/evx_8bzY 👍 Shopify: https://lnkd.in/eAKgEHNW Skrill: https://lnkd.in/e2HGTq4q 👍 Zendesk: https://lnkd.in/euxijT5m 👍 Wise: https://lnkd.in/eWk-Mvf9 ✤ Books – Strategic Writing for UX, by Torrey Podmajersky – Content Design, by Sarah Winters – Nicely Said, by Nicole Fenton, Kate Kiefer Lee – Everybody Writes, by Ann Handley – Conversational Design by Erika Hall – Writing Is Designing, by Michael Metts, Andy Welfle ✏️ [continues in the comments ↓ ] #ux #writing

Why do so many communicators lose their audience? Often, it’s because we try to share everything. When communicating a complex project, whether it’s a new product feature, a design sprint, or a strategic pivot, we often see broadcasting ideas into the world as our goal. We want to show every wireframe, every debated nuance, and every data point we collected along the way. But our brains are not wired to absorb a stream of disconnected information. When we overwhelm our audience, we increase their cognitive load and quickly lose their attention. Our goal should be to make sure our audience understands. The antidote is structure. Structure acts as a psychological roadmap. It guides both the speaker and the listener through a clear, reasoned journey. On the Think Fast Talk Smart: The Podcast, I often talk about the importance of packaging ideas so they are easy to follow and easy to remember. One framework I often recommend for complex projects is what I call the 5P structure. It helps presenters walk their audience through a clear progression of ideas so the story behind the work is easy to understand. 1) Problem: Define the issue at hand 2) Process: Shaping your thinking 3) Proposal: Outlining the solution 4) Proof: Sharing the potential impact 5) Progress: Pointing forward Instead of overwhelming people with information, the structure guides them through the challenge you were solving, how you approached it, what you designed, the evidence behind it, and what comes next. When people can clearly follow the story, they are far more likely to trust the idea and help move it forward.

🎨🖊️ "Draw two circles under a rectangle…" "Now, make the circles connect to the rectangle" - some of the instructions that were given to me by our Head of Architecture during a recent offsite. We engaged in an exercise that underscored the importance of clear and effective communication. Each participant paired up, with one partner facing a screen displaying an image and the other facing a blank wall with a pen and paper. The challenge? The partner facing the screen had to guide their teammate in drawing the image using only directional and descriptive language. This exercise was a powerful reminder of how crucial it is to be clear, descriptive and thoughtful when sharing requirements, feedback or instructions. In the world of technology, we often fall into the trap of using complex language, acronyms, and omitting details we assume are "obvious." This can lead to confusion, misunderstandings, rework, and ultimately, wasted time. The key takeaway? Being specific doesn't always mean being overly detailed or long-winded. There's a beautiful balance between being specific and descriptive. It's about conveying the right amount of information in a way that's easily understood. Here are some common pitfalls to avoid when striving for specificity in communication: - Overloading with Details: Focus on the most relevant information to avoid overwhelming your audience. - Using Jargon and Acronyms: Consider your audience and provide explanations when necessary. - Assuming Shared Knowledge: Provide necessary context to ensure understanding. - Being Vague: Use precise language to prevent misunderstandings. - Neglecting the Audience's Perspective: Tailor your communication to the needs and understanding of your audience. I am reminded of a quote by Mark Twain: "I apologize for such a long letter - I didn't have time to write a short one." Concise communication takes time and effort, but it's always worth it. In our fast-paced world, mastering the art of effective communication is essential. It not only enhances collaboration but also drives efficiency and innovation. #Communication #Leadership #EffectiveCommunication

I’ve been working on a massive prompt that extracts structured data from unstructured text. It's effectively a program, developed over the course of weeks, in plain English. Each instruction is precise. The output format is strict. The logic flows. It should Just Work™. And the model? Ignores large swaths of it. Not randomly, but consistently and stubbornly. This isn't a "program," it's a probability engine with auto-complete. This is because LLMs don’t "read" like we do, or execute prompts like a program does. They run everything through the "attention mechanism," which mathematically weighs which tokens matter in relation to others. Technically speaking: Each token is transformed into a query, key, and value vector. The model calculates dot products between the query vector and all key vectors to assign weights. Basically: "How relevant is this other token to what I’m doing right now?" Then it averages the values using those weights and moves on. No state. No memory. Just a rolling calculation over a sliding window of opaquely-chosen context. It's kind of tragic, honestly. You build this beautifully precise setup, but because your detailed instructions are buried in the middle of a long prompt -- or phrased too much like background noise -- they get low scores. The model literally pays less attention to them. We thought we were vibe coding, but the real vibe coder was the LLM all along! So how to fix it? Don’t just write accurate instructions. Write ATTENTION-WORTHY ones. - 🔁 Repeat key patterns. Repetition increases token relevance, especially when you're relying on specific phrasing to guide the model's output. - 🔝 Push constraints to the top. Instructions buried deep in the prompt get lower attention scores. Front-load critical rules so they have a better chance of sticking. - 🗂️ Use structure to force salience. Consistent headers, delimiters, and formatting cues help key sections stand out. Markdown, line breaks, and even ALL CAPS (sparingly) can help direct the model's focus to what actually matters. - ✂️ Cut irrelevant context. The less junk in the prompt, the more likely your real instructions are to be noticed and followed. You're not teaching a model. You're gaming a scoring function.

I used to think using complex terminology demonstrated expertise. That "leveraging synergies" and "utilising frameworks" showed I belonged in business conversations. The reality? No one was impressed. They were just confused. 💡 The breakthrough came when I started writing exactly how I think not how I speak. This transformed my newsletter engagement (open rates jumped over 30%) Here's why writing how you think (not how you speak) works: 1. Authenticity cuts through noise - Your natural thought stands out in a sea of corporate-speak - Readers sense when you're being genuine vs. performing - Trust builds faster with authentic communication 2. Simplicity enables action - Clear instructions get implemented - Complex directions get abandoned - Young entrepreneurs especially value directness 3. Relatable language builds connection - Industry jargon creates outsiders - Conversational tone creates community - Speaking their language shows you understand their world 📊 In marketing specifically: - Conversational emails see 17% higher click-through rates - Simple language in sales pages increases conversion by 2.1x - Readability improvements can boost engagement by 58% ➡️ Your readers aren't stupid. They're busy. They want to understand your point in seconds, not decode your buzzword bingo. When writing for my newsletter, pitching to investors, or speaking to young entrepreneurs, I constantly remind myself: "If my 16-year-old self wouldn't understand it, it needs a rewrite." Clear writing shows clear thinking. So next time you write anything: If a shorter word works, use it If you wouldn't say it in casual conversation, don't write it If it sounds like a "business robot," start over Simple, isn't it?

Most HR teams think their onboarding is solid. → Laptop ready. → Paperwork completed. → First day meet and greet? Check. But here is the truth we see behind the curtain: Most teams skip the parts that matter most for long-term success. Here are two steps most teams forget during onboarding and what to do instead. 1. 𝗖𝘂𝗹𝘁𝘂𝗿𝗲 𝗰𝗹𝗮𝗿𝗶𝘁𝘆 𝘁𝗵𝗮𝘁 𝗴𝗼𝗲𝘀 𝗯𝗲𝘆𝗼𝗻𝗱 𝘁𝗵𝗲 𝗵𝗮𝗻𝗱𝗯𝗼𝗼𝗸 Telling someone your values is easy. Showing them how the team 𝘳𝘦𝘢𝘭𝘭𝘺 works is the magic. New hires do not struggle with the handbook. They struggle with the unwritten rules. Give them real language instead of vague gestures. For example, instead of asking… "Do you use Slack?" Try saying… "Our team lives in Slack during business hours. We expect same day responses for most messages and a quicker reply if it is from your manager or during core hours." Other examples to spell out clearly: • How often leaders drop in for updates • When cameras are expected on • How people give feedback • When it is okay to block focus time • Preferred communication style (short pings or detailed notes) And pair them with a culture buddy. Someone who can answer real questions like "Is it normal to send a calendar note before messaging the VP?" That saves so much social anxiety and avoids awkward first month missteps. 2. 𝗥𝗼𝗹𝗲 𝗰𝗹𝗮𝗿𝗶𝘁𝘆 𝗮𝗻𝗱 𝗺𝗲𝗮𝗻𝗶𝗻𝗴𝗳𝘂𝗹 𝗲𝗮𝗿𝗹𝘆 𝗰𝗵𝗲𝗰𝗸𝗽𝗼𝗶𝗻𝘁𝘀 A job title is not direction. People want to know exactly how to succeed. → Get specific. → Paint the picture. Instead of saying… "You will lead onboarding." Try… "In your first 30 days, you will run onboarding for three new hires. Success looks like zero missed system access steps, plus a feedback survey score of 4.5 or higher." Then schedule a 30 day check in. Not to judge. To support. Ask questions like: "What has been clear so far?" "What has been confusing?" "Where do you need resources or examples?" And tell them one thing they are doing well. Everyone needs a confidence anchor early. Strong onboarding is not fancy. It is clear, human, and consistent. Which onboarding detail made the biggest difference for you in a new role? If this sparked ideas, share it with another HR pro building better onboarding. #OnboardingTips #HRLeadership #PeopleFirst ♻️ I appreciate 𝘦𝘷𝘦𝘳𝘺 repost. 𝗪𝗮𝗻𝘁 𝗺𝗼𝗿𝗲 𝗛𝗥 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀? Click the "𝗩𝗶𝗲𝘄 𝗺𝘆 𝗡𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿" link below my name for weekly tips to elevate your career!

I’ve trained in rooms where people speak English, but think in Marathi, Hindi, Bengali, Tamil Same company, same goals, but completely different communication styles. We love patting ourselves on the back for being diverse. But when a South Indian team feels a North Indian manager is "too aggressive," or a Gen Z employee thinks their Gen X boss is "dismissive", we call it a "communication gap." When really it's India's invisible boardroom barrier. Because while communicating, you’re navigating: 🔹 Cultural nuances 🔹 Generational gaps 🔹 Language preferences 🔹 Urban vs regional perspectives And if you're not adapting, you’re alienating. Here's my 3A’s of Cross-cultural communication framework: 1. Awareness: Recognize that your communication style is shaped by region, generation, and upbringing. It's not universal. 2. Adaptation: Match your message to your audience. One style doesn't fit all rooms. 3. Ask: When in doubt, clarify: What does yes mean here? How do you prefer feedback? What's the protocol for disagreement? India's diversity is incredible. But if we are not actively learning to communicate across cultures, not just languages, we're wasting it. P.S. What's your biggest cross-cultural communication struggle? #CrossCulturalCommunication #AwarenessAdaptationAsk #3AsFramework #Awareness #Adaptation #Ask #CommunicationGaps