Four principles I build into every product, from the first requirement to production.
Start with the user
Watch the work before writing the requirement.
When people jump through hoops to get their job done, I find the workaround and remove it, with a feature, a simpler process or better training. Help belongs in context, not in a one-inch manual.
ProofA customer opposed the first phase of a feature, so I put them on the review team before rollout. They became our strongest advocate.
Secure by design
Protect sensitive data from the first requirement.
Personal and financial data, from Form I-9 to bank accounts, is protected in the requirements: masked SSNs, encryption in transit and at rest, secure file upload and one-time passcodes.
ProofDefined NACHA-mandated encryption of ACH data at rest, delivered ahead of the deadline. Served on the GDPR Task Force and led I-9 Audit Download at Ultimate Software (UKG).
Accessible to everyone
Accessibility from day one, not as an add-on.
WCAG contrast, a logical keyboard order and layouts that work on any screen are requirements, not polish. Teaching students with vision and hearing impairments taught me to plan for every learner.
ProofThis website and my student tools are built to work with a keyboard, a screen reader and a phone.
Built to support
Make problems quick to find and fix.
I build in logging and diagnostics that never expose sensitive data, so production support can solve more on its own and engineers can pinpoint the rest faster.
ProofAt Ultimate Software, every feature passed Gut Check and Kick Off checklists covering privacy, security and serviceability.
- Regulated domains
- InsuranceFintechHCMBankingAutomotive
- Compliance
- GDPRSOXNACHAForm I-9
- Integrations
- TransUnionPaymentsACH processingReconciliation
- Platforms
- Cloud migrationMainframe retirementSharePoint Online
- Data
- SQLOracleData warehousingStatisticsGenerative AI
- Delivery
- ScrumKanbanAzure DevOpsJira