Efficient process design is the practice of defining a goal, mapping the sequence of work, assigning the right resources, testing the flow, and keeping the documentation current.
Andrew Schrage is CEO and co-founder of Money Crashers, a personal finance publication. In this interview, originally conducted in 2014, he explains how his team designs and documents repeatable business processes.
Andrew Schrage on designing efficient processes
The conversation below preserves Andrew’s original advice. Where the tools have changed, current product links clarify what readers can find today.
1. What company do you work for? What do they do?
Andrew Schrage: Money Crashers. It’s a personal finance website.
2. What team do you work in?
Andrew: As the co-owner and CEO, I’m involved with many different teams.
3. What is your role?
Andrew: Most roles are of a supervisory nature.
4. What are your five most common processes?
Andrew: Some of the more common business processes include contract management, talent acquisition, delivery of product or service, staff development, and financial reporting.
5. What is your involvement in the design and documentation of these processes?
Andrew: My senior team does most of the initial design and documentation of our processes, and I advise and adjust as necessary.
6. What software do you use to create this documentation?
Andrew: Two software titles to consider for process documentation include ProcessMaker and PerceptiveSoftware.
Current context: These names reflect the software landscape when the interview was conducted. ProcessMaker now describes its product as a cloud platform for low-code process management and workflow automation. Perceptive Software’s content and process management product is now offered by Hyland as Perceptive Content.
7. What are some important best practices for writing effective process documentation?
Andrew: Think logically and objectively when creating the steps for your process. Identify all needed resources for effective process completion. Test your process before it’s officially implemented.
8. What are the most common mistakes you find in process documentation?
Andrew: One mistake in process documentation is not having a goal in mind for the process before you start documenting. Not mapping out the event sequence beforehand is another one. Another mistake is not having a contingency plan in place if a particular aspect of the process breaks down. This should also be thought out beforehand.
9. What innovations would you like to see in the process documentation space?
Andrew: Process documentation in and of itself needs to be more interactive to keep costs down. Process documentation should be written in clearer language that can be easily understood by both experts and those with little experience with the process. Companies should pay more attention to the documentation of their processes as time goes on. Often the documentation will need to change in order to remain relevant.
What Andrew’s process design advice gets right
Andrew’s answers outline a practical method for designing efficient processes without overcomplicating the work:
- Start with the outcome. Define what the process must accomplish before writing steps.
- Map the sequence. Put actions and handoffs in a logical order before implementation.
- Involve the people closest to the work. Let experienced team members create the first version, then have leaders review and adjust it.
- Identify resources and owners. Make clear who does the work and what information or tools they need.
- Test before launch. Run the process with realistic inputs and fix friction before making it standard.
- Plan for breakdowns. Add contingency paths for exceptions instead of assuming every run will be ideal.
- Keep documentation usable. Write plainly, make guidance interactive where useful, and revise it as the work changes.
A strong process documentation template gives teams a repeatable structure for capturing these elements while leaving room for the details of each workflow.
Putting efficient processes into practice
Good documentation becomes operational when people can follow it, supply evidence, handle approvals, and adapt to exceptions in the same place. Process Street is a single Compliance Operations Platform with Docs and Ops capability areas plus built-in AI, helping teams connect governed procedures with the recurring work those procedures control.
Frequently asked questions
What is efficient process design?
Efficient process design defines the outcome, maps the sequence of work, assigns resources, tests the flow, prepares for exceptions, and keeps documentation current.
Who should design a business process?
The people closest to the work should shape the initial process. Leaders can then review the goal, controls, resources, and exception paths without losing the team’s practical knowledge.
How should a team test a new process?
Run it with realistic inputs before launch, observe the handoffs and failure points, and revise unclear steps or missing contingencies. A small pilot usually reveals more than a theoretical review.
How often should process documentation be updated?
Review documentation whenever tools, owners, regulations, or operating conditions change. Critical processes also benefit from scheduled recurring reviews, even when no obvious change has occurred.
The post Designing Efficient Processes with Andrew Schrage of Money Crashers first appeared on Process Street | Compliance Operations Platform.
0 Commentaires