IIMS

A custom ERP built for an organisation that had outgrown every tool it had. Real-time programme monitoring, 5-tier access control, dynamic scheduling, task allocation, and complete audit logging — all in one web application used daily across every level of the organisation.

I embedded myself in the organisation — attending meetings, shadowing every role, mapping workflows by hand. What I found was structural fragmentation that had built up over years.

• No single source of truth

  Programme data lived across spreadsheets, WhatsApp threads, paper registers, and memory. Decisions were made on outdated information.

• Scheduling ran on verbal agreements

  Staff allocation via verbal briefings. Conflicts weren't caught until they became crises.

• Administrators were flying blind

  Programme status could only be checked via physical walkthrough or an end-of-day call.

• No task accountability

  When things weren't done, there was no trail — and the same gaps repeated every cycle.

Every module maps to a problem found during research. If a team didn't need it, it wasn't built.

• Admin Management —

  User creation, roles, permissions, and full audit trail.

• Real-Time Monitoring —

  Live programme dashboards — auto-refreshing, no phone calls.

• Scheduling Engine —

  Conflict detection, recurring events, calendar views by day/week/month.

• Task Allocation —

  Assign, acknowledge, track progress, and log completion in real time.

• Role-Based Access —

  5 tiers — each role sees only what it needs.

• Reporting & Analytics —

  Auto-generated reports, exportable as PDF or CSV, indefinitely searchable.

• Staff & Participant Records —

  Centralised, searchable, linked to task history and programme logs.

• Audit Log —

  Every action logged. Non-deletable. Total accountability.

Login, dashboard, and reports carried the most daily load. Login had to be fast — field staff have short windows. The dashboard shows three different views for three different roles. Reports had to be readable without training.

I ran three usability sessions with real staff on actual builds — not prototypes. Everything that looked fine in Figma got tested until it held up in real conditions.

• 01 — Immersion —

  Two weeks on-site: meetings, floor walks, staff interviews

• 02 — Journey Mapping —

  Workflow maps for every role, start to finish

• 03 — Wireframes —

  3 iterations with stakeholders before going hi-fi

• 04 — Design System —

  80+ components — built before screens, not after

• 05 — Usability Testing —

  3 on-site rounds with actual staff, actual tasks

• 06 — Build & Rollout —

  QA, training, staged launch across the organisation

Staged rollout — admin core first, then operational staff. Adoption was faster than projected with no resistance. The system matched how people already worked, so the learning curve was nearly zero.

"For the first time, we can see what's happening across the entire organisation without picking up a phone. IIMS didn't just give us software — it gave us operational clarity."
— Senior Administrator, Client Organisation