As a platform admin, I want to see every onboarded organization in one list, so I can quickly spot who's active, inactive, or falling behind.
AIM: the AI Maturity
Assessment Framework.
This case study is confidential.
The client hasn't made this work public, so the write-up and the screens are behind a password. Enter the password to carry on, or get in touch and I'll walk you through it myself.
What is AIM?
AIM is the AI Maturity Assessment Framework. It lets a company look at its AI the way it looks at revenue or headcount: as a score you can track, compare and argue about.
Plenty of companies have rolled AI tools out across their teams. Far fewer can tell you whether it worked. AIM measures adoption, engagement and performance impact for a whole organization and for each department inside it, then lets you put two organizations next to each other and see who's doing better.
Problem statement
Organizations buy AI tools faster than they can measure them. Leadership knows the licences were paid for. Ask who's actually using them, how often, and whether it moved any number that matters, and the answers get vague.
So adoption gets reported anecdotally. A team quietly stops using the tool and nobody notices for two quarters. And even good numbers mean very little, because there's nothing to compare them against. The job was to turn "we think this is helping" into something specific enough to act on.
Users & user stories
Two groups use it, and they overlap. Platform owners look after the list of onboarded organizations. Org-level stakeholders only really care about their own.
As a platform admin, I want to select two or more organizations and compare them directly, so I can identify what a strong org is doing differently.
As an organization owner, I want a single score that combines adoption, engagement, and results, so I don't have to interpret three separate metrics myself.
As an organization owner, I want to see performance broken down by department, so I know exactly where to focus enablement efforts.
As a first-time user, I want a clear next step when I have no organizations yet, so I'm never looking at an empty screen without knowing what to do.
User journey map
Mapped for the platform admin, from first login through to doing something about a comparison.
Sign in
Logs into AIM with a work account.
ConfidentEmpty state
No organizations yet, so the screen has to give them one obvious thing to do.
UncertainCreate organization
Onboards the first org and starts seeing live data populate.
EncouragedScan the list
Reviews all organizations, scores, and trend direction at a glance.
In controlDeep dive
Opens a single org to see department-level performance and growth.
InformedCompare
Selects two or more orgs to benchmark them side by side.
DecisiveUI/UX goals
Four rules I kept coming back to.
Glanceable first, detailed second
Every screen opens with a handful of numbers, before any table or chart. If someone has to read to find out whether things are fine, the screen has failed.
One score, then the story
Each organization gets one combined score to anchor it. Adoption, engagement and impact sit underneath for anyone who wants to know why.
Guide, don't block
Empty states and errors, like the compare modal, say what happened and what to do about it. No dead ends.
Calm, trustworthy surface
People open this thing every morning. A soft sage palette and plenty of white space keep a data-heavy product from feeling like a chore.
Colors & type
Muted sage and forest greens, so a screen full of data doesn't shout. Coral is kept for downward trends and warnings only, which means colour here always tells you something.
The product
Six screens covering the whole loop, from signing in to putting two organizations head to head.