> ## Documentation Index > Fetch the complete documentation index at: https://docs.bluplai.com/llms.txt > Use this file to discover all available pages before exploring further. # Challenges > Map the friction points, pain, and blockers standing between the customer and their goals. Challenges section on the Discover page showing the header Challenges with subtitle Friction points mapped as opportunities, an Add Challenge button, and an empty state reading No challenges identified yet with the prompt Add challenges and friction points to track and resolve. ## Why you're here The Challenges section sits below Goals on the Discover page and captures what's in the way. Every friction point, pain, blocker, or risk the customer raises lives here — framed as an opportunity rather than a complaint. Logged challenges travel forward into Qualify (where they become validated problems) and Plan (where they map to initiatives and actions). ## What you'll see The section header reads "3 Challenges — Friction points mapped as opportunities." Inside, a sub-header shows **Challenges** and a counter (for example, "0 challenges identified") with a black **+ Add Challenge** button on the right. When no challenges have been logged, the empty state displays a warning triangle icon, the text "No challenges identified yet," and a prompt: "Add challenges and friction points to track and resolve." Click **+ Add Challenge** to log one — name the friction point, note the goal it blocks, and capture any early thoughts on how to resolve it. ## Creating a challenge Add Challenge dialog with fields for Title, Description, Priority, Status, Owner, and Due Date, and a dark Add Challenge button. ### Why you'd create one A challenge captures a friction point, pain, or risk standing between the customer and their goals. Logging it here makes it a tracked record that travels into Qualify → Value case (so the problem is sized against the outcome it blocks) and Plan → Risks (so delivery work accounts for it). ### How to create one From `/discovery?section=challenges`, click **+ Add Challenge** in the top right of the Challenges sub-header. Short name for the challenge — the friction point framed as an opportunity. Longer explanation of the pain, what it blocks, and any early thoughts on how to resolve it. How urgent the challenge is relative to others. Defaults to Medium. Current state of the challenge. Defaults to Open. Person accountable for resolving the challenge. Defaults to None. Target date to have the challenge resolved or decided. Click **Add Challenge**. The new challenge appears in the Challenges section with its counter incremented. ### What happens after A saved challenge feeds Qualify → Value case as a validated problem attached to the goal it blocks, and it shows up in Plan → Risks so the team can track mitigation alongside the initiatives that resolve it. ## When to use it * During a discovery call when a stakeholder describes something that's not working today. * After reviewing call notes or AI-extracted insights, logging each pain point so it doesn't get lost between stages. * Pairing a new challenge to an existing goal so the relationship between "what they want" and "what's in the way" is explicit. * Before moving to Qualify, reviewing the challenge list with the customer to confirm priority. ## Next Drop raw notes and half-formed ideas onto the shared whiteboard. Map each challenge to a proposed solution and score the fit.