> ## Documentation Index > Fetch the complete documentation index at: https://docs.dacard.ai/llms.txt > Use this file to discover all available pages before exploring further. # Read people, process, and product tensions > How the three-framework tension map surfaces your biggest growth constraints. Three frameworks, three reads. When team capability, process maturity, and product capability are aligned, you compound. When they're not, the tension map tells you where to invest. # Read people, process, and product tensions As a founder, you want to read the tensions between your team's capability, your build process, and your product itself so you can surface the real constraint on growth and put resources on it. ## The three-framework tension map Each framework reads a different thing. | Framework | What we read | Think of it as | | ------------------------- | --------------------------------------- | ----------------------------------------------- | | **Team Operations** | Team capability across 27 dimensions | **People** (can your team execute?) | | **Development Lifecycle** | Build process maturity across 6 stages | **Process** (do you have discipline?) | | **Product Assessment** | Product capability across 27 dimensions | **Product** (does the product show capability?) | When the three are aligned, you compound. When they're misaligned, you have tension, and the tension tells you where to invest. ## Common tension patterns ### Product ahead of team **What it looks like:** your product has impressive features, but team operational maturity hasn't kept up. You shipped fast, probably with a small founding team, but now scaling is hard. **Symptoms:** * Features break and nobody knows why * Inference cost is rising faster than revenue * New hires can't maintain what the founding team built * Quality is uneven across features **The move:** invest in operational maturity. Establish monitoring, eval frameworks, and documentation before adding more capability. Slow product velocity to let operations catch up. ### Team ahead of product **What it looks like:** you have a strong, experienced team that follows good process, but the product itself hasn't yet expressed that capability. **Symptoms:** * The team talks about capability but the product doesn't show it * Internal tools are more capable than the customer-facing product * Engineering uses Copilot or Cursor but the product has no equivalent * Competitive products are pulling ahead on integration **The move:** channel your team's capability into the product. The skills are there; the bottleneck is product strategy. Run a lifecycle assessment to surface which build stages are incomplete. ### Process without capability **What it looks like:** you've adopted modern process (agile, discovery, eval frameworks) but the team doesn't have the skills to execute it well. **Symptoms:** * Ceremonies and process exist but don't produce outcomes * Retros surface problems but nothing changes * The team follows a playbook but can't adapt when it doesn't work * High process overhead with low output quality **The move:** hire or upskill before adding more process. Process amplifies capability. Without capability, it amplifies frustration. ### All three misaligned **What it looks like:** team, process, and product are all at different maturity levels. The most common pattern for early-stage companies. **Typical example:** team at Building, lifecycle partially done, product at Foundation. The team has some skills, limited process, and capability hasn't yet shipped into the product. **The move:** start with the quickest win. For most founders, that's operational maturity (it creates the foundation for everything else). Then establish process and apply both to the product. ## Using tensions in board conversations Tensions aren't weaknesses. They're investment signals. Frame them for your board. * "Our tension map shows team capability (58) is ahead of product capability (34). We have the talent but haven't yet prioritized capability in the product. We're addressing this with \[specific initiative]." * "Our product (72) is ahead of our operations (45). We need to invest in operational maturity to sustain our product lead. We're hiring \[role] and implementing \[process]." ## Running the tension analysis Head to `/score` and score your product URL for the 27-dimension maturity read. Open the Lifecycle tab and run the 36-task self-assessment with your team. Open the Product view for the product-level capability read. Ask DAC: "compare my three frameworks and surface the biggest tension in my organization." The most useful tension analysis comes from running the Lifecycle assessment with your leadership team together. Different members often have different reads of process maturity. The conversation itself is valuable. ## What's next Frame your tension analysis for investor conversations. Package tension maps for stakeholders. The cross-framework read for deeper analysis. Ask DAC to build a plan grounded in your tensions.