# How to stay up to date: managing new knowledge in industrial companies **Context:** Industrial companies constantly encounter three main sources of new knowledge: external documentation from suppliers and customers, research literature in their field, and internal knowledge from new projects or product lines. Most industrial work operates in a hybrid product/project mode, meaning you need to rapidly absorb knowledge from all these sources to stay effective. **Goal:** Transform these knowledge influxes from time-consuming disruptions into quick, actionable insights. ## Knowledge source 1: external documentation (suppliers & customers) **When this happens:** You receive new supplier proposals, customer specifications, partner documentation, or technical submissions that you need to understand quickly. ### Step-by-step workflow 1. **Upload the entire document folder** * Don't cherry-pick files - upload everything at once * Let MAIA see the full context 2. **Start with high-level summarization (select the files you just uploaded!)** ```plaintext "I just received documentation from supplier [X] for project [Y]. Please summarize what they're proposing, including key technical specifications, costs, timeline, and any potential concerns." ``` 3. **Compare against your baseline (if applicable)** **Pro tip:** Upload two versions with different folder names, then simply refer to them by the folder names. ```plaintext "I have two versions of this supplier proposal - one in the 'March_Proposal' folder and one in 'June_Proposal' folder. What are the key changes between the March and June proposals?" "Compare the 'Supplier_A_Proposal' folder against our internal requirements in the 'Internal_Requirements' folder. Where do they align and where are the gaps?" ``` 4. **Extract actionable next steps** ```plaintext "Based on this analysis, what are the top 3 questions I should ask this supplier in our next meeting?" "What information do I need to gather internally before we can make a decision on this proposal?" ``` **Expected outcome:** 15-minute document review instead of 2-hour deep dive, with clear next steps identified. ## Knowledge source 2: research literature & industry updates **When this happens:** You need to stay current with research in your field, industry trends, or new technological developments, but don't have time to read everything thoroughly. ### Step-by-step workflow 1. **Batch upload weekly research papers** * Upload all papers at once (typically 3-10 papers) * Include papers in any language - MAIA handles translation 2. **Get comprehensive overview (select the files you just uploaded!)** ```plaintext "I've uploaded this week's research papers in [field/technology area]. Please provide a summary of each paper including: main findings, methodology, and potential applications." ``` 3. **Filter for relevance to your work** ```plaintext "Given that I work on [specific product line/technology] for [specific applications], which of these papers are most relevant to my work and why?" "Are there any findings that could impact our current product development strategy or competitive position?" ``` 4. **Identify actionable insights** ```plaintext "Based on the relevant papers, what are 2-3 specific opportunities or threats I should discuss with my engineering team?" "Should we be changing our approach to [specific technology] based on these research findings?" ``` **Expected outcome:** Stay current with research field in 30 minutes/week instead of hours, with clear business relevance identified. ## Knowledge source 3: internal knowledge (new projects & product lines) **When this happens:** You're assigned to a new project, supporting a different product line, or need to understand adjacent areas within your company. ### Step-by-step workflow 1. **Upload all available documentation** * Technical specifications and project docs * Marketing materials and previous project files * Competitive analyses and internal reports 2. **Start with comprehensive overview (select the files you just uploaded!)** ```plaintext "I'm new to [project X / product line Y] and need to get up to speed quickly. Please give me a comprehensive summary including: key objectives, main technical challenges, customer requirements, and how this fits in our overall strategy." ``` 3. **Understand technical fundamentals** ```plaintext "What are the main components and technologies that make up this [project/product line]? Explain how each component contributes to the overall performance and objectives." "What are the key technical advantages and limitations compared to alternatives or previous approaches?" ``` 4. **Dive deeper into critical areas** ```plaintext "Walk me through how [specific technology/approach] shapes the project outcomes. Why is this approach better than what we've done before or what competitors do?" "What are the 3 most important concepts I need to master to be effective supporting this [project/product line]?" ``` 5. **Identify learning priorities** ```plaintext "Based on this overview, what should I focus on learning first to be most helpful to the engineering and sales teams?" "What are the most common challenges or technical questions for this [project/product line] that I should be prepared for?" ``` **Expected outcome:** Functional knowledge of new project/product line in 2-3 hours instead of weeks of reading and meetings. ## Universal tips for all knowledge sources **Context is everything:** Always provide MAIA with your role, goals, and why you need this information. **Ask for reasoning:** When you need to understand "why," ask MAIA to explain its logic and decision-making. **Follow-up strategically:** Use follow-up questions to drill into areas most relevant to your immediate responsibilities. **Create reusable resources:** After any valuable MAIA conversation, create summaries for future team reference. **Tips for Industrial Knowledge:** When working with product and product knowledge, try to ask how technology creates components creates products. The attributes and pros/cons of an industrial product are usually created at the technology level, but not immediately apparent in the documentation. ```plaintext "Explain how the [specific technology] in this product creates its key performance characteristics. How does this technology choice affect product attributes like durability, efficiency, or cost?" "Walk me through the technology → component → product relationship. How do the underlying technologies shape what this product can and cannot do?" ``` **Time-saving mindset:** These workflows replace the traditional "read everything then synthesize" approach with "synthesize first, then dive deep only where needed." **Remember:** The goal isn't to become an expert in everything, but to quickly identify what matters most and where to focus your detailed learning efforts.