Problem before solution
A discovery process should turn a proposed solution back into the underlying problem before committing to build.
GetZed Identity / Knowledge Atlas
游客可以直接浏览、收藏和记录阅读进度,数据先留在当前浏览器。Google 登录只用于云同步和账号管理;登录本身不会上传本机记录,也不代表同意全部条款。
已登录
Google 与 Cloudflare 参与账号及托管处理;跨境、保存期限、导出、删除和未成年人规则见主站法律页。正式公开前仍需专业律师复核。
reviewed
A source-backed route from problem framing through alpha prototypes, live improvement, and knowledge-card distillation.
A discovery process should turn a proposed solution back into the underlying problem before committing to build.
Discovery should end with a decision about whether the evidence justifies moving into a more expensive exploration phase.
A prototype is most useful when it focuses on the riskiest assumption instead of recreating the entire product.
Alpha work should be judged by what it teaches, not by whether the prototype survives into production.
A live product still needs research, testing, accessibility checks, quality assurance, and performance metrics.
Knowledge card distillation turns useful product lessons into short, source-linked, reusable cards.