Practice — Hot · The Rollout Memo
Skills focus. Deployment architecture under real constraints — including two
requests that should be pushed back on.
Ungraded, open-ended. The deliverable is the memo.
Scenario
Lantern & Pine's leadership approves the report for company-wide rollout, with this requirements list from various stakeholders:
| # | Request |
|---|---|
| 1 | All 500 HQ and store staff can view; the 6 regional managers see only their regions |
| 2 | Data refreshes nightly from the ERP's export folder on the HQ file server |
| 3 | The three analysts keep building new pages weekly |
| 4 | "Send everyone the file so they always have a copy that works offline" (the COO) |
| 5 | "Give all the store managers edit access so they can fix things they spot" (the VP of Stores) |
Requirements
- Architect requests 1–3: workspace roles, distribution mechanism, RLS design (static or dynamic — with 6 managers, argue your choice), and the refresh path (name the component request 2 requires and why).
- Push back on 4 and 5 — professionally. For each: what the request actually costs (be specific about which guarantees break), and the alternative that serves the underlying need (offline access has real answers; so does "managers spot errors").
- Write the memo — under 250 words, to leadership, covering the architecture and both pushbacks. The COO and VP read it; write like they will.
Reflection
- Request 4's underlying need is legitimate. What is it, and what actually serves it?
- Six managers sits near the static/dynamic RLS boundary. What tips your choice, and what future fact would flip it?