We're now at the final step of the startup guide. SOPs don't just end after creation—they truly serve the field only when they're used in practice, refined by feedback from the floor.

Here, we'll show you how to nurture your SOPs, starting with what the field wants and what challenges they face.

Ask the field which SOPs to create

It's common to get stuck asking "which SOP should we create?" Starting with a systematic inventory tends to be heavy and slow.

Dive recommends having field members themselves post "Desired procedures." Everyone—including newcomers, View-only users, and members with Guest permission—can easily post what they want: "I want an SOP like this" or "I'm struggling here." Anyone wanting the same thing can show support by clicking "Want."

By creating SOPs in the order votes come in—which is the order they're actually needed—you reduce unused, unread procedures.

The cycle for growing desired SOPs

1. Gather: From "Desired procedures" in the sidebar, everyone on the field posts what they want and what challenges them. "Want" clicks show demand strength.
2. Create: Start with what's most wanted (= most needed). Follow the Step 1–Step 4 flow to create and publish your SOPs.
3. Respond: When you link a Completed SOP to a request, anyone who posted it or clicked "Want" gets a notification: "Responded to your request."

The more you repeat this cycle, the more real-world SOPs stack up in the field. For more details, see How to use Desired procedures (Idea notebook).

Don't let one person do all the creating

It's fine if your implementation lead creates them at first, but if one person handles everything alone, you'll stall. The "Desired procedures" board is where people who want SOPs meet people who can create them. Once your operational staff start filming and creating themselves, SOPs grow on their own.

Optional next step: Making your organization's skills visible

As SOPs are used in the field, the accumulation of usage becomes a window into skill visibility: "Who can do what and how far?" If you want to systematically manage your organization's Skill Status, use the Skill Map feature. This is an optional next step—you don't need to take it from the start.

• What is Skill Map? / How to read skill marks
• Creating a Skill Map from industry templates
• How to use Skill Map during operations

That completes the startup guide! Great work!