You probably think you know what's wrong with your website. It's slow. It looks dated. The CMS is a nightmare to work in. And somewhere in a Teams channel, someone has already used the hashtag "redesign." But asking a follow-up question tends to thin out the certainty.
Most large organisations can describe their website's problems in adjectives. Far fewer can describe them in evidence and give answers on who actually uses this site, and for what.
If you can’t describe and document the problem, you can’t fix it. You need to understand your current situation to build the foundation and plan that gets you to where you want to be.
The key is the define the scope. Or else it turns out bad.
Where it usually starts
Strategic mapping projects rarely start with ambition. They start with a deadline, often due to a technical trigger. Like a CMS vendor is sunsetting support or a migration has to happen because the alternative is a system nobody can maintain.
Under that kind of pressure, the instinct is to move straight to an RFP (Request for Proposal). Define the requirements, brief a handful of agencies, pick one. It feels efficient. It's also how organisations end up rebuilding the exact same problems in a newer framework.
Don’t skip the diagnose
The step that gets skipped is the diagnostic one: what's actually working, what isn't, and for whom.
Instead, it gets assumed. Internal stakeholders know the site is clunky because they're the ones fighting the CMS every week, so the CMS becomes the story. Meanwhile, the intended website users rarely is in the room.
We see this constantly: a corporate website's navigation ends up shaped like the org chart, not like what a visitor came to find. It's built to make every department feel represented, not to help anyone get an answer.
That's not incompetence. It's a natural byproduct of who's in the room when decisions get made — internal pride, a bit of conflict-avoidance, nobody wanting their team's page cut from the menu. But it means the redesign, when it happens, often optimises for the wrong audience: the one that already works here.
The solution is a strategic mapping
Strategic mapping is our answer to that gap. It's a structured analysis of where an organisation's digital presence stands today, set against where the business genuinely needs to go, commercially, organisationally, and technically.
It's deliberately holistic. We look at the technology (what's the platform actually capable of, what's it costing to run), the UX and design (does the experience match how people actually use it), the brand and market position (how does the website match your story and ambitions), the business case (what does the current setup cost, what would a better one cost, what does it return), and the governance behind it all (who owns what, and whether the team maintaining the site has the structure and skills to do it well).
The output isn't a verdict that says "redesign." It's a diagnosis of how much needs to change, and where.
Sometimes that means evolution: the platform is fine, but three key pages and the content workflow are quietly costing the business money.
Sometimes it means revolution: a full rebuild, because the foundation can't support what the organisation needs next. And the change itself isn't always visual, in some cases, the fix is entirely internal, a governance model that gets the right people talking to each other before content goes live, rather than after something breaks.
Knowing which kind of change you need, before you commit budget to it, is the actual value here.
The process of mapping
We start by talking to the organisation itself — stakeholders across business areas, not just the team that owns the website — so the picture reflects the whole organisation rather than the loudest department. Then we talk to the people outside it: how do external users actually experience the site, and what do they say about it, unprompted? That's usually where the internal narrative and the external reality diverge.
Signifly's role here is deliberately narrow. We're not selling the fix — we're building the argument for it, or against it, based on what we find. That independence is the point: an organisation can trust the diagnosis precisely because we don't need it to end in a redesign.
The output is concrete, not conceptual. We answer questions like
On top of that, we propose an organisational structure for maintaining the site going forward, one that works across communications and tech, instead of falling through the gap between them.
From there, the actual website work — if there is any — typically goes to tender. Strategic mapping isn't a pitch for the build. It's the groundwork that makes the build brief worth writing.
In practice: Dansk Industri
When we ran this process with Dansk Industri, the outcome wasn't a decision we made for them. It was a case their own team could make for themselves.
DI's internal team knew their website needed work. What they didn't have was a way to make that case to their board, the evidence, structured clearly enough to justify budget. That's what the analysis produced: a sales presentation their team could take upstairs, built on the findings from the mapping process rather than internal conviction alone.
It's a useful example of what this service actually delivers. Not a redesign handed down from outside, but the documentation an organisation needs to make its own case, internally, credibly, with evidence behind it.
The real question
The question worth asking isn't "do we need a redesign." It's whether you know what you're actually deciding, and how much of it genuinely needs to change.
That's a different starting point than most website projects get. It's a better one.
