MCPC

Mobility programs usually stall for the same reason — and it isn't the technology.

The fleet grows faster than the structure managing it. What breaks is everything around the devices: ownership that was never clearly assigned, policies applied inconsistently across device types, and an IT team managing mobile devices on top of an already full plate.

The result is a program that's technically live but never mature. Devices are enrolled, but visibility is partial and support is reactive.

Getting unstuck takes less new technology and more structure:
1. 𝗔 𝗰𝗹𝗲𝗮𝗿 𝗼𝘄𝗻𝗲𝗿. Someone accountable for the mobility program end to end.
2. 𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁 𝗽𝗼𝗹𝗶𝗰𝘆 𝗲𝗻𝗳𝗼𝗿𝗰𝗲𝗺𝗲𝗻𝘁 across every device type, not just the easy ones.
3. 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 𝗰𝗮𝗽𝗮𝗰𝗶𝘁𝘆 𝘁𝗵𝗮𝘁 𝘀𝗰𝗮𝗹𝗲𝘀 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗳𝗹𝗲𝗲𝘁 — because enrollment grows automatically, but support doesn't.

The organizations that get this right treat mobility as a managed program, not a side task for an already stretched IT team.

More in comments →

Most of the DEX conversation is about the platforms: tools that pull telemetry from devices, capture sentiment, and surface friction before someone files a ticket. They're genuinely valuable, and the organizations serious about DEX already run them.

What sets the leaders apart is where they look next.

What the platform sees, it sees well: the steady state, a device running in the hands of someone already working. The organizations pulling ahead have started paying attention to everything that happens outside that frame — at the moments before the device is in use and as it changes hands.

Day one. The replacement after a failure. The exit.

Those moments shape how people feel about their technology as much as any daily metric. We wrote about where to find them and what to measure at each one. Link in the comments. 👇

Device costs don't end at purchase. That's usually where they start compounding.

Deployment time, support tickets, downtime, and end-of-life handling all factor into total cost of ownership (TCO) — and most organizations track them in separate budgets, if they track them at all. The real savings live in the parts of the lifecycle nobody's measuring end to end.

Lifecycle services reduce TCO by targeting:
1. Deployment efficiency through standardized, zero-touch provisioning
2. Support costs through proactive lifecycle visibility instead of reactive tickets
3. Refresh timing based on data instead of a fixed schedule
4. Recovery value through remarketing and responsible disposition, instead of devices depreciating in storage

TCO doesn't come down by spending less on devices. It comes down by wasting less across their lifecycle.

People forgive a broken laptop. Hardware fails — everyone knows that.

What they don't forgive is the week that follows: the waiting, the loaner that has nothing installed, the replacement that shows up bare and restarts the whole setup problem while the work piles up. It's one of the sharpest tests of the digital employee experience (DEX) — and one of the least watched.

The failure is never the story. The recovery is.

Ask someone what they remember about their company's technology.

It won't be an average Tuesday when everything worked. It'll be their first morning — whether the login worked. The week their laptop was down. And if they've left a job, how the exit was handled.

The moments people actually remember are the ones that happen when a device is changing hands. Which is exactly the part of the digital employee experience (DEX) nobody's measuring.

Article in comments →

Device prices have risen for seven consecutive months, and July added four more actions: HP and Lenovo on the first, Apple's protection plans mid-month, Microsoft Surface at month's end.

The useful part is what comes next. Lenovo has already published increases for September 1 and October 1, which makes August a window rather than a warning.

That's the first issue of the Device Price Watch: every price action we tracked last month, the effective dates ahead, and the lead times worth planning around. Four pages, published monthly. Link in the comments.

For organizations in regulated industries, choosing a device lifecycle partner is a governance decision, not just an operational one. Every device that touches sensitive data becomes part of your audit story — where it's been, who handled it, and how it was retired.

That changes what you should evaluate:
• 𝗗𝗲𝗳𝗲𝗻𝘀𝗶𝗯𝗹𝗲 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻. The provider should produce chain-of-custody records on demand, not reconstruct them when an auditor asks.
• 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗮𝘁 𝗲𝘃𝗲𝗿𝘆 𝘀𝘁𝗮𝗴𝗲. Data protection can't start at disposition. It has to hold from deployment through return, repair, and retirement.
• 𝗔𝘂𝗱𝗶𝘁-𝗿𝗲𝗮𝗱𝘆 𝗿𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴. Records should map to the requirements your auditors actually check, in a format they'll accept.
• 𝗔 𝘀𝗶𝗻𝗴𝗹𝗲 𝘀𝗼𝘂𝗿𝗰𝗲 𝗼𝗳 𝘁𝗿𝘂𝘁𝗵. One consistent asset record across the lifecycle. If your data lives in three systems that disagree, every audit starts with reconciliation.

The right partner doesn't just manage devices. They reduce audit risk before the audit happens.

What's driving your documentation requirements most right now — regulatory audits, security reviews, or sustainability reporting?

Details in comments →

The modern workforce has evolved. The way most organizations manage the devices behind it has not.

A modern approach to device management is built to close that gap. It treats the device as part of a connected lifecycle — selected for the role, deployed without friction, secured by policy, supported proactively, and planned around where work is heading. The payoff shows up across the business: in productivity, in security, in cost predictability, and in how supported employees feel.

Read the full article for what modern device management looks like and what it delivers across HR, finance, and IT

→ Link in the comments

The workplace has modernized. The workforce has modernized. The devices employees rely on have modernized. The management model behind them should be modern too.

That means an operating model built for distributed work, widely varied roles, high expectations, and an environment that keeps evolving. In practice, it comes down to eight capabilities:
- Persona-based devices
- Automated, zero-touch provisioning
- Modern collaboration tools, fully integrated
- Policy-driven security that follows the device
- Lifecycle visibility from deployment to retirement
- Proactive, experience-driven support
- AI-ready refresh planning
- Sustainable, secure asset retirement

No single one delivers a modern device program on its own. The value comes from how they work together.

Read the full article for what each capability looks like and what modern device management delivers across the business
→ Link in the comments