I’ll introduce the importance of keeping PRD (Product Requirements Document) continuously updated to the latest state.

What is PRD (Product Requirements Document)?

This article won’t cover how to write a PRD, so please read the following articles:

• スタートアップのための製品要求仕様書(MRD & PRD)の書き方 | by Hiroki Shimada | Medium
• 初めて書くPRD（プロダクト要求仕様書）｜94｜note

PRD is a Roadmap for Product Development

I consider PRD to be a roadmap for project development, and I believe it’s important to create and share it, then keep updating it to the latest state.

I myself have followed this flow when writing PRDs (prerequisite: this is based on startup company experience):

PRD Creation and Operation Flow

1. First create a Google Doc and immediately share it with team members
2. Create chapters and write from the parts you can write
3. Update the PRD every time there's a change
4. Announce to the team every time you update

Changes naturally occur as development projects progress.

And discussions and decision information about those changes are scattered across various places like Slack, GitHub, and verbal confirmations in meetings.

I didn’t leave it as is, but reflected it in the PRD so team members would only need to look at that one place.

That’s all from the Gemba, where I want to keep PRD always up to date so team members can develop without getting lost.