Objective: To define the scope of the mobile experience, prioritize essential data for the "My Inbox" approval workflow, and map the current notification journey.

1. Usage Context & Scope

Goal: Understand "Why" and "When" the mobile version is used to prevent feature creep.

• Primary Use Case: "What is the single most important task you need to complete when accessing Munafasset on your mobile? (e.g., Quick status check, Urgent approval while traveling, or Full review?)"
• Feature Scope: "Is the mobile experience strictly for Viewing and Approving pending items, or do you anticipate needing to Create or Edit RFPs on your phone?"
  • Follow-up: "If editing is required, what specific fields would you edit on the go?"
• Environment: "Where are you usually located when accessing the mobile version? (e.g., In transit, between meetings, or just away from the desk?)"

2. Content Prioritization (RFP Details)

Goal: Solve the 'Overwhelming Details' issue by identifying the Minimum Viable Data.

• Data Density: "Mobile screens have limited space, and we want to avoid overwhelming you with the full desktop view. To keep it focused, what are the top 5 fields you absolutely must see to make a decision?"
  • Prompts: Project Name? Budget Value? SLA Status? Vendor Name?
• Hidden Details: "What information can be safely hidden behind a 'Show More' button or omitted entirely on mobile?"
• Attachments: "Do you review attached documents (PDFs/Contracts) on your phone, or is that a task you save for the desktop?"

3. Workflow & Notifications

Goal: Map the 'Trigger to Action' path.

• The Trigger: "Currently, how are you notified that an RFP needs your approval? (Email, SMS, Teams?)"
• The Journey: "When you receive that email notification on your phone and click the link:
  1. Does it currently take you to the mobile browser?
  2. Does it require you to log in every time?
  3. Does it land you directly on the specific RFP, or do you have to search for it?"
• Deep Linking: "Ideally, should the email link take you directly to the specific 'My Inbox > Pending Approval' tab we discussed?"

4. Naming & Terminology Validation

Goal: Verify if the current module names align with the user's mental model.

• Clarity Check: "Do you find the names of the modules—'Search RFP', 'My Approvals', and 'My Inbox'—confusing in any way?"