You've reached the final step of the startup guide. An SOP isn't "complete" when you finish writing it—it becomes a true skill-transfer system only when it's used on the floor and refined through real feedback from your team.

Here's how to grow your SOPs by starting with what your team actually needs and struggles with.

Ask the floor what SOPs to create

It's common to get stuck wondering, "Which SOP should I make first?" Trying to map everything out systematically from the start feels heavy and makes progress slow.

That's why we recommend having team members post the SOPs they want directly. Everyone—including new hires, view-only users, and guests—can easily post requests like "I need a procedure for this" or "I got stuck here," and others who want the same thing can upvote with "+1."

When you create SOPs in order of votes received, you're building only what's actually needed and cutting down on unused documentation.

The cycle for growing desired SOPs

1. Collect: Everyone posts what they need or where they struggle in "Desired procedures" from the sidebar. The "+1" votes show how urgent the need is.
2. Create: Start with the requests with the most "+1" votes (the most needed). Create and publish SOPs following the Step 1–Step 4 process.
3. Respond: When you link a completed SOP to a request, everyone who posted it or upvoted it gets a notification: "Responded to your request."

Each cycle you run builds more SOPs that are actually used on the floor. For detailed instructions, see How to use Desired procedures (Idea board).

Don't let one person handle all the creation

It's fine for the person managing the rollout to create SOPs at first, but if one person owns it all, things will stall. The "Desired procedures" board is where people who need something and people who can make it meet on the same screen. Once your team culture shifts to people shooting their own content and creating SOPs themselves, your SOP library will grow on its own.

Next: Visualize your organization's skills (optional)

As SOPs get used on the floor, that work builds toward visibility of "who can do what and to what level"—a skills snapshot. If you want to manage your organization's Skill Status systematically, try the Skill Map feature. This is an optional advanced step. You don't need to start it right away.

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

That's the end of the startup guide. Great work!