The problem
Discovery, customer evidence and product decisions scatter across decks and threads. The roadmap remains. The reasoning that produced it is harder to find.
What goes in the repository
- Customer problems
- Product principles
- Discovery
- Specifications
- Experiments
- Positioning
- Strategy
- Decisions
product/ ├── index.md ├── strategy/ ├── discovery/ ├── customers/ ├── decisions/ └── specs/
Why an open repository helps
Later work is easier to judge when the strategy and the evidence are still in the same place as the decision.
How Okide helps
Okide keeps strategy, discovery and decisions as linked files, so a new request can be read against what the product already decided.
Humans and agents, same files
Product agents can evaluate new work against existing strategy and customer evidence rather than optimizing the latest request in isolation.
OPEN BY DEFAULT
Keep the repository. Change the tools around it.
The roadmap can change. The reason for the last change should still be readable. Okide helps you work with the repository without turning it into an Okide-only format.