How it works
It starts by understanding how the work actually happens.
Every workflow follows the same seven steps, from the first conversation to the support that keeps it working. You work with Michael from step 01, and nothing goes live until you have reviewed and approved it.
The process
Seven steps, one person accountable.
Step 01: Discover
We learn how the work actually happens.
- What happens
- A conversation about one process: who does it, which systems it touches, where the time goes and what tends to go wrong.
- Your part
- Describe the work as it really happens, including the workarounds.
Step 02: Map
We identify repetitive steps, systems, decisions, handoffs and risks.
- What happens
- Each step is written down, including the exceptions people handle from memory, the handoffs between people and the decisions along the way.
- Your part
- Check that the map matches reality, and point out what’s missing.
Step 03: Design
We design the workflow and decide where human control belongs.
- What happens
- The proposed workflow is laid out: what moves automatically, what gets checked, and exactly where a person reviews or approves.
- Your part
- See the proposed workflow before anything is built, and decide where control belongs.
Step 04: Build
We connect the systems and create the automation.
- What happens
- The systems are connected and the workflow is built, using only the access it needs.
- Your part
- Provide or approve access to the systems involved.
Step 05: Test
We test normal conditions, exceptions and failure scenarios.
- What happens
- The workflow is run against normal cases, exceptions and failure scenarios, including what should happen when something is missing or wrong.
- Your part
- Try it with real examples of your work and confirm the results.
Step 06: Deploy
The approved workflow moves into production.
- What happens
- The workflow is reviewed with you and moves into production only after your approval.
- Your part
- Give the final approval to go live.
Your approvalNothing goes live without it.
Step 07: Support
We help maintain and adapt the workflow as systems and requirements change.
- What happens
- Systems and requirements change. The workflow is monitored and adjusted with them.
- Your part
- Tell us when something in your process changes.
Human control
Control is designed in, not added later.
Where a person reviews, approves or decides is part of the design from step 03. The more an action matters, the more control the workflow keeps with your team.
The Chronosero principle
Automation should not remove good judgment. It should remove the repetitive work surrounding good judgment.
- Human approval is built in where the consequences require it.
- Workflows are designed to use only the access they need.
- Workflows are tested against normal conditions, exceptions and failure scenarios before deployment.
Getting started
What the first conversation needs.
You don’t need a project plan or a list of requirements. A single process is enough to start.
- One process that takes too much of your team’s time
- Who does it today, and roughly how often
- The systems or documents it involves
- What happens when it goes wrong or gets missed
Questions
Common questions
Do we need to replace our software?
Usually not. Chronosero designs the connections between the tools you already have. Which systems can be connected depends on the software, its access options and your requirements, which is part of what discovery works out.
Will automation make decisions for us?
No. Workflows handle the gathering, filing, checking and reminding. Higher-consequence actions can require approval before they continue. Where a person approves is decided with you during design.
Who will we work with?
Michael Pruitt, from the first conversation through support. The person who learns your process is the person who designs the workflow.
What does it cost?
Every workflow is different. We first understand your process, systems, requirements and goals before designing the solution.
What happens after the workflow goes live?
Support continues. When your systems or requirements change, the workflow is adjusted with them.
Start a discovery
What is your business still doing manually?
Tell us about one process that takes too much of your team’s time. Michael personally reviews every discovery request.