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 logistics & warehousing, roughly a hundred-person team, based around coastal tech hubs. QA walked the main path three times on real devices and flagged edge cases around inquiry form conversion path. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Testing & Acceptance

The same requirement can sound different across departments; writing it down helps align decisions on inquiry form conversion path. We hit a case of mini program review rejected. Troubleshooting started with logs on CDN, then followed our reproduction steps. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling. Last week we reviewed channel & URL planning 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 enterprise chat, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Operations & Collaboration

The same requirement can sound different across departments; writing it down helps align decisions on company website development. QA walked the main path three times on real devices and flagged edge cases around company website development. Archive screenshots and config change IDs for this company website development round so next month's retrospective stays concrete. This write-up is for colleagues progressing website and CMS work. The client is in media & creative, roughly a multi-division group, based around free-trade zones. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to site performance optimization first. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling.

Risks & Mitigations

Last week we reviewed channel & URL planning with the client's IT lead. They care more about stability than buzzwords. We hit a case of holiday traffic spikes slowing the site. Troubleshooting started with logs on object storage, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions. The same requirement can sound different across departments; writing it down helps align decisions on channel & URL planning. QA walked the main path three times on real devices and flagged edge cases around channel & URL planning. 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 company website development with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but company website development still needs a one-page rule sheet to cut verbal rework. Next, we recommend to lazy-load homepage assets by route. If more features are added, scope the blast radius before scheduling.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on mobile responsiveness. QA walked the main path three times on real devices and flagged edge cases around mobile responsiveness. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling.