Example brief used for this template
Hypothetical creation brief for this authored edition, not a historical prompt transcript. The sample answers describe the actual example rendered here.
- Purpose and audience
- A market landscape organized by user needs, solution approaches, and evidence gaps.
- Working context
- This fictional landscape examines ways small teams organize project knowledge. It is a conceptual map, not a current estimate of market size, share, or vendor performance.
- Example records
- Approach: Shared storage · Primary job: Keep files accessible · Typical tradeoff to investigate: Context lives elsewhere
Approach: Knowledge base · Primary job: Explain recurring work · Typical tradeoff to investigate: Needs editorial maintenance
Approach: Project workspace · Primary job: Coordinate current delivery · Typical tradeoff to investigate: History can become scattered
Approach: Personal notes · Primary job: Support individual thinking · Typical tradeoff to investigate: Sharing may be inconsistent
- Content decisions
- Define the boundary: The landscape concerns project knowledge for small teams, not every collaboration product. State what is inside and outside the analysis before comparing approaches.
Look for unmet work: A team may already store files successfully but struggle to transfer responsibility. Investigate that specific task rather than assuming the market needs another all-purpose workspace.
Evidence needed: For a real assessment, collect current product observations, customer behavior, and credible market sources. Separate known facts, estimates, and hypotheses in the final map.
- Format and interaction
- comparison layout; section navigation and expandable detail where useful; matching portrait document PDF.
- Sharing and provenance
- A hypothetical example informed by Claw Me’s small-team and Agent workflows. These are not Pete’s actual clients, finances, travel plans, research results, or commitments. Keep the real adaptation private until the owner chooses to share.