Explain the result
The scheduling example shows which rules a plan must follow and what the model tries to improve. You can see what “best” means before relying on the answer.
See how the schedule is chosenAbout Decision Systems
Close to the problem.
Accountable for the work.
Decision Systems has partnered with businesses and organizations across six countries.
We help teams work through decisions they face regularly, from scheduling people to dividing a limited budget. The tool needs to fit the way the team actually works.
We start by understanding the decision, writing down the rules and agreeing what a useful result looks like. Then we build and test it with you.
How we workThe disciplines behind the work.
- Optimization and operations research
- Statistics and econometrics
- Forecasting and uncertainty analysis
- Algorithms and experiment design
The method follows the question. Sometimes a simpler existing tool is the right recommendation.
What you can expect
from the work.
The examples show how we explain a result, check its limits and help someone use it.
Make the tradeoffs clear
In the allocation example, you choose how much time to reserve locally. The tool shows how that choice changes the number of visits each location can support.
Try a different allocationLeave room for uncertainty
A change can look promising without enough evidence to rely on it. The evaluation example separates what happened, what caused it and whether the difference is useful.
Read the evaluation planStart with one decision,
then build from there.
Start with a decision your team makes often, and involve someone who can help test the result in practice. We agree what to build, who will use it and how you’ll know it works.
If you later need support, new rules or more locations, we can agree that work separately. Changes to the way a tool is used may need fresh testing.
How we workTell us what your team needs to decide.
Describe how you handle it now and what gets in the way.