Your story hasn't changed - How you tell it can

This morning, I had a conversation with a client about one of their project pages. Their team has grown significantly, and they wanted to expand the page to reflect this growth. It's a request I hear often - a team evolves, achievements accumulate, and the instinct is to add more content, create more space.

But as we talked, something became clear: their project story hasn't actually changed. The mission is the same. The impact they're working toward is the same. What's changed is their capacity to deliver on that mission - and that's not a different or new story, just a different angle.

"Perhaps," I suggested, "we should talk to the project team first. Not about what to add, but about how to reframe what's already there."

The Conversation Before Anything Else

This is where understanding people and building websites meet - my favorite intersection. The main web team knows the site and understands the technical possibilities. But the project team knows their story. They know which outcomes matter most, which aspects of their work are hardest to communicate, where people misunderstand their mission.

These conversations reveal things. Not just facts to document, but narrative tensions to resolve. Sometimes a team realizes they've been leading with process when they should lead with impact. Sometimes they discover their "About" section is really a "Why" section in disguise. Sometimes they find that what they thought was a content problem is actually a confidence problem - they have the story, they're just not sure it's interesting enough.

(It always is.)

Ways to Reframe Your Story

So what does it actually look like to tell the same story from a different angle? Here are some approaches worth considering:

Lead with Impact, Not Process

What you put first is what you value. When we put team bios at the top, we're saying "trust us because of who we are." When we put outcomes first, we're saying "trust us because of what we've achieved." Both are valid, but they tell very different stories.

The project team's growth isn't just a fact to document; it's evidence of something deeper. It suggests that the work they're doing resonates, that their approach is effective, that their outcomes matter. But you can't see that if you're just adding staff bios to the bottom of an "About" section.

Use Structure as Narrative

The hierarchy of information on a page isn't just about making things easier to find - it's about making a statement of priority. Moving outcomes to the top and making "About" secondary isn't a UX tweak, it's an editorial choice. It says "here's what we've done, and here's who we are" instead of the other way around.

The beautiful thing is that this isn't about creating new content or manufacturing a different narrative. The outcomes were always there. The impact was always documented. We're not changing the story - we're changing how we tell it.

Give Your Content Room to Breathe

Different content types deserve different treatments. A pull quote isn't just a styling choice - it's a way of saying "this is the heart of it." An image gallery isn't just prettier than a list - it's a different emotional register. A statistics block isn't just information display - it's evidence given weight.

Think about whether your key messages are buried in paragraphs when they should stand alone. Whether your evidence is presented as running text when numbers or images would land harder. Whether you're using one format for everything when variety could help different types of information shine.

Let the Technology Enable, Not Constrain

Here's where Plone with its Volto front-end becomes quietly revolutionary. In the past, restructuring a page like this would have meant developer time, testing, potentially breaking things, definitely creating dependencies. It would have been enough friction that organizations might not bother - better to leave well enough alone than risk the disruption.

But with Volto's block-based approach, restructuring is now as simple as shuffling blocks. The project team themselves could experiment with leading with impact instead of process. They could try featuring key outcomes prominently and see how it feels. They could test different ways of integrating team information into the narrative rather than treating it as a separate concern.

This isn't just easier - it's fundamentally different. It puts editorial power where it belongs: with the people who know the story best. Not because they're technical experts, but because they're living the mission every day.

Make Format Choices That Support Story Choices

When I talk about giving editors "different ways of showcasing content," I'm not talking about feature bloat. I'm talking about narrative tools that serve clear purposes.

These tools only work if the people using them understand why each option exists. If blocks and components are transparent in their purpose - if it's clear what each one is for narratively - then editors can make genuine storytelling choices, not just technical ones.

Starting the Year with Stories

As we move into 2026, I'm thinking a lot about this intersection of story and structure. About how the best technical solutions enable rather than constrain. About how growth isn't just something to document - it's evidence to deploy.

Your story probably hasn't changed as much as you think it has. Your mission is likely still your mission. Your values are likely still your values. But how you tell that story - what you lead with, what you emphasize, how you structure the narrative - that can transform everything.

Sometimes the best redesign is just a reframe. Sometimes the most powerful technical solution is one that gets out of the way and lets the story breathe. Sometimes what you need isn't more content - it's more clarity about what your existing content is really saying.

And sometimes, the most important conversation happens before you touch the CMS at all.