ArticleDesign systems7 min read
Do you need a design system or just well-defined components?
Not every product needs a complete design system. Sometimes a small component library and clear rules solve the problem faster and require less maintenance.
Insights
Building or reworking a website? Find explanations of budget, content, platforms and editing, so you know what to ask and where to focus. I also write about UX and digital products, drawing on problems encountered in projects.
ArticleWebsites and delivery8 min read
When to repair a website and when to rebuild it
Not every problem requires a new website. Assessing content, technology and the cost of change shows whether repair or rebuilding makes sense.
ArticleDesign systems6 min read
What is a design system? A jargon-free explanation
A design system is the shared set of decisions, components and rules that helps teams build consistent experiences without solving the same problem repeatedly.
ArticleWebsites and delivery8 min read
What you actually pay for when building a new website
A website price covers more than its visible pages. It includes decisions, content, design, implementation, verification and the system's ability to remain useful after launch.
ArticleWebsites and delivery9 min read
What to clarify before requesting a website proposal
A comparable proposal needs context: objectives, content, functionality, responsibilities, integrations and acceptance criteria.
ArticleIndustry and collaboration8 min read
How to choose between a freelancer, an agency and an internal team
You are not choosing only a price or a number of people. You are choosing the continuity, coordination, specialisation and accountability the project needs.
ArticleSEO and AI8 min read
How I use AI without sacrificing verification and quality
AI can accelerate exploration and execution, but its output becomes trustworthy only when sources, decisions and final behaviour are explicitly verified.
ArticleWebsites and delivery8 min read
How to prepare content without blocking the project
Content prepared early reduces assumptions, rework and delays. It need not be perfect, but it must be complete, structured and owned.
ArticleProducts and UX9 min read
How to prioritise features without building everything
Prioritisation is not an arbitrary choice about what to cut. It identifies the smallest version that creates value and reduces an important uncertainty.
ArticleProducts and UX8 min read
How to recognise requirements that make a product unnecessarily complex
Some requirements address a real case, while others turn assumptions and rare exceptions into a permanent cost for users and the team.
ArticleDesign systems8 min read
How a design system reduces development costs
A design system reduces costs when it removes repeated decisions, prevents accidental variants and gives teams tested components they can change in a controlled way.
ArticleWebsites and delivery7 min read
How to reduce the cost of future changes
The cheapest changes are anticipated through structure, components, clear content and genuine ownership of the system.
ArticleWebsites and delivery7 min read
Why you should be able to update your website without a developer
A developer should solve development problems, not be the only person able to correct a sentence, replace an image or publish a service.
ArticleWebsites and delivery7 min read
Why every page should have one objective
A page can contain several pieces of information and actions, but it needs one priority to organise the message and reduce competing decisions.
ArticleIndustry and processes9 min read
Why rapid code generation does not remove the need for good architecture
When code can be produced faster, decisions about boundaries, data, dependencies and change become more important, not less important.
ArticleWebsites and delivery7 min read
Why maintenance should not mean paying for every change
Healthy maintenance keeps the system secure and functional. Routine editorial updates should largely remain under the team's control.
ArticleWebsites and delivery8 min read
Why a simple website change can take weeks
A small change is not always a small task. I explain where time is lost, when the cost is justified and how to build a system that remains easy to change.
ArticleProducts and UX8 min read
Why a visual redesign does not always solve the problem
A new interface can improve perception, but it does not automatically repair unclear content, broken processes or technical product constraints.
ArticleWebsites and delivery8 min read
Why a cheap website can become the most expensive option
The initial price is only part of the cost. Rework, supplier dependency and missed opportunities can turn early savings into a major expense.
ArticleProducts and UX7 min read
Designer, developer or product designer: who do you need?
The roles overlap, but they are not interchangeable. The right choice starts with the problem you need to solve, not the title on a profile.
ArticleProducts and UX8 min read
Before design: what problem should the product solve?
A useful brief starts not with screens or features, but with the situation we want to change and the people for whom it matters.
ArticleWebsites and delivery7 min read
Your website should not be rebuilt every time the business changes
A healthy website can absorb new services, markets and messages without turning every business change into a new technical project.
ArticleProducts and UX7 min read
A beautiful website is not automatically a good website
Visual appeal can attract attention, but a good website must explain, build trust and help people take the next step.