### 🧩 What are we building and who is it for? Defining the problem is the foundation of every successful product. Without a clear understanding of the problem you're solving and who you're solving it for, it’s easy to build features that feel disconnected, misaligned, or unnecessary. When you get it right, everything becomes easier—from prioritizing features to onboarding users. ## 💡 What is the problem we're solving? This isn't just a feature list—it’s a clear, concise statement of the core solution you’re working on. It should reflect: - The job your product is helping users get done - The pain or inefficiency it's solving - The value users will gain from using it This part of the problem definition ensures the team is aligned on what you're actually trying to deliver, not just what you're building in code Avoid vague or overly technical descriptions. Focus on intent and outcome. **Good examples:** - _We’re building a lightweight tool for remote teams to run fast, asynchronous user research without formal training._ - _We’re building a dashboard that gives operations leaders real-time visibility into supply chain risks._ ## 👥 Who are we solving for? Identifying your [[Customers|target audience]] means going [[Customers|beyond demographics]] and job titles. You need to understand: - Their [[Roles]] and contexts - Their pain points and goals - Their current alternatives (competitors, workarounds, or inaction) Forge encourages you to root this in [[Personas]], interviews, and [[User Research]]—not assumptions. Knowing your user deeply helps you make better product decisions, prioritize features, and communicate value. **Helpful questions to ask:** - Who feels this problem the most urgently? - Who will benefit the most from our solution? - Who will make the decision to adopt or buy this?