tech
Workflow
The sequence of steps that takes a task from start to completion.
Definition
A workflow is the defined sequence of steps a task moves through: who does what, in what order, with what handoffs. Common workflows in service businesses: lead-to-customer, customer onboarding, project delivery, invoicing-to-collection. Documented workflows reveal inefficiency, enable handoffs, and allow automation. Undocumented workflows live in the founder's head and break the moment they're delegated.
The five workflows every US service business should document first
Priority order. Lead-to-customer: prospect inquiry to signed contract; defines sales motion, response time SLAs, qualification criteria. Customer onboarding: contract signature to first delivered value; defines kickoff, expectations, initial deliverables, success metrics. Project delivery: from kickoff to final deliverable; defines milestones, review cycles, change management. Billing and collection: invoice creation to payment received; defines billing trigger, invoice format, follow-up cadence, late escalation. Customer renewal or expansion: from contract end to next contract; defines QBR cadence, renewal conversation timing, expansion offer criteria. Most US service businesses have all five workflows running implicitly in founder's head; documenting them is the first step to scaling beyond founder capacity. Budget 4 to 16 hours per workflow for initial documentation, plus quarterly review and refinement.
How to document a workflow effectively
Effective workflow documentation has six elements. Purpose: one sentence on why this workflow exists and what outcome it produces. Trigger: what initiates the workflow (form submission, contract signature, calendar date, manual start). Steps: numbered sequence with single action per step, owner per step (role not person name), expected duration per step. Handoffs: explicit transitions where work moves between people or systems. Tools and templates: links to specific templates, software systems, or scripts used at each step. Success criteria: how you know the workflow completed successfully. Use a consistent template across all workflows; Notion, Confluence, ClickUp, or Process Street work well. Visual workflow diagrams (Lucidchart, Miro, Whimsical) help for complex multi-handoff workflows. Update workflows quarterly; outdated documentation is worse than no documentation.
Identifying workflow bottlenecks
Three diagnostic questions reveal bottlenecks. One, where does work pile up? The step with persistent backlog is the constraint. Two, where do handoffs fail? Steps with dropped balls, missed handoffs, or rework signal handoff design problems. Three, where is the most rework? Steps where work is redone or corrected indicate quality or specification issues upstream. US service business workflow bottlenecks predictably cluster: senior review steps (founder reviews everything, becomes constraint), client communication steps (waiting on client responses), and approval steps (multiple stakeholders required before next step). Address bottlenecks by reassigning ownership (delegate senior reviews), restructuring (eliminate unnecessary approval steps), or batching (group review tasks rather than per-item). Theory of Constraints applies: improve only at the bottleneck; improvements elsewhere create inventory but no throughput gain.
When to automate workflows
Three criteria for automation candidacy. Volume: workflow runs at least 20 times per month; below that, automation maintenance cost exceeds savings. Stability: workflow has not changed materially in 6 months; automating a frequently-changing workflow creates constant rework. Repeatability: steps are rule-based rather than judgment-based; rule-based steps automate well, judgment-based steps benefit from AI assistance rather than full automation. For US small businesses, the highest-ROI automated workflows are: lead capture and CRM update, customer onboarding email sequences, billing and payment reminders, calendar scheduling, internal status updates. Avoid automating customer-facing communication that requires judgment without human review checkpoints. Workflow automation is high-leverage when applied to the right workflows; misapplied automation creates more problems than it solves.
FAQ
What is the difference between a workflow and a process?
Largely overlapping terms with subtle distinction. Process: broader concept including the work itself, the rules governing it, and the outcomes produced. Workflow: more specific - the sequence of steps and handoffs within a process. A 'sales process' encompasses your overall sales philosophy, methodology, qualification framework, and culture; a 'sales workflow' is the specific sequence: lead arrives, qualify within 24 hours, schedule call, demo, proposal, close. In US business usage, the terms are often interchangeable; do not get hung up on the semantic difference. Use whichever term is clearer in your context.
Should I document workflows in writing or in software?
Both. Written documentation (Notion, Confluence, Google Docs) captures the why and the context; software (Asana, ClickUp, Monday, Process Street) operationalizes the workflow with task assignment, due dates, and tracking. The pattern: written process documents serve as canonical reference and onboarding material; software templates instantiate workflows for each new execution. Process Street specializes in this - templates with checklists that get triggered for each instance. For US small businesses, start with written documentation in Notion or Google Docs; add software workflow management when volume and team size justify it (typically 3 plus team members executing the workflow regularly).
How often should I review and update workflows?
Quarterly for active workflows; annually for stable ones. Reviews should ask: what is breaking? Where are people improvising? What changed in the business that the workflow has not reflected? Are any steps unnecessary? Could automation help any step now that did not exist 6 months ago? Workflow review meetings work well as 60-minute sessions with all involved team members; capture changes in real-time and update documentation immediately. Failure to review workflows produces drift; the documented workflow no longer matches actual practice, and new team members get confused.
Who should own each workflow?
Each workflow should have a single named owner responsible for its outcomes, documentation, and ongoing improvement. Workflow owner is typically a department lead (sales workflows owned by sales leader, operations workflows owned by operations leader). Owner does not necessarily execute every step but is accountable for the workflow working end-to-end. US small businesses commonly fail to assign workflow ownership; result is no one updates documentation, no one investigates breakdowns, no one champions improvements. Workflow ownership is one of the highest-leverage management investments - clear accountability multiplies execution quality.
What workflow tools should I use?
Three layers. Documentation: Notion, Confluence, Google Docs - written process documents and SOPs. Visual: Lucidchart, Whimsical, Miro - flowcharts and process diagrams for complex workflows. Operational: Asana, ClickUp, Monday, Process Street, Trello - templates and tracking for actual workflow execution. For US small businesses under 20 employees, Notion plus Asana covers 80 percent of workflow management needs at 20 to 50 dollars per user per month combined. Process Street specializes in repeatable workflows with checklists; valuable for businesses with high-volume standardized processes (onboarding 50 plus new customers per month, frequent recurring operations). Avoid tool sprawl; consolidate workflow tools across the business.
In your business
- →Document the 5 most-repeated workflows first
- →Look for handoffs - they're where work falls through cracks
- →Automate the repeatable parts once the workflow is clean - automating a broken workflow just amplifies the breakage