关于 rd-management
rd-management 是用于规划研发战略、技术路线图、研究项目与创新组合的技能,提供投资分析、治理、合作、指标及技术人才发展的框架。
主要功能
- 01研发组合与投资分析
- 02技术路线图规划与评审
- 03研究项目类型框架
- 04学术合作模式
- 05研发指标与治理
- 06技术职业路径与社群框架
适用场景
- 01按研究类型构建研发项目组合
- 02规划并维护技术路线图
- 03使用里程碑和研发 KPI 评审项目
- 04评估学术合作模式
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ travisjneuman/ .claude --skill rd-management安装后在 Claude Code 中输入/rd-management确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
references/ip-strategy-tech-scouting-skill.mdrd-portfolio-management-skill.mdregulatory-clinical.mdresearch-frameworks.md详细介绍
研发管理专家
涵盖研究战略、技术路线图和创新管线管理的综合研发框架。
研发战略
研发组合框架
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
研发投资分析
| 指标 | 公式 | 基准 |
|---|---|---|
| 研发强度 | 研发支出 / 收入 | 因行业而异 |
| 研发效率 | 新产品收入 / 研发支出 | >2x |
| 专利产出 | 专利数 / 研发支出 | 各不相同 |
| 上市时间 | 从概念到上市 | 逐步缩短 |
| 项目成功率 | 成功项目 / 项目总数 | 20-40% |
研发运营模式
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 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
路线图制定流程
| 阶段 | 活动 | 输出 |
|---|---|---|
| 规划 | 范围、团队、时间表 | 章程 |
| 分析 | 市场、技术、差距 | 洞察 |
| 综合 | 优先级排序、确定顺序 | 路线图草案 |
| 验证 | 利益相关者审查 | 修订后的路线图 |
| 沟通 | 发布、培训 | 已部署的路线图 |
| 维护 | 更新、治理 | 持续更新的文档 |
技术成熟度
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
研究管理
研究项目类型
| 类型 | 目标 | 周期 | 风险 |
|---|---|---|---|
| 基础研究 | 新知识 | 3-10+ 年 | 很高 |
| 应用研究 | 特定应用 | 2-5 年 | 高 |
| 开发 | 产品化 | 1-3 年 | 中等 |
| 工程 | 商业化 | 6-18 个月 | 较低 |
如需了解详细的研究方法、实验室管理、产品开发框架和工程标准,请参阅研究框架参考。
学术合作
合作模式
| 模式 | 投资 | 知识产权 | 合作方式 |
|---|---|---|---|
| 资助研究 | 资金 | 协商确定 | 基于项目 |
| 联盟 | 共同投入 | 竞争前共享 | 多方合作 |
| 许可 | 版税 | 获得许可 | 交易型 |
| 合资企业 | 股权 | 共享 | 深度合作 |
| 讲席/奖学金 | 捐赠基金 | 无 | 人才获取 |
大学合作
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
如需了解详细的监管路径和临床开发阶段,请参阅监管与临床开发参考。
研发指标与治理
研发 KPI
| 类别 | 指标 | 基准 |
|---|---|---|
| 投入 | 研发支出 | 占收入的百分比 |
| 流程 | 项目里程碑 | 按时完成率 |
| 产出 | 已发布产品 | 每年 |
| 效率 | 单个项目成本 | 持续改善 |
| 质量 | 首次成功率 | >30% |
| 速度 | 周期时间 | 逐步缩短 |
研发治理
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 |
研发人才
技术职业发展路径
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
技术社群
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
参考资料
另请参阅
评论
支持 Markdown