A feature that lets you check your team's Dive usage, creation status, and economic impact all in one screen. By narrowing down the period and groups, you can grasp in numbers and graphs "how much it's being used," "how much know-how has been turned into procedures," and "how much time spent on training and answering questions can be replaced." Use this for internal sharing after implementation, updating investment proposals, and reporting to upper management.

The screen layout has filtering options (period, groups, and more) at the top and three tabs below: [Viewing records] / [Draft status] / [Economic Impact / ROI]. At the top of the [Viewing records] tab is a summary that totals the period's figures (views, users, procedures referenced, wrong-answer rate, self-completion rate, creation time, publish count, and economic impact). The [Economic Impact / ROI] tab and the summary's Economic impact are visible only to Owners / Team Administrators.

About the Usage Report

This is a report screen that aggregates your team's actual Dive usage within a period. It displays information split across three perspectives.

Viewing records: Who viewed which procedure and how many times. If the procedure has checkpoints, the response results also show the wrong-answer rate, stumbles, and self-completion rate
Draft status: The status of procedures that are in progress, rejected, or stalled
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, groups, and user range.

How to Open the Page

Open it from [Usage Report] in the sidebar. Who can see depends on user permissions (Owner / Team Administrator can see the whole team; Group Administrator can see only their own groups. Group Administrators not in any group see only their own). When a Created user or View-only user opens [Usage Report], their personal page's [Viewing records] tab opens.

Specifying Period and Filters

Choose 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 using the [Period] calendar
Filter by [Group] as needed (multiple and hierarchical selection allowed)
Entering text in the name column header of the table filters by procedure name (in the [By Group / User] table, by group name or user name). The total row at the top remains even when filtered
All KPIs and tables are recalculated for the selected period and groups

Metrics Visible in the [Viewing records] Tab

This tab shows how much the procedures were used on the floor during the period and how the checkpoints were answered. You check using the summary at the top and the details table (switch between [By Group / User] / [Procedures]). The names and meanings of the figures are the same as in the personal page and procedure-specific viewing records.

Main Metrics

Views: Total times procedures were opened during the period (each time the same person opens the same procedure counts as 1). Includes views of pre-revision versions
Users: The actual number of unique users who viewed a procedure at least once during the period (no duplicates). Includes past usage by users who have been deactivated (left the company). In the procedure table, it shows what percentage of active employees saw it (penetration) in parentheses
Procedures referenced: The number of unique procedures viewed during the period (duplicates not counted; a revised procedure counts as 1)
Views per procedure: On average, how many times a single procedure was viewed (= Views ÷ Procedures referenced). A larger value means "repeatedly used on the floor = people self-solve without asking a colleague" (1.0 = viewed once, 3.0 = referenced on average 3 times)
Views per person: On average, how many times users who viewed procedures viewed a single procedure (= Views ÷ Users). Displayed in the procedure table
Last view: The date and time the procedure was last viewed during the period. Displayed in the procedure table
Wrong-answer rate: Incorrect checkpoints reached ÷ Total scoring-eligible answers. The higher it is, the more people are getting stuck at checkpoints
Answer count: Total answers to scoring-eligible checkpoints (the denominator for wrong-answer rate). Displayed in the procedure table
Stumbles: Number of times people stumbled at a checkpoint (even if someone gets the same checkpoint wrong multiple times in one view, it counts as 1)
Self-completion rate: Of the completed views, the percentage that passed all checkpoints without a wrong answer
Creation time (h): Total actual work time spent editing and creating the procedure
Publish count: Total number of procedures newly published or revision-published during the period

Wrong-answer rate, answer count, stumbles, and self-completion rate are displayed only when the procedure has checkpoints and there are answer records during the period.

By Group / User

Displayed as a tree: Groups → child groups → users. A group row shows the total of everyone below it. Entering text in the name column header filters by group name or user name (if a group name matches, all people in that group are shown). Use the button at the right end of the header to toggle between expanding and collapsing all. Clicking a user name opens that person's personal page [Viewing records] tab (described later).

Procedures

Procedures are displayed in folder order (Folder → Procedure; numbers in names are sorted numerically, so they appear in item number order). A folder row shows the total of procedures within it. Clicking a number column header sorts within each level. When looking for procedures with a high wrong-answer rate, sort by the wrong-answer rate column. Clicking a procedure name opens that procedure's viewing records (described later).

Checking Unviewed Procedures

Use the [All / Viewed / Never viewed] filter at the top of the procedure list to filter and find procedures that have never been viewed. You can discover procedures that were created but never used, and use that to spark communication and improvement.

Viewing Checkpoint Responses (Wrong-answer rate, Stumbles, Self-completion rate)

From the responses to checkpoints (confirmatory questions) placed in procedures, you can check "who, on which procedure, completed it solo." You can verify not just the "quantity" of viewing but also the "quality" of understanding. These figures appear in the [Viewing records] tab summary and in columns of the [By Group / User] and [Procedures] tables.

Dive defines completion as when you view a procedure to the end and submit a completion report. The self-completion rate is the percentage of completed views where the person passed all checkpoints set on each procedure without getting a single answer wrong. By narrowing the period, you can interpret it as "this quarter they got it right without mistakes = understanding has improved."

When you want to check per person "can that person do this procedure solo," use the "Solo completion" column in the procedure's viewing records. It uses the same judgment as skill auto-evaluation, and the team chooses how many times to approve it (Once is enough / 2–5 times on different days) (Checking procedure-specific viewing records (who viewed, performance records, and stumble map)).

※ This applies only to procedures with checkpoints set in the steps. For instructions on how to set checkpoints, see Step-level questions.

Stumble Map

In the [Procedures] table, clicking a procedure name opens that procedure's viewing records. Switch to [Stumble map] and you can instantly see at which checkpoint, how many people, and which answers got stuck, leading to improvements in procedures with high stumble counts and discovery of people who need individual follow-up. For details, see Checking procedure-specific viewing records.

[Draft status] Tab Metrics

This tab makes visible procedures that are stuck mid-creation. Completed (published) procedures are not included.

In draft: Procedures the creator is still editing
Rejected: Procedures rejected in the approval workflow
Stalled: Procedures not updated for a long time since the last edit

Understand by user how many procedures are stuck in whose hands, and identify operational bottlenecks.

Clicking a procedure name in the list opens that procedure's viewing records (performance records).

[Economic Impact / ROI] Tab Metrics (Owner / Team Administrator only)

Based on viewing and publishing results, we display "the time that would have occurred without Dive" in monetary terms. The calculation logic comprises three components.

Impact Breakdown

A. Initial training substitution = First-view count in period × Old training time per view (default 30 min)
This is the replacement for time new employees would have spent learning orally from veterans.
B. Question substitution = Re-view count in period × Old question-answering time per view (default 15 min)
This is the replacement effect for "quickly asking a colleague" being self-solved with procedures.
C. Creation efficiency = Publish count in period × (Old creation time − Dive creation time)
By default, it calculates old 90 min − Dive 15 min = 75 min saved per procedure. When actual edit-time data is available, that value is used.

At the top of the screen, Total impact time (h) / Total impact amount (JPY) / ROI multiple for your current plan / Payback period (days) are displayed. The payback period is calculated as Monthly fee ÷ Monthly savings × 30 days, and gives you an idea of how many days it will take to recover Dive's adoption cost.

Adjusting Base Values to Your Company's Figures

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

Click the following items in [Impact breakdown] to begin editing
- Average hourly pay (JPY/hr)
- Old training time per first view (min)
- Old question-answering time per re-view (min)
- Old procedure creation time (min/procedure)
- Standard creation time in Dive (min/procedure, default when actual data is not available)
Save

After the change, KPIs and breakdown are recalculated with the new base values.

Individual User Drill-Down (Personal Page [Viewing records] Tab)

Clicking a user name in the [By Group / User] table opens that user's personal page [Viewing records] tab, where you can check that user's viewing status in detail. The period selected in the usage report is carried forward. You can switch with one click to the personal page's other tabs (Education, Development, Qualifications, Comparison). For details, see Personal page (see one person's education, development, qualifications, comparison, and viewing records at a glance).

In the [Viewing records] tab you can check the following.

Summary (the same figures as the usage report, but for that person)
Procedures: Procedures that person viewed, displayed in folder order. Pressing a procedure name opens that person's procedure-specific viewing records
Viewing history (chronological): Pressing a row opens the details of that performance record
Daily view trend / Viewing pattern by time of day / Viewing pattern by day of week

This is useful when you want to understand the actual situation on the floor, such as "which procedures a particular person often views" or "what times they're using it."

Procedure Name Click Opens "Viewing records"

Clicking a procedure name in the [Procedures] table opens that procedure's viewing records. It carries forward the period and filters selected in the usage report, and lets you switch between [By Group / User] (who viewed and who hasn't yet) / [Performance records] (answers to each view's checkpoints) / [Stumble map]. For procedures containing pass/fail checkpoints, performance records become inspection form and checklist records. For details, see Checking procedure-specific viewing records and Pass/fail checkpoints and performance records.

Exporting to Excel

From the [Export to Excel] button in the top right of the screen, you can download all usage report totals as one Excel file (containing sheets for Summary / By Group & User / By Procedure / Daily trend / Stumbles / Wrong-answer rate / Stumbles / By group / Draft status / By group / Draft status / Item list / Economic Impact / ROI). Use it for pasting into internal materials and reports, or transcribing into monthly reports.

The export scope follows the currently selected period, groups, and permissions filters (draft status applies to the full period regardless of period filter). The Economic Impact / ROI sheet is exported only for Owner / Team Administrator.

Tips for Using in Proposals and Internal Reports

Each figure in the usage report shows a different aspect of impact. By choosing the right metrics for the situation, you can show Dive's adoption benefits from viewpoints beyond just labor reduction.

When You Want to Show "Self-solve Degree"

Show whether "without asking a colleague, people are self-solving by viewing procedures."

Views per procedure: 1.0 = "viewed once," 2.0+ = "repeatedly referenced," 3.0+ = "relied on by the floor"
Users (penetration): What percentage of the floor has it adopted
B. Question substitution (Economic Impact tab): Re-view count × question-answering time replacement amount

When You Want to Show "Know-how Visualization"

Show the volume of tacit know-how that has taken the form of procedures.

Publish count: Number of procedures newly published or revision-published in the period
Procedures referenced: Number of procedures actually used on the floor (can be used to contrast against sleeping assets)
Count of unviewed procedures: Procedures created but not yet reaching the floor (presented as room for improvement)
C. Creation efficiency (Economic Impact tab): Savings effect from the difference between old and new creation times

When You Want to Show "Training Efficiency"

Show the time savings effect on new-hire training and on-the-job training.

A. Initial training substitution (Economic Impact tab): First-view count × training time replacement amount
Individual user first-view count: Can be read per new hire as the number of procedures self-taught without learning from a veteran
Viewing pattern by time of day: You see real usage in training scenarios such as before morning huddles, during work, and end-of-day review

When You Want to Show "Understanding Visualization"

When you want to show not just the "quantity" of viewing but the "quality" of understanding, first use the [Viewing records] tab's wrong-answer rate, stumbles, and self-completion rate (summary and table columns). For procedures with checkpoints, you visualize whether the floor can pass on the first try (zero wrong answers).

Self-completion rate: Shows whether people who viewed a procedure can pass through solo to the end
Stumble map (opened from a procedure name in viewing records): You can see at which steps and which checkpoints people tend to get stuck, clearly showing education bottlenecks

For continuous and systematic proficiency tracking, you can combine the following features in your operations.

Checkpoint feature: Place checkpoints at each step, and prevent advancing to the next step until the correct answer is given, to confirm understanding (see Step-level questions)
Skill Map: Combine an education plan with evaluation standards (Lv1–Lv4) to continuously evaluate and track proficiency progression (see What is Skill Map? / How to read Skill Mark)

By combining "self-completion rate" and "Lv changes on Skill Map" with the usage report's view count, you can organize both the quantity (views) and quality (understanding) in one report.

Alternative Metric When Proficiency Timeline Shortening Is Hard to Quantify

Proficiency timeline shortening can be difficult to quantify depending on the type of work and workforce composition. In that case, you can show adoption impact from these angles using the metrics above.

"Questions to colleagues decreased" shown by cumulative amount in "B. Question substitution"
"The work of creating procedures itself got faster" shown by "C. Creation efficiency" and edit actual time
"Used on floor / unused procedures are visible" shown by "Count of unviewed procedures" and "Views per procedure"
"Training quality was made consistent" shown by "Users," "Self-completion rate," and "Skill Map Lv distribution"

By tracking these month-to-month or quarter-to-quarter, you can more easily present them as cumulative impact.