Talk it through. Leave with the SOP.
20 minutes. Bring one real process. Leave with the finished document.
Finished SOP
Hiring and onboarding
| # | Role | System | Deadline | Action |
|---|---|---|---|---|
| 1 | Hiring manager | ATS | Within 1 day | Submit approved role brief |
| 2 | Recruiter | ATS | Within 2 days | Publish the vacancy |
| 3 | Hiring manager | Calendar | Within 3 days | Complete candidate interviews |
| 4 | COO | Slack | After 5 days | Escalate if the role remains blocked |
From conversation to an accountable process.
Talk it through
Describe the process by voice or text. Start with what people actually do, not with a blank template.
Answer the gaps
The assistant asks for ownership, verification, systems, deadlines, and the escalation path.
Use the finished SOP
Receive one consistent document that can sync with Confluence, Notion, or Markdown.
Every document follows the same clear structure.
No improvised format. No hidden accountability. The same questions must be answered every time.
The last row is always the escalation: the named action that starts if the process does not finish on time.
A structure informed by published standards.
The method draws on established approaches for accountability, process ownership, plain language, and process classification. BI Bootstrap does not imply certification.
The document lives where the team already works.
Two-way sync keeps the process document in Confluence, Notion, or Markdown. Every version can remain visible in git history. BI Bootstrap does not have to become another place people forget to open.
Useful because it is explicit. Honest about its limits.
BI Bootstrap documents the process people describe. It does not observe the work, infer what really happened, or update the SOP by itself.
If someone describes a process differently from how it actually runs, the document will differ too. The finished SOP makes that description concrete enough for the team to review and correct.
Bring the process that is slowing your team down.
In 20 minutes, talk through one real process and see it become a finished, structured SOP.