android-mcp

--- ### **The Idea-to-Execution Brainstorming Workflow** This workflow is designed to guide you and your team through five distinct phases, moving from a vague problem to a concrete plan. #### **Phase 1: Define the Core Problem & Vision (The "Why")** **Goal:** To establish a crystal-clear understanding of the problem you are trying to solve before you even think about solutions. If you get this wrong, everything that follows will be flawed. **Guiding Question:** *Are we solving a real, important problem?* **Activities & Questions to Answer:** 1. **Problem Statement:** * What is the specific problem or unmet need? (e.g., "Our login process is insecure and causes user frustration.") * Be precise. Use data if you have it (e.g., "We get 200 password-reset support tickets per week."). 2. **Target Audience / Persona:** * Who is experiencing this problem? (e.g., "All of our general banking customers who use the web portal.") * What are their goals and motivations? 3. **Impact & Pain Points:** * Why does this problem matter? What are the consequences? (e.g., "It hurts user trust, increases operational costs, and makes us look outdated.") 4. **Vision & Success Metrics:** * In a perfect world, what does the solution look like? (e.g., "A secure, seamless login experience that users love.") * How will we measure success? (e.g., "Reduced support tickets, faster login times, positive user feedback.") > **Phase 1 Output:** A one-page summary that everyone on the team agrees on. This is your "North Star." --- #### **Phase 2: Divergent Brainstorming (The "What If?")** **Goal:** To generate the widest possible range of potential solutions without judgment. At this stage, there are no bad ideas. Quantity over quality. **Guiding Question:** *What are all the possible ways we could solve this problem?* **Activities & Techniques:** 1. **Set the Stage:** Gather a diverse group (engineers, designers, support staff, etc.). Set a timer (e.g., 25 minutes). 2. **Quantity Over Quality:** The goal is to fill the whiteboard. Encourage wild ideas. 3. **Use Prompts to Spark Creativity:** * **The "Magic Wand":** If technology and budget were no issue, what would we do? * **Remove a Constraint:** What if we had to build it in one day? What if we had to do it with zero budget? * **The "How would [X] do it?" Method:** How would Apple solve this? How would Google? How would a 5-year-old? * **Working Backwards (Amazon's Method):** Start by writing the future press release or FAQ for the perfect solution. What does it say? > **Phase 2 Output:** A long, unorganized list of raw ideas (e.g., on sticky notes, a whiteboard). --- #### **Phase 3: Convergent Refinement (The "How")** **Goal:** To systematically evaluate the raw ideas and select the most promising candidates. This is where you switch from creative to critical thinking. **Guiding Question:** *Which ideas are the most viable and impactful?* **Activities & Techniques:** 1. **Group & Theme:** Organize the raw ideas into logical categories or themes. 2. **Impact vs. Effort Matrix:** This is the most powerful tool in this phase. Draw a 2x2 grid. * **X-Axis:** Effort (Low to High) * **Y-Axis:** Impact (Low to High) * Place each idea onto the matrix. This will reveal four categories: * **High Impact, Low Effort (Quick Wins):** Do these now! * **High Impact, High Effort (Major Projects):** Plan these carefully. * **Low Impact, Low Effort (Fill-ins):** Do them if you have free time. * **Low Impact, High Effort (Time Sinks):** Avoid these. 3. **Define Selection Criteria:** Score the top ideas (e.g., from 1 to 5) against your project goals. * **Impact:** How well does it solve the core problem? * **Effort:** How complex is it to build? (Rough estimate is fine) * **Alignment:** Does it fit our strategic vision? * **Risk:** Are there any major security or technical unknowns? > **Phase 3 Output:** A short, ranked list of 1-3 promising solutions. For our project, "Passwordless QR Login" was the clear winner. --- #### **Phase 4: Define the First Feature (The "What")** **Goal:** To create a clear, detailed definition of the chosen solution's first version (the Minimum Viable Product). **Guiding Question:** *What is the smallest version of this idea that delivers real value?* **Activities & Techniques:** 1. **Write the Core User Story:** "As a [user type], I want to [perform an action], so that I can [achieve a benefit]." 2. **Define Scope (In / Out):** * **In Scope:** List the absolute must-have features for the MVP. (e.g., "Must display QR code," "Must have mobile approval screen with context.") * **Out of Scope:** List all the great ideas that you are *intentionally not building yet*. This is critical for preventing scope creep. (e.g., "Number matching," "Device management dashboard.") 3. **Draft High-Level Requirements:** Briefly list what the web, mobile, and backend components need to do. This is a simplified version of the PRD. > **Phase 4 Output:** A one-page MVP definition that is clear enough for an engineer to start designing a technical solution. --- #### **Phase 5: Outline the Execution (The "Who & When")** **Goal:** To create a rough, high-level plan for how to bring the MVP to life. **Guiding Question:** *What are the major steps and potential roadblocks?* **Activities & Techniques:** 1. **Identify Key Tasks:** What are the major workstreams? (e.g., Backend API design, Web UI development, Mobile UI development, Security review, QA plan.) 2. **Assess Risks:** What could go wrong? What are the biggest unknowns? 3. **Assign Roles:** Who needs to be involved? Who is the project lead? 4. **Estimate a Timeline:** This is a rough estimate, not a commitment. Break it down into phases (e.g., Design, Development, Testing, Launch). > **Phase 5 Output:** A basic project outline that can be used to kick off the detailed technical planning (TRD) and development sprints.