Workflow deconstruction example

• ← back

I had a consulting engagement for a BigTech company. The brief was to fix a slow, manual device-provisioning process for schools. The real finding: fixing it isn't worth solving in itself; it's worth solving the bigger system. Short structured recap below, to show thought process.

recap mental model

Input: 18 interviews + market data → 22 pain points.
Analysis: map to 5-stage journey → 3-filter funnel (frequency → time → deviation) → 3 prioritized areas with quantified fixes → reality check ($960/yr is too small).
Output: don't sell provisioning, sell a one-stop tech shop — build the device first, sequence the fixes, and only large players can win.

Input ingested — what the team gathered

• Primary research: 18 interviews total — 15 K-12 IT teams (12 of which use tablets), plus other IT teams and one third-party service provider (an Account Executive). Among tablet users, 10 of 12 (83%) use iPads exclusively, which is why the whole study narrows to the iPad provisioning journey.
• Secondary research: market-share data (StatCounter, Source 6), education tablet market sizing (TechNavio, Source 2), and vendor documentation for Apple ADE/ASM, Google Zero-Touch, and Samsung Knox.
• The raw signal: 22 distinct pain points surfaced across the interviews, fragmented across the customer journey.

Structural analysis — how raw input became a recommendation

Step 1 — Map the journey. Five stages: (1) setup MDM + accounts, (2) purchase & enroll into ASM, (3) enroll into MDM + push policies/apps, (4) asset-tag & enroll into RMS, (5) deploy. This gives every pain point a location.

Step 2 — Prioritize the 22 pain points through three sequential filters:

• Frequency → shortlisted 6 (each ~33%+ of mentions).
• Average time spent → grouped the 6 into 3 areas; RMS integration had the lowest avg time (7 min) → ranked 3rd.
• Maximum deviation → broke the tie between the top two: OS-MDM integration's 24-hour worst case (1-in-5 failure) beat network connectivity's 120 min → ranked 1st.

Result of the funnel: 3 prioritized problem areas → (1) OS Management Portal–MDM Integration, (2) Network Connectivity, (3) RMS Integration.

Step 3 — Match each area to a recommendation + quantified impact:

• OS-MDM → unified portal → saves 10–15 min/device.
• Network → auto-reconnect + smart scheduling → cuts wait 75% (2 hrs → 30 min).
• RMS → engraved barcodes + integrated portal/API → saves ~5 min/device.

Step 4 — Pressure-test against business reality. The savings are real but small: ~2.5 days/year/school ≈ $961.5/year. That fails to drive demand on its own.

Structural output — what the team recommended

The pivot: provisioning fixes alone aren't a business — they're a feature. The actual recommendation is a one-stop tech shop: integrate the full value chain (tablet manufacturing + apps + MDM + OS management) so a customer picks a device and add-ons in one portal and receives it fully provisioned, with provisioning bundled into device cost.

The sequencing: first build a competitive K-12 tablet + education-app ecosystem; then layer the Section 3 fixes (network solutions first, unified portal + auto-tagging second).

The strategic caveat: full-chain integration is a barrier to entry — feasible only for large players, who must position as either a differentiator (beat iPadOS experience) or a low-cost leader.