Discovery Phase

At Kindgeek, our product discovery phase is divided into two stages. In the problem identification stage, we focus on understanding your business pains, stakeholder and user needs, and product expectations to elicitate requirements. In the problem-solving stage, we delve into architecture design, and create user flows and UI/UX designs that align with your goals. We utilize high-fidelity prototypes to provide a realistic solution representation, allowing for valuable feedback and validation.

At Kindgeek, we leverage the combined power of Customer-centric design and the Lean Startup methodology throughout the product discovery phase. This helps us define clear problem statements and identify the right questions to ask. We embrace the Lean Startup approach in the solution phase to test and iterate potential solutions rapidly. 

 

To gather insights, we employ the following techniques:

 

Analysis techniques:

• Competitive benchmarking

• Process analysis

• Root cause analysis

Visualization techniques:

• Mind mapping

• Sequence diagrams

Requirements techniques:

• Functional decomposition

• Non-Functional Requirements (NFR) analysis

• User story workshops

Design techniques:

• Prototyping

Management techniques:

• Backlog management

 

Effective communication and collaboration are vital to our process. We maintain regular meetings, progress updates, and interactive sessions to align priorities. Leveraging project management software, issue-tracking systems, and collaborative document sharing, we ensure seamless coordination and transparency.

Agile approach: We follow an agile approach to project management, which involves breaking the work into smaller, manageable iterations called sprints. During weekly sprint planning, we collaborate with you to prioritize goals and deliverables based on their highest priority and value.

 

Iterative planning: By focusing on delivering tangible outcomes at the end of each sprint, we use these results as a starting point for planning subsequent sprints. This iterative process allows us to adapt and refine the scope and duration of the product discovery phase based on evolving priorities and requirements.

 

Resource allocation: We carefully assess the resources required for each sprint, including the expertise, skills, and capacity needed to meet the defined goals. Our team works collaboratively to allocate the necessary resources to ensure efficient execution and timely completion of the product discovery phase.

 

By adopting weekly sprint planning and focusing on delivering high-priority deliverables, we ensure that the product discovery phase progresses in a structured and goal-oriented manner. This iterative approach allows us to adjust the scope and duration based on evolving needs and priorities, ensuring optimal resource utilization and timely completion of the discovery phase.

We actively involve stakeholders and, if needed, end-users during the product discovery phase. We conduct stakeholder workshops, interviews, and requirements elicitation sessions to gather their feedback and insights. We also employ various end-user research methods, such as in-depth interviews and analysis, to gain insights into their preferences, pain points, and behaviors. Additionally, we conduct design testing to gather prototype feedback and ensure a user-centric approach.

At the end of the product discovery phase, you can expect several important deliverables that guide the subsequent implementation phase. These deliverables will vary based on the project scope and requirements but typically include the following:

• Click-through UI prototype

• Development-ready mockups and UI kit

• Architecture vision

• Technology, frameworks  & tools

• 3-party solution assessment

• Infrastructure vision 

• Implementation efforts estimate

• Development team composition

• Implementation budget

• Implementation roadmap

Our iterative approach and weekly sprint planning allow us to adapt the scope based on your evolving requirements and budget constraints, remove low-priority deliverables, and ensure effective budget utilization.

At Kindgeek, we proactively handle potential risks and challenges that may arise during the product discovery phase. Here's an overview of our approach:

 

• Risk Identification and Assessment: Our project manager creates a risk register, systematically identifying and assessing potential risks and challenges that could impact the project. This includes considering technological uncertainties, resource constraints, and changing requirements.

 

• Risk Management Strategies: Once risks are identified, we develop appropriate risk management strategies. This involves defining mitigation plans, contingency measures, and alternative approaches to address potential issues. We prioritize risks based on their potential impact and likelihood of occurrence.

 

• Communication and Collaboration: We maintain open and transparent communication with our clients throughout the discovery phase. We involve you, as the client, in the risk management process, seeking your input and suggestions for mitigation strategies. We ensure that you have the authority to approve and implement any necessary risk mitigation actions.

 

• Risk Response and Monitoring: If a risk event occurs, we promptly communicate it to you, providing all relevant details. We discuss the potential impact on timelines, scope, vision, and deliverables. We collaborate to adjust plans and mitigate the risk effectively.

 

• Out-of-Scope Management: We work closely with you to clearly define the project's boundaries and establish what is within the scope of the product discovery phase. If any requirements or features fall outside this defined scope, we identify them as out-of-scope items. 

 

Our goal is to ensure that any potential risks are addressed promptly and efficiently, enabling the smooth progression of the project and the achievement of your business goals.

We are committed to maintaining transparency and open communication regarding budget control and any potential additional costs. Here's how we ensure budget control and address any additional costs:

 

• Budget Burndown: We closely monitor and track the budget throughout the product discovery phase. By regularly reviewing the actual expenditure against the planned budget, we maintain transparency and provide visibility into how the budget is being utilized. This helps us identify any deviations and take corrective actions, if necessary, to stay within the agreed budget.

 

• Monthly Budget Predictions: We provide monthly budget predictions outlining the expected expenses for each phase of the product discovery process. This lets you understand the projected costs and make informed decisions based on your budget constraints.

 

Following the Scrum methodology ensures you receive actionable deliverables regardless of your budget after each sprint. Our iterative approach allows us to provide value consistently throughout the product discovery phase.

 

Regarding additional costs, we may request a license or other resources if your project scope includes third-party testing and investigation. Any such potential costs will be communicated to you in advance. We will provide detailed information about the nature of these costs, allowing you to decide whether to proceed with them or explore alternative solutions.

Our criteria for transitioning from the product discovery phase to the implementation phase are as follows:

 

• High-Level Vision, Design, and MVP Scope: We consider completing the high-level vision, design, and solutions for the Minimum Viable Product (MVP) scope an essential criterion for transitioning. This ensures a clear direction and understanding of the product's goals and features.

 

• Detailed Vision for Future Sprints: We require a clear vision for the upcoming sprints, including specific features, functionalities, and priorities to be implemented. This enables a smooth progression and incremental development of the product.

 

To ensure a seamless transition and continuity, we follow these practices:

 

• Gradual Onboarding: If additional team members are required for the implementation phase, we gradually onboard them. This approach allows for effective knowledge transfer and ensures the new team members are familiar with the project and its objectives.

 

• Option for Internal Team: If you prefer to proceed with your internal team for the implementation, we provide all the actionable deliverables from each sprint. These deliverables guide your team, outlining the user stories, feature specifications, and other necessary documentation.

 

By meeting these criteria and facilitating a smooth transition, we aim to ensure that the product discovery phase seamlessly integrates with the implementation phase. This approach promotes effective collaboration, knowledge transfer, and successful execution of your project.