Technical Risks

🔴 HIGH RISK: No Direct User Access for Research

• Risk: Cannot conduct user interviews, usability testing, or field studies with actual CEOs and Financial Managers
• Impact:
  • Design decisions based on assumptions rather than validated user needs
  • Cannot test prototypes with real users
  • Risk of building features users don't need or misunderstanding pain points
  • No direct validation of design solutions
• Mitigation:
  • Leverage stakeholder knowledge (they interact with clients daily)
  • Analyze support tickets and complaint patterns from client relations team
  • Review past user feedback and surveys if available
  • Use Hotjar session recordings and heatmaps to understand actual user behavior
  • Review CX (Customer Experience) documents for historical pain points
  • Analyze meeting recordings with internal stakeholders
  • Request anonymized screen recordings or session replays if available
  • Use analytics data to identify friction points (drop-offs, time-on-task)
  • Conduct "proxy testing" with internal staff who use similar workflows
  • Build in post-launch feedback mechanisms to validate assumptions
  • Plan for iterative improvements based on real usage data after launch
• Owner: Aymen + Stakeholder Team

🔴 HIGH RISK: Scope Ambiguity - Additional Features

• Risk: List of "additional features" from touchpoints needs scope clarification (Insurance, Financial Data, Letter of Credit, Non-Envisaged Items, etc.)
• Impact:
  • Unclear what needs redesign vs what can remain as-is
  • Potential scope creep
  • Resource allocation uncertainty
• Mitigation:
  • Conduct feature audit in Phase 1 Discovery
  • Prioritize based on usage data from Hotjar/analytics
  • Create "Must-have vs Nice-to-have" framework
  • Define V1 vs V2 scope clearly with stakeholders
• Owner: Aymen + Product Owner + Stakeholders

🔴 HIGH RISK: Nafath & Absher Integration Complexity

• Risk: API integration may have technical limitations or delays
• Impact: Affects registration and digital signing flows - critical user journeys
• Mitigation:
  • Early technical discovery with IT team
  • Create fallback flows
  • Parallel design exploration for alternative approaches
  • Test integration early in development phase
• Owner: Technical Lead + Aymen

🟡 MEDIUM RISK: Legacy System Constraints (Tamkeen Plus Backend)

• Risk: Tamkeen Plus backend may limit UI flexibility or real-time data availability
• Impact: Design vision may need compromise, especially for "Radical Transparency" features