Context
StayNTouch is a cloud-based PMS used by hotels for daily front-desk operations. Over time the system had accumulated technical debt that was slowing development and showing up in the workflows staff relied on most.
Problem
Engineering was spending more time fixing things than building. On the other side of the same modules, front-desk staff were running into friction in everyday flows like check-in and room management.
Key Insight
Tech debt and the user-experience issues weren't separate problems. The same legacy modules that were slowing the team down were also the ones causing pain at the front desk.
Solutions
- Bundled refactors with feature work so debt got paid down on the same modules users touched.
- Prioritised the highest-frequency workflows, starting with front-desk operations.
- Added lightweight discovery to make sure the problem was clear before scoping a fix.
- Tightened the loop between product, design, and engineering so trade-offs were visible early.
Trade-offs
We slowed short-term feature output to invest in foundations, and stepped back from chasing parity with competitors so core reliability could improve first.
Impact
Over two quarters, release cadence improved meaningfully, regressions on touched modules dropped, and feedback from front-desk staff indicated daily workflows felt better.