Behind the badge: what an editorial idea has to survive

How Sage’s The lessons behind the badge went from interview transcripts to a live page, and which decisions mattered most along the way.

The lessons behind the badge is now live on sage.com. It takes one business lesson from each of three EFL clubs: Tranmere Rovers on connecting purpose, people and performance, Club Doncaster Foundation on how small changes create lasting impact, and AFC Wimbledon on building pathways rather than one-off opportunities. Each club section has evidence cards, a short business lesson, three questions for the reader’s own organisation and a link to the full customer story. The proposition is simple: every football club is a business, and the best have lessons any organisation can learn from.

I developed the concept, worked through the interview evidence, wrote the lessons and copy, and specified the page for the web team. Colleagues did the club relationships, the customer stories and video the page draws on, the assets and the build. I added a short note about the launch to an earlier piece on the EFL customer-story work. This is the longer account, because most of what made the page work is invisible on the page.

The evidence chose the lessons

The working sequence was transcripts, then evidence mapping, then a lesson for each club, then content architecture, copy, wireframe, CMS translation and handover. The order is the important part. I mapped what each interview could genuinely support into an evidence table before writing any page copy, and each club’s lesson came out of that table rather than being assigned in advance.

That order changed at least one lesson. When I first wrote about the hub, I expected AFC Wimbledon to say something about fan ownership and trust in financial information. The evidence for pathways was stronger: mentoring, progression, and investing in people without sacrificing quality. So pathways became the lesson. If I had fixed the lessons first and gone looking for support, the page would have been neater on paper and weaker in substance.

I also rejected a tidier idea. One option was a single governing thesis across the clubs, something like “great organisations create the conditions for success”. It would have made the three stories feel unified, but it would also have meant every future club had to prove the same narrow claim, on a page designed to grow through the season. The broader proposition, that football clubs face recognisable business challenges and each can teach something different, is less elegant and much more durable. The working rule I took from it was coherence without conformity.

Content architecture before interface

Before there was a final wireframe, the page was broken into editorial components: hero, introduction, club navigation, club introduction, video, evidence cards, business lesson, reflection questions, Sage connection, shared lessons and a closing call to action. Settling that structure first meant the design was built around the story logic rather than the story being squeezed into a layout that already existed.

The copy deck became more than a copy document. By the time it went to the web team, it recorded component order, copy, calls to action, asset requirements, media treatment, accessibility notes, character counts and the places where video still had no confirmed location. Unknown items were marked as to be confirmed rather than left out or filled with something plausible. A gap you can see is a dependency someone can resolve; a gap hidden behind invented content becomes an error someone has to find later.

The request for more Sage

The most useful test came from feedback. The copy was in good shape, but stakeholders wanted a stronger Sage connection through the stories, without the page feeling product-led. That is a common request, and the common response is to add brand messaging wherever there is room.

I went back to the transcripts instead. The rule became: where Sage is part of the evidence, make it part of the story, and where it is not, don’t force it. Each club got one evidence card carrying a concrete, customer-evidenced proof point: finance, HR, payroll and timesheets running on Sage at Tranmere, live Sage reporting across Doncaster’s programmes, and around a day of spreadsheet work saved at Wimbledon.

The return to the evidence also made the claims more accurate. The feedback described Sage’s visibility at Doncaster as supporting 36 projects; the source material said 36 programmes. The working copy for Wimbledon said Sage saved a full day each month; the source said roughly a day. Both corrections are small, and both are on the live page. Strengthening the commercial link turned out to mean making it more precise rather than louder, which may be the most transferable lesson in the whole project. When a claim feels weak, the answer is usually better evidence, not stronger copy.

Protecting the idea, not the mock-up

Then came the build. The web team translated the concept wireframe into the components sage.com actually supports, and the copy moved into a production deck based on the content management system’s structure. This is where editorial ideas usually thin out, because each individual compromise is reasonable on its own.

The useful discipline was separating an editorial requirement from a presentation preference. The original concept had a hero video montage, but the requirement was to establish the proposition quickly, and a still image does that, so the hero video became optional. The separate Sage call-to-action blocks planned for each club were collapsed into one shared signpost after the club sections. Because the Sage proof already sat inside the evidence cards, the stories kept their commercial relevance without three promotional interruptions. If losing a presentation device breaks an idea, the idea was depending on the mock-up rather than on its structure.

Some things were worth holding: one club, one lesson; Sage as the enabler rather than the hero; and the guardrails on programmes and the qualified time saving. The reflection questions were an open question during the build, and a component that doesn’t fit neatly is often the first thing dropped. They survived on the live page. I also found it useful to treat the editorial specification and the production specification as different documents with traceability between them, rather than insisting my original deck stay the delivery format once the web team’s structure existed.

The fair objection

Every club section follows the same structure, which sits awkwardly with my earlier claim that the hub shouldn’t force every club into a template. My answer is that a shared structure and a shared lesson are different things. The structure makes the page scannable and lets new clubs be added without a redesign, while the lessons stay distinct because each came out of a different body of evidence.

That answer is provisional. Three clubs is a small sample, and as more are added the template could start bending lessons to fit its slots: four evidence cards may be too many for one club and too few for another. The test is whether the next club’s lesson still comes from its evidence rather than from the shape of the page.

What the case shows, and what it doesn’t

The case shows that editorial work on a project like this is not mainly writing. It crossed transcript analysis, evidence mapping, narrative judgement, information architecture, product-proof discipline, accessibility, CMS translation and handover. The copy was the visible part, but writing it was also an exercise in judgement: making each lesson clear without stretching the evidence. That judgement continued through decisions about what to leave out and what to protect when the build forced trade-offs. The separate editorial and production specifications also made handoffs more explicit and future additions easier to plan for. Whether they reduce rework in practice is something I would still need to test.

What it does not yet show is impact. A live page establishes that the idea survived production. It doesn’t tell me whether readers used the lessons, whether the page sent anyone on to the customer stories, or whether the modular design holds up when new clubs arrive. Those need evidence I don’t have yet, and they are the next things worth recording.