Category · 35 guides
Design & UX
UX audits, design sprints, design systems and accessible interfaces, explained for the people who buy design work and have to live with the result.
Designing a B2B site for a long sales cycle
In B2B, nobody buys on the first visit and nobody buys alone. Design for the researcher, the decision maker and the procurement check, and measure influence rather than form fills.
Brand colours that pass contrast checks
Most brand colours were chosen for a logo, not for body text. Here is how to build tints and shades around them so every text, button and background pair passes, without changing the brand.
Conversion-focused design: principles, not tricks
Pages convert when visitors understand the offer, trust it and can act without effort. Button colours are not the lever. Here are the principles that are.
Customer interviews that don't lead the witness
'Would you use this?' gets a polite yes and tells you nothing. Here is how to ask questions that reveal what customers actually do and need.
Dashboards people actually read
Most dashboards are opened once and ignored. The ones that get read start from a decision, show few numbers with context, and alert people instead of waiting to be looked at.
Design QA: check the build against the design
The design looked right in Figma. The build is almost right. Design QA is the routine that closes the gap before customers see it.
What happens in a five-day design sprint
Five days, one decision-maker, one prototype, five real users. Here is what each day is for, who has to be there and when a sprint is the wrong tool.
What does a design system cost?
A design system is priced by how much it covers and whether it ships as Figma only or as working code. Here is what each level includes and what it costs to keep alive.
Designing for older users
Older users do not need a simplified version of your site. They need the choices that make any site easier: readable text, fewer steps, familiar patterns and honest language.
Designing for WCAG 2.2 AA: a practical primer
Most accessibility failures are decided in the design file, long before code. Here are the criteria a designer controls and how to check them before handover.
Designing long forms and applications
Applications, onboarding and quote requests fail when they feel endless. Here is how to cut fields, split steps, save progress and write errors that help people finish.
Does your company need a design system?
The signs a design system will pay off, what it contains, the lighter options for smaller teams, who has to maintain it, and when it is simply too early.
Empty states, errors and loading screens
Designs show the happy path full of data. Users meet empty lists, errors and spinners first. Patterns for the screens that decide first impressions.
Figma handover developers can build from
Components before screens, the states nobody designs, tokens instead of magic numbers, annotations that answer questions before they are asked, and one meeting that saves weeks.
Figma, Penpot or Sketch for teams?
Figma dominates, Penpot is the open-source challenger you can host yourself and Sketch remains a Mac-native option. Here is how to choose based on your team, not the hype.
Choosing fonts for a Swedish brand
A font that looks great in an English mock-up can fail on Å, break a licence in the app, or send visitor IP addresses abroad. Check these four things first.
How to brief a designer
Most disappointing design work traces back to the brief. Here is a one-page structure that gives a designer what they need and gives you a fair way to judge the result.
Logo, visual identity or design system: which level do you need?
Three deliverables, three price levels, three very different jobs. Buy the one your stage needs now and make sure it grows into the next one.
Measuring UX: task success, time and drop-off
You do not need a research team to measure usability. Four simple measures show where users struggle and what fixing it is worth.
Microcopy: button and error text that helps
The texts that lose users are the smallest ones: a vague button, an error that blames, an empty screen with no next step. This guide rewrites them, in Swedish and English.
Rebrand checklist for your digital assets
A new logo is the easy part. The hard part is finding every place the old one still lives. A checklist from favicon to invoices and app stores.
Test a clickable prototype before paying for code
A week of prototype testing costs less than one wrong feature. Here is what a clickable prototype can prove, how realistic it must be, and how to read five test sessions honestly.
User testing with five people and no lab
You do not need a lab, a researcher or a budget line. You need five people who resemble your customers, a screen share and a list of tasks. Here is the whole recipe.
UX audit checklist
A UX audit is only worth paying for if it ends in a prioritised list of fixes tied to your goals. This checklist tells you what a proper review contains.
Not sure which package fits?
Book a free 15-minute call and we will match your needs to the right package — or tell you honestly if none of them fit.
Free · ~15 minutes · No obligation