Where to start
Few days ago I published "Structuring your project" where outlined basic framework for documenting a project.
Despite being basic, it's a multiline nested checklist, which is, frankly, frightening. When you have a blank piece of paper, it's difficult to start.
So, let your first step would be the creation of Whitepaper outline:
Problem
Stakeholders
Usecases
Solution
Next, write draft paragraph of the problem statement. Why are you starting the project? What bugs you? Who else is affected? What they will get from your solution?
Say, you're creating an Uniswap - automated market making exchange on Ethereum. Then, the problem statement could look like:
Many Ethereum projects create ERC20 tokens to achieve their goals. Yet, the listing process on centralized exchange is long, difficult, costly, and may be subject to regulation. On the other hand, onchain order-based exchanges are expensive to use (on-chain order storage is expensive) or subject to centralization. We introduce Uniswap: AMM exchange that always provides liquidity at any price using a simple formula. This enables permissionless trade and listing. The liquidity providers are incentivised by earning a small commission on each trade.
Your problem statement has not be perfect. On contrary, this problem statement will be subject to change, while you learn more about your users and develop your startup.
In Stakeholders section unfold the problem statement by listing everyone, who will be affected by your project.
Likewise, for the Uniswap it might be something like:
Traders: Can buy and sell any ERC20 token at any time, without permission.
Token issuers: Can list their ERC20 token for trades at any time, without permission.
Liquidity providers: Can earn additional revenue on their ERC20 token reserves by providing them as a liquidity source.
Developers: Can provide ERC20 token exchange functionality in their apps, enhancing users' experience.
You can take it from here, describing how Traders will trade, Token issuers will list their tokens, etc.
Hope, this helps get things moving.
I’ll touch other documents in the project structure in the upcoming newsletters.