Work structured into connected artifacts.
ProjectBook doesn't store tasks and documents. It builds execution artifacts — each one a deliberate step in a traceable chain of product thinking.
Eight artifact types. One connected execution system.
Five stages. One continuous thread.
The primary execution chain moves from user insight to validated outcome. Each artifact hands off context to the next — nothing is lost, nothing is assumed.
Captures the user context that initiates the entire chain. Stories encode real observations before any solution thinking begins.
"Every execution artifact has an origin in observed reality."
Frames validated pain points derived from user stories. Problems are scoped, categorised, and always traceable to the insight that surfaced them.
"Structured problems prevent premature solution thinking."
Represents solution explorations anchored to specific problems. Ideas never float in isolation — they always reference the problem they address.
"Solutions without problems are assumptions, not insights."
Moves ideas into active execution. Tasks inherit the full context lineage — the why is always visible alongside the what.
"Purposeful tasks carry their origin with them."
Validates execution outcomes against the original intent. Feedback closes the loop by feeding observations back toward the story that initiated the chain.
"Outcomes validate — or invalidate — the hypotheses that started the work."
Supporting artifacts enrich the chain.
Three additional artifact types sit alongside the primary execution chain. They provide context, documentation, and reference without disrupting workflow integrity.
Maps the full user experience across touchpoints and time. Journeys provide spatial context for pain points, enriching stories and grounding problems.
Rich documentation anchored to any artifact in the chain. Pages capture rationale and reasoning without becoming part of the execution chain itself.
External links, references, and assets attached directly to artifacts. Resources keep context close without cluttering the workflow.
Built for traceability, not just storage.
Every artifact carries the full chain of decisions that created it. When you open a Task, you see the Idea, the Problem, and the Story — not just a description of work.
Nothing is assumed. Relationships between artifacts are explicit, navigable, and searchable. The system shows you what is connected — and what is not.
Artifacts enforce their own rules. A Task without an Idea, an Idea without a Problem — these states are surfaced, not silently permitted. Structure is the feature.