We've finally reached the last step of the getting started guide. SOPs are not just "create and done"—they truly work on the floor only when they are used on the floor and grow from floor feedback.

Last, we'll introduce how to grow SOPs starting from the floor's "want" and "issues".

Ask the floor which SOPs to create

"I don't know which SOP to create" is something that often stops progress. When you try to organize everything from the start in a structured way, it becomes heavy and it's hard to move forward.

That's why Dive recommends having floor Members themselves post "Desired procedures" they want. Newcomers, View-only users, and Guest invitations—everyone can easily post "I want this kind of SOP" or "I had trouble here", and people who want the same thing can support it with "want".

By creating SOPs in the order that votes are gathered = the order that is truly needed, you can reduce SOPs that are created but not used.

Cycle to nurture Desired procedures

1. Collect: From "Desired procedures" in the sidebar, everyone posts the floor's "wants and issues". "Want" shows the strength of demand.
2. Create: Start with those with many "wants" (= those that are needed). Create and Publish SOPs following the flow of Steps 1 to 4.
3. Respond: When you Link a Completed SOP to a request, "Responded to your request" Notifications are sent to the person who posted and those who pressed "want".

The more you run this Cycle, the more SOPs that are actually used on the floor accumulate. For detailed instructions, see How to use Desired procedures (idea notebook).

Don't let one person do all the creating

At first, it's OK if the implementation lead creates them, but if one person does it all, progress stops. The "Desired procedures" board is a place where people who want something and people who can create it meet on the same screen. When a culture starts where business owners shoot and create themselves, SOPs grow on their own.

Further: to visualize your organization's Skills (Optional)

Once SOPs start being used on the floor, this accumulation also leads to visualizing "who, what, and how far they can do" in terms of Skills. If you want to systematically manage your organization's Skill Status, use the Skill Map Feature. This is an optional advanced step. You don't need to work on it from the start.

• What is Skill Map? / How to read Skill marks
• Create a Skill Map from Industry templates
• How to use Skill Map during operations

That concludes the getting started guide! Thank you for your hard work!