Skip to main content
Activating a use case signals that a feature or product is live with your customer and it’s time to start tracking impact. This should map directly to your organization’s rollout plan.
When to activate: When a feature gets rolled out to teams and you’re ready to start measuring the improvement metrics.

​
Finding inactive use cases

When you open a Value Tracker, you’ll see all use cases from the original business case. The ones not yet activated appear at the bottom of the Use Cases tab with an “Activate” button.
  1. Navigate to the Use Cases tab
  2. Scroll to the Inactive Use Cases section at the bottom
  3. Review the use case name and description to confirm it matches your rollout plan
  4. Click Activate to begin the configuration process

​
Configuration methods

Depending on how the use case was originally set up, you’ll follow one of two paths:

​
Automatic configuration

When a use case has been pre-configured in your company’s value framework, activation is instant. The system already knows which metrics to track and how to calculate benefit.
1

Click Activate

Click the Activate button next to the inactive use case.
2

Confirm details

Review the calculation setup—it’s already configured and ready to go.
3

Start measuring

The use case moves to the Active section and improvement metrics appear in your Measurements tab.
That’s it! You can now start recording measurements for this use case.

​
Manual configuration

Custom use cases often need manual configuration. You’ll tell the system which input to measure over time and how it drives the benefit calculation.
1

Click Activate

Click Activate next to the inactive use case.
2

Choose your calculation type

Select how this use case calculates value—either percentage improvement or absolute values.
3

Map your improvement metric

Tell the system which input you’ll measure each month (details below).
4

Confirm and save

Review the setup and click Save to activate the calculation.

​
Calculation types explained

Manual configuration requires you to choose how your use case calculates value. Pick the approach that matches your use case structure.

​
Percentage improvement

Use this for calculations based on an expected improvement percentage—like “Increase Rep Efficiency” or “Reduce Processing Time.” How it works:
  • You have a baseline metric (e.g., “Avg. Tickets per Day - Before”)
  • You’ll measure the current metric over time (e.g., “Avg. Tickets per Day - After”)
  • The system calculates the percentage improvement automatically
  • This percentage drives the benefit calculation
Example setup:
Percentage improvement configuration showing baseline and measurement selection
Choose this method when: - Your use case includes a projected percentage gain (like “50% efficiency increase”) - You have clear before/after metrics in your calculation - The benefit scales based on the percentage change from baseline Common examples: Increase productivity, reduce error rates, improve conversion rates

​
Absolute values

Use this for calculations that compare two distinct values without a percentage—like “Current Time on Task” vs. “Future Time on Task.” How it works:
  • You have two separate inputs representing before and after
  • You’ll measure one of these inputs over time
  • The system calculates benefit based on the absolute difference
  • No percentage is derived or displayed
Example setup:
Absolute value configuration showing current and future value selection
Choose this method when: - Your calculation compares two standalone numbers (not a percentage) - The inputs are labeled “Current” vs. “Future” or “Before” vs. “After” - Benefit is calculated from the direct difference between values Common examples: Reduce hours per task, decrease cost per unit, lower average handle time

​
Mapping improvement metrics

When manually configuring a use case, you’ll need to identify which input to measure over time. This becomes your improvement metric—the value you’ll record monthly in the Measurements tab.

​
For percentage improvements

  1. The system shows you all inputs from the original calculation
  2. Look for the input that represents current or actual performance (usually labeled “After” or “Current”)
  3. Select this input as your improvement metric
  4. The baseline (usually labeled “Before” or “Baseline”) stays fixed from the business case
Quick check: The improvement metric should be the value that changes as your customer adopts and uses your product.

​
For absolute values

  1. The system shows you both the “Current” and “Future” inputs
  2. Select the input you’ll measure each month (usually “Current”)
  3. The other value stays fixed as the target or comparison point

​
Multiple calculations per use case

Some use cases have multiple benefit calculations. For example, a use case might calculate both cost savings AND revenue increase.
When this happens: You’ll go through the configuration process once for each calculation, mapping the appropriate improvement metric for each one.
Each calculation gets its own improvement metric that appears in the Measurements tab.

​
After activation

Once you activate a use case, several things happen automatically:

Use Cases tab

The use case moves to the Active section at the top and displays an expandable card with the measurement table.

Measurements tab

Improvement metrics for this use case appear in the monthly view, ready for data entry.

Overview tab

The use case appears in the active breakdown and contributes to the total benefit calculation.

Milestones

Any milestones linked to this use case become visible and trackable.

​
Editing or deactivating

Need to change something after activation?
Click the 3-dot menu on the active use case card and select Edit Configuration to adjust which metric you’re tracking or how the calculation works.
Click the 3-dot menu and select Deactivate to stop tracking this use case. Historical measurements are preserved, but no new data can be entered.
Deactivating removes this use case from your total benefit calculation going forward.
Go to the Inactive Use Cases section and click Activate again. Your previous measurements and configuration are restored.

​
Best practices

Align with rollout

Only activate use cases when the corresponding feature is truly live with end users. Premature activation leads to confusing zero or low values.

Communicate timelines

Let your customer champion know when you’re activating a use case and what data you’ll need to track together.

Set expectations

Some use cases take time to show impact. A ramp-up period with low initial measurements is normal and expected.

Document decisions

Use the notes feature to record why you chose a specific improvement metric or any configuration decisions for future reference.

​
Common scenarios

  • Phased rollout
  • Multiple calculations
  • Baseline uncertainty
  • Delayed impact
Scenario: You’re rolling out to different teams or departments over several months. Approach: - Activate the use case when the first team goes live - Use notes to document which teams are included each month - Consider adjusting unit inputs (like ”# of employees”) as more teams onboard
Use case activated! Next, learn how to record your first measurements.