Apple fleets: measure employee experience and support workload
An Apple fleet should let employees work without waiting for support. Here is our protocol to measure friction and choose tasks to automate.
1. The starting point: a best-practice publication
On November 11, 2026, Jamf outlines three ways to improve digital employee experience: automate repetitive tasks, enable self-service and improve fleet visibility. These are recommendations rather than a new version announcement. Underside proposes a measurement method before wider rollout.
2. Choose one journey and establish a baseline
We recommend starting with one journey: obtaining an approved application on a work Mac. Define the starting point, expected outcome, service owner and the point at which the request is resolved. Keep installation, permission changes and data access separate in your measurements.
Before changing the journey, record time from request to first successful use, IT interventions and reopened requests over a representative period. Then compare the pilot with a group doing comparable work. Document the sample size and concurrent changes: fewer tickets alone do not prove an improvement.
3. Build a usable pilot record
We propose five fields: scope (application, user group, locations, macOS versions and distribution channel); prerequisites (licence, authorised identity, network, business owner); outcome (installation, opening and a business test task); exceptions (offline device, insufficient storage, denied access); evidence (timings, interventions, outcome and resolution owner).
This record is our proposed acceptance procedure, not a list of guaranteed Jamf features. Check what Jamf or your MDM can actually observe and automate. Add brief user feedback: could they work, did they understand the failure message and did they know whom to contact?
4. Underside analysis: keep exceptions visible
Our view is that a self-service journey warrants expansion when it reduces waiting without hiding failures. Set acceptance criteria before the pilot: a business-defined time target, no excessive permissions, support documentation and tested recovery. An application appearing in a catalogue does not prove successful use.
Connect this measurement to your application catalogue and self-service. Its focus is distinct: assessing the journey and support workload rather than selecting applications. For device handover, consult our guide to Apple onboarding and inventory. Apple Business Manager, Automated Device Enrollment and MDM need to be addressed in the architecture; this pilot assesses the service delivered after that preparation.
5. What this changes for a Belgian or French business
For a small business, we recommend a simple record and a single owner before adding tools. Mid-sized organisations, large enterprises and public bodies can compare outcomes by location and user group without ranking individual employees. For organisations operating in Belgium and France, use shared indicator definitions and instructions adapted to working languages.
Limit collection to the information needed for diagnosis, with a defined retention period and restricted access. Have the relevant owners review the approach for your circumstances. This pilot demonstrates neither overall regulatory compliance nor headcount savings: it helps prioritise improvements.
6. Decide whether to expand
Compare time to successful use, IT interventions, unresolved exceptions and employee feedback. Expand the journey if the agreed criteria are met. Otherwise, first address the main dependency: licensing, identity, distribution or networking. Retain the results and measure again after a significant change.
Underside, an Apple Business Partner, supports Apple deployment, management and support in Belgium and France. Discuss your Apple support journeys.
Source : Jamf — How Lean IT Teams Can Improve DEX Without Adding Headcount (2026-11-11).