Palace Hotels (18 properties, ~15,000 employees) restructured its technology org into durable teams organized by business vertical — sales operations, vacation club, HR, hotel operations, etc. — rather than by project or technical layer. Each team permanently owns the maintainability, security, and quality of its software, so ownership never reverts to a central "keep the lights on" pool once a project ships.
Staffing ratio: roughly 1 PM : 1 tech lead : 1 designer per team, or one designer shared across two teams when design capacity is scarce.
This differs from Org-Architecture Mirroring (Squads ↔ Microservices), which mirrors org structure to microservices architecture along technical seams — here the axis of division is the business vertical served, not a technical boundary. It's the org-level container that Product Trios sit inside, and durable ownership is what makes Outcome-Based Roadmap Reframing sustainable: a team that owns a vertical for years has both the incentive and the context to be measured on outcomes rather than one-off delivery.
Palace Hotels organized product/design/engineering into standing teams aligned to business verticals — sales operations, vacation club, hotel operations, and others — each permanently owning its software's maintainability, security, and quality rather than being dispersed after a project ships. This is the structural opposite of the Software Factory Delivery Model pattern, where a delivery team scatters once Jira marks work 'done.' The CPTO's line "I hired a team that allows me to be bold" frames durable ownership as what created the psychological safety for the org to take bigger bets, tying team topology directly to risk appetite rather than treating it as a pure org-chart concern.
Из тем: Transformation in Practice