rd-management
R&D management expertise for R&D portfolio management, technology roadmapping, research methodology, patent strategy, lab management, academic partnerships, and regulatory pathways. Use when managing research programs, planning technology roadmaps, or building patent portfolios.
What this skill does
# R&D Management Expert Comprehensive R&D frameworks for research strategy, technology roadmapping, and innovation pipeline management. ## R&D Strategy ### R&D Portfolio Framework ``` PORTFOLIO DIMENSIONS: BY TYPE: - Basic Research (10-20%) - Applied Research (20-30%) - Development (50-70%) BY TIME HORIZON: - Near-term (<2 years) - Mid-term (2-5 years) - Long-term (>5 years) BY RISK: - Core (incremental) - Adjacent (new territory) - Breakthrough (transformational) PORTFOLIO BALANCE: Mature companies: More development, less research Growth companies: More research, balanced development Disruption risk: More breakthrough investment ``` ### R&D Investment Analysis | Metric | Formula | Benchmark | | ------------------- | ------------------------------- | ----------------- | | **R&D Intensity** | R&D Spend / Revenue | Industry specific | | **R&D Efficiency** | New Product Revenue / R&D Spend | >2x | | **Patent Yield** | Patents / R&D Spend | Varies | | **Time to Market** | Concept to launch | Decreasing | | **Project Success** | Successful / Total projects | 20-40% | ### R&D Operating Models ``` CENTRALIZED: - Single R&D organization - Economies of scale - Technology leverage - Long-term focus Pros: Efficiency, coordination Cons: Distant from business DECENTRALIZED: - Business unit R&D - Close to market - Faster response - Application focus Pros: Relevance, speed Cons: Duplication, short-term HYBRID: - Central research labs - BU development teams - Shared services - Technology transfer Pros: Balance Cons: Coordination complexity ``` ## Technology Roadmapping ### Roadmap Structure ``` TECHNOLOGY ROADMAP LAYERS: MARKET LAYER: - Customer needs - Market trends - Competitive dynamics - Regulatory changes PRODUCT LAYER: - Product generations - Feature evolution - Platform decisions - Release timing TECHNOLOGY LAYER: - Core technologies - Enabling technologies - Emerging technologies - Technology dependencies RESOURCE LAYER: - Capabilities needed - Skill development - Partnerships - Infrastructure ``` ### Roadmapping Process | Phase | Activities | Output | | ----------------- | -------------------------- | ---------------- | | **Planning** | Scope, team, timeline | Charter | | **Analysis** | Market, technology, gap | Insights | | **Synthesis** | Prioritization, sequencing | Draft roadmap | | **Validation** | Stakeholder review | Refined roadmap | | **Communication** | Publication, training | Deployed roadmap | | **Maintenance** | Updates, governance | Living document | ### Technology Maturity ``` TECHNOLOGY READINESS LEVELS (TRL): TRL 1: Basic principles observed TRL 2: Technology concept formulated TRL 3: Experimental proof of concept TRL 4: Technology validated in lab TRL 5: Technology validated in relevant environment TRL 6: Technology demonstrated in relevant environment TRL 7: System prototype demonstrated in operational environment TRL 8: System complete and qualified TRL 9: Actual system proven in operational environment INVESTMENT BY TRL: TRL 1-3: Research funding TRL 4-6: Development funding TRL 7-9: Engineering/Launch funding ``` ## Research Management ### Research Project Types | Type | Goal | Duration | Risk | | --------------- | --------------------- | ----------- | --------- | | **Basic** | New knowledge | 3-10+ years | Very High | | **Applied** | Specific applications | 2-5 years | High | | **Development** | Productization | 1-3 years | Medium | | **Engineering** | Commercialization | 6-18 months | Lower | For detailed research methodology, lab management, product development frameworks, and engineering standards, see [Research Frameworks Reference](references/research-frameworks.md). ## Academic Partnerships ### Partnership Models | Model | Investment | IP Rights | Engagement | | ---------------------- | ---------- | --------------- | ------------- | | **Sponsored Research** | Funding | Negotiated | Project-based | | **Consortium** | Shared | Pre-competitive | Multi-party | | **Licensing** | Royalties | Licensed | Transaction | | **Joint Venture** | Equity | Shared | Deep | | **Chair/Fellowship** | Endowment | None | Talent access | ### University Collaboration ``` COLLABORATION FRAMEWORK: RELATIONSHIP BUILDING: - Faculty engagement - Student recruiting - Advisory boards - Speaking engagements PROJECT MANAGEMENT: - Clear objectives - Milestone tracking - Regular communication - IP agreements upfront TECHNOLOGY TRANSFER: - Licensing evaluation - Patent prosecution - Startup spin-offs - Joint development SUCCESS METRICS: - Publications - Patents - Technologies adopted - Hires from program ``` For detailed regulatory pathways and clinical development phases, see [Regulatory & Clinical Development Reference](references/regulatory-clinical.md). ## R&D Metrics & Governance ### R&D KPIs | Category | Metric | Benchmark | | -------------- | ------------------ | ------------ | | **Input** | R&D spend | % of revenue | | **Process** | Project milestones | On-time % | | **Output** | Products launched | Per year | | **Efficiency** | Cost per project | Improving | | **Quality** | First-time success | >30% | | **Speed** | Cycle time | Decreasing | ### R&D Governance ``` GOVERNANCE STRUCTURE: PORTFOLIO REVIEW BOARD: - Investment allocation - Project prioritization - Resource decisions - Go/No-go decisions PROJECT GOVERNANCE: - Stage gate reviews - Technical reviews - Business case updates - Risk management TECHNICAL GOVERNANCE: - Architecture decisions - Technology standards - Platform decisions - Make/buy/partner MEETING CADENCE: | Forum | Frequency | Participants | |-------|-----------|--------------| | Portfolio Review | Quarterly | Executives | | Project Review | Monthly | Project sponsors | | Technical Review | As needed | Technical leaders | | Team Standups | Weekly/Daily | Project teams | ``` ## R&D Talent ### Technical Career Path ``` DUAL LADDER SYSTEM: TECHNICAL TRACK: - Associate Engineer - Engineer - Senior Engineer - Principal Engineer - Fellow - Distinguished Fellow MANAGEMENT TRACK: - Team Lead - Manager - Director - VP Engineering - SVP/CTO EQUIVALENCIES: Principal Engineer ≈ Director Fellow ≈ VP Distinguished Fellow ≈ SVP CAREER DEVELOPMENT: - Technical certifications - Publication requirements - Patent expectations - Leadership development ``` ### Technical Community ``` COMMUNITY BUILDING: KNOWLEDGE SHARING: - Technical forums - Lunch & learns - Internal conferences - Best practice sharing DEVELOPMENT: - Training programs - Mentoring - Rotation programs - External conferences RECOGNITION: - Technical awards - Patent recognition - Publication support - Innovation prizes ``` ## References - [Research Frameworks Reference](references/research-frameworks.md) - Research methodology, lab management, product development, engineering standards - [Regulatory & Clinical Development Reference](references/regulatory-clinical.md) - Regulatory strategy, industry pathways, clinical trial phases ## See Also - [Fortune 50 Innovation](../fortune50-innovation/SKILL.md) - [Fortune 50 Product Management](../fortune50-product-management/SKILL.md) - [Fortune 50 Operations](../fortune50-operations/SKILL.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.