Team building &
1st Hackathon
Let’s Start
*
Let’s Start *
Today, you aren’t just joining a program; you are entering a high-intensity laboratory. These first two days are designed to help you master the craft of building and to forge the bonds that define great teams.
Why are we working on external challenges?
We have assigned external challenges rather than letting you dive straight into your own startups.
Why? Because it levels the playing field. It allows you to detach your focus from the "idea" and focus entirely on the methodology: customer validation, rapid prototyping, and team dynamics.
Don't worry: You will have plenty of opportunities to apply these exact frameworks to your own ideas as we move forward. Think of this as a "test" to sharpen your tools before the real mission.
Challenge
Problem Refinement
The HMW questions provided below are general challenges. Think of them as a starting point: you are encouraged to adapt and pivot them based on the specific direction your team chooses to explore.
Validating the Market
To build a robust and venture-backed solution, you must step out of your "bubble" and validate the problem using real-world data.
1. Identify your Ideal Customer Profile (ICP)
Your first goal is to map out who suffers most from the problem you are solving. Your fellow participants in this program are your first "living laboratory." Look for potential users and "early adopters" among members of other teams:
The Specialist: Does their specific role (Developer, Legal, Marketing, etc.) lead them to face this problem daily?
The Power User: Are they using workaround tools or "hacks" because the official solution is too slow or non-existent?
The Decision Maker: Would they be the ones paying for a solution, or are they just the ones feeling the pain?
2. User Interviews & Data Collection
Conduct brief (10–15 minute) discovery interviews with people around you to gather qualitative evidence:
Capture real-world use cases: "Tell me about the last time you faced [Problem X]. What were you trying to achieve?"
Gauge the "Pain Level": "How are you solving this right now? On a scale of 1-10, how frustrated are you with the current process?"
Identify Friction: "What is the biggest obstacle stopping you from being more efficient/secure/productive in this task?"
3. Segmentation & Focus
Analyze your interview findings to segment your potential targets.
Who has the highest frequency of this problem?
Who faces the highest risk (financial, legal, or time-wise) if the problem isn't solved?
This process will allow you to transition from a broad challenge to a laser-focused market solution with a validated target audience.
Final Output
Each team is required to deliver three outputs by Sunday:
Teams must carry out a minimum of 5 interviews with real potential users, documenting key insights, recurring pain points, and any pivots in their understanding of the problem.
A tangible, testable representation of the proposed solution. This does not need to be a fully functional product. What matters is that the prototype has been tested with at least 2 real users and that the team can demonstrate what they learned from that testing.
A pitch deck covering: the problem and the evidence behind it, the proposed solution, the target user, a demo of the prototype. Presentations are 3 minutes followed by 5 minutes of Q&A.
Your Toolkit
To help you build faster, we’ve unlocked two essential resources for you:
Lovable Pro Access
Build full-stack web apps in minutes using this vibe coding tool.
Link: XXX
Code: XXX
Note: You must use the email address you used to register for Dock Startup Lab for the code to be valid.