Separate the brief into jobs
Give goals, user problems, decisions, risks, and evidence their own Points so each can be revised independently.
Use casesProduct strategy
Turn a product brief into decisions, risks, and next work.
Product briefs often mix goals, assumptions, evidence, risks, and tasks. BaseHalf turns those pieces into a Map so teams can discuss the right object without rewriting the whole brief.
PromptCreates 3 Points
Turn this product brief into goals, user problems, decisions, open questions, risks, evidence, and next work.
- Product goal
- User evidence
- Decisions and tradeoffs
Workflow
From one request to reusable context
Open decisions as pages
Record the chosen path, alternatives, reasoning, and the condition that would make the decision change.
Keep risks connected
Reference the evidence or assumption behind each risk so mitigation work has context.
Review as the plan evolves
Promote resolved questions into decisions and convert accepted risks into tests or follow-up tasks.
Complex scenario
Example: turning a messy product brief into a launch plan
A product brief mixes a customer problem, proposed solution, risks, unresolved pricing decisions, and several follow-up tasks. The team needs a workspace, not a cleaner paragraph.
Keep the brief as source
Preserve the rough brief so the team can inspect what was assumed, unclear, or already decided.
Split the objects
Create Points for goal, user problem, audience, evidence, decisions, risks, and next work.
Open the tradeoff
Use Point pages to compare alternatives and capture why one option wins for now.
Review the plan
Promote resolved questions into decisions and turn accepted risks into tests or launch tasks.
Map structure
What the workspace should contain
Product goal
The change the work should create for users and the business.
User evidence
Research notes, support examples, customer quotes, and usage signals.
Decisions and tradeoffs
Chosen path, rejected alternatives, reasons, and revisit conditions.
Risks and tests
Assumptions that could break the plan and how the team will learn.
Outcomes
What should exist after the work
- A strategy Map that stays useful after the first draft.
- Decision memory that future teammates can inspect.
- Risks and follow-up work connected to the context that created them.