Michael Alabi

Case Files

Problems solved, with the evidence.

Real problems from real systems, written up from the work itself: what broke, what the evidence showed, and how it was fixed.

  1. Case file · June to August 2023

    7+ weeks of downtime. One Java bug.

    Patricia, an IP management system, was down for over seven weeks while developers and technical teams tried to fix it. The cause was a bug in the Java JDK underneath it.

    • Root cause analysis
    • Java JDK
    • JVM configuration
    • Elasticsearch
    • Windows Server services
    • Test environments
    • Vendor escalation
    Read the case file →

  2. Case file · October 2025 to March 2026

    A confidentiality clause decided which AI tool lawyers got.

    Jackson Etti & Edu needed an AI tool for legal work that would not train on client confidential information. I evaluated Legora AI and Harvey AI with lawyers on live matters, chose the one whose contract ruled that out, rolled out Microsoft Copilot for everyone else, and built the governance and training around it.

    • Legora AI
    • Client Confidentiality
    • ISO 27001:2022
    • Canary Data Testing
    • Microsoft Copilot
    • AI Usage Policy
    • Role-Based Permissions
    • Data Privacy
    • Enterprise Training
    Read the case file →

  3. Case file · 2022 to 2024

    Hours lost every day to slow laptops. Fixed, one batch at a time.

    More than 80 users were losing 2 to 3 hours of productive time a day to a laptop fleet that couldn't keep up. I built the business case for a new device standard and ran a phased 24-month replacement across the organization.

    • Root Cause Analysis
    • Hardware Strategy
    • Device Standardization
    • Change Management
    • Digital Transformation Readiness
    • Phased Rollout
    Read the case file →

  4. Case file · 2024 to 2025

    A laptop was formatted on the way out. The firm couldn't remotely stop it.

    When employees leaving the firm, including a Senior Partner, formatted their laptops before departure, corporate data was lost and a gap in endpoint security was exposed: the firm owned the devices but had no way to remotely lock, wipe, or secure them. I evaluated MDM and endpoint-security options against three requirements, chose DriveStrike, and moved the firm from device recovery to device-and-data protection.

    • Endpoint Security
    • Mobile Device Management
    • DriveStrike
    • Data Loss Prevention
    • Remote Wipe & Lock
    • Employee Offboarding
    Read the case file →