GDI Rent Management — a six-week engagement from the first requirements conversation to production deployment, with continuous refinement during onboarding and training.
Refinement overlapped onboarding and training — changes landed while users were already using the platform.
Stakeholder interviews, operational workflow mapping, and existing-process audit. Established the functional scope and success metrics before any code was written.
Stood up a working prototype covering the core flows — renters, invoicing, receipts, deposits — for stakeholder review. Feedback loop ran tight so every demo produced a concrete decision.
Finalised scope, pricing, and service expectations. Aligned on what would ship on day one vs. what would come in post-launch iteration.
Production data migrated, user accounts provisioned, company settings configured. Refinements — small UX tweaks, label changes, workflow adjustments — shipped live as onboarding revealed them.
Role-based sessions with admins and staff, supported by a built-in Job Aid and Submit-a-Ticket channel. Training feedback fed back into the same refinement backlog.
Refinement wasn't a separate phase — it ran alongside onboarding and training. Each change was logged in Jira, prioritised with the customer, and deployed without interrupting daily use.
Adoption of a new system depends on people as much as on software. We ran the engagement through Prosci's ADKAR model.
Identified the operational pain points with stakeholders.
Aligned on what a better day-to-day workflow should feel like.
Trained admins and staff on the new dashboard and processes.
Hands-on support during onboarding — real tasks, real coaching.
Jira-tracked iteration kept new habits from drifting back.
Every change request, bug report, and onboarding observation landed in a single Jira board. Prioritisation, traceability, and sprint reviews all ran from that one source of truth — no stale spreadsheets, no lost feedback.
Onboarding and training doubled as a live feedback loop. When a user said "this label would be clearer as X," the change was in the Jira backlog the same day and live within the week.