On this page
Field notes from Shriram IT Ventures delivery work on Travel: Data Model Guide: the constraints that matter, the shortcuts that haunt you, and a checklist we still use.
Who this is for
Ship a thin vertical slice, measure, then widen. Big-bang rewrites rarely survive the first month of real traffic.
Decisions that still look smart in 18 months
Ship a thin vertical slice, measure, then widen. Big-bang rewrites rarely survive the first month of real traffic.
Build checklist we actually use
Ignore the buzzwords. For Travel: Data Model Guide, the hard constraint is usually data ownership or ops capacity — not how many features fit on a roadmap slide.
Failure modes we keep seeing
Use boring technology where the risk is operational. Save novelty for the one wedge that makes the product worth buying.
How we measure rollout
Teams that write trade-offs down before coding burn fewer sprints when a stakeholder changes their mind mid-build. We keep ADRs short on purpose.
We update this when delivery patterns change on live client work.