01Challenge
Membership, education, payments and governance, held together by hand.
The institution managed membership, documents, payments, professional education and governance through spreadsheets, paper records and disconnected administrative practices. Finding a member’s complete history could mean searching separate files, checking balances and certificates manually, and asking colleagues to reconstruct context.
The result was repeated data entry, slow verification, inconsistent workflows, little visibility of pending requests and dependence on individual knowledge. As responsibilities grew, more work risked meaning more staff. The objective was to give the existing team more capacity through connected information and standardized processes.
It needed more than a database. Membership eligibility, financial obligations, certificate rules, review responsibilities and permissions had to become explicit business rules before they could become dependable software.
02Diagnosis
Four discovery workshops, one shared picture.
Each workshop examined one part of the institution’s operations with the people responsible for it, and ended with concrete follow-ups.
- Workshop 1
Member registry and data import
Registration fields, profiles, search and filters, membership status, balance logic, suspension and documents.
- Workshop 2
Member portal and education
A member-facing portal, a gatekeeper review for profile edits, and the professional education workflow.
- Workshop 3
Certificates and meeting records
Internal and external certificates, request tracking, institutional documents and meeting records.
- Workshop 4
Finance and disciplinary requirements
Income and expenses, categories, recurring entries, upcoming obligations, and case handling requirements.
03Design
From institutional rules to a delivery backlog.
Workshop findings were translated into functional requirements and user stories that link roles, information fields, permitted actions, status changes and dependencies: member lifecycle rules, approval and rejection procedures, financial tracking, certificate conditions, reviewer responsibilities and role-based access.
Data preparation was a workstream in its own right: consolidating member information, standardizing identifiers and profile fields, reconciling duplicates and education records, and preparing master lists and document templates.
- MVP 1Core platform, member registry, member portal, gatekeeper review and historical data ingestion.
- MVP 2Certificates, professional education and meeting records.
- MVP 3Action items, financial management, administration and security.
04Platform
One platform where there used to be many files.
The platform connects the administrative and member experiences around shared information. These capabilities were developed across the three MVPs; feature-level acceptance testing was still being completed at the time of writing.
Member registry
Searchable profiles bringing together registration details, status, documents, payments and education history.
Member self-service portal
Members view information, certificates and request status, and request eligible profile changes.
Gatekeeper review
Profile changes and requests are approved, rejected or followed up by an authorized reviewer.
Certificates and documents
Application, review, generation and retrieval, connected to member information.
Professional education
Education records, credits and supporting certificates in the same place as membership.
Financial records
Structured financial records and membership balances for institutional oversight.
Meeting records
Discussions, participants and decisions, kept for continuity and follow-through.
Roles and access
Administrative accounts and configurable access aligned with responsibilities.
- 01Member requestA member submits a change or application through the portal.
- 02Gatekeeper reviewAn authorized reviewer approves, rejects or follows up.
- 03Official recordOnly reviewed changes update the member’s record.
05Delivery & status
Iterative delivery, honestly reported.
Delivery moved from discovery and design to successive MVPs, each demonstrated, tested and refined with stakeholder feedback.
- Discovery and requirementsFour workshops, follow-ups and scope reviews.
- Test-environment demonstrationsWalkthroughs and an acceptance-testing period for the first MVP.
- All three MVPs submitted and demonstratedOctober 2026. Committee members then received access for review.
- Deployment, training and handoverIn preparation at the time of writing, with training material and documentation to follow deployment.
06Value
What we can say, and what we can’t yet.
A broad set of institutional needs became an organized backlog and working MVPs, connecting member and administrative experiences.
Work involving spreadsheets, information retrieval, document preparation and manual verification that took hours can be handled in minutes through connected records and structured workflows.
A qualitative account of capability, not a timed study.
Turnaround times, rework, backlog age and active usage, compared before and after adoption.
We’ll publish measured results once they are confirmed with the institution.