“Useful on its own” is clear. What behavior will show that each product has earned repeat use?
AnswerJB
Strategic choiceBuild for the next product decision
In reviewOwner: JordanReview Aug 12
Decision
Keep each tool useful on its own.
Product Hub and Feedback share one project space, but neither depends on a manufactured suite workflow.
Applies toEntire product
What would change this choice?Add the missing counter-evidence before approval.
Agent review2 open
This principle governs the entire product, not only the current modules.
ConfirmedProduct Hub
Keep the product clear while the software changes.
A living product record and collaborative space where people and agents build, challenge, and maintain the context behind what you make.
Useful for one builder first. Ready when a team or agent joins.
Building got faster
Software can be generated quickly. Direction cannot.
More implementation capacity does not answer who the product is for, which problem matters, what evidence to trust, or why one choice is better than another.
Old documents look authoritative
Strategy, research, and decisions drift across pages, notes, and conversations long after their assumptions have changed.
Speed amplifies unclear choices
When the direction is weak, faster implementation only lets the product drift faster.
Every handoff rebuilds context
People and agents repeatedly reconstruct users, constraints, evidence, and intent before useful work can begin.
One living product record
A maintained record of what the product means.
Connect the reasoning behind the work without turning every choice into a document-production exercise.
Establish the context
Record who the product serves, what matters now, what has been learned, and what remains uncertain.
Make choices inspectable
Keep the owner, evidence, scope, review state, comments, and history attached to consequential decisions.
Revisit what may no longer be true
Treat product context as something with a lifecycle—not a page that becomes authoritative merely because it exists.
StrategyOutcomesProblemsDiscoveryCommitmentsReleasesLearning
Clear scope, little administration
One product record. The parts stay distinct.
Keep product-wide context beside context for a particular module or offering. Product Areas show whether a record applies to the whole product, one area, or several—without separate workspaces or a portfolio hierarchy.
Entire productProduct HubFeedbackProduct Hub + FeedbackNot classified
People own the product
Agents should challenge the context, not merely generate more of it.
Product Hub is being built for agent skills that gather missing input, expose assumptions, run adversarial reviews, find contradictory or stale claims, and prepare task-relevant context. Consequential changes remain visible and human-owned.
Interview for missing context
Ask collaborators for the evidence, constraints, and definitions a record still needs.
Run adversarial reviews
Expose assumptions, counter-evidence, contradictions, and choices that are not ready.
Maintain the record
Find stale claims, overdue reviews, and context that no longer matches current work.
Brief other agents
Supply the relevant context to coding, research, and planning agents without a blank prompt.
The boundary
Not another static wiki.
Product Hub is a system of record for product thinking and a place to develop that thinking collaboratively. Stored context is not assumed to be correct merely because it exists.
The promise
Not strategy by autocomplete.
The job is to keep reasoning available, testable, and current enough to guide the next change—not to outsource judgment to an AI-generated summary.
Start with the context you already depend on
Give the next build a clearer reason.
Make your product context easier to question, maintain, and use—before more software gets generated in the wrong direction.