We are pleased to announce the launch of the Usage Report. Moving beyond the "create and forget" cycle common to video SOP tools, we've created a single screen where you can see at a glance "Is it being used in the field?" and "What impact is it having?" This article highlights the key points of this update.

About the New Usage Report

Until now, Dive had pages to check individual user activity, but there was no place to view how SOPs are being used and what impact they're having at the team or group level. In response to feedback like "We deployed it, but I'm not sure how much it's helping," we've created a new cross-team report screen.

● Three perspectives covered by the Usage Report

• ① Investment: How easily SOPs are being created (creation time)
• ② Value: Whether created SOPs are repeatedly viewed in the field (cumulative views)
• ③ Economic Impact: Time and monetary value conversion of ① and ② (and ROI)

This transforms Dive from "an SOP creation tool" to "a platform where customers can verify field adoption and its impact themselves".

Feature ① : Usage Status Analysis Across Three Axes

Previously, to understand "who on our team is using this and how much" or "which SOPs are being viewed and which are sitting unused," you had to check individual pages one by one. This release enables analysis across three axes—Group / User axis, Procedure axis—with one-click switching, allowing you to view the same data from different angles.

● Key metrics Dive prioritizes: "Repeat use" and "Repeat rate"

• Repeat use (Group / User axis): On average, how many times is a single SOP viewed?
• Repeat rate (Procedure axis): On average, how many times do people who viewed that SOP review it?

The higher both values, the more "the SOP is repeatedly referenced in the field = people are solving problems on their own without asking their supervisors". Since this is at the heart of Dive's value, we display it most prominently on screen in bold and color-coded (≥3 green / ≥2 blue / ≥1.3 gray / <1.3 orange).

● Other key displays

• Inactive users / heavy users: Instantly identify "who should I reach out to expand adoption?" and "whose usage patterns should I share across the team?"
• Unused SOP filter: Select "never viewed" on the Procedure axis to list SOPs created but never watched
• Daily trend graph: Track views and repeat use trends over time
• Drill-down: Click a row to dive deeper from Group → sub-groups → individual users

From user names and member lists on the report, drill down with one click to individual usage history pages. Individual usage status pages have also been redesigned as Usage Reports. You can view the detailed data for that individual, which forms the basis of the calculations above. Individuals can also view their own page.

Feature ②: Economic Impact / ROI Tab — Quantify Time and Cost Savings

Previously, to explain "how much labor Dive saves," customers had to manually collect data and do the math themselves. The Economic Impact / ROI tab multiplies activity data by assumptions (hourly rate, substitute time) to automatically calculate Savings, Saved time, ROI multiple, and Payback period. Only those with Owner / Team Administrator permissions see this tab.

● Impact breakdown (Cards A / B / C)

• A. Training (Initial Training Substitution): Time saved when new hires teach themselves from SOPs instead of being walked through by supervisors
• B. OJT (Question substitution): Time saved when people resolve "I forgot, please teach me again" by using Dive. Highlighted in blue as Dive's core value
• C. Creation (Creation efficiency): Time savings from creating SOPs in Dive versus traditional Excel/paper methods. SOPs with measured data show "Measured"; others show "Assumption"

● How ROI is presented

• Savings vs. Monthly fee comparison, ROI multiple, and Payback period all on one screen
• "How much we're spending and how much we're getting back" displayed in a format ready to submit to management

This makes the Usage Report not just a confirmation of field adoption but also "a dashboard for regular reporting to leadership".

Since assumptions vary significantly by organization, we've enabled customers to set their own Assumption values. "Our senior staff's hourly rate is higher" or "We spend 1 hour per person on training"—you can adjust to match your reality.

● Editable assumptions (defaults in parentheses)

• Hourly rate (3,000 yen/h)
• Training time per first view (30 min/item)
• Supervisor question time per re-view (15 min/item)
• Traditional creation time (90 min/item)
• Dive creation time fallback (15 min/item)
• Additional time for revisions (30 min/item)

● Operational recommendations

• Default values are set conservatively. Right after deployment, keep them as-is; after 1–2 months of operation, adjust to match your field reality.
• For business cases, "we're seeing this much benefit even with conservative assumptions" is the most persuasive approach. Inflated assumptions often get rejected in internal review, so keep all values conservatively positioned.
• Changed assumptions are saved across the entire team. Multiple administrators stay aligned on values, preventing numbers from shifting with each report.

⑤ Other improvements

• Export to Excel: Download all Usage Report data (overview tab + Economic Impact tab + assumptions) to Excel. Sheet names and column names exactly match the screen, so you can use them directly in business cases and management reports.
• Flexible filtering: Supports period (All time / Today / 1 week / 1 month / 3 months / 6 months / 1 year + custom dates), Group hierarchy, and multiple permission combinations. See the target user count for your filtered results in real time.
• Automatic Group Administrator permission limits: Group Administrators automatically see only their Direct group and its sub-groups in the aggregated data. Sensitive information is designed to be invisible without proper permissions.
• One-click navigation to individual reports:
• Unified group naming: "Ancestor path / name" notation is consistent across all screens. Even in deep organizations, mistaking same-named groups becomes less likely.

For Existing Users

This feature is an additional release. There is no impact on existing SOPs, user settings, or Group settings. Default assumptions are automatically applied, so you can start using it right away with no sign-up or initial setup required.

Note that Edit session (creation time) data is only counted from April 27, 2026 onward. Historical creation times before this date were not recorded, so when looking back, creation time will be based on assumptions (other Usage Report and Economic Impact values do include historical data).

Stop treating video SOP tools as "create and done." Now "be used and be effective"—something you confirm monthly yourself. We hope this update becomes your Partner through the operational phase of field DX.

Thank you for continuing to use Dive◎