Website project retrospective: image weight control (two hundred+ staff)

Context: Last week we reviewed role-based access control with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to role-based access control first. Next, we recommend to compare staging vs production configuration diffs. If more features are added, scope the blast radius before scheduling.

Testing & Acceptance

This write-up is for colleagues progressing website and CMS work. The client is in cross-border trade, roughly a multi-division group, based around historic downtown districts. QA walked the main path three times on real devices and flagged edge cases around static asset caching. Next, we recommend to log API status codes and latency. If more features are added, scope the blast radius before scheduling. Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but search indexing diagnostics still needs a one-page rule sheet to cut verbal rework. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed corporate website redesign with the client's IT lead. They care more about stability than buzzwords. We hit a case of CMS image uploads over-compressed. Troubleshooting started with logs on Postman, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Risks & Mitigations

Last week we reviewed site performance optimization with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to site performance optimization first. Archive screenshots and config change IDs for this site performance optimization round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on basic accessibility. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on enterprise chat, then followed our reproduction steps. Archive screenshots and config change IDs for this basic accessibility round so next month's retrospective stays concrete.

Operations & Collaboration

The same requirement can sound different across departments; writing it down helps align decisions on role-based access control. We hit a case of CMS image uploads over-compressed. Troubleshooting started with logs on Git, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. This write-up is for colleagues progressing website and CMS work. The client is in legal services, roughly about thirty people, based around the Middle East. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to role-based access control first. Next, we recommend to log API status codes and latency. If more features are added, scope the blast radius before scheduling. Last week we reviewed basic accessibility with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around basic accessibility. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Takeaways: Last week we reviewed static asset caching with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around static asset caching. Add a field dictionary to the docs so new joiners ask fewer repeat questions.