MSIA Series · 10 Candidates

Products diagnosed.
Failures named.

Ten developer-built products put through the five-lens UX Intelligence method. Each one has a structural failure — identified, named, and documented with a prioritised fix list. One candidate is fully published. The rest are in sequence.

Structure Feedback Readability Flow Consistency
Audit candidates
Failing lenses
Feedback Structure
Fix list
Add inline confirmation after every transaction state — silence reads as failure even when the backend succeeded
Promote "Receive Money" to primary action — current equal-weight dashboard buries the product's core job
Surface transfer status persistently on the dashboard — users re-entering the app have no anchor
Watch audit (opens Loom in new tab) Case study (opens Behance in new tab)
Failing lenses
Readability Structure
Fix list
Establish a clear type hierarchy — financial data at equal weight forces users to read everything to find the number that matters
Restructure the ledger view around the primary action: reconcile, not browse
Reduce visual noise in data rows — density without rhythm breaks scan patterns
Loom · Behance — publishing in sequence
Failing lenses
Structure Flow
Fix list
Define a primary action per screen — savings products with multiple parallel CTAs collapse user intent
Fix the funding flow: confirmation steps appear before the user has committed, creating false friction
Group wallet and savings views by job-to-be-done, not by product type
Loom · Behance — publishing in sequence
Failing lenses
Feedback Consistency
Fix list
Normalise alert severity language — three different terms for the same incident state break trust in the monitoring system
Add persistent system status to the dashboard header — monitoring tools must answer "is anything down right now" in under 2 seconds
Unify action states: "disable", "pause", and "mute" are doing the same job with different words
Loom · Behance — publishing in sequence
Failing lenses
Consistency
Fix list
Align component behaviour across mobile and desktop — the same action produces different visual outcomes on different screen sizes
Establish a single CTA pattern for listing pages — four button variants for "contact seller" train users to distrust the interface
Standardise empty states — each section invents its own language for "nothing here yet"
Loom · Behance — publishing in sequence
Failing lenses
Readability Flow
Fix list
Make cron syntax human-readable at the point of entry — displaying raw expressions without translation breaks the creation flow for non-expert users
Redesign the job log view: timestamps at equal weight to status codes create a reading task, not a scan
Add a confirmation step before destructive job actions — delete and disable are adjacent with no visual distinction
Loom · Behance — publishing in sequence
Failing lenses
Flow ×2
Fix list
Collapse the top-up flow from 5 steps to 3 — identity verification is requested twice across a single session
Fix the payment confirmation loop: successful payments return users to the start screen with no receipt state
Separate the "pay fees" and "transfer money" flows — sharing a flow for two distinct jobs creates decision paralysis at the most critical screen
Loom · Behance — publishing in sequence
Failing lenses
Structure Feedback
Fix list
Make live location the primary element on every active-delivery screen — it is currently below the fold behind order metadata
Add granular delivery status states — "in transit" covers a 45-minute window with no intermediate feedback
Surface the driver contact action persistently — buried in a collapsed panel during the one moment users need it most
Loom · Behance — publishing in sequence
Failing lenses
Flow Readability
Fix list
Separate form building from form publishing — two distinct jobs share one screen, creating a constant context-switching problem
Increase field label contrast — labels render at the same weight as placeholder text, making the builder hard to navigate
Add a preview mode that reflects the actual respondent view — builder and output are visually identical, breaking the mental model
Loom · Behance — publishing in sequence
Failing lenses
Feedback
Fix list
Show the invoice screen before the dashboard on first load — starting with the spend overview creates false confidence before the user has verified their data
Add cost-change indicators to every line item — the dashboard shows totals without delta, making it impossible to act on the information
Surface anomaly alerts above the fold — buried notification system means cost spikes go undetected until the invoice arrives
Loom · Behance — publishing in sequence
Your product · Next

Yours could be MSIA-011.

Your product. Your diagnosis. ₦15,000 · async · 48–72 hrs.

Book the audit

Manny Aziba · Interface Intelligence Studio