Notes from strategy, product and technology.
Practical thinking from the work: architecture choices, performance, commerce, product decisions and what we learn while building.
11Strategy / Technology / Product / Performance / Commerce / Notes
When not to rebuild your website.
A rebuild is expensive. Sometimes the right answer is architecture work, content restructuring, performance remediation or a smaller product change.
Read note ↗Headless CMS without the hype
Where decoupling creates real value, and where it only creates another system to maintain.
Read note ↗Performance / 02Performance is a business constraint
Why critical-path speed belongs in product and commercial conversations, not only Lighthouse.
Read note ↗Product / 03When a design system pays for itself
A system is useful when it reduces decisions and drift, not when it becomes a second product.
Read note ↗Technology / 04Location data at product scale
Why spatial data changes architecture choices once maps become more than decoration.
Read note ↗Strategy / 05Technical SEO before content volume
Indexation, rendering and information architecture can invalidate a great content plan.
Read note ↗Commerce / 06Commerce beyond the storefront
The expensive complexity often sits behind checkout: catalogue, operations, payments and integrations.
Read note ↗