# Explore Captured Product Flows Captured product flows help you review how people move through a product and how screens, components, and supporting systems relate to one another. Use this view when you need to understand a user journey before reviewing, documenting, or publishing product knowledge. ## Overview Product flows provide a structured way to explore the paths captured from a product. Rather than reviewing isolated screens, you can use flows to understand the sequence of user actions and the relationships between parts of the product experience. This is especially useful when you are preparing documentation, validating a review, or trying to understand how a feature works from beginning to end. For example, a flow may show how a user starts on one page, uses a component or action, and then reaches another part of the product. Captured information can include frontend, backend, database, API schema, configuration, documentation, and infrastructure areas. This broader context helps you distinguish the visible user experience from the systems that support it. Relationships can also help explain how components render other components or use shared functionality. > 📷 _Screenshot pending: Product flow review area showing captured journeys and their connected product elements._ ## Prerequisites Before you begin, make sure that you have: - Access to the relevant project and version. - A product review that contains captured information. - Permission to view the project’s review materials. - An understanding of the feature, journey, or business process you want to investigate. - A completed or in-progress review when you need to use **Review & Publish**. ## Step-by-Step Instructions 1. **Open the project review for the version you want to examine.** Start from the relevant project and open its version review. The review area is where you can assess captured information before it is turned into published documentation. If you are returning from another review area, select **Back to Review** to return to the main review context. 2. **Open the product-focused view.** Select **Product** when you want to focus on the captured product experience rather than source-oriented details. This view is useful for understanding journeys in terms of screens, interactions, and user-facing behavior. Depending on your review context, you may also see **Loop Flows**. Use it to examine repeated or connected flow paths that may be relevant to a broader journey. 3. **Review the flow summary.** Select **1 Review Summary** to see the current review summary. Use the summary to orient yourself before examining individual journeys or product areas. Look for the sequence of captured steps and identify: - Where the journey begins. - Which user-facing area or action advances the journey. - Where the journey ends or changes into another flow. - Any connections to related components, pages, or services. 4. **Follow the journey in the order it is presented.** Review each captured step from start to finish. Treat each step as part of a user journey, not as an isolated implementation detail. As you review, ask what the user is trying to accomplish at that point and what outcome they should expect. Where the captured view identifies entities, use their type to understand their role. For example, a captured entity may represent a page, layout, component, hook, route, context, provider, store, controller, service, repository, or middleware. User journeys will usually be easiest to understand when you begin with pages and components, then use the supporting relationships only when more context is needed. 5. **Use relationship information to clarify connections.** When a flow shows relationships between items, use them to understand how one part of the experience leads to another. A relationship may indicate that one component **renders** another component or **uses** shared functionality. This is helpful when a journey appears to change unexpectedly. Instead of assuming a gap in the captured flow, check whether the current item connects to another component, hook, or page. 6. **Switch to source-oriented context only when necessary.** If you need additional detail to validate what was captured, select **View Source** or **Source**. Use this view to confirm supporting context, then return to the product review so that you can continue assessing the journey from the user’s perspective. Avoid relying on source-oriented details as the primary description of the journey. Your documentation should explain what users see and do. 7. **Prepare the flow for documentation review.** When you understand the journey, return to the summary and select **Review & Publish**. This lets you move from exploration into reviewing the documentation output. You may also see **Preview** or **2. Preview Modal** during the review process. Use preview options to check whether the flow is understandable before publication or export. > 📷 _Screenshot pending: Review Summary showing product-flow information and the Review & Publish action._ ## Tips and Best Practices - **Start with the user’s goal.** Identify what the user is trying to complete before examining supporting technical relationships. This keeps your review focused on the actual product journey. - **Review flows in sequence.** A captured flow is most valuable when read from beginning to end. Skipping directly to a connected item can make it difficult to understand why the user reached that point. - **Use categories for context, not as the journey itself.** Categories such as frontend, backend, database, API schema, configuration, documentation, and infrastructure help you understand scope. The product flow should still be described in terms of user actions and outcomes. - **Check repeated paths carefully.** When using **Loop Flows**, look for steps that may recur or connect to another journey. Repeated paths can indicate shared navigation, reusable interactions, or a point where users may need clearer guidance. - **Preview before publishing.** Use **Preview** to confirm that the journey is understandable to someone who did not capture it. If the sequence is unclear, return to the review and clarify the flow before selecting **Review & Publish**. - **Use source context sparingly.** **View Source** can help verify a connection, but it should not replace a plain-language explanation of the user experience. ## Related Pages - [Review and Publish Documentation](#) - [Use the Review Summary](#) - [Preview Documentation Before Publishing](#) - [Export Documentation](#) - [Understand Product Intelligence](#) ## Troubleshooting ### You cannot find the flow you expect Return to **1 Review Summary** and confirm that you opened the correct project version. A flow may be associated with a different version or may not have been captured in the current review. ### The journey is difficult to follow Review the flow from its first step and inspect the relationships between connected items. If needed, use **View Source** to confirm supporting context, then return to the product view to describe the journey in user-facing terms. ### You are not ready to publish Do not select **Review & Publish** until the flow sequence and user outcome are clear. Use **Preview** to assess the documentation output, then return with **Back to Review** if you need to continue exploring or refining your understanding.