Level of details in communication (to know when should communicate at high level/low level)
Expectation management
Tasks
{{renderer :todomaster}}
DONE Feedback Weekathon Project: [[Weekathon 2025]] Priority: #P2
DONE Write 1on1 note - Nov 2025
Project: [[Internal]] Priority: #P2
Support presales
- Superbexperience
- Dynamic filtering
- Performance issue
- Mindstorm
- Optimization, deal won
- Add2Cart
- Bad: detail-level communication when updating progress at high-level
- Superbexperience
Onboarding calls
- Trust Wallet
- MOK
- Clarity Pediatrics
- Add2Cart
Weekathon
- ((69267795-5e44-4b4a-9f5f-926299cdc2dc))
((69136bc9-af13-42eb-b4cb-799bb647677e))
Question: ICEYE-EU case
DONE Document the change request for the Shopee use case
Project: [[Add2Cart]] Priority: #P1
- What we have:
- Mental model: 4P Business Model logseq.order-list-type:: number
- In the data layer, we store most of the tables under a redshift schema. Except one table: PRICE_HISTORY is stored as a S3 bucket. The reason is this table can be exponential increase the volume very fast due to its grain: retailer x product x date
- This S3 bucket will then be exposed back to redshift as an external table via AWS Spectrum
- Complete and call a Huy
- Draft the message to Simon and send a Huy
- What we have:
DONE Meet 1on1 with a Triet
Project: [[Internal]] Priority: #P1
DONE Teach Duc Anh
/ 2025-11-26
Created Wed, 26 Nov 2025 00:00:00 +0000
Modified Mon, 25 May 2026 06:02:25 +0000