-
Notifications
You must be signed in to change notification settings - Fork 8
add proposal for techcamp product #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
9364c6a
to
a5ee2cd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a comprehensive curriculum proposal for the 1024 TechCamp product, outlining design principles, three training phases, feature modes, evaluation mechanisms, and future optimization directions.
- Introduces the overall course framework and core competencies across three phases.
- Specifies deliverables and AI-assisted practices in product thinking, architecture, and implementation.
- Details training features (real projects, collaboration, iterations) and assessment methodology.
Comments suppressed due to low confidence (3)
proposal/techcamp-product.md:25
- Typo: '表诉' should be '表述' in the parentheses.
- 竞品分析方法 (一张表诉所有)
proposal/techcamp-product.md:25
- [nitpick] Use full-width parentheses for Chinese text to match the rest of the document (i.e., '(一张表述所有)').
- 竞品分析方法 (一张表诉所有)
proposal/techcamp-product.md:7
- The acronym 'PBL' should be expanded on first use (e.g., '项目式学习 (PBL)') for clarity.
**创客 PBL 模式融入**:我们借鉴创客空间(Maker Space)和项目式学习(Project-Based Learning)的理念,强调"做中学"、"协作共创"、"迭代改进"的学习模式,让学员在真实项目实践中获得成长。
- 竞品分析方法 (一张表诉所有) | ||
- 功能对比矩阵:列出核心功能点,对比各竞品的实现情况 | ||
- 技术架构分析:研究竞品的技术选型和架构设计 | ||
- 用户体验分析:从用户角度体验竞品,记录优缺点 | ||
- 差异化定位:识别竞品的特色功能和市场定位 | ||
|
||
2. **产品设计思维** | ||
|
||
- 思维理念 (初级产品经理喜欢做加法,顶级产品经理做的是减法) | ||
- 做减法思维:从加法到减法的转变 | ||
- 精准定位:减到刚好精准命中用户心智 | ||
- 价值聚焦:识别核心价值,避免功能堆砌 | ||
- 用户思维 | ||
- 以用户为中心:从用户视角思考问题 | ||
- 用户旅程地图:理解用户使用产品的完整流程 | ||
- 同理心设计:站在用户角度感受痛点和需求 | ||
- 数据思维 | ||
- 数据驱动决策:基于数据而非直觉做产品决策 | ||
- 关键指标定义:识别产品的核心成功指标 | ||
- A/B 测试思维:通过实验验证产品假设 | ||
- 迭代思维 | ||
- 快速试错:小步快跑,快速验证 | ||
- 持续优化:基于反馈不断改进产品 | ||
- 版本规划:合理规划产品迭代节奏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Nested bullet points under a numbered heading may be clearer if converted to a numbered sublist to maintain consistent structure.
- 竞品分析方法 (一张表诉所有) | |
- 功能对比矩阵:列出核心功能点,对比各竞品的实现情况 | |
- 技术架构分析:研究竞品的技术选型和架构设计 | |
- 用户体验分析:从用户角度体验竞品,记录优缺点 | |
- 差异化定位:识别竞品的特色功能和市场定位 | |
2. **产品设计思维** | |
- 思维理念 (初级产品经理喜欢做加法,顶级产品经理做的是减法) | |
- 做减法思维:从加法到减法的转变 | |
- 精准定位:减到刚好精准命中用户心智 | |
- 价值聚焦:识别核心价值,避免功能堆砌 | |
- 用户思维 | |
- 以用户为中心:从用户视角思考问题 | |
- 用户旅程地图:理解用户使用产品的完整流程 | |
- 同理心设计:站在用户角度感受痛点和需求 | |
- 数据思维 | |
- 数据驱动决策:基于数据而非直觉做产品决策 | |
- 关键指标定义:识别产品的核心成功指标 | |
- A/B 测试思维:通过实验验证产品假设 | |
- 迭代思维 | |
- 快速试错:小步快跑,快速验证 | |
- 持续优化:基于反馈不断改进产品 | |
- 版本规划:合理规划产品迭代节奏 | |
1. 竞品分析方法 (一张表诉所有) | |
1. 功能对比矩阵:列出核心功能点,对比各竞品的实现情况 | |
2. 技术架构分析:研究竞品的技术选型和架构设计 | |
3. 用户体验分析:从用户角度体验竞品,记录优缺点 | |
4. 差异化定位:识别竞品的特色功能和市场定位 | |
2. **产品设计思维** | |
2. 思维理念 (初级产品经理喜欢做加法,顶级产品经理做的是减法) | |
1. 做减法思维:从加法到减法的转变 | |
2. 精准定位:减到刚好精准命中用户心智 | |
3. 价值聚焦:识别核心价值,避免功能堆砌 | |
3. 用户思维 | |
1. 以用户为中心:从用户视角思考问题 | |
2. 用户旅程地图:理解用户使用产品的完整流程 | |
3. 同理心设计:站在用户角度感受痛点和需求 | |
4. 数据思维 | |
1. 数据驱动决策:基于数据而非直觉做产品决策 | |
2. 关键指标定义:识别产品的核心成功指标 | |
3. A/B 测试思维:通过实验验证产品假设 | |
5. 迭代思维 | |
1. 快速试错:小步快跑,快速验证 | |
2. 持续优化:基于反馈不断改进产品 | |
3. 版本规划:合理规划产品迭代节奏 |
Copilot uses AI. Check for mistakes.
|
||
**知识共享机制**: | ||
|
||
- **技术分享会**:每周进行技术分享? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Replace the half-width question mark with a full-width one ('?') or remove it if not intended as a question.
- **技术分享会**:每周进行技术分享? | |
- **技术分享会**:每周进行技术分享 |
Copilot uses AI. Check for mistakes.
No description provided.