Website project retrospective: product-site information architecture (around fifty employees)

Context: This write-up is for colleagues progressing website and CMS work. The client is in restaurant chains, roughly two hundred+ staff, based around the Middle East. Editors know the CMS well enough, but corporate website redesign still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Background & Goals

Last week we reviewed multilingual website build 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 multilingual website build. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed company website development 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 company website development first. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling. Last week we reviewed role-based access control with the client's IT lead. They care more about stability than buzzwords. We hit a case of payment succeeded but orders still pending. Troubleshooting started with logs on Redis, then followed our reproduction steps. Next, we recommend to compare staging vs production configuration diffs. If more features are added, scope the blast radius before scheduling.

Testing & Acceptance

Last week we reviewed search indexing diagnostics 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 search indexing diagnostics. 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 electronic components, 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 site performance optimization first. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Delivery Approach

This write-up is for colleagues progressing website and CMS work. The client is in home & building materials, roughly a hundred-person team, based around free-trade zones. Editors know the CMS well enough, but site performance optimization still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions. This write-up is for colleagues progressing website and CMS work. The client is in construction, roughly a hundred-person team, based around county-level cities. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to multilingual website build first. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling. The same requirement can sound different across departments; writing it down helps align decisions on CMS publishing workflow. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to CMS publishing workflow first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Operations & Collaboration

Last week we reviewed CMS publishing workflow 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 CMS publishing workflow first. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed channel & URL planning 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 channel & URL planning first. Archive screenshots and config change IDs for this channel & URL planning round so next month's retrospective stays concrete.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on CMS publishing workflow. We hit a case of legacy outbound links broken. Troubleshooting started with logs on CDN, then followed our reproduction steps. Archive screenshots and config change IDs for this CMS publishing workflow round so next month's retrospective stays concrete.