VOICE OF CUSTOMER RESEARCH | DENTAL LABORATORY SOFTWARE
How should a case-handoff dashboard show exceptions and required action?
A B2B Opinion Mission designed to resolve what laboratory teams need to see, who should act and when a case must leave the standard workflow.
CLIENT DECISION
Select the dashboard structure that makes ownership, urgency and the next case action clear without overwhelming routine work.
Background
A dental laboratory software provider was redesigning the dashboard used to coordinate digital and physical cases across intake, design, production, quality review and dispatch.
The product team needed a customer view on how exceptions should appear when information is missing, a design approval is late, a remake risk is identified or delivery timing changes.
The decisions
EXCEPTION VISIBILITY
Which issues should interrupt the standard case view?
ACTION OWNERSHIP
Which role should be named as the next responsible party?
ESCALATION TIMING
When should an exception become urgent or leave the dashboard?
Customer task moments
RECEIVE
Check that the case is complete and ready to enter production.
CLARIFY
Resolve missing information or an approval dependency.
REPLAN
Respond to a production, remake or dispatch risk.
CLOSE
Confirm the case moved forward and the exception is resolved.
Why an independent customer view was needed
An external research route allowed owners, coordinators and technicians to describe workarounds and accountability problems without defending the current software configuration or their laboratory's internal process.
CUSTOMER ROOM AND OUTREACH
Reach customers with direct experience of the decision
Audience parameters and outreach routes are matched to this specific Opinion Mission.
Illustrative customer room
The example uses 21 verified participants across 7 to 9 dental laboratories. Counts and participation are hypothetical and would be adjusted to the client customer base.
7 OWNERS / MANAGERS
Accountable for turnaround, staffing and customer commitments.
7 CASE COORDINATORS
Manage intake, clarification, approvals and handoffs.
7 TECHNICIANS
Handle design, production, quality and exception recovery.
Selection conditions
- Current use of dental laboratory workflow or case-management software.
- Direct responsibility for at least one case-handoff moment tested in the mission.
- Recent experience of an incomplete, delayed, remade or reprioritised case.
- Variation in laboratory size, case mix, digital maturity and operating region.
What outreach looks like
1 ACCOUNT MAP
Identify eligible laboratories and role coverage.
2 PERMISSION
Agree contact and confidentiality boundaries.
3 VERIFY
Confirm role and recent exception experience.
4 SCENARIO
Send the neutral handoff task and options.
5 ADJUDICATE
Complete the choice and selected follow-up.
Case Handoff Adjudication
1 RECONSTRUCT AN EXCEPTION
Each participant anchors the activity in a recent case that stopped, changed owner or required clarification.
2 JUDGE THREE DASHBOARDS
Participants complete the same timed handoff scenarios using three alternative information hierarchies.
3 RESOLVE DISAGREEMENT
Nine role-balanced participants explain conflicting choices and define the minimum information required for action.
All 21 participants complete the scenario choice. Follow-up is selected by role disagreement, unusual exception type and the need to explain an ownership boundary.
CONTEXTUAL QUESTIONING
Frame questions around one realistic case exception
The sequence tests what participants notice, interpret and act on before asking which design they prefer.
BACKGROUND SHOWN TO PARTICIPANTS
Imagine that a laboratory case is due to enter production tomorrow. The prescription and scan are present, but the shade information is inconsistent and approval from the dental practice has not been recorded. Review each dashboard option as if you were responsible for moving the case forward.
Stimulus used in the activity
STATUS FIRST
Case stage, due date and exception status lead the view.
OWNER FIRST
Responsible role, pending action and elapsed time lead the view.
RISK FIRST
Turnaround, remake and customer-impact risk lead the view.
Sample questions
VERIFY
Which part of this handoff have you handled personally during the last three months?
Confirms direct workflow responsibility.
NOTICE
What is the first item you would look at, and what decision would it help you make?
Tests the information hierarchy before preference is discussed.
ACT
Using this option, what would you do next and who should receive the action?
Reveals whether the proposed ownership is operationally clear.
COMPARE
Which dashboard lets you resolve the case with the least interpretation, and what do the other options hide?
Forces a grounded scenario choice.
ESCALATE
At what point should this exception interrupt routine work or trigger contact outside the dashboard?
Defines the urgency and channel boundary.
CONDITION
What additional field or confirmation would change your selected option?
Identifies the minimum viable exception record.
Question wording, terminology, language and stimulus detail would be adapted to the client decision, customer relationship and permitted-use boundaries.
DECISION VIEW
Turn the customer response into a specific decision
The visual and Decision Board are designed around the evidence produced by this mission, not a reusable generic score.
Hypothetical scenario decision pattern
DASHBOARD OPTION | OWNERS / MGRS | COORDINATORS | TECHNICIANS | ALL ROLES |
|---|---|---|---|---|
Owner first | 3 / 7 | 5 / 7 | 3 / 7 | 11 / 21 |
Status first | 2 / 7 | 2 / 7 | 4 / 7 | 8 / 21 |
Risk first | 2 / 7 | 0 / 7 | 0 / 7 | 2 / 21 |
Role counts show the option selected most often after participants completed the same exception task. They are hypothetical and are not market estimates.
What differs across the customer room
OWNERS / MANAGERS
Prefer a clear risk and escalation view when turnaround or customer commitments may change.
CASE COORDINATORS
Need owner, missing input and follow-up timing in one actionable block.
TECHNICIANS
Prioritise the exact production constraint and approval state over commercial impact.
VoC Decision Board
DEFAULT VIEW
Lead with case stage, named owner, missing input and due-time consequence.
EXCEPTION RULE
Interrupt routine work only when the case cannot advance, customer timing changes or remake risk rises.
CONTACT BOUNDARY
Clinical interpretation and unresolved prescription conflicts retain a visible route to direct confirmation.
OWNER AND NEXT CHECK
The product owner prototypes the selected hierarchy; laboratory users then complete a find-and-act validation task.
PROJECT DELIVERY
Turn the customer evidence into an exception dashboard blueprint
The handoff connects customer decisions to dashboard hierarchy, exception logic, ownership and the next usability check.
What the client receives
SCENARIO EVIDENCE
Role choices, action errors, missing fields and escalation conditions.
DASHBOARD BLUEPRINT
Default hierarchy, exception states, owner labels and action timing.
DECISION RECORD
Supported choices, minority-critical needs, owners and validation questions.
How teams use the result
1 PROTOTYPE
The product team converts the selected information hierarchy into a testable dashboard.
2 DEFINE
Operations and customer teams confirm status definitions, ownership and exception triggers.
3 VALIDATE
Role-specific users complete new handoff tasks without moderator assistance.
Delivery and boundaries
Typical timeline
Approximately five to seven weeks, depending on account permission, role coverage and follow-up availability.
Delivery route
Scenario-choice evidence, exception hierarchy, ownership map, Decision Board and a working session with product and customer teams.
Evidence boundary
The result reflects the participating laboratory roles and the scenarios tested. It does not validate clinical decisions or represent every laboratory workflow.
Note: The company situation, participant counts and findings in this example are hypothetical. They demonstrate how the service could be applied and are not presented as real client outcomes.
Contact Us
DISCUSS YOUR VOC QUESTION
Tell us the workflow decision, customer roles, software context and account-access boundaries. August Research will help define the Customer Room, Opinion Mission and decision view required.