Workflow Automation & Process Improvement
Replace manual, paper, spreadsheet, or repetitive work with practical, easy-to-use systems that match how the business operates.
As a business grows, recurring procedures, information, and software accumulate. Without a deliberate system for how they work together, the staff become the connection. In order to keep work moving they are left re-entering data, managing workarounds, and relying on individual knowledge.
I start by looking at how work moves through the business. Then I identify what the business needs that workflow to do. From there, I determine what needs to change in the process and systems that support it.
What the Work Often Involves
Systematize Internal Processes
- Remove unnecessary steps or reorder the sequence of work.
- Codify internal rules and decision logic into the system instead of leaving them dependent on someone’s memory.
- Standardize how recurring work is performed and documented.
Structure Company Information
- Replace paper forms, emails, or unstructured intake with information the next step can use.
- Establish one primary record rather than storing competing versions in multiple places.
- Turn business rules, calculations, and connections between information into something the system can act on.
Connect Operational Systems
- Integrate business software to transfer information between systems without requiring someone to re-enter it.
- Identify which system should be responsible for how information should pass between them.
- Determine when a software limitation workaround has become more burdensome than changing the system.
Automate Predictable Work
- Automating predictable actions, routing, notifications, calculations, reporting, or follow-up.
- Combining existing tools into a workflow that carries work from one stage to the next without requiring someone to manually trigger every step.
- Using rules to move records or transactions to the next stage of a process.
From Manual Order Handling to Connected Workflow
Workflow does not mean automation. It’s the real-world sequence of work and information that naturally flows through a business.
In one order-processing project, the workflow all ran through the owner and looked like this:
Before
Customer calls in an order → owner processes the order → owner enters the shipping address into the carrier website → owner pays for shipping and prints the label → owner emails the shipping information to the customer.
After
Customer places an order through the website → payment is processed → shipping cost is calculated → shipping information is passed to EasyPost → label is generated → tracking information is associated with the order → customer receives the shipping information.
The objective was not simply to generate a shipping label. It was to give the order a clearly defined path from purchase to delivery. With that path defined, the system could carry information between steps instead of leaving the owner to manage every handoff.
[Read LOG_12 →]
One Record, Two Outputs
At an equipment dealership, sales staff could print inventory pages from the website, but the pages printed as web pages rather than professional sales materials.
To create flyers, another staff member maintained the same equipment specifications in Word. The business was maintaining the same information in two places.
The client asked whether the website could generate a PDF flyer directly. I researched and implemented a way for the inventory already maintained on the website to produce the print-ready flyer.
One update could then serve both the online listing and the printed sales material.
[Read LOG_02 — Scaling Equipment Dealer Website for Campus Expansion →]
Don’t Start With the Software
I don’t begin with a particular platform and try to make the business fit it. Once I understand what the process and systems need to do, then I select the tools that best support that work.
If the workflow itself is unproven, a working prototype can test the assumptions before committing to a larger build. [Eventually this could be an internal link to another field note or service page perhaps]
When standard tools do not fully meet the requirement, I research the alternatives. This can include:
- Comparing available options.
- Reviewing documentation and limitations.
- Evaluating the quality of vendor support.
- Testing whether systems can exchange information as required.
- Communicating with vendors about specific capabilities and the intended use.
When more than one option makes sense, I explain the differences so the client can participate in choosing the system they will ultimately use.
The appropriate solution is often a standard tool. In certain occasions, an integration, careful configuration, or limited custom logic is needed.
For one QuickBooks integration, I evaluated several options for security, support responsiveness, and fit with the business’s existing accounting practices. Before allowing the new workflow to affect live accounting records, I used a developer sandbox with dummy accounts to map transaction types and validate that it would not create duplicate, overwritten, or corrupted records.
[Read LOG_06 — Automating QuickBooks to Eliminate Manual Order Entry →]
When Automation Isn’t the Solution
Not every manual or repetitive step should be automated. Some work is better left with people when it involves:
- Unusual or infrequent situations and exceptions.
- Experience and firsthand judgment.
- Quality review of the output.
- Added complexity or software dependencies that outweigh the benefit.
The deciding factor is which routine work should be carried forward by the system, and which parts should remain with the people who operate it.