jm.JEFF MUTSCHLER
← Selected work
DELL TECHNOLOGIES / 1995–1999

Technical support.
A clearer path to an answer.

Interface design and web-based tooling for support teams and customers, connecting troubleshooting, documentation, and internal resources.

Support.dell.comCustomer-facing support
DellTechInternal resources
MPSSimulator interface
01 / CONTEXT AND ROLE

Support software should reduce the support burden.

During a period of rapid growth in personal computing, support staff and customers needed a clear route through hardware problems. The engagement combined customer-facing support interfaces, internal tools, troubleshooting documentation, and the Multiple Program Simulator interface.

As Senior Application Developer / Web Technologist II, Jeff designed and implemented support experiences and partnered with support teams to turn operational problems into working web-based systems.

Customer experience

Browser-delivered tools put guidance into an interface people could reach without first installing another support application. The design challenge was to sequence technical information in a way that helped a person take the next step. Accessibility wasn't optional here - a customer troubleshooting a hardware problem is often dealing with a display that's already partially broken, so the interface had to hold up under real-world impairment, not just an ideal one.

Internal experience

DellTech brought tools, documentation, and support resources into a coherent internal system. The information architecture had to work for people handling repeated technical questions under time pressure.

02 / INTERACTION DESIGN

Turn technical knowledge into decisions.

The following board is a newly created portfolio reconstruction. It illustrates diagnostic sequencing with generic observations; it is not an original Dell screen or a real hardware troubleshooting procedure.

Editable support workflow board showing one diagnostic question, clear observations, back and continue actions, and escalation with context
Design considerations illustrated by the reconstruction
Design choiceReasonReview question
Ask one observable question at a time.Separate what the person sees from the diagnosis.Can a novice answer without guessing?
Preserve the path already taken.Avoid repeating checks after a backtrack or handoff.Does returning to a step retain meaningful context?
Make escalation explicit.Recognize when the guided workflow has reached its boundary.Does the next person receive the evidence and history?
Organize resources around tasks.Help the support agent locate the right next tool.Can the same intent be found through familiar labels?
03 / DELIVERY AND EVIDENCE

The interface and the documentation worked together.

The work covered support interfaces, a simulator interface, hardware-troubleshooting material, and internal resource organization. That combination connects information design with technical execution: the wording, sequence, and implementation all contribute to the same support task.

Documented result

Jeff’s résumé reports an approximately 40% improvement in technical-support efficiency. The historical account also describes recognition for the work. The portfolio reconstruction does not reproduce the original measurement data or claim a new measured improvement.

Proposed evaluation today

A contemporary review would measure correct next-step selection, repeated diagnostic steps, escalation completeness, time to locate a resource, and successful recovery after an incorrect branch. These are proposed measures, not historical test results.

Original career account ↗Full Dell narrative and the original archive image.Editable support design board ↓SVG artwork for Figma import and further iteration.