Portfolio Case Study Writer by paramchoudhary/resumeskills
npx skills add https://github.com/paramchoudhary/resumeskills --skill 'Portfolio Case Study Writer'当用户出现以下情况时使用此技能:
为何案例研究很重要:
1. 概述(项目摘要)
2. 问题(需要解决的问题)
3. 过程(你的处理方法)
4. 解决方案(你创建/交付了什么)
5. 结果(产生的影响)
6. 经验教训(你会做哪些不同的事情)
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
目的: 吸引读者,提供背景
包含内容:
示例:
# 重新设计结账流程
**公司:** E-Commerce Inc.
**角色:** 首席产品设计师
**时间线:** 6 周
**团队:** 2 名设计师,3 名工程师,1 名产品经理
**摘要:** 通过简化的三步结账流程,将购物车放弃率降低了 35%,带来了 200 万美元的挽回收入。
目的: 说明这项工作为何重要
包含内容:
示例:
## 问题
E-Commerce Inc. 正经历 68% 的购物车放弃率——显著高于 55% 的行业平均水平。退出调查和用户研究揭示了几个问题:
- **步骤过多:** 我们的结账流程有 7 个页面
- **强制账户创建:** 用户在购买前必须注册
- **隐藏成本:** 运费直到第 5 步才显示
- **移动端摩擦:** 表单未针对移动端优化
**目标:** 在 3 个月内将购物车放弃率降低到 50% 以下。
**约束条件:**
- 不能更改现有的支付集成
- 必须保持 PCI 合规性
- 在假日季前有 6 周的时间线
目的: 展示你的思考和方法论
包含内容:
示例:
## 过程
### 研究
我首先深入理解问题:
- 分析 Mixpanel 漏斗数据以找出流失点
- 对 10 位最近放弃购买的用户进行访谈
- 审查热图和会话记录
- 对标 5 个竞争对手的结账流程
**关键洞察:** 73% 的流失发生在账户创建页面。用户想要购买,而不是建立长期关系。
### 构思
我探索了几种方法:
1. 仅限访客结账(最简单)
2. 社交登录选项(摩擦更低)
3. 渐进式用户画像(随时间收集信息)
4. 单页结账(亚马逊风格)
在权衡可行性、时间线和影响后,我们选择了混合方法...
### 做出的决策
- **优先访客结账:** 将注册设为可选且可在购买后进行
- **价格透明:** 在第一个页面显示运费
- **移动优先设计:** 为移动端设计,然后适配桌面端
- **进度指示器:** 添加清晰的"第 1 步,共 3 步"指示器
目的: 展示你实际创建了什么
包含内容:
示例:
## 解决方案
### 新的结账流程
**之前:** 7 个页面,强制注册
**之后:** 3 个页面,可选访客结账
[图片:前后对比]
### 关键变更
**1. 透明价格小部件**
[图片:价格小部件模型]
从一开始就显示订单总额、运费和税费。没有意外。
**2. 访客结账选项**
[图片:访客结账页面]
将账户创建设为可选,并清晰说明注册的价值主张。
**3. 智能表单设计**
[图片:表单设计]
- 移动端采用单列布局
- 电话号码/卡号自动格式化
- 地址自动补全集成
- 清晰的错误信息
**4. 信任信号**
在整个流程中添加安全徽章、退款保证和客户服务联系方式。
目的: 用数据证明影响
包含内容:
示例:
## 结果
### 主要指标(上线后 90 天)
| 指标 | 之前 | 之后 | 变化 |
|--------|--------|-------|--------|
| 购物车放弃率 | 68% | 44% | -35% |
| 结账完成率 | 32% | 56% | +75% |
| 移动端转化率 | 18% | 41% | +128% |
| 每访问者收入 | $2.40 | $3.85 | +60% |
### 业务影响
- **第一季度增加 200 万美元收入**
- **移动端订单增加 15%**
- **关于结账的客户支持工单** 减少了 45%
### 次要影响
- 账户创建实际上增加了 20%(购买后)
- 平均订单价值保持稳定
- 回头客率有所改善
目的: 展示成长心态和自我认知
包含内容:
示例:
## 经验教训
### 哪些做得好
- **早期用户研究** 防止我们构建错误的解决方案
- **跨职能协调会议** 使每个人保持一致
- **上线时配备分析** 让我们能立即衡量影响
### 我会做哪些不同的事情
- **更多的 A/B 测试:** 我们一次性推出了完整的重新设计。更倾向于测试单个变更以了解哪些驱动了结果。
- **更早关注移动端:** 我们先设计桌面端然后适配。从移动端开始会更高效。
- **干系人教育:** 花了太长时间说服领导层。下次会更早开始协调干系人。
### 发展的技能
- 高级 Figma 原型设计
- 使用 A/B 测试框架
- 向高管展示数据驱动的设计决策
关注点:
关注点:
关注点:
关注点:
创建案例研究时:
# 案例研究:[项目名称]
## 快速事实
- **角色:** [你的角色]
- **公司:** [公司]
- **时间线:** [持续时间]
- **团队:** [团队构成]
- **影响:** [一句话结果]
---
## 概述
[2-3 句话的项目摘要]
## 问题
[背景和挑战 - 需要解决的问题]
## 过程
### 研究
[你学到了什么]
### 方法
[你如何解决它]
### 关键决策
[重要选择及其理由]
## 解决方案
[你构建/创建了什么 - 包含视觉描述]
### 功能 1
[描述]
### 功能 2
[描述]
## 结果
[量化的影响]
| 指标 | 之前 | 之后 | 变化 |
|--------|--------|-------|--------|
## 经验教训
[反思和成长]
---
## 视觉资产清单
[所需图片/截图列表]
每周安装次数
–
代码仓库
GitHub 星标数
180
首次出现时间
–
安全审计
Use this skill when the user:
Why Case Studies Matter:
1. Overview (Project summary)
2. Problem (What needed to be solved)
3. Process (How you approached it)
4. Solution (What you created/delivered)
5. Results (The impact)
6. Learnings (What you'd do differently)
Purpose: Hook the reader, provide context
Include:
Example:
# Redesigning the Checkout Flow
**Company:** E-Commerce Inc.
**Role:** Lead Product Designer
**Timeline:** 6 weeks
**Team:** 2 designers, 3 engineers, 1 PM
**Summary:** Reduced cart abandonment by 35% through a streamlined 3-step checkout process, generating $2M in recovered revenue.
Purpose: Set up why this work mattered
Include:
Example:
## The Problem
E-Commerce Inc. was experiencing 68% cart abandonment—significantly higher than the industry average of 55%. Exit surveys and user research revealed several issues:
- **Too many steps:** Our checkout had 7 screens
- **Forced account creation:** Users had to register before purchasing
- **Hidden costs:** Shipping wasn't shown until step 5
- **Mobile friction:** Forms weren't optimized for mobile
**Goal:** Reduce cart abandonment to below 50% within 3 months.
**Constraints:**
- No changes to existing payment integrations
- Had to maintain PCI compliance
- 6-week timeline before holiday season
Purpose: Show your thinking and methodology
Include:
Example:
## Process
### Research
I started by understanding the problem deeply:
- Analyzed Mixpanel funnel data for drop-off points
- Conducted 10 user interviews with recent abandoners
- Reviewed heatmaps and session recordings
- Benchmarked against 5 competitor checkout flows
**Key Insight:** 73% of drop-offs occurred at the account creation screen. Users wanted to purchase, not commit to a relationship.
### Ideation
I explored several approaches:
1. Guest checkout only (simplest)
2. Social login options (lower friction)
3. Progressive profiling (collect info over time)
4. One-page checkout (Amazon-style)
After weighing feasibility, timeline, and impact, we chose a hybrid approach...
### Decisions Made
- **Guest checkout first:** Made registration optional and post-purchase
- **Transparent pricing:** Showed shipping on the first screen
- **Mobile-first design:** Designed for mobile, then adapted for desktop
- **Progress indicator:** Added clear "Step 1 of 3" indicator
Purpose: Show what you actually created
Include:
Example:
## Solution
### The New Checkout Flow
**Before:** 7 screens with mandatory registration
**After:** 3 screens with optional guest checkout
[IMAGE: Before/After comparison]
### Key Changes
**1. Transparent Pricing Widget**
[IMAGE: Pricing widget mockup]
Showed order total, shipping, and taxes from the start. No surprises.
**2. Guest Checkout Option**
[IMAGE: Guest checkout screen]
Made account creation optional with clear value proposition for why to register.
**3. Smart Form Design**
[IMAGE: Form design]
- Single-column layout on mobile
- Auto-format for phone/card numbers
- Address autocomplete integration
- Clear error messaging
**4. Trust Signals**
Added security badges, money-back guarantee, and customer service contact throughout the flow.
Purpose: Prove impact with data
Include:
Example:
## Results
### Primary Metrics (90 days post-launch)
| Metric | Before | After | Change |
|--------|--------|-------|--------|
| Cart Abandonment | 68% | 44% | -35% |
| Checkout Completion | 32% | 56% | +75% |
| Mobile Conversion | 18% | 41% | +128% |
| Revenue per Visitor | $2.40 | $3.85 | +60% |
### Business Impact
- **$2M additional revenue** in first quarter
- **15% increase in mobile orders**
- **Customer support tickets about checkout** dropped by 45%
### Secondary Effects
- Account creation actually increased 20% (post-purchase)
- Average order value stayed stable
- Return customer rate improved
Purpose: Show growth mindset and self-awareness
Include:
Example:
## Learnings
### What Worked
- **Early user research** prevented us from building the wrong solution
- **Cross-functional alignment** meetings kept everyone on the same page
- **Launching with analytics** let us measure impact immediately
### What I'd Do Differently
- **More A/B testing:** We launched the full redesign at once. Would have preferred to test individual changes to understand what drove results.
- **Earlier mobile focus:** We designed desktop-first then adapted. Starting mobile-first would have been more efficient.
- **Stakeholder education:** Spent too long convincing leadership. Would start stakeholder alignment earlier next time.
### Skills Developed
- Advanced Figma prototyping
- Working with A/B testing frameworks
- Presenting data-driven design decisions to executives
Focus on:
Focus on:
Focus on:
Focus on:
When creating a case study:
# CASE STUDY: [PROJECT NAME]
## Quick Facts
- **Role:** [Your role]
- **Company:** [Company]
- **Timeline:** [Duration]
- **Team:** [Team composition]
- **Impact:** [One-line result]
---
## Overview
[2-3 sentence summary of the project]
## Problem
[Context and challenges - what needed to be solved]
## Process
### Research
[What you learned]
### Approach
[How you tackled it]
### Key Decisions
[Important choices and rationale]
## Solution
[What you built/created - include visual descriptions]
### Feature 1
[Description]
### Feature 2
[Description]
## Results
[Quantified impact]
| Metric | Before | After | Change |
|--------|--------|-------|--------|
## Learnings
[Reflections and growth]
---
## Visual Asset List
[List of images/screenshots needed]
Weekly Installs
–
Repository
GitHub Stars
180
First Seen
–
Security Audits
竞品拆解分析工具:使用 inference.sh CLI 进行结构化竞品研究与截图
7,500 周安装