Building a product - Requirement gathering

Situation:

At Qatar Airways, I was assigned to develop a data dashboard that would help the Revenue Management team monitor route profitability and optimize load factors across different international markets. Previous dashboards had low adoption due to irrelevant metrics and inconsistent data sources.


Task:

My goal was to gather clear, actionable requirements to design a data product that aligned with the team’s operational and strategic needs—ensuring data accuracy, trust, and adoption.


Action:

I used a hybrid requirement gathering technique that combined stakeholder interviews, shadowing sessions, and a prototyping-first approach:


  • Conducted one-on-one interviews with revenue analysts, route planners, and senior decision-makers to identify key KPIs, pain points, and decision cycles.
  • Shadowed analysts for a week to observe how they sourced data, validated it, and generated insights—this uncovered several undocumented dependencies and manual data joins.
  • Developed a low-fidelity prototype early using mock data to validate assumptions with stakeholders in iterative feedback loops.
  • Maintained a living requirements document using Confluence and ensured regular alignment through bi-weekly check-ins.



Result:

The final dashboard integrated booking, yield, and competitor fare data using automated SQL pipelines and met all stakeholder needs. It was adopted by all 12 regional route managers, replaced five legacy reports, and directly contributed to route reconfiguration decisions that improved profitability by 8% over the next quarter.


From Blogger iPhone client