Writing

𝗖𝗹𝗲𝗮𝗿 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗶𝘀𝗻'𝘁 𝗮𝗯𝗼𝘂𝘁 𝘄𝗿𝗶𝘁𝗶𝗻𝗴. 𝗜𝘁'𝘀 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴. I came across a video about why clear documentation matters, and although it was lighthearted, it captured a challenge I've seen repeatedly while working with organizations. Most teams believe they have documented their processes. What they've often documented are the steps, while leaving out the judgment behind them. Experienced people fill in those gaps automatically because they know which shortcuts to take, which exceptions to ignore, and which decisions require extra attention. New colleagues don't have that advantage, which is why the same document that looks perfectly clear to one person can be frustratingly incomplete to another. 𝗜𝗳 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗼𝗻𝗹𝘆 𝘄𝗼𝗿𝗸𝘀 𝘄𝗵𝗲𝗻 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝗮𝗿𝗲 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗼𝗼𝗺, 𝗶𝘁 𝗶𝘀𝗻'𝘁 𝗮 𝗽𝗿𝗼𝗰𝗲𝘀𝘀. 𝗜𝘁'𝘀 𝘁𝗿𝗶𝗯𝗮𝗹 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲. The strongest organizations don't become resilient because they hire exceptional people. They become resilient because exceptional people make their knowledge transferable. They create documentation that explains not only what to do, but also why it matters, when to adapt, and how success should be measured. That's becoming an increasingly valuable leadership skill because every new hire, every cross-functional project, and every technology initiative depends on the same foundation. Clarity. 𝗪𝗵𝗲𝗿𝗲 𝗱𝗼𝗲𝘀 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺 𝘀𝘁𝗶𝗹𝗹 𝗿𝗲𝗹𝘆 𝗼𝗻 𝘁𝗿𝗶𝗯𝗮𝗹 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗰𝗹𝗲𝗮𝗿 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻? #Leadership #KnowledgeManagement #FutureOfWork #Management #Communication Source: Noelidavid

🪂 How To Make Your Design System AI-Ready (https://lnkd.in/dtnpy7CM), a practical guide on how to reduce drifts, minimize mistakes, maintain context and improve the quality of AI-generated prototypes — with structured spec files, automated auditing and token layers. Put together by Hardik Pandya from Atlassian. --- 🔹 1. Design Decisions Are Infrastructure AI-generated prototypes often don't deliver consistently decent results because of tiny inconsistencies scattered all across a design system. Often it's decisions made but not documented, hard-coded values never cleaned up, or relying too much on AI making sense of mock-ups or design flows on its own. Unsurprisingly, better AI prototypes come from better data — but also from better human guidance. We shouldn’t assume that AI knows how to choose the right component, and how to design with accessibility in mind. It needs priorities, a clear path on how we make decisions, design principles, examples, do's and don'ts. In fact, we should treat design decisions as infrastructure. That means that every time we make a decision — not just a design decision, but even decision on how actually prioritize our work and how we make decisions around here — it must find a path into the spec file that is then consumed by AI. --- 🔶 2. Three Layers: Spec Files + Token Layer + Audit To ensure quality, we establish design principles, guidelines, rules in a form of “spec files”). It's structured Markdown files that include spacing rules, color choices, component usage guidelines, priorities etc. AI is going to read and reuse that spec file every time it's going to generate a prototype. Because the spec files are text files, it's much more cost-effective, but also much more accurate just because we don't rely on AI recognizing or decoding patterns from mock-ups, but gets specific guidelines instead. In fact, extending code is often a more effective way than generating code from mock-ups. Token layer lists and keeps updated all tokens used throughout the design system. AI always chooses from a closed set of named variables instead of inventing plausible values ad-hoc. An audit script catches what AI gets wrong. It scans the prototype and flags every hard-coded value and flags it if necessary. It can be a regular software doing that, with AI waiting for its feedback to come back. Finally, when a design system ships updates, a sync routine flags which spec files need updating. The goal is to make sure that AI always reads up-to-date, current specs, not the ones written against an outdated version. --- 🔺 3. Examples of AI-Ready Design Systems ⌾ Atlassian: https://lnkd.in/dVsGc3Cp ⌾ Carbon: https://lnkd.in/d4zq4WWb ⌾ CMS Design System: https://lnkd.in/dHHzV3en ⌾ Nordhealth: https://lnkd.in/d8C4j2ZA Yet again, AI can’t magically resolve technical debt or design debt — it needs guidance, decisions, priorities and principles.

Every person should have one folder in their computer that is the "In Case of Death" folder... and this is how it is structured... The folder is used to manage and pass on one's assets to successors easily... and to avoid any legal hassles. This folder is divided into 5 parts: 1/ Personal IDs - Birth Certificate - Marriage Certificate - Aadhaar and Passport - Divorce Decrees - Change of Name Affidavits 2/ Legal & Estate Management Documents - Last Registered Will with notarized copy - Succession Certificates for Movable Assets - Guardianship Documents for minor children / dependants 3/ Financial Assets and Accounts - Bank Account details and statements - Demat Account, Shares, Mutual Funds, Investment Portfolio - Insurance Policy Documents with Beneficiaries - Outstanding loan documents - Bank Locker or Safe Deposit Locations and Access details 4/ Property Documentation - Real Estate and Business - Property Deeds and Titles for Real Estate - Mortgage Documents - Rental Agreements - Business Ownership Documents and Succession Plan 5/ Digital Assets and Access Information - Email with recovery information - Social media contact and legacy contact preferences - Domain names, Cloud Storage - Digital Subscriptions of material value The best way to manage passwords here is to provide access to Password Managers where you can add an Emergency Contact who can access all passwords in case of such conditions. There are apps like 1Password, NordPass and Keeper which offer printable PDF documents for emergency access that can be kept in this folder. These apps allow a waiting period from last activity after which the emergency contacts can use the data. Also, please ensure that you submit all such documents for probate and get them drafted by a trusted lawyer. I would also hope you would tell trusted family members about where you have stored this information so that they can access it when required. Above all, wish you all a long and healthy life. #casarthakahuja

As a junior lawyer, I had to learn how to make it easy for supervisors to review my work. In case it helps, here's a step-by-step guide (with an example): 1️⃣Make it clear what the matter / document is and when input is needed. 2️⃣ Set out the context and approach to preparing the deliverable What needs to be reviewed, how was it prepared, and what’s the timeline? If you're attaching a document, include the live link to your file management platform (e.g. iManage or Sharepoint) as well as a static version. 3️⃣ Set out the next steps and your ask Make it clear what your supervisor needs to review. Set this out at the top of your email and proactively provide some recommendations. You can also follow up in person to make sure deadlines aren't missed. 4️⃣ Explain how the draft is marked up Make it easy to navigate with specific questions (either in the document or extracted in the email). If there are mark ups against a particular document / version, identify what that is. 5️⃣ Summarise your inputs Let them know what your draft reflects, and attach the relevant inputs so they can see everything in one place. This will give your supervisor confidence that you've captured everything, and make it easier for them to check your work. 6️⃣ Flag key aspects / assumptions If there are key assumptions / principles that have a big impact on how your draft is prepared, it's helpful to set them out in the email as a point of focus. Try to also set out the relevant clause / section / reference where possible. Is there anything else that you'd add? What else have you found helpful in making drafts easier to review, either as a junior lawyer or a supervisor? ------ Btw, if you're a junior lawyer looking for practical career advice - check out the free how-to guides on my website. You can also stay updated by sending a connection / follow. #legalprofession #lawyers #lawstudents #lawfirms

The New York Times just revealed everything wrong with how brands think about creators. Their headline yesterday: "How Brands Are Taking Back Social Media from Influencers" “Taking back?" As if social media was ever theirs to begin with. The Times covered Hasbro hiring a full-time creator for Nerf. Smart move. But they missed the bigger pattern. From my years at YouTube, Facebook, and Spotter, here's what the best brands are actually doing: 𝗧𝗵𝗲𝘆'𝗿𝗲 𝗻𝗼𝘁 𝘁𝗮𝗸𝗶𝗻𝗴 𝗯𝗮𝗰𝗸 𝗰𝗼𝗻𝘁𝗿𝗼𝗹. 𝗧𝗵𝗲𝘆'𝗿𝗲 𝗳𝗶𝗻𝗮𝗹𝗹𝘆 𝗹𝗲𝘁𝘁𝗶𝗻𝗴 𝗴𝗼 𝗼𝗳 𝗶𝘁. The winners aren't picking one type of creator. They're building portfolios: USER-GENERATED CONTENT (UGC) The RealReal gave their superfan editorial control of their Substack. No brand guidelines. No approval process. Result: Authentic enthusiasm that converts. CREATOR-GENERATED CONTENT (CGC) Traditional influencer partnerships. But the smart brands aren't micromanaging scripts anymore. They're trusting creators to know their audiences better. EMPLOYEE-GENERATED CONTENT (EGC) The massive blindspot. Your team is already creating content — just not for you. Because you haven't given them permission to be themselves. The Times frames this as brands "taking back" their narrative. But the real winners are doing the opposite:  • Your barista with 50K on TikTok doesn't need your talking points  • Your designer's YouTube following trusts them, not your brand guidelines   • Your customers' real results beat any scripted testimonial I've watched this evolution from inside the platforms. The brands winning aren't choosing between UGC, CGC, or EGC. They're orchestrating all three by replacing control with trust: → Customers showing unfiltered results → Creators bringing their authentic voice → Employees sharing real insider perspectives While the NYT thinks this is about "taking back" social media, smart brands are asking: "How do we empower EVERY authentic voice in our ecosystem?" The best content strategies I've seen don't come from controlling the message. They come from trusting the messengers. In 2025, your brand voice isn't what you say. It's who you trust to speak for you. Your move. #CreatorEconomy #ContentStrategy #BrandContent

McKinsey & Company 𝗮𝗻𝗮𝗹𝘆𝘇𝗲𝗱 𝟭𝟱𝟬+ 𝗲𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗚𝗲𝗻𝗔𝗜 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁𝘀 — 𝗮𝗻𝗱 𝗳𝗼𝘂𝗻𝗱 𝗼𝗻𝗲 𝗰𝗼𝗺𝗺𝗼𝗻 𝘁𝗵𝗿𝗲𝗮𝗱: ⬇️ One-off solutions don’t scale. The most successful projects take a different path: They use open, modular architectures that enable speed, reuse, and control. → Designed for reuse → Able to plug in best-in-class capabilities → Free from vendor lock-in This is the reference architecture McKinsey now recommends — optimized to scale what works while staying compliant. It consists of five core components: ⬇️ 𝟭. 𝗦𝗲𝗹𝗳-𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝗽𝗼𝗿𝘁𝗮𝗹: → A secure, compliant “pane of glass” where teams can launch, monitor, and manage GenAI apps. → Preapproved patterns, validated capabilities, shared libraries. → Observability and cost controls built-in. 𝟮. 𝗢𝗽𝗲𝗻 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 → Services are modular, reusable, and provider-agnostic. → Core functions like RAG, chunking, or prompt routing are shared across apps. → Infra and policy as code, built to evolve fast. 𝟯. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 𝗴𝘂𝗮𝗿𝗱𝗿𝗮𝗶𝗹𝘀 → Every prompt and response is logged, audited, and cost-attributed. → Hallucination detection, PII filters, bias audits — enforced by default. → LLMs accessed only through a centralized AI gateway. 4. 𝗙𝘂𝗹𝗹-𝘀𝘁𝗮𝗰𝗸 𝗼𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆 → Centralized logging, analytics, and monitoring across all solutions → Built-in lifecycle governance, FinOps, and Responsible AI enforcement → Secure onboarding of use cases and private data controls → Enables policy adherence across infrastructure, models, and apps 5. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻-𝗴𝗿𝗮𝗱𝗲 𝗨𝘀𝗲 𝗖𝗮𝘀𝗲𝘀 → Modular setup for user interface, business logic, and orchestration → Integrated agents, prompt engineering, and model APIs → Guardrails, feedback systems, and observability built into the solution → Delivered through the AI Gateway for consistent compliance and scale The message is clear: If your GenAI program is stuck, don’t look at the LLM. Look at your platform. 𝗜 𝗲𝘅𝗽𝗹𝗼𝗿𝗲 𝘁𝗵𝗲𝘀𝗲 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁𝘀 — 𝗮𝗻𝗱 𝘄𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝗺𝗲𝗮𝗻 𝗳𝗼𝗿 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲𝘀 — 𝗶𝗻 𝗺𝘆 𝘄𝗲𝗲𝗸𝗹𝘆 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿. 𝗬𝗼𝘂 𝗰𝗮𝗻 𝘀𝘂𝗯𝘀𝗰𝗿𝗶𝗯𝗲 𝗵𝗲𝗿𝗲 𝗳𝗼𝗿 𝗳𝗿𝗲𝗲: https://lnkd.in/dbf74Y9E

Working with multiple LLM providers, prompt engineering, and complex data flows requires thoughtful organization. A proper structure helps teams: - Maintain clean separation between configuration and code - Implement consistent error handling and rate limiting - Enable rapid experimentation while preserving reproducibility - Facilitate collaboration across ML engineers and developers The modular approach shown here separates model clients, prompt engineering, utils, and handlers while maintaining a coherent flow. This organization has saved many people countless hours in debugging and onboarding. Key Components That Drive Success Beyond folders, the real innovation lies in how components interact: - Centralized configuration through YAML - Dedicated prompt engineering module with templating and few-shot capabilities - Properly sandboxed model clients with standardized interfaces - Comprehensive caching, logging, and rate limiting Whether you're building RAG applications, fine-tuning foundation models, or creating agent-based systems, this structure provides a solid foundation to build upon. What project structure approaches have you found effective for your generative AI projects? I'd love to hear your experiences.

15 years ago, I wrote "Write Better, Sell Better". The tagline that defined my career. Since then, I've written copy for Fortune 500 companies, projects that made millions, and taught copywriting at the university → Yep, writing is my life. But you don't have all semester long to learn. This post contains my 7 biggest writing lessons: (Save and repost this 60-second class ♻️) --- 1. Clarity is 90% of your writing Clarity beats cleverness 10 times out of 10. Remember: First, write clearly. Then, write creatively. Most focus on "creative" right off the bat = big no. (If you can do both, jackpot) --- 2. Use signposting to showcase authority I teach this technique to every single client. (This sentence you just read was a signpost) Signposts are short "signals" to your expertise and results. Think of them as signs on the side of the road, which allow you to "trust" the journey you're on. Can you notice where else I used it in this post? 😉 --- 3. Too much copy? Make it choppy. Here are 2 examples (the second one is better): Sometimes, we write super long sentences that we have no time to breathe and neither do our readers. Sometimes, we write super long sentences. We have no time to breathe. And neither do our readers. Chop it up! It's easier to read. --- 4. Write unselfishly. Edit relentlessly. Think about it. Writing is 80% editing. You are tweaking, optimizing, and making things sound perfect. One bit of advice: Don't hold back. Edit (ehm, delete) anything that isn't on-topic. I've deleted probably 40% of this post. --- 5. Use sensory words. Add texture to text. That had to hurt! → That had to "sting"! Having a bad day? → Having a "rough" day? A seamless process → A "silky-smooth" process All of the 2nd descriptions above can be "felt". It's how your readers "touch an emotion", not just "read text". --- 6. Never write to "everyone" Remember this for all time: "Everyone" is not your audience. Sales happen when your prospect can clearly "see" themselves in your writing. So how do you go about this? --- 7. The "Dear son" writing method Pick "one" person to speak to → I speak to my son. For you, it could be your best friend, the old you etc. I start everything with "Dear son" and end with "Love, Dad". In the end, I simply delete these 2 parts. Doing so creates such a powerful connection with your readers + a consistent tone of voice. With every word. Where there's connection, there's trust. And where there's trust, there's sales. Words to live by. --- Write Better, Sell Better = that's the whole game! Let me know which lesson you enjoy the most. Professor Jay, out. (Repost this for your network ♻️)

Want to stay motivated every single day? Borrow a strategy from Harvard. Then borrow another from stand up comedy. Together, they’re a powerhouse for momentum, motivation, and mastery. Here’s how it works: Let’s start with Harvard. Researcher Teresa Amabile studied 12,000 daily work diaries across 8 companies. She wanted to know: What truly motivates people on a day to day basis? What she found changed how we understand drive. The #1 driver of daily motivation wasn’t: Money Praise Perks It was progress. The days people made progress on meaningful work were the days they felt the best. Progress isn’t a luxury. It’s a psychological necessity. So how do we make progress feel visible especially on days when it’s not? Use a “Progress Ritual.” → At the end of the day, pause. → Write down 3 small ways you moved forward. → That’s it. No fanfare. Just ritual. This works because we rarely notice our progress in real time. It gets buried under busyness, meetings, and mental noise. The act of looking back gives your brain the reward it needs to keep going. Momentum builds from meaning. Now let’s add some comedy. Young Jerry Seinfeld had one goal: write new material every day. To stay on track, he created a brilliant system. Each day he wrote, he put a big red X on his calendar. Soon, a chain of Xs formed. And here’s the key: Don’t break the chain. One red X becomes two. Two becomes ten. Ten becomes identity. Whether you’re writing, coding, or training Daily action + visual chain = long-term motivation. Summary: The Two-Part Motivation System From Harvard: Record 3 ways you made progress each day. From Seinfeld: Mark an X for each day you show up then don’t break the chain. Progress fuels purpose. Consistency fuels confidence. Apply both and you’ll stay on track especially on the tough days. Because when your days get better, your weeks get better. When your weeks get better, your months get better. When your months get better, your life gets better. It starts with one small win today.

People treat storytelling like a soft, squidgy skill. Not a “proper” skill like finance or coding. But sales? That's storytelling. Hiring? Storytelling. Getting hired? Storytelling. Most skills that matter have some element of storytelling in them. And if you don't tell your story... someone else will make it up for you. So here are 7 different storytelling frameworks (for different situations): 1/ Hero's Journey • A transformation arc showing struggle, growth, and return. • Use when: Pitching yourself in an interview or telling your founder story. 2/ The Golden Circle • Start with Why, then How, then What. Inspire before you sell. • Use when: Explaining your company to someone who doesn't get why it matters. 3/ The Mountain Structure • Tension builds with each step until the final breakthrough. • Use when: Telling a story at dinner or giving a talk with a big payoff moment. 4/ Pixar's Story Framework • Once upon a time, every day, until one day - the ideal story arc. • Use when: Making someone care before you ask for anything. 5/ The 3-Act Play • Act 1: Set up. Act 2: Conflict. Act 3: Resolution. • Use when: Writing a case study or explaining how you solved a client problem. 6/ What, So What, Now What • Turn data and facts into insights and action. • Use when: Presenting to execs or making a case for budget. 7/ The Problem–Agitate–Solution (PAS) • Expose a problem, make people feel it, then fix it - the one I use for most LinkedIn posts. • Use when: Writing a sales page, cold email, or LinkedIn post selling something. Next time you're out for dinner and about to launch into a monologue, pause and think. "What if I tried one of those frameworks I saw on LinkedIn?" Then as you talk, watch peoples' reactions. When do they get bored? When do they lean in? Do that over and over, and watch yourself improve with only a wee bit of effort. 📌 Start telling your story one post at a time. Here's my free email playbook: https://lnkd.in/ga7QpS8v ♻️ Repost to help your network tell their stories better. ➕ Follow me (Will McTighe) for more like this.