01
Travel search starts with several decisions at once
Route, trip type, dates, traveller count and class all affect the search. The entry experience had to gather that context without turning the first screen into a dense operational form.
Project leadership / Travel platform
Holiday PlannerTravel Platform.
Leading a two-developer delivery across travel search, fare discovery, UX direction and booking-oriented product flows.
- Brand
- Holiday Planner BD
- Year
- 2026
- Role
- Project Lead
- Delivered through
- Brandylane
- Team
- 2 developers under my supervision
Travel search entry
Discovery / Search
Case-study scope
Holiday Planner was delivered through Brandylane with two developers under my supervision. This case study focuses on the requirements, product direction, coordination, review and delivery I owned as Project Lead rather than presenting the platform as a solo build.
01 / Project context
This was a travel product, not a brochure website.
The core experience had to move a traveller from intent into search and then into a result set where real trade-offs become visible: price, time, stops, airline, refundability and fare choice.
At the same time, the public interface had to make room for other travel-service paths and discovery content. The project therefore needed product structure, not just a set of attractive pages.
Primary journeyFlight search → results → fares
Broader entryHoliday · Visa · Umrah · More
Delivery modelProject Lead + two developers
RelationshipDelivered through Brandylane
02 / The challenge
Travel interfaces compress a lot of decisions into very little space.
02
A result list can become hard to compare very quickly
Price, duration, stops, airline, refundability and timing compete for attention. The results experience needed a clear hierarchy so customers could narrow the list instead of reading every option line by line.
03
The platform had more than one travel intent
The public experience also had to make room for holiday, visa, Umrah and broader travel discovery without losing the flight-search journey at the center of the interface.
04
The build had to stay coherent across multiple contributors
With two developers working under my supervision, requirements, interaction behavior, review and delivery needed a shared direction rather than separate implementation decisions drifting apart.
03 / My responsibility
Turn requirements into work the team could actually ship.
01
Requirements & scope
Translate the business request into concrete journeys, screens, states and implementation priorities the team could work from.
02
UX direction
Shape the search and discovery experience around what a traveller needs to understand at each stage rather than around isolated interface components.
03
Delivery planning
Break the broader platform into manageable work, sequence dependencies and keep implementation moving toward the same product outcome.
04
Developer supervision
Coordinate two developers, clarify expected behavior and review implementation as the product moved from requirement to working interface.
05
Review & QA
Check the completed flows against the intended journey, surface inconsistencies and push fixes before treating an interface state as delivered.
06
Project ownership
Act as the layer between business requirements, user experience and implementation so decisions did not get lost between client feedback and development.
04 / Traveller journey
Map the decision before polishing the interface.
- 01
Search intent
- 02
Trip details
- 03
Flight results
- 04
Filter & compare
- 05
View fares
- 06
Booking-oriented next step
The useful unit was the journey, not an isolated screen. Search inputs establish context; the results page needs to preserve it; comparison tools reduce the list; and the fare action moves the traveller into the next decision.
This public case study stops at the states visible and confirmed in the delivered product. It does not claim undocumented payment, ticketing or supplier-backend behavior.
05 / Search & discovery
Results should answer: what deserves attention first?
- 01
Keep the route context visible
The results page keeps the origin, destination, date, traveller count and class visible at the top so the customer can understand what every result belongs to.
- 02
Create shortcuts before asking users to inspect every fare
Best Value, Cheapest, Fastest and Earliest act as quick decision anchors above the list and reduce the amount of comparison work required.
- 03
Keep filters beside the decision
Price, airline, refundability and time controls sit next to the results rather than being detached from the options they affect.
- 04
Make the next action explicit
Each flight option presents a clear View Fares action, separating result discovery from the deeper fare decision that follows.
Flight discovery
Results / Compare / Filter
06 / Delivery leadership
Keep product intent and implementation moving in the same direction.
My role sat between the business requirement and the day-to-day implementation. I translated the project into flows and priorities, clarified expected behavior, supervised two developers and reviewed the product as those pieces came together.
That matters on a platform like this because a locally correct component can still create a globally confusing journey. The project-lead responsibility was keeping search, results, comparison and next actions coherent as one product.
- Requirements
- Translate business needs into executable scope
- Direction
- Define user-flow and interaction expectations
- Team
- Two developers under my supervision
- Review
- Behavior, consistency and implementation QA
- Delivery
- Coordinate feedback, fixes and completion
07 / Review & QA
Review the flow, not just the pixels.
- 01
Review behavior, not only appearance
A screen could look complete and still fail the journey. Review therefore focused on whether search context, filters, result hierarchy and next actions behaved as expected together.
- 02
Resolve ambiguity before it becomes rework
When a requirement could be interpreted in multiple ways, the useful project-lead work was clarifying the expected behavior before separate implementations started to diverge.
- 03
Keep feedback attached to the user flow
Changes were considered in the context of the traveller journey instead of treating each request as an isolated visual revision.
- 04
Own the handoff between business and development
My responsibility was not to present the platform as a solo build, but to keep product intent, implementation and delivery aligned across the team.
08 / Implementation oversight
Own the layer between product decisions and development.
I was responsible for deciding what the experience needed to do, communicating that intent clearly enough to be implemented, and then reviewing whether the delivered behavior matched the product decision.
The engineering implementation was carried out by the supervised team. My portfolio claim here is project leadership, UX direction, technical supervision and delivery ownership — not sole authorship of the codebase.
FrontendResponsive web application
BackendNode.js
DatabaseMongoDB
ProductTravel search, discovery and booking-oriented flows
The backend and database stack are confirmed. I am intentionally not naming a frontend framework here until the original frontend source or package manifest is available to verify it.
09 / Delivered result
A working travel-discovery experience centered on search and fare comparison.
The delivered interface connects the homepage search entry to a structured flight-results experience where travellers can preserve context, compare options, narrow the list and progress toward fare selection.
The result is documented through shipped interface states and confirmed delivery scope. No traffic, revenue or conversion uplift is presented without verified measurement.
Visit live website- 01Travel-search entry experience with flight, holiday, visa, Umrah and additional service paths
- 02Flight search inputs for trip type, route, departure, traveller count and class
- 03Results interface that preserves route and search context
- 04Best Value, Cheapest, Fastest and Earliest comparison shortcuts
- 05Price, airline, refundability and time-oriented result filtering
- 06Per-flight details and a clear View Fares progression
- 07Broader homepage discovery content supporting travel offers and destinations
10 / Gallery
From search intent to a comparable result set.
01 / Search entry
Trip context02 / Results
Compare / Filter03 / Fare discovery
Detailed result state
12 / Start a conversation
Need someone to turn a complex brief into a working delivery?
I can help shape the requirements, map the experience, coordinate implementation and keep the project moving from business problem to delivered product.