Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
159530 stories
·
33 followers

Brand Guidelines Are Ruining Your Website

1 Share

Why print-first brand systems break online, and how to push back without demanding a full rebrand.

I've been grumbling about this one for years, because although almost everyone now meets a brand through a screen, we're still handed identities designed for brochures, business cards, and the occasional exhibition stand, and then told to make the website behave itself. So this month I have a proper rant about it and Marcus does his best to talk me down, which he largely manages. We also get into top task analysis, which is one of my favorite research techniques, and the free app I've built because I got fed up running it the hard way.

App of the Week

Top Task Analysis is a free app I've built to make top task analysis considerably less painful, mainly because I'd spent years running it with a spreadsheet, a survey tool, and a fair amount of swearing.

How top task analysis works

Top task analysis is a technique Gerry McGovern came up with, and it works a bit like a survey except that it stops people from being greedy, because an ordinary survey hands you a long list of everything your users say they'd quite like and no sense whatsoever of what they'd actually walk over hot coals for. This forces them to prioritize, so you end up knowing which small handful of things the majority genuinely care about. Gerry's classic example is the Microsoft Office knowledge base that kept answering more and more questions and kept watching its satisfaction score slide, because the answers people actually needed were buried under a hundred they didn't.

I use it for all sorts, from shaping information architecture and working out which objections are worth answering, through to prioritizing features and deciding what has earned its place on a dashboard. Roughly 80% of your users want about 20% of what's on your site, and this is how you find the 20%.

What the app does

The reason nobody runs it as often as they should is that it needs at least 2 rounds, one to gather the tasks and another to vote on them, so the app handles both in a single pass. You seed it with a starter list from AI, from the client, or from whichever stakeholder shouts loudest, and it genuinely doesn't matter if that list is a bit rubbish, because visitors can search it, pick the 5 tasks that matter most to them, and add anything that's missing, which then appears for everyone who arrives after them. A second screen asks them to put their 5 in order, and the back end lets you see the lot, merge the 14 different ways people phrase the same task, and tidy up anything unhelpful. And yes, there's a profanity filter, because I have met the internet before.

Marcus made the good point that you want a segmentation question alongside it so you can see top tasks broken down by audience, which is already in there, and he also dug up a hospital trust site we worked on years back where we dropped the top 8 tasks straight under the main navigation. They're still sitting there 8 years later, which either says something flattering about the technique or something less flattering about how often that site gets touched.

Give it a go

It's free, because I did think about charging for it and then couldn't be arsed, which is not the sharpest business decision I've ever made. Have a play and tell me what's broken.

  • The app: Top Task Analysis
  • The step-by-step guide: Top Task Analysis: A Free App And Step-by-Step Guide
  • Feedback: paul@boagworld.com

When brand guidelines fight the web

Most people meet a brand through a screen these days, and yet the web is still treated as the place where you paste in whatever was designed for print. A branding agency mocks up a homepage that has never met a real sentence, the guidelines get signed off after 18 months and roughly all of somebody's political capital, and then some poor soul is handed the job of protecting it, at which point they'll defend an unreadable contrast ratio to the death because it's sitting on page 47 of the PDF. Consistency matters and I'm not arguing otherwise, but being consistently difficult to read isn't much of an achievement.

Marcus agreed with the general complaint and pointed out that Headscape has described itself as a brand interpreter for digital for something like 15 years now, for exactly this reason. He also told the story of a charity working with deafblind people whose shiny new sub-brand logo failed color contrast checks, and if I'd invented that example nobody would have believed me.

A brand should serve the organization and its audience, so the moment its rules make the website harder to use, those rules need to change.

What a brand actually is

A lot of the confusion comes from shrinking brand down to a logo, some colors, a typeface, and a photography style, when all of that is really just the clothes the organization turns up in. The brand itself is closer to a personality, made up of what the organization believes, how it talks, and how it treats people when nobody important is watching, and your copy and your customer service will say far more about that personality than a logo ever manages. Which means we have considerably more room to move online than the brand police like to let on.

Why print-first branding breaks online

Print gives a designer a beautifully controlled environment and the web gives them almost none of it, which is where most of the trouble starts. Somebody working on a poster knows the exact dimensions, the exact paper, and the exact ink, whereas online you're designing for a canvas you can't see, on screens that run from a cracked phone in bright sunlight to a 32 inch monitor with the brightness turned up to painful, at whatever zoom level somebody's eyesight demands that day. Pantone certainty becomes display roulette, where pale colors wash out, dark colors go muddy, and the elegant light gray text you signed off on a calibrated screen simply vanishes on a cheap laptop in a train carriage.

A poster sits still and a website refuses to

Then there's the small matter that a poster sits still and a website refuses to. Websites need hover states, focus indicators, error messages, forms, navigation that collapses gracefully, and buttons that look like buttons, and most traditional guidelines have nothing at all to say about any of it, because it never occurred to anyone in the room that it might come up. Add a few thousand combinations of real content, German translations that run half as long again, and pages that grow arms and legs over 3 years, and the handful of polished examples in the brand book stops being much use to anybody.

The familiar symptoms

The same problems keep turning up, and once you've noticed them you can't stop seeing them. There are the walls of capital letters that slow reading to a crawl, the brand color pairings with contrast so poor you can fail them by squinting, the decorative typefaces that turn to mush at small sizes, and the logos that only really work when they're the size of a bus, although responsive logos that simplify as they shrink are a lovely solution whenever anyone can be bothered to make one.

The typographic hierarchy problem

The one that genuinely baffles me, and I've run into it twice in recent months, is a brand book from an actual branding agency with no meaningful typographic hierarchy in it at all, as though headings were a passing fad we'd all agreed to ignore. Then come the layouts that can't cope with content nobody wrote in advance, the complete silence on containers and components, and the fact that there's frequently no contrasting color available for a call to action, because heaven forbid anybody should click on anything.

Where the cost lands

Any one of those on its own looks like a small compromise you can live with, but stack them up and the brand starts shoving people away from the website it was supposed to make them love. The cost lands on accessibility, on comprehension, on conversion, on trust, and eventually on the confidence of the designers themselves, who stop challenging the daft rules and start ignoring them when nobody's looking, which is how you end up with 9 versions of the brand in the wild and not one of them right.

What the attention test showed

I recently tested a brand-compliant homepage against a more flexible treatment using an AI attention prediction tool. The looser version came back with roughly 20% higher predicted clarity and focus, and predicted attention on the main call to action went up by more than 80%. These are modeled predictions rather than real conversion data, so please don't quote them as gospel, but they do give stakeholders something more interesting to argue about than personal taste. I was insufferable for the rest of the day.

Where Marcus and I disagree

I made the case for a digital-first approach, where you start with the personality and the principles rather than the letterhead, get UX, accessibility, content, and frontend people into the room while the decisions are still being made, design actual interface elements instead of stationery, and use the website as the place where the brand gets proven with real content on a small screen before it ever reaches print.

Marcus' counterargument

Marcus has tried that more than once and reckons it falls apart in practice, because running the digital interpretation alongside or ahead of the main branding project leaves nobody clearly in charge, and Headscape's opinion carries very little weight while the brand itself is still up in the air. He'd rather let the branding agency finish and get everything signed off, then arrive afterward with the client already warned that interpreting it for digital will mean changes, the typeface being the almost inevitable first casualty. He also pointed out that very few branding agencies build anything, which is a fair argument for keeping the two jobs apart.

Where we landed

I came round to that as the more practical position, with one condition attached, which is that whatever gets handed over has to be understood as a starting point for digital rather than a finished artifact that must never be questioned by anyone with a browser.

Consistency, not uniformity

The phrase I keep coming back to came from Neil Eastell at the National Trust years ago, and it's consistency, not uniformity. A brand system that works online is one that's clear about what has to stay fixed and honest about what's allowed to bend, so the logo keeps its essential form while picking up responsive versions, the core colors stay recognizable while gaining accessible digital variants, and the typographic personality survives a change of body typeface for the sake of download size or legibility, as long as nobody wanders off from a serif to a sans serif and hopes we won't spot it. Think of it as a jazz standard rather than a military march, where everyone is playing the same tune but there's room to improvise around it.

Questions worth asking

  • Which parts of this identity genuinely express the personality, and which are just habits nobody has questioned?
  • Was this rule written for screens, or copied across from print because it was already sitting in the document?
  • What user or business outcome does it protect, if any?
  • Does it still hold up on a small phone, at 200% zoom, in bright sunlight?
  • What does that logo honestly look like as a favicon?
  • How are you getting feedback on the brand from users rather than only from the board?
  • When brand compliance and readability disagree, which one wins, and who gets to decide?

The practical takeaway

Whatever you do, don't open with a demand for a rebrand, because that conversation is over before it starts and you'll be the difficult one for the rest of the project. Find the specific places where the brand rules and basic usability are openly at war, fix the ones doing the most damage, measure what changes, and use that evidence to earn permission for the bigger conversation later on. And when you hit a wall, offer to test the brand-safe version against a looser one and let the numbers do the arguing for you, because a brand guardian will happily fight your opinion all afternoon but they'll rarely take on their own users.

A brand exists to build recognition and trust, so when protecting the rules starts eating away at both, we're guarding the wrong thing entirely. Or, to put it the way I put it on the show, be a bit more flexible about your bloody brand guidelines.

And because Marcus got his plug in twice, here is Headscape.

Marcus' Joke

When a TV antenna married another TV antenna, the service wasn't great, but the reception was amazing!

Marcus fluffed the delivery, which if anything improved it.

Find The Latest Show Notes





Download audio: https://cdn.simplecast.com/media/audio/transcoded/eea3ff50-d316-4ff7-b8db-24c157eb37ff/ae88e41b-a26d-4404-8e81-f97bca80d60d/episodes/audio/group/bd754d64-e6e9-4c74-a461-a85ac412892d/group-item/55840531-f4db-427d-b95a-6ea7fdf75e10/128_default_tc.mp3?aid=rss_feed&feed=XJ3MbVN3
Read the whole story
alvinashcraft
just a second ago
reply
Pennsylvania, USA
Share this story
Delete

The Distributed Agile Team That Hid Problems Behind Follow-Up Stories | Joshua McDonald

1 Share

Joshua McDonald: The Distributed Agile Team That Hid Problems Behind Follow-Up Stories

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

 

"They started to separate and call each other out, which is definitely not Agile." - Joshua McDonald

 

Joshua shares the story of a 17-person distributed team spread across time zones, cultures, and communication styles. Some team members were direct and ready to challenge problems in public. Others preferred quieter, one-on-one conversations. Over time, those differences created a blame environment where people stopped asking for help and started hiding problems. Long-running work was closed and replaced with follow-up stories, then part two, then part three, until the real issue disappeared under Jira housekeeping. The result was not better flow, but delayed learning, missed upskilling opportunities, and a stressful team environment where quieter people stopped speaking in standups and retrospectives. Joshua explains what he would do differently now: split the team by communication patterns, listen to what each group needs, act as a mediator, and only bring the whole group together once people feel heard.

 

In this segment, we talk about different communication styles.

 

Self-reflection Question: What signals tell you that people are hiding problems because the team environment does not feel safe enough?

Featured Book of the Week: Never Eat Alone by Keith Ferrazzi

Joshua recommends Never Eat Alone by Keith Ferrazzi because it reframed networking as a relationship practice, not a transaction. The book helped him see that staying connected with people creates learning, support, and a safety net over time. He also mentions the Bible as a daily source for reflecting on respect, peace, and conflict resolution, especially because Scrum Masters often need more than process knowledge to help teams work well together. For Joshua, both recommendations point to the same deeper idea: our work improves when we treat relationships as something to maintain before we urgently need them.

 

[The Scrum Master Toolbox Podcast Recommends]

🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥

Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.

 

🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

 

Buy Now on Amazon

 

[The Scrum Master Toolbox Podcast Recommends]

 

About Joshua McDonald

 

Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he's already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.

 

You can link with Joshua McDonald on LinkedIn.





Download audio: https://traffic.libsyn.com/secure/scrummastertoolbox/20260818_Joshua_McDonald_Tue.mp3?dest-id=246429
Read the whole story
alvinashcraft
just a second ago
reply
Pennsylvania, USA
Share this story
Delete

Web Weekly #198

1 Share

Guten Tag! Guten Tag! 👋

Have you heard of the new Git history commands? Are you overwhelmed by Chrome's performance profiler? And do you use the inert attribute in your sites?

Turn on the Web Weekly tune and find some answers below. Enjoy!

::: song by="Paul" title="Wet Leg — Tiny Desk Concert" youtube="AzUHNjKMeV4" I recently learned about the band Wet Leg when I saw them perform on NPR's Tiny Desk on YouTube. Their album moisturizer has been on repeat often since then. :::

Do you want to share your favorite song with the Web Weekly community? Hit reply; there are three more songs left in the queue.


I've been cleaning up some tabs the last couple of days and even though I'm no font person, here are some fonts that might come in handy in the future.

The charts below some controls. One bar chart, a sparkline and a pie chart.

Datatype is a variable font that turns text into charts. 🤯 I've got no idea how this works technically, but it can definitely be useful for inline graphics or sparklines. Disclaimer: be aware of accessibility issues. You should probably go with a role="img" and span combination when using it.

Squiggly lines that look like a paragraph and a heading.

Redacted Script is a font that looks like hand-written placeholder text. I'd love to see a skeleton placeholder with it. 😅

Some black blocks on white.

And if that's too fancy, Flow Block does the same but without the handwriting.

Maybe I should sit down one day to understand how all this font magic works...


If you enjoy Web Weekly, share it with your friends and family.

A quick "repost" really helps this indie newsletter out. Thank you! ❤️

Web Weekly Housekeeping

This week's bag of karma points goes to Nadja and Charles!

This week's summer bag of karma points goes to Nadja and Charles, who started to support Web Weekly financially. This brings the supporter count to the amazing number of 56.

After subtracting the cost of sending and hosting, Web Weekly now makes around $160 per month. Thank you all for supporting this newsletter! ❤️

If you enjoy Web Weekly, give back with a small monthly donation on Patreon or GitHub Sponsors. It really makes a difference in these hard times of AI slop and low-effort web creation.

Something that made me smile this week

Firefox in WebAssembly

There's nothing to see here, it's just a browser running in your browser.

<a class="btn btn__small" href="https://developer.puter.com/labs/firefox-wasm/">Spin up Firefox</a>

No code

The "No code" section turned out to be rather technical this week. 🫣 If you have good articles outside of the tech bubble, shoot them my way!

The experimental git history command

$ git history fixup ghi9012

Git ships a new history command that makes it easier to change and fix commits. If you dislike interactive rebasing, you'll really like this one.

<a class="btn btn__small" href="https://lalitm.com/post/git-history/">Change history</a>

Element states in JavaScript and (!) CSS

element.addEventListener("focus", (event) => {   if (event.target.matches(":focus-visible")) {     /* Do something */   } });

I really liked this one. Daniel put CSS states (:focus-visible, :popover-open, :fullscreen etc) next to possible JavaScript implementations. He also went into the fairly new event-trigger CSS props and that's some fancy stuff!

<a class="btn btn__small" href="https://css-tricks.com/css-states-and-javascript-events/">Tailor to state</a>

New in Edge: network efficiency guardrails

Document-Policy: network-efficiency-guardrails; report-to=neg-endpoint Reporting-Endpoints: neg-endpoint="/neg-reporting/"

I dig this a lot! Edge now ships an experimental feature that warns you about and monitors network activity that isn't optimized, like uncompressed assets or large images.

<a class="btn btn__small" href="https://www.debugbear.com/blog/network-efficiency-guardrails">Stay fast</a>

Understand the performance profile

A profile network waterfall.

If you're intimidated by the Chrome DevTools performance tool, you'll dig this one. Joan put together a nice explainer about all the details you need to know!

<a class="btn btn__small" href="https://perf.reviews/profile-guide">Get into it!</a>

The wonderful creepy weird web – cookie-less fingerprinting

For years, everyone online has known the deal: websites can fingerprint you. Identify you. Follow you around.  So we decline the cookie banners. We hunt for the reject all button. We feel a little safer. Modern browsers don't really need the cookie anymore.

I'd say I was pretty aware of all the possibilities and information my browser shares about me, but it's still wild to see all this data in black and white.

<a class="btn btn__small" href="https://kuber.studio/cookie/">Know your fingerprint</a>

On overflowing images

A container with a red border showing that image can overflow.

Here's Temani yet again doing Temani things explaining how to tweak and adjust the overflow of individual images using object-fit and object-position.

The <img> element (the HTML element) is the “container”, and the image resource (the actual image) is loaded inside that “container” and becomes the “content”. We have our container-content relation so we can talk about overflow.

It's a great read to understand img fundamentals.

<a class="btn btn__small" href="https://master.dev/blog/something-nobody-told-you-about-the-image-element-it-can-overflow/">Understand images</a>

View transitions block interactions

:root {   view-transition-name: none; } ::view-transition {    pointer-events: none; }

Have you ever noticed that "things become unclickable" when a view transition is running? If you're running long animations, Chris shared what you can do about it.

<a class="btn btn__small" href="https://master.dev/blog/view-transitions-careful-not-to-make-stuff-unclickable/">Keep things interactive</a>

Gap decorations are rolling out — some links

.decorated {   grid-template:        repeat(auto-fill,minmax(30px,1fr))/       repeat(auto-fill,minmax(30px,1fr));   gap: 5px;   rule: solid;   rule-color: red, red, blue;   rule-width: 1px, 1px, 3px; }

Since releasing the Web Weekly redesign, I've been waiting for CSS gap decorations to ship across browsers, because the design includes plenty of borders, and styling everything across viewports caused a mild headache.

CSS gap decorations are shipping in Chromium already. If you want to dive deeper, here are some links.

Visual design rules

Visual design rules you can safely follow every time. You do not have to follow these rules every time. If you have a good reason to break any of them, do. But they are safe to follow every time.

I'm pretty sure I read this post years ago (seems to have been extended since) and I'm still following some of the rules. These easy-to-remember rules will help you out if you don't have an eye for design.

<a class="btn btn__small" href="https://anthonyhobday.com/sideprojects/saferules/">Prettify things</a>

Random MDN – inert

div inert   label for=button2Button 2/label   button id=button2I am inert/button /div

From the unlimited MDN knowledge archive...

If you're dealing with elements that shouldn't be accessible or reachable at all, the HTML inert attribute helps out!

<a class="btn btn__small" href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/inert">Make elements inert</a>

TIL recap – @keyframe animations in the CSS cascade

The cascade determines what properties to apply to an element: 1. user-agent (browser) 2. user 3. author (developer) 4. CSS keyframe animations 5. author (developer) !important 6. user !important 7. user-agent (browser) !important 8. CSS transitions

Did you know that keyframe animations have a special place in the CSS cascade? No? Then this post is for you!

<a class="btn btn__small" href="https://www.stefanjudis.com/today-i-learned/keyframe-animations-have-a-special-role-in-the-css-cascade/">Animate</a>

::: highlight info Find more short web development learnings in my "Today I learned" section. :::

New on the baseline

Three new baseline widely available features: Array.fromAsync, avif images and :has()

There doesn't seem to be a new feature that recently went on the baseline, so let me share three things that just went baseline widely available! 🎉

I might be getting old, but it still feels like these features landed yesterday.

Three valuable projects to have a look at

A new Tiny Helper

A graph showing the comparison of testing frameworks.

The folks behind the TanStack software factory released another tool to compare npm download stats. It's not the first site that does this, but it has some more config options if you want to dive deeper.

<a class="btn btn__small" href="https://tanstack.com/stats/npm">Compare</a>

::: highlight info Find more single-purpose online tools on tiny-helpers.dev. :::

Thought of the week

As I'm turning 41 this week, I feel every word of this post. Keeping friendships alive often becomes hard work and "friends for life" can quickly become "people I used to know" if you're not careful.

::: highlight quote

Adult friendship became one of the most emotionally significant and least discussed losses of modern life. :::

Did you learn something from this issue?

❤️ If so, join 56 other Web Weekly supporters and give back with a small monthly donation on Patreon or GitHub Sponsors.

This is all, friends!

Loved this email? Hated this email? I want to hear about it!

If you think something needs improvement or something sparked some joy, reply to this email because I want to know more!


And with that, take care of yourself - mentally, physically, and emotionally.

I'll see you next week! 👋

Read the whole story
alvinashcraft
20 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Building a Browser-Based PDF Workflow for Medical Billing using .NET C#

1 Share
Learn how to create a browser-based PDF workflow for medical billing with .NET C# and TX Text Control. TX Text Control .NET Server offers different components optimized for the individual parts of the workflow, making it easy to implement these requirements.

Read the whole story
alvinashcraft
47 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

GitHub Brings Stacked Pull Requests to Public Preview

1 Share

GitHub has announced that Stacked Pull Requests are now available in public preview, introducing native support for breaking large software changes into smaller, dependent pull requests that can be reviewed and merged independently.

By Craig Risi
Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete

Partnering with CodeAI to prepare the first AI generation

1 Share
OpenAI and CodeAI are partnering to help students build AI literacy, think critically about AI, and develop the skills to use and shape it responsibly.
Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories