How a usage assessment unfolds

This guide describes our flagship Application Usage Assessment. Shorter engagements compress the same sequence; workshops skip analysis and focus on interpretation habits your team can sustain.

1. Week 0

   Intake & scope lock

   We confirm the application list, the questions the assessment must answer, data access paths, and named stakeholders. Out-of-scope systems are written down so they do not creep back in mid-project.

2. Week 1

   Inventory reconciliation

   Owners, purposes, environments, and license models are recorded with confidence marks. Shadow utilities discovered in interviews are added rather than ignored.

3. Week 2

   Evidence gather

   Usage extracts, seat lists, and access roles are collected. Stakeholder interviews cover seasonal work, break-glass accounts, and where people still route tasks through older files.

4. Weeks 3–4

   Analysis & draft findings

   We map adoption and dormancy by team, flag overlapping tools, and draft reclaim or training actions with confidence bands. Sparse logs produce narrower claims, not invented precision.

5. Final week

   Workshop & handoff

   Stakeholders walk through findings together. You receive the written assessment and a ninety-day backlog. Optional follow-on work is scoped separately — never assumed.

What you prepare

• A current application inventory, even if imperfect.
• Read-only access to usage exports or admin consoles.
• Ninety minutes with each named stakeholder.
• Any renewal or rollout date that should shape priorities.