This case study is gated. Enter the access key to view Le Train in full. Access persists for the rest of this session.
Request for proposal (RFP) for Le Train.
This is a placeholder case study for Le Train. It demonstrates the long-form structure that will host the real request for proposal (rfp) for le train write-up. Pedro joined the team to lead ui, ux design and rfp across discovery, definition, and delivery — bridging product, engineering, and stakeholder expectations with a calm, evidence-led practice.
The work spanned research, ideation, prototyping, and hand-off. It is presented here as a representative example of the depth and rigour that the final case study will reflect.
The starting brief was deceptively simple. In practice, three forces pulled the product in opposite directions: legacy data structures inherited from older platforms, a roadmap shaped by quarterly OKRs, and a user base whose tolerance for friction was thinning by the week.
The team needed an honest baseline — what worked, what hurt, and what was politely tolerated — before any new screens were drawn.
I framed the engagement around three questions: Who is the workflow really serving? Where does it betray that user? And what would a confident, modern alternative feel like?
Answering them required quiet listening, structured benchmarking, and a willingness to challenge sacred cows — gently.
Stakeholder interviews, contextual inquiries with Le Train's actual users, heuristic audit, and competitive teardown. We surfaced 47 friction points and grouped them into 6 themes.
Reframed the problem with the product team using a North Star statement, JTBD prompts, and a measurable success rubric. Aligned four squads behind the same vocabulary in two workshops.
Sketched, wireframed, and prototyped at increasing fidelity. Tokenised the visual language against the existing design system and shipped a Figma library engineering could consume directly.
Paired with engineers through sprints, ran moderated tests on each release candidate, and instrumented the new flows so the team could see — not guess — what the product was doing in production.
Pedro's clarity gave us back our roadmap. The team finally agreed on what we were actually building. — Lead PM, Le Train
Six representative slots — wireframes, flows, design system specimens, prototypes — that will host the real screenshots once the case study is unlocked.
Placeholder metrics — illustrative only. The real KPIs will land here when the Le Train case study is published.
Every project leaves a list. For Le Train, the most valuable lesson was about cadence — shipping smaller, narrower releases would have surfaced edge cases six weeks earlier and bought the team a calmer launch window.
A second lesson was about evidence: investing in lightweight, always-on instrumentation paid back the effort within a single quarter. The full reflection — the wins, the regrets, the people — will appear here in the migrated case study.