August 25, 2026

Shadow work discovery is the systematic identification of the unofficial tools and habits an organisation actually relies on — the personal spreadsheets, chat groups, private trackers and manual steps that sit outside the systems management believes are being used. The purpose is not enforcement. It is to find out where the official system is wrong.

Workarounds are diagnostic, not defiant

People build workarounds because the sanctioned route costs them something the designers didn't measure. The workaround is precise evidence of where the design failed to match reality. Every shadow tool is a specification for a missing feature, written by the person who needed it most.

What discovery looks for

A spreadsheet repeatedly emailed as an attachment. A chat group named after a project. Manual re-keying between two systems. A personal tracker for work items. Recurring can-you-just-send-me requests. Approvals given in chat, recorded later. Most leave a clear trace in ordinary telemetry without reading message content.

Triage: bless, absorb, or retire

Bless it lightweight, low-risk, and building it into enterprise software would make it worse. Absorb it — real, recurring and carries risk in its current form. Retire it — solves a problem that no longer exists.

Where the risk genuinely sits

Client or personal data in ungoverned storage (live regulatory risk under DPDP, GDPR). Records with legal weight held in personal accounts. Business-critical logic in a file with one author. Material pasted into ungoverned AI tools.

FAQs

Isn't this just shadow IT discovery?
How long does a discovery exercise take?
What if leadership wants to enforce rather than absorb?
Does this apply to small teams?

Contact us

Subscribe to our newsletter

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.