With two refresh options, Dryrun appears to overthink user experience, however, a manual refresh option at both the forecast and scenario level is evidence of the power and control that Dryrun users have in modeling out their future ‘what ifs’
While many of the API processes run automatically in the background, Dyrun’s Refresh options are deliberately ‘manual’ - the user needs to click a link or a button to initiate the intelligent import process that syncs data one way to our platform.
Global or ‘forecast’ refresh: Located in the top right corner of every forecast
Scenario refresh: Located within the Scenario settings of each scenario within the forecast.
- “What is most efficient?”
- “What is most impactful to show my team?”
- "How do I encourage/avoid redundancy and use it to my advantage while modelling?"
When users start in the Dryrun platform they often use Global refresh to the exclusion of other options.
Advanced Users/Success Criteria
There’s a trend in user time-in-platform and use of Scenario refresh that has to do with how nuanced a particular forecast needs to be.
Use Case 1
After Global refresh, user sees a financial anomaly/circumstance/event that would be advantageous to preserve and discuss with the team - however, the team isn’t scheduled to meet until the end of the week. User:
- Makes a duplicate of the anomalous scenario and renames it “Anomaly: To be discussed”
- Manually refreshes each scenario but “Anomaly: To be discussed”, thus preserving it
*Having scenario-only refresh allows the user to preserve that without overwriting with current data from your accounting platform..
**Having an automatic sync would void this opportunity.
Use Case 2
A common use case is a more static forecast with one or two dynamic scenarios connected to the import feeds, needing ongoing imports from accounting platform data (common case with Cash Flow Actuals + Sales Revenue What ifs in scenarios #2 and 3 updating from Pipedrive. User should:
- Use scenario-only refresh option to refresh a single imported scenario