This feature lets you see your entire team's Dive usage, creation status, and economic impact on a single screen. By narrowing down by period and group, you can understand "how much it's being used," "how much know-how has been turned into SOPs," and "how much time spent on training and answering questions has been replaced" through numbers and graphs. Use this for internal sharing after launch, budget proposal updates, and reporting to upper management.

The top of the screen displays hero KPIs for the entire period (Views / Creation time / Economic impact), and the bottom shows 4 tabs ([Views / Usage] / [Stumble] / [Draft status] / [Economic Impact / ROI]). The [Economic Impact / ROI] tab and Economic impact hero KPI are displayed only to Owners / Team Administrators.

What is the Usage Report?

A report screen that aggregates your team's actual Dive usage during a period. It displays information across four perspectives.

Views / Usage: Who viewed which SOP and how many times
Stumble: Based on question answer results, visualizes whether people could complete the SOP independently
Draft status: Status of SOPs in progress, rejected, or stuck
Economic Impact / ROI: Time and cost savings calculated from viewing and publishing results (Owner / Team Administrator only)

All figures are aggregated for the selected period, group, and user range.

How to open the page

Open it from the sidebar's "Usage Report". The range you can view varies by user permission (Owner / Team Administrator can see the whole organization, Group Administrator can see their own group, Members can only see themselves).

Specify period and filters

Select from the period presets at the top of the screen ([All time] / [Last 1 week] / [Last 1 month] / [Last 3 months] / [Last 6 months] / [Last 1 year]), or specify start and end dates in the calendar under [Period]
If needed, filter by [Group] (multiple selections and hierarchical selection available)
All KPIs and tables are recalculated for the selected period and group

Metrics visible in the [Views / Usage] tab

This tab shows how much SOPs were used on the floor during the period. You can drill down with tables organized by group and user.

Main metrics

Views: Total times procedures were opened during the period (each view counts as 1, even if the same person viewed the same SOP multiple times)
Active users (user count): The actual number of users who viewed an SOP at least once during the period. Includes past usage by deactivated (ex-employee) users. The accompanying penetration rate (in parentheses) shows the percentage of current employees who accessed it (used as a metric not exceeding 100%)
Procedures referenced: The number of unique SOPs viewed during the period
Views per procedure: How many times an individual SOP was viewed on average (= Views ÷ Unique procedures). A larger value means "the procedure is used repeatedly on the floor = people can solve problems themselves without asking seniors" (1.0 = viewed once, 3.0 = referenced 3 times on average)
Views per person: Average number of views per user who viewed this SOP (= Views ÷ User count). A value of 2.0 means people who viewed it referenced it an average of 2 times (formerly called "repeat rate")
Creation time (h): Total actual work time spent on editing and creating the SOP
Publishes: Total number of SOPs newly published or revised during the period

Group / User axis

SOP axis

Check unviewed SOPs

Use the [All / Viewed / Never viewed] filter at the top of the SOP list to narrow down SOPs that have never been viewed. You can discover SOPs created but unused, and use that as an opportunity for promotion or improvement.

Metrics visible in the [Stumble] tab

This tab visualizes "who, which SOP, and whether they could complete it independently" based on question answer results from Checkpoints embedded in procedures. You can assess not just the "quantity" of views, but the "quality" of understanding.

In Dive, we define completion as having viewed the procedure through to the end and submitted a completion report. "Solo completion" is defined as having answered all Checkpoints (questions) set at each step without any mistakes.

※ This tab is for SOPs where Checkpoints are set in the procedure. For information on how to set questions, see Step-level questions.

User × SOP status

The table displays the status of each user-SOP combination as follows.

Self-completion rate shows the percentage of procedures with questions that were completed without any mistakes out of all completed procedures.

By narrowing the period, you can see changes like "this period they succeeded without errors = proficiency improved".

Stumble map

Click the SOP name to view the viewing history. Click the "Stumble map" button in the top right to open the stumble map. You can see at a glance which Checkpoints people stumbled on, how many, and which answer choices they selected. This helps identify which procedures need improvement or which people need individual follow-up.

Metrics visible in the [Draft status] tab

This tab visualizes SOPs stuck in progress. Published/completed SOPs are not included.

In draft: SOPs that the creator is still editing
Rejected SOP: SOPs rejected in the approval workflow
Stalled: SOPs that haven't been updated for a long time

You can identify how many items are stuck with which users by user, and pinpoint operational bottlenecks.

Metrics visible in the [Economic Impact / ROI] tab (Owner / Team Administrator only)

Based on viewing and publishing results, we calculate and display the "time that would have been spent if Dive didn't exist" in monetary terms. The calculation logic consists of three breakdown categories.

Impact breakdown

A. Initial training substitution = First views in the period × Previous training time per case (default 30 minutes)
This replaces the time new employees spent being trained orally by veterans.
B. Question substitution = Subsequent views in the period × Previous question response time per case (default 15 minutes)
This is the replacement effect for situations where "just asking a senior" was solved with the SOP instead.
C. Creation efficiency = Publishes in the period × (Previous creation time − Dive creation time)
The default calculates a saving of 90 minutes − 15 minutes = 75 minutes per SOP. When actual edit time is available, that value is used.

The top of the screen displays total impact hours / total impact amount (¥) / ROI multiplier for current plan monthly fee / payback period (days). The payback period is calculated as Monthly fee ÷ Monthly savings × 30 days, giving you an estimate of how many days it will take to recover the Dive implementation cost.

Adjust baseline values to your company's figures

The unit prices and minutes that are the basis for calculation can be changed from the settings items in [Impact breakdown] to match your company's actual situation.

Click the following items in [Impact breakdown] to begin editing
- Average hourly labor cost (¥/hour)
- Previous training time per first view case (minutes)
- Previous question response time per subsequent view case (minutes)
- Previous SOP creation time (minutes/SOP)
- Standard Dive creation time (minutes/SOP, default when actual measured value is unavailable)
Save

After changes, the KPI and breakdown are recalculated with the new baseline values.

Drill down into individual users (Personal page [Usage] tab)

Click a user row in the table to open that user's Personal page at the [Usage] tab, where you can see that user's usage in detail. It's part of a 3-tab structure (Training (Courses) / Skill development / Usage (viewing and usage patterns)), with one-click switching to other tabs. For details, see Personal page (view one user across three tabs: Training / Skill development / Usage).

The [Usage] tab shows:

Daily view trend
Viewing pattern by time of day (before morning briefing / during work / evening review usage)
Viewing pattern by day of week
Repeatedly viewed procedures ranking
Viewing history (time series)

This is useful when you want to verify actual conditions on the floor like "which SOPs a specific person views often" or "what times things are used".

"Viewing record modal" that opens when clicking an SOP name

Click an SOP name in the SOP-by-SOP table to open the viewing record modal, from which you can branch to three options: [Open SOP] / [SOP-level details] / [Stumble map]. For SOPs with pass/fail questions, the viewing record modal functions as a hub for Checklists. For details, see Pass/fail questions and viewing records.

Export to Excel

From the [Export to Excel] button in the top right of the screen, you can download the entire Usage Report aggregation as one Excel file (includes sheets for overview / group-user axis / SOP axis / daily trend / draft status / economic impact-ROI). Use this for pasting into internal materials or reports, and for entering into monthly reports.

The export range follows the currently selected period, group, and permission filters (draft status is all-time, not subject to period filter). The Economic Impact-ROI sheet is exported only for Owners / Team Administrators.

Tips for use in proposals and internal reporting

The Usage Report metrics show different aspects of impact. By using them strategically based on your situation, you can demonstrate Dive's benefits from perspectives beyond just labor reduction.

When you want to show "self-resolution rate"

Shows whether people can solve problems by reading SOPs themselves, without asking seniors.

Views per procedure: 1.0 means "viewed just once", 2.0 or higher means "repeatedly referenced", 3.0 or higher means "relied on at the site"
Active users / Employee count: What percentage of the floor is it penetrating?
B. Question substitution (Economic Impact tab): Monetary value replacing subsequent views × question response time

When you want to show "know-how visualization"

Shows the volume of previously siloed know-how that has been turned into SOP form.

Publishes: The number of newly created or revised SOPs during the period
Procedures referenced: The number of SOPs actually used on the floor (can be compared against dormant assets)
Unviewed SOP count: SOPs created but not yet reaching the floor (presented as room for improvement)
C. Creation efficiency (Economic Impact tab): Savings from difference against previous creation time

When you want to show "training efficiency"

Shows the time-savings effect of new employee training and OJT.

A. Initial training substitution (Economic Impact tab): Monetary value replacing first views × training time
Individual user first-view count: Can be read as the number of procedures each new employee learned independently without being trained by a veteran
Viewing pattern by time of day: You can see actual usage in training scenarios like before morning briefing, during work, and evening review

When you want to show "understanding visualization"

When you want to show not just the "quantity" of views but the "quality" of understanding, start with the [Stumble] tab. For SOPs with questions, it visualizes whether people can pass without mistakes.

Self-completion rate / Completion rate: Shows whether people who viewed the SOP can complete it on their own
Stumble map: Shows which procedure and which Checkpoint people tend to stumble on, allowing you to specifically demonstrate educational bottlenecks

To track proficiency continuously and systematically, combine with the following features:

Question feature: Place questions at each step to prevent moving to the next step until the correct answer is given, confirming understanding (See: Step-level questions)
Skill Map: Continuously evaluate and track proficiency stages by combining training plans with evaluation criteria (Lv1–Lv4) (See: What is a Skill Map? / How to read Skill Marks)

By combining "Self-completion rate" and "Skill Map Lv changes" with the Usage Report view count, you can organize both quantity (views) and quality (understanding) into one report.

Alternative metrics when it's difficult to quantify proficiency shortening in days

Proficiency shortening can be difficult to quantify depending on work content and personnel composition. In such cases, you can demonstrate implementation impact using the above metrics with cuts like these:

"Questions to seniors have decreased" shown as cumulative amount from "B. Question substitution"
"The work of creating SOPs itself has sped up" shown with "C. Creation efficiency" and actual edit time
"Which SOPs are used on the floor and which aren't is now visible" shown with "unviewed SOP count" and "Views per procedure"
"Training quality can be made consistent" shown with "Active users", "self-completion rate / completion rate", and "Skill Map Lv distribution"

These become easier to present as cumulative effects when tracked month-to-month or quarter-to-quarter.