Blog
Notes from the studio.
Practical answers for restaurant operators and teams making website, brand, and growth decisions.
- What should a restaurant website include?Menus, reservations, ordering, hours, location details, and the complete path from discovery to a real guest action.
- How should a restaurant menu work on mobile?Readable HTML, familiar categories, current prices, clear dietary details, and direct actions that do not cover the menu.
- How long a rebrand actually takesSix to eight weeks for the identity. Longer if approvals are slow. Here is where the time goes.
- What a design project actually costsNobody likes publishing prices. Here is what the work costs and what moves the number.
- Naming a company without hating it laterMost naming advice is about being clever. The hard parts are legal and practical.
- How to write a design briefA good brief fits on one page. Here is what belongs on it.
- Why your website is slowIt is almost always images and fonts. Here is how to check, and what to do about it.
- Why good interface work starts as an argumentBefore we draw anything, we write down what a screen is for. It sounds slow. It saves months.
- What a design system is, in plain wordsNot a style guide. Not a folder of files. Here is the actual thing.
- Identity systems that survive contact with product teamsBrand books die in downloads folders. Here is what to hand over instead.
- The website is not the deliverableLaunch day feels like the end. It is closer to the start.
- Questions worth asking a design studioPortfolios all look good. These questions tell you more.
- Signs you need a rebrand, and signs you do notBeing bored of your logo is not a reason. Here are the reasons that are.
- Positioning is a subtraction exerciseThe hard part is not finding what to say. It is agreeing what to stop saying.
- Why we stayed at nine peopleGrowing was the default. Staying small was the decision.
- Accessibility is not a checklistPassing an audit and being usable are two different things. Here is the gap.
- How to give design feedback that helpsSay what is wrong, not how to fix it. That one change makes feedback far more useful.