Internal operations product · 2024

Hot Seat Technician Tool

A role-aware workflow for requesting and managing technical support during high-volume legal meeting scenarios.

RoleLead UX & Service Designer
ToolsFigma, FigJam, Jira, Pendo, Zoom, Teams, Miro
FocusRBAC, support workflows, service design, internal tools
Original Hot Seat Technician case study cover. Click to review the document up close.
01

Projected 25–30% reduction in task-switching time.

02

Improved prototype task success from 68% to 94%.

03

Reduced redundant fields from 12 to 5.

04

Integrated role-aware logic into existing meeting workflows.

Problem

Support work was split across tools, roles, and permissions.

Technicians needed a way to appear in the right meeting context, with the right role, without forcing support teams to over-escalate or manually coordinate every dependency.

Permission and role requirements helped define which actions each user type needed.
Request flow mapped the path from meeting need to technician assignment.

Approach

Map the service before polishing the screen.

  • Interviewed technicians and support partners to understand coordination pain points.
  • Mapped dependencies across court reporting, meeting operations, customer support, and technical support.
  • Translated RBAC complexity into clear interface visibility and action rules.
  • Identified edge cases where the system needed to prevent impossible or high-risk requests.

Design decisions

Show the right work to the right role.

  • Reduced redundant form fields so users only entered information that changed the support outcome.
  • Created role-aware visibility for technicians, reporters, and support users.
  • Created edge-case states for short-notice scheduling and post-meeting creation.
  • Balanced stakeholder requests against user clarity and operational risk.
He’s got a good eye, works fast, and has a keen sense of what users do and do not want.
Mark BakerMark Baker · CTO
Previous: Outlook Add-InNext: Service Design