MARRIOTT
Through Giggr, I mapped business processes for Marriott’s future platform, challenged the staffing assumptions behind its India expansion and created CodeFest.
Delivered- Role
- Engagement lead through Giggr
- Duration
- Feb 2023 – Aug 2024
- Team
- Giggr and Marriott teams
- Status
- Delivered
Start with the work behind the headcount
The workforce proposal called for growing Marriott’s team from 35 to 500 in five years without explaining how it arrived at those numbers. I challenged that assumption and surveyed nine technology tower leads to find out what Marriott needed to build in India. Their input gave us a way to discuss capability, location and operating requirements before committing to a hiring plan. I led vendor qualification through the selection of ANSR and the choice of Hyderabad.
My engagement record documents my role and the accelerator’s planned 3,000-seat capacity. ANSR publicly confirmed its role and Marriott’s choice of Hyderabad. Marriott announced the opening in October 2025, after the Giggr engagement ended.
Put the architecture up for review
I led the mapping of nine end-to-end processes across Commerce, Hotel Operations, Loyalty and Finance. We modelled them in Signavio at four levels across eight experience segments. That let reviewers trace a business step to the role, interface or event behind it, including where booking and order orchestration, the GraphQL experience layer and the Kafka event hub came into play. Subject-matter, architecture and engineering reviewers took the models through segment sign-off.
Give prototypes somewhere to go
I created and led CodeFest, which ran for three editions. Each team had to bring a hypothesis, a working prototype and a place for it on Marriott’s architecture map. That last requirement made a pitch answer a practical question: where would someone use this? I designed weighted judging, score normalization and written feedback. The first edition drew 110+ associates across 32 teams.
The billed Giggr engagement ran from February 2023 to August 2024 and covered approximately 3,100 hours.
The record
What the evidence says.
- Approximate billed hours across the engagement
- 3,100
- Professional profile billing record
- Future-state processes mapped through four levels
- 9 × 4
- BPMN 2.0 in Signavio
- Planned seats at the Hyderabad Technology Accelerator
- 3,000
- Professional profile engagement record
- Teams in CodeFest 01
- 32
- 110+ associates, May 2023
The system
Trace the process.
Choose a layer to see how the engagement connected business processes to the technology that supports them.
L0 / Technology layer
Governance and access
Defines the roles that take part in a process and the actions each role can perform.
- Business roles
- Access decisions
L1 / Technology layer
User experience
Maps the points where a person uses an interface to carry out the process.
- User journeys
- Channel interfaces
L2 / Technology layer
Systems and adapters
Identifies the systems that receive those actions and the adapters that connect them.
- Systems of engagement
- Domain adapters
L3 / Technology layer
Workflow
Shows how the work is coordinated and where the flow branches or hands over.
- Process steps
- Handoffs
L4 / Technology layer
Events
A Kafka hub listens, interprets and publishes events for normal, alternate and exceptional flows.
- Normal and alternate flows
- Exception events
L5 / Technology layer
Data
Traces master, operational, analytical and intelligent data through the architecture.
- Operational data
- Lakes and warehouses
Schematic of the six architecture layers described in the engagement record.
Marriott / Workflow
How the workforce plan reached a location decision
- Question the ramp
The workforce RFP proposed five years of headcount growth without a stated basis.
- Gather requirements
Survey nine technology tower leads and frame the decision around capabilities, location and operating needs.
- Qualify vendors
Lead provider evaluation through Marriott’s selection of ANSR and Hyderabad.
Worked explanationFollow the location decision
- Input
- A proposed five-year headcount ramp has no stated basis.
- Decision / rule
- Input from nine technology tower leads defines capability and operating needs for provider and location evaluation.
- Outcome
- Marriott selects ANSR and Hyderabad after the qualification work.
Scope of this exampleThis is one workstream in the Giggr engagement. The accelerator opened after that engagement ended.
Working through a similar decision?
Talk to me about your project