Copyright © Brave Digital 2018
Web design agency in South Africa hero banner imageSouth Africa web design hero image with city lights and mountain view

Planning a Website Redesign:

What to Decide Before You Brief a Developer

Website redesign planning often starts with layouts, platforms or features, but the useful decisions usually come much earlier.

Planning a Website Redesign:

What to Decide Before You Brief a Developer

Website redesign planning often starts with layouts, platforms or features, but the useful decisions usually come much earlier.

Let's connect





    Web Development

    BRAVE Digital delivers website development for South African businesses.

    Businesses that need a site that’s fast, easy to manage, and built to perform on mobile.

    Before you brief a developer, you don’t need to know which CMS, framework or stack to choose, but you do need clarity on why the redesign is happening, who the site must serve, what content exists, who owns it, and how you will judge success.

    That shift matters. When the business goal is clear, the development partner can help shape the right structure, discovery process, information architecture, UX direction and build approach. Without that clarity, redesign conversations can drift into preferences and assumptions, which leads to workarounds later. Good website redesign planning is less about sounding technical and more about making decisions that give the project a solid foundation.

    If you’re a communications or marketing lead, the good news is simple: you don’t have to pretend to be a developer to brief one well. You just need to be clear about the problem, the audience, the content, the governance model and the outcome you are aiming for. That is the practical starting point.

    Start with the reason for the redesign

    Every redesign should begin with the problem you’re trying to solve. A site may be hard to update, unclear to visitors, too fragmented for the team to manage, or no longer aligned with what the organisation needs to communicate. If you can’ describe the reason clearly, the project can become a set of competing opinions about pages, colours or features.

    Ask “what is not working now?” Is the issue that content is difficult to find? Are different teams publishing without a shared structure? Has the current site grown around internal needs instead of audience needs? The answer shapes everything that follows. A business seeking better service journeys needs a different approach from one that mainly needs stronger content governance or clearer navigation.

    This is also the moment to define non-negotiables. A communications team may need approval workflows, consistent messaging or space for campaign updates. A business may need the site to support lead generation, recruitment or stakeholder communication. Those requirements should be visible from the start because they affect both the website development process and the information structure behind it.

    Before you brief a developer, decide the business problem in plain language. BRAVE helps you solve the “what is this redesign for?” question before the team gets drawn into the “what does it look like?” conversation.

    Web design agency in South Africa hero banner image

    Decide what success should look like

    Before you brief a developer, agree on what a successful redesign needs to achieve. You don’t need to promise numbers or speculate about results, but you do need a shared view of what improvement means. Success might involve clearer journeys, easier publishing, stronger governance, better findability, or a structure that supports the organisation’s priorities more cleanly.

    Good website redesign planning turns broad ambitions into practical measures. For example, if the aim is to make the site easier to use, define what “easier” means in context. If the aim is to improve content control, decide which teams need to publish, review or approve content. If the aim is to support business priorities, identify which pages, actions or user journeys matter most.

    This stage is not about analytics detail or technical setup. It is about defining the questions the new site should be able to answer once it is live. That gives your development partner a clearer brief and helps everyone evaluate choices against the same purpose. Before you brief a developer, decide the success test first. BRAVE helps you solve the “what does good look like?” question without pushing you into premature technical choices.

    Web design agency in South Africa hero banner image

    Map the users and their jobs to be done

    Many redesigns go off track because the project begins with internal preferences instead of user needs. Before you brief a developer, identify who the site is for and what those people are trying to do. Different audiences often arrive with different intent, and the site needs to support those differences without making the experience feel fragmented.

    For communications or marketing leads, this usually means separating the audience groups that matter most. A prospective customer may need reassurance and quick access to service information. An existing client may need support or updates. A media stakeholder may need facts, contact details or corporate information. A candidate may be looking for culture, vacancies or practical next steps. Each group brings a different task.

    Once you know the users, describe their jobs to be done in plain language. What do they need to find, understand, compare or complete? This helps shape the website UX design conversation later. It also reduces the risk of building around internal department structures that make sense to the organisation but not to the visitor.

    Don’t try to solve every journey at this stage. Focus on the most important ones and the most costly gaps in the current experience. That is enough to guide the development partner into a useful discovery process. Before you brief a developer, decide who the site must serve and why. BRAVE helps you solve the audience question in a way that supports the rest of the project.

    Audit content and clarify ownership

    Content is where many redesigns become more complicated than they need to be. Before you brief a developer, know what content exists, what should stay, what should change and who is responsible for each part. A redesign is rarely only a design or build exercise. It is also a content decision, and those decisions affect structure, editing effort and governance.

    Start with a simple inventory. Identify the main page types, key sections and recurring content areas. Then decide what needs rewriting, what can be migrated, what should be merged, and what should be removed. You do not need a perfect spreadsheet to begin, but you do need enough clarity to avoid carrying confusion into the build.

    Ownership matters just as much as volume. If multiple teams contribute to the site, decide who approves updates, who writes new content, and who maintains consistency over time. Without that model, even a well-built site can become difficult to manage. This is especially important for communications teams that need a website structure they can actually govern after launch.

    A development partner can help you think about content workflow, but the business still needs to define the practical responsibilities. That makes the website redesign for businesses more realistic, because the site is designed around how the organisation works, not only how it looks. Before you brief a developer, decide what content belongs, who owns it and who signs it off. BRAVE helps you solve the governance side without overcomplicating the brief.

    Web design agency in South Africa hero banner image

    Set the right-level decisions for information architecture and UX

    Website information architecture and website UX design do not need to be fully specified before you speak to a developer. What you do need is direction at the decision level. In other words, you should know the broad shape of the experience you want to support, not every wireframe detail.

    Decide which content groups belong together, which journeys should feel immediate, and which actions deserve priority on key pages. Think about how users will move through the site. Where should they start? What should they see first? What should happen when they need a next step? Those decisions help define the structure without locking you into a final design too early.

    This is also the right moment to flag any constraints. For example, if certain messages must appear in specific places, or if multiple internal audiences need shared navigation patterns, the architecture has to account for that. Clear constraints help the design work better because they prevent later compromises that feel bolted on.

    Brave Digital works with communications teams to turn these early decisions into a practical discovery process, which means that the conversation stays focused on the right questions: what the site needs to do, how people will use it, and what structure will support that work. Before you brief a developer, decide the principles behind the structure. BRAVE helps you solve the IA and UX question at the right altitude.

    Decide what you need to know for search, measurement and delivery

    It helps to separate requirements from implementation. Before you brief a developer, you do not need to pre-select the CMS or choose a specific technology stack. What you do need is enough clarity for the partner to assess fit. That includes your content needs, governance requirements, integration considerations, measurement needs and any search visibility concerns that matter to the business.

    For search and measurement, focus on foundations. What should be trackable? Which actions matter most? Are there reporting needs that the new site must support? Which content areas need stronger discoverability? These are useful requirements even when the technical approach is still open. They give the development partner the context needed to recommend a suitable solution.

    The same applies to integrations. You may not know the best technical route yet, but you should know what systems or workflows need to connect to the site, or where manual work is currently causing friction. That information helps shape the website development process and reduces the chance of choosing a build that looks fine on paper but creates avoidable operational effort later.

    Before you brief a developer, decide the requirements that matter most to search, measurement and delivery. BRAVE helps you solve the foundations first, then works with you on the implementation details that fit those needs.

    Work out how stakeholders will make decisions together

    Redesigns move more smoothly when the working model is clear from the start, so before you brief a developer, decide who needs to be involved, who approves what, and how decisions will be made. This is especially important when communications teams are coordinating across departments because a site often has many stakeholders but only a few real decision-makers.

    Clarity here prevents delay and rework. If content approvals, brand checks, legal review or technical sign-off are all part of the process, say so early. If certain groups need visibility but not control, define that too. A good partner can work with this structure, but they need to understand it in advance.
    BRAVE’s role is to help you turn that collaboration into a workable plan.

    Discovery, information architecture, UX/UI, development, testing and launch all become easier when the internal decision model is realistic. The goal is not to force a rigid process. The goal is to make the project understandable to the people who have to support it.

    What you can leave for the development partner

    A strong brief is clear about the problem, but it does not pretend to solve every technical question in advance. That is where a good development partner adds value. Before you brief a developer, decide the business context and the audience needs; then leave room to solve the build approach together.

    You can leave the recommended CMS fit, the detailed build approach, the SEO/search implementation foundations, the analytics instrumentation approach and the integration route to the partner, as long as you have explained the requirements behind them. That is the difference between a vague brief and a smart one. Vague means “we need a new website.” Smart means “we need a site that helps these users do these tasks, with these content responsibilities and these measurement needs.”

    You can also leave room for recommended IA refinements and UX/UI patterns. The brief should point to the priorities, not dictate every solution. That way, the discovery process can surface better choices rather than forcing the team to defend an early guess. Before you brief a developer, decide what needs to be fixed and what should be explored together. BRAVE helps you solve the fit question without pre-selecting a stack too soon.

    Web design agency in South Africa hero banner image

    What a good brief looks like

    A strong website brief does not have to include a final CMS choice or a fully mapped technical stack. It does need enough detail for a partner to understand the challenge, assess the options and propose a practical path. If you can answer the core questions below, you are in a good place to begin the conversation.

    • Why are we redesigning now?
    • Who are the main audiences and what do they need to do?
    • What content exists, what needs to change and who owns it?
    • What must the new structure support for users and the business?
    • What needs to be measured or reported after launch?
    • Which teams need to be involved in approvals and content governance?
    • What is already fixed, and what should be solved together?

    If you can answer those questions clearly, your brief is probably good enough. It gives the development partner the context they need without pretending you have to know everything in advance. That is the practical balance in website redesign planning: enough certainty to move forward, enough openness to let the right solution emerge. It is also the point where a communications-led conversation becomes genuinely useful, because the team can focus on decisions instead of jargon.

    A better redesign conversation starts with the right questions

    The best redesign conversations are grounded in purpose, users and content before they reach the build stage. That approach keeps the project focused, helps teams avoid unnecessary workarounds and creates a clearer path into the website development process. You do not need to pre-select the technology to brief the work well. You do need to know what the site must achieve and what it must support.

    If you are getting ready to start a redesign, BRAVE can help you discuss the goals, users and practical constraints that shape a better brief. Start there, and the decisions around information architecture, UX/UI and delivery become much easier to make together.

    Web design agency in South Africa hero banner image

    Talk to BRAVE about your redesign goals and users

    If you are planning a website redesign, BRAVE can help you clarify the goals, users, content and working model before the development conversation begins. Use that first discussion to build a brief your team can confidently act on.

    ×
    General (Long Form)
    • Step 1
    • Step 2
    • Step 3
    • Step 4
    • Step 5
    Hi there!

    Before we kick off, we would like to get
    to know you a little better.

    * these fields are required