Org Design and Goal Meeting
Summary meeting 18 July 2016:
- definition of product/platform/service eng is working, high cohesiveness and low coupling.
- sub-team design can be further optimized.
- optimal sub-teams HLM (the goal is to acquire inventory, and help MM or Hotel to grow our revenue), HCM (the goal is to get and manage our hotel data effecticely)
- ARI will be combined with rateplan and promotion. This includes on allotment and rate calculation operation.
- Inventory and fulfillment will be separated into 2, inventory operation (search, book, issue, reschedule, cancel), and finance operation (payment).
- internal tools team has 2 definition internal tools for travelokan users and admin.
- microservice architecture: ARI (including RP and promotion), Finance ops, Inventory Ops, CM (public API), HNET frontend, data(???), Provider -->local (???).
Summary meeting 22 July 2016:
- Value Creation of TERA https://docs.google.com/spreadsheets/d/1-dL1l29inJ9HzFGggSor2lXYaoer7V8QOLQ7GaVI4KY/edit#gid=0
- Internal tools definition:
- Internal Traveloka (fin, ops, MM)
- Internal TERA (PD/PM/Eng)
- Mix between internal TVLK and TERA –->depends on usage volume of user
- Microservice defintion –> Autonomous, General, Single Purpose
- When to handover supply innovation initiative to each sub-team?
- Initiative has met success metrics and/or product market-fit
- Incremental Improvement (no major innovation or major unknown)
Next steps:
- revised org design, and align with microservice (all)
- define tera goal (all) - Revenue ID =>2X, Trx Intl >=10X
- define tera sub-team goal (all)