Negotiating Creative Briefs

From IP basics to IP strategy 🌟 Scientists are key creators of intellectual property (IP). Therefore, it is important that they know about IP rights. It enables them to recognize patentable inventions, comply with IP policies, and make informed decisions about publishing and patenting. IP rights protect creations of the mind. The most common rights are: 💡 Patents: protect inventions, such as a genetically modified microorganism or a new drug. 🎨 Design rights: cover the appearance of products, like the look of a smartphone or the shape of a lamp. 🛡️ Trademarks: names and logos that distinguish a product from other products, e.g., the Google logo. 🔒 Trade secrets: confidential information that is kept secret, like a manufacturing process or chemical composition. 📚 Copyright: protects original works, including art and research articles 🌱 Plant breeder's rights: protect new plant varieties. Often, products aren't protected by a single IP right, but multiple. For instance, a biotech company may have: - Patents for technical aspects of a product, e.g., an improved version of CRISPR-Cas9. 🛡️ - Trademark for the product's name, e.g., HelixForge.™️ - Trade secrets for its manufacturing methods or the optimal buffer composition. 🔒 Such an IP strategy combines various IP rights, each protecting a different aspect of the product. This enhances product protection as it is harder for competitors to copy the product or create similar products legally. By aligning IP strategy with business objectives through marketing, further R&D, licensing and strategic partnerships, IP decisions become a cornerstone for building a long-term competitive advantage for a company. 🚀 Organizations of all types and sizes, from universities and startups to large corporations, use IP strategies. Check the examples below to see how various IP rights can synergistically protect a product.

🧠 “How We Brainstorm And Choose UX Ideas” (+ Miro template) (https://lnkd.in/eN32hH2x), a practical guide by Booking.com on how to run a rapid UX ideation session with silent brainstorming and “How Might We” (HMW) statements — by clustering data points into themes, reframing each theme and then prioritizing impactful ideas. Shared by Evan Karageorgos, Tori Holmes, Alexandre Benitah. 👏🏼👏🏽👏🏾 Booking.com UX Ideation Template (Miro) https://lnkd.in/eipdgPuC (password: bookingcom) 🚫 Ideas shouldn’t come from assumptions but UX research. ✅ Study past research and conduct a new study if needed. ✅ Cluster data in user needs, business goals, competitive insights. ✅ Best ideas emerge at the intersections of these 3 pillars. ✅ Cluster all data points into themes, prioritize with colors. ✅ Reframe each theme as a “How Might We” (HMW) statement. ✅ Start with the problems (or insights) you’ve uncovered. ✅ Focus on the desired outcomes, rather than symptoms. ✅ Collect and group ideas by relevance for every theme. ✅ Prioritize and visualize ideas with visuals and storytelling. Many brainstorming sessions are an avalanche of unstructured ideas, based on hunches and assumptions. Just like in design work we need constraints to be intentional in our decisions, we need at least some structure to mold realistic and viable ideas. I absolutely love the idea of frame the perspective through the lens of ideation clusters: user needs, business problems and insights. Reframing emerging themes as “How-Might-We”-statements is a neat way to help teams focus on a specific problem at hand and a desired outcome. A simple but very helpful approach — without too much rigidity but just enough structure to generate, prioritize and eventually visualize effective ideas with the entire team. Invite non-designers in the sessions as well, and I wouldn’t be surprised how much value a 2h session might deliver. Useful resources: The Rules of Productive Brainstorming, by Slava Shestopalov https://lnkd.in/eyYZjAz3 On “How Might We” Questions, by Maria Rosala, NN/g https://lnkd.in/ejDnmsRr Ideation for Everyday Design Challenges, by Aurora Harley, NN/g https://lnkd.in/emGtnMyy Brainstorming Exercises for Introverts, by Allison Press https://lnkd.in/eta6YsFJ How To Run Successful Product Design Workshops, by Gustavs Cirulis, Cindy Chang https://lnkd.in/eMtX-xwD Useful Miro Templates For UX Designers, by yours truly https://lnkd.in/eQVxM_Nq #ux #design

𝗬𝗼𝘂𝗿 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗷𝘂𝘀𝘁 𝗶𝗻𝘃𝗲𝗻𝘁𝗲𝗱 𝘆𝗼𝘂𝗿 𝗰𝗼𝗿𝗲 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝗼𝗻 𝘆𝗼𝘂𝗿 𝘁𝗶𝗺𝗲, 𝘂𝘀𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗲𝗾𝘂𝗶𝗽𝗺𝗲𝗻𝘁, 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗼𝗳𝗳𝗶𝗰𝗲. 𝗧𝗵𝗲𝘆 𝘀𝘁𝗶𝗹𝗹 𝗼𝘄𝗻 𝘁𝗵𝗲 𝗽𝗮𝘁𝗲𝗻𝘁 𝗿𝗶𝗴𝗵𝘁𝘀. This shocks every founder who hears it. "But they're my employee!" Employment doesn't equal ownership. Not for patents. 𝗖𝗼𝗺𝗽𝗮𝗻𝘆 𝗔 hires a brilliant ML engineer. Standard employment agreement with confidentiality and "work for hire" provisions. The engineer develops a breakthrough algorithm that becomes Company A's secret sauce. Two years later, the engineer leaves. Then files their own patent application on "their" invention. Company A's lawyers review the employment agreement. No patent assignment clause. The copyright provisions? Irrelevant. The engineer owns the patent rights. 𝗖𝗼𝗺𝗽𝗮𝗻𝘆 𝗕'𝘀 identical situation plays differently. Their employment agreement included: "𝗘𝗺𝗽𝗹𝗼𝘆𝗲𝗲 𝗵𝗲𝗿𝗲𝗯𝘆 𝗮𝘀𝘀𝗶𝗴𝗻𝘀 𝗮𝗹𝗹 𝗶𝗻𝘃𝗲𝗻𝘁𝗶𝗼𝗻𝘀 𝗰𝗼𝗻𝗰𝗲𝗶𝘃𝗲𝗱 𝗱𝘂𝗿𝗶𝗻𝗴 𝗲𝗺𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝘁𝗼 𝗖𝗼𝗺𝗽𝗮𝗻𝘆 𝗕." When their engineer leaves, the patent rights stay. The gap between copyright and patent law creates this trap: • 𝗖𝗼𝗽𝘆𝗿𝗶𝗴𝗵𝘁: "Work for hire" doctrine can automatically vest rights in employer • 𝗣𝗮𝘁𝗲𝗻𝘁𝘀: No equivalent doctrine—inventors own their inventions absent explicit assignment The dangerous scenarios multiply: • Your CTO who built your platform before signing proper paperwork • That contractor you converted to employee but never updated agreements • The intern who contributed to your core algorithm • Your co-founder who left before IP assignments were cleaned up One missing signature can mean: • You can't file patents on your own technology • You need inventor cooperation (and negotiation) for every patent filing • Your acquisition falls apart during due diligence • Your former employee becomes your competitor—using "your" technology The solution is mechanical but critical: Every technical employee, contractor, and consultant needs an agreement with: ✓ Present assignment language ("hereby assigns" not "agrees to assign") ✓ Coverage of all inventions during employment/engagement ✓ Cooperation obligations that survive termination ✓ Clear definitions of what constitutes a covered invention Missing these agreements? Fix them now—while everyone's still friendly. Retroactive assignments get expensive fast. Need help securing your IP rights? Let's close those gaps. P.S. This post focuses on U.S. law—other countries handle employee inventions differently, which is yet another reason to never assume, always verify. #patents #intellectualproperty

Happy New Year! 🥂 As we begin 2026, I’ve been reflecting on the briefs that were especially effective this past year—briefs that were organized, readable, and concise. In that spirit, here are ten practices I think consistently strengthen written advocacy: 🥂Use regular sentence capitalization throughout your brief. In tables of contents, issues presented, and point headings, sentence‑style capitalization is the easiest for the reader to process. It keeps the structure clean and the eye moving naturally. 🥂Place important facts, rules, and analysis in full sentences. Key information carries more weight in the text than in parentheticals or footnotes. If removing a parenthetical or footnote drains a sentence or paragraph of meaning, that’s a sign the information belongs in the main flow. 🥂Streamline your introductory sections. Introductions, summary of the arguments, roadmaps, and topic sentences all have their purpose, but beware of unnecessary repetition. Choose the pieces that genuinely help orient the reader - repetitive orientation can cause the reader to stop reading and start searching for substance. 🥂Let necessary repetition speak for itself. Some concepts must be repeated for clarity or structure. There’s no need to call attention to it with phrases like “as explained before.” Trust your organization to guide the reader. 🥂Use acronyms sparingly and only when they help. Familiar acronyms—FBI, DSS, SBI—are efficient. Others often slow the reader down. When in doubt, a simple descriptor (“the Department,” “the Board”) keeps the prose smoother. 🥂Define parties and terms only when clarity requires it. Once you’ve introduced “Plaintiff, John Michael Smith,” you can comfortably refer to “Plaintiff” or “Mr. Smith” without parenthetical definitions. If the reader won’t be confused, the simpler path is the clearer one. 🥂Favor possessives over “of” phrases. “Plaintiff’s attorney” reads more naturally than “attorney of plaintiff,” and these refinements add up across a brief. 🥂Move directly to the action when the action matters. Phrases like “decided to,” “thought to,” or “elected to” often delay the verb that carries the sentence. When the decision isn’t the point, let the action lead: “John crossed the road.” 🥂Draft your table of contents as a true outline of your argument. Point headings that reflect the full structure of your reasoning create a roadmap a judge or clerk can digest quickly. A well‑built table of contents is one of the most helpful tools you can provide. 🥂Use visual formats—bullet points, timelines, charts—when they clarify complex information. A well‑designed chart, for example, can convey what might otherwise take a full page of text, especially when comparing cases or summarizing a timeline. More tips? Please drop them below. Wishing you a new year filled with clear, effective writing and strong advocacy!

As an IP consultant, I often encounter confusion about the different types of intellectual property protection. They all safeguard different aspects of creativity and innovation, but they differ in their approaches. Here's a quick breakdown to help you navigate: 📐 𝗣𝗮𝘁𝗲𝗻𝘁𝘀: ↳ Protect: New inventions and processes ↳ Duration: Generally, 20 years from filing date ↳ Example: A new type of smartphone camera technology or pharmaceutical formulation ™️ 𝗧𝗿𝗮𝗱𝗲𝗺𝗮𝗿𝗸𝘀: ↳ Protect: Brand names, logos, slogans ↳ Duration: Potentially indefinite with proper use and renewal ↳ Example: The Nike swoosh or "Just Do It" slogan ©️ 𝗖𝗼𝗽𝘆𝗿𝗶𝗴𝗵𝘁𝘀: ↳ Protect: Original creative works (literature, music, art, software) ↳ Duration: Life of author/creator + 60 or 70 years (in most cases) ↳ Example: A novel, a song, or a painting, software source code 𝗗𝗲𝘀𝗶𝗴𝗻 𝗣𝗮𝘁𝗲𝗻𝘁 / 𝗜𝗻𝗱𝘂𝘀𝘁𝗿𝗶𝗮𝗹 𝗗𝗲𝘀𝗶𝗴𝗻 ↳ Protect: Shape or aesthetic look of an object ↳ Duration: 10 years to 25 years (Vary from country to country) ↳ Example: Furniture, Jewellery, Textile design, Automobile vehicles ✔️ 𝗞𝗲𝘆 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀: 👉 Patents require novelty and non-obviousness 👉 Trademarks are about distinguishing your brand in the marketplace 👉 Copyrights arise automatically upon creation of the work 👉 Design patent to protect the aesthetic look of the product These protections can overlap. Your product might need a patent for its technology, a trademark for its brand, a copyright for its expression or art, and a design patent for the unique shape of the product. Choosing the right IP protection is crucial for safeguarding your innovations and brand. What type of IP protection is most relevant to your business? Don’t Shy Away, Ask us Why, What, How and When to Protect…!!! #IntellectualProperty #IPProtection #Patents #Trademarks #Copyrights #DesignPatent #BusinessProtection #BrandProtection #StartupTips

Copyright. Trademark. Patent. These three terms get thrown around a lot—but do you actually know which one you need? Let’s break it down in simple terms: 📜 Copyright protects creative works. - This includes books, music, films, art, and even website content. - If you create something original, copyright automatically protects it as soon as it’s in a fixed form, but registration strengthens enforcement. ™️ Trademark protects brand identity. - This applies to business names, logos, slogans, and distinctive brand elements. - If you’re building a brand and don’t want someone else to use your name or logo, you need a trademark. ⚙️ Patent protects inventions. - This covers new products, unique processes, and technological innovations. - If you invent something new and useful, a patent prevents others from making or selling it without your permission. Which one do you need? - If you wrote a book, produced a song, or designed an illustration—copyright. - If you launched a brand and want to protect its name and logo—trademark. - If you invented a new product or process—patent. Intellectual property law can feel overwhelming, but securing the right protection from the start can save you major headaches down the line. Have questions about protecting your work? Drop them in the comments.

I've seen founders complain about lack of innovation while sitting at the head of a 10-foot table, arms crossed, waiting for "bold ideas." Then they wonder why the room goes silent. Here's the thing: no one writes poetry in front of a firing squad. You can't demand creativity while radiating authority. The two don't coexist. When status is high, people optimize for safety, not originality. They pitch what won't get them fired, not what might actually work. In the best brainstorming sessions I've witnessed, the leader showed up differently. They sat in the middle, not at the head. They shared a bad idea first. They laughed at themselves. They asked questions instead of making statements. Lowering your status doesn't mean losing respect. It creates space for others to think freely. Because creativity requires vulnerability. And vulnerability requires safety. And safety disappears the moment someone in the room feels like they're performing for judgment instead of collaborating toward something. If you want real ideas, stop being the smartest person in the room. Start being the most curious. #work #business #creativity #entrepreneurship

Day in a life of a content marketer: I had to redesign my entire blog brief template because of AI search. Earlier, my briefs looked like this: – target keywords – reference articles – competitor links Useful? Yes. But in now, it's not enough. Here’s what I do now 👇 I start with questions, not keywords. Before creating an outline anything, I pull up real questions from: • AnswerThePublic • Google’s “People Also Ask” • Reddit threads These places tell me what real humans are confused about, frustrated with, or actively searching for. Then I take those questions and turn them into my H2s and H3s. Because if people are already asking, your blog should be the one answering. 💡 Second big shift: depth > decoration. Instead of adding generic fluff, I answer every question with actual detail. I avoid adding those typical summary paragraphs that add no real value - obvious advice like “content is king” or “always provide value.” 💡 Third shift: show, don’t tell. Every brief includes: • product screenshots • screen recordings • step-by-step visuals If a reader lands on your blog with a question, they should leave with a solution. With AI search in place, the bar for what “helpful” actually means has increased. So, stop writing for algorithms and start writing for real questions people are asking. Build briefs around intent and show your product in action, not in theory.

Requirements Engineering aligns your data project with stakeholder needs. Here’s how you can effenciently gather requirements: 1. 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀: Begin with in-depth interviews to understand business objectives and the challenges stakeholders are facing. Document their specific needs and expectations, ensuring alignment with the project's goals.     2. 𝗖𝗹𝗲𝗮𝗿 𝗢𝗯𝗷𝗲𝗰𝘁𝗶𝘃𝗲𝘀: Translate stakeholder insights into clear, actionable objectives. Define what "success" looks like and how it will be measured. Having a strong objective framework helps prevent scope creep later.     3. 𝗦𝗰𝗼𝗽𝗲 𝗗𝗲𝗳𝗶𝗻𝗶𝘁𝗶𝗼𝗻: Clearly outline the project scope by identifying what data will be used, the analysis techniques required, and the expected deliverables. Ensure all stakeholders are on the same page about what will (and won’t) be included.     4. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻: Not all requirements hold equal weight. Work with stakeholders to prioritize the most critical objectives first, balancing them against time, resources, and technical constraints.     5. 𝗜𝘁𝗲𝗿𝗮𝘁𝗶𝘃𝗲 𝗥𝗲𝗳𝗶𝗻𝗲𝗺𝗲𝗻𝘁: Requirements are rarely static. Build flexibility into the process to refine and adjust as new insights emerge. Regularly revisit requirements to ensure they remain aligned with evolving business needs.     6. 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸: Regularly validate that the project's outcomes are meeting stakeholders' expectations. Incorporate their feedback into iterative improvements and adjust your analysis as necessary.     7. 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻: Maintain comprehensive documentation of the requirements, analysis process, and key decisions. This ensures continuity across teams and provides a reference for future projects. By implementing these requirements engineering principles, you can significantly enhance the clarity, focus, and impact of your data projects. Aligning technical work with clear business needs ensures that insights translate directly into actionable business decisions. What challenges have you faced in translating stakeholder requirements into data analysis projects? ---------------- ♻️ Share if you find this post useful ➕ Follow for more daily insights on how to grow your career in the data field #dataanalytics #datascience #businessintelligence  #requirementsengineering #stakeholdermanagement

Are you creating amazing 3D models using AI tools like Gemini AI and excited to share them with the world? Hold on for a second! Before you hit that upload button, here are some important Intellectual Property considerations you must keep in mind. 🔸 Who Owns the Rights? When you use AI tools to generate images or 3D models, check the terms of service of the platform. Some tools claim ownership of the generated content, while others may allow you full rights. Always clarify who holds the copyright or license. 🔸 Originality Matters Even if the images look unique, if they are derived from existing copyrighted works, uploading them publicly can lead to infringement claims. Be cautious if you modify existing works. 🔸 Trademark Issues Avoid using recognizable logos, brand designs, or famous character likenesses in your 3D models without proper permission. This can attract trademark infringement problems. 🔸 Right of Publicity If your model resembles a real person, their consent may be required before commercial use. As a Media & IPR lawyer, I always recommend being informed to protect your creativity and avoid legal troubles. Stay creative, but stay safe! #IntellectualProperty #IPR #GeminiAI #3DModels #AIContent #DigitalCreatives #LawTips #MediaLaw #Copyright #Trademark #CreatorsRights