Website Strategy Workshop: What to Define Before Design Starts

A website redesign can move quickly into visual decisions before the team has agreed on what the site needs to accomplish. A website strategy workshop creates space to define the goals, priority audiences, key journeys, page requirements, measurement, and delivery constraints before design begins. The result is a clearer brief that gives design and development something concrete to work from instead of asking the interface to resolve unresolved strategy.

Brand Vision Creative Director Hamoun Ani frames the workshop around three early decisions: who the site is for, what the main goal is, and which pages need to exist. Making those choices before high-fidelity design helps teams evaluate later creative work against an agreed foundation rather than personal preference.

At a Glance

• A strategy workshop is where you define the decisions design depends on, not where you brainstorm aesthetics.
• Useful outputs are tangible artifacts: a KPI tree, priority journeys, sitemap rules, content briefs, and a measurement plan.
• Pre-work, a decision-ready group, and clear constraints make the session easier to facilitate.
• Performance and accessibility should be written as requirements you can test, not subjective polish. (web.dev) (W3C)
• Scannable structure matters because people often scan web pages rather than read every word. (Nielsen Norman Group)

Our Workshop Lens: Evidence Over Opinions

At Brand Vision, a branding agency, the workshop lens is evidence over opinion. The session should clarify measurable goals, the journeys that matter most, and the constraints that will shape each page. Documenting those decisions as artifacts gives stakeholders a shared reference for later design and development reviews.

• We bring evidence into the room: analytics, sales objections, and real user tasks.
• We convert opinions into decisions by writing artifacts people can approve.
• We define what success means so the site can be measured and improved after launch.

Why You Should Run a Strategy Workshop Before Design

Design cannot resolve a problem the team has not defined. When strategy stays unresolved, projects can inherit unclear calls to action, navigation built around internal departments, content that misses buyer intent, or measurement that does not connect to business outcomes. This is especially important for B2B marketing support, where the site may need to serve several stakeholders with different questions about outcomes, cost, risk, and proof.

This also matches how people behave online. Many visitors scan rather than read every line, which makes structure and message hierarchy important (Nielsen Norman Group). Defining what each core page must accomplish gives the team a clearer standard for deciding what belongs on it.

• You reduce rework by agreeing on goals, journeys, and constraints upfront.
• You speed up approvals because decisions are documented and visible.
• You improve lead quality by designing around intent, proof, and routing.

What a Website Strategy Workshop Should Produce

The value of a website strategy workshop is in what it produces. The outputs should become a brief the team can execute, whether the build is handled internally or with a web design agency. Tangible artifacts also give stakeholders something specific to review instead of reopening the same strategic questions during design.

Here are the artifacts we expect at minimum:

• KPI tree with definitions, targets, and owners
• Priority journeys and conversion paths for top audiences
• Information architecture rules plus a draft sitemap, supported by clear website navigation architecture
• Page level content briefs for the core pages
• Measurement plan: events, forms, routing, and reporting cadence
• Requirements list: accessibility and performance criteria you can test against (W3C) (web.dev)

The Pre Work Checklist: What to Collect Before the Meeting

A workshop runs on inputs. Without pre work, you’ll spend the session debating assumptions instead of making decisions. The goal is to bring shared evidence so the meeting becomes a decision session, not a discovery argument. When teams do this step well, the workshop stays short and productive.

Bring these inputs:

• Access to measurement tools: GA4, Search Console, CRM reporting, and tag manager access if available (Google Analytics Help)
• Top landing pages and top conversion pages, plus pages with high exits or drop offs
• Sales objections and common “why you” questions pulled from real calls and emails
• Competitor set and a few example sites you admire for clarity, not aesthetics
• Known constraints: CMS, integrations, compliance needs, timeline, internal review gates
• Existing brand strategy, positioning notes, messaging, and proof assets such as case studies and testimonials

As our Creative Director, Hamoun Ani points out, a homepage designed to drive leads is built differently than a homepage designed as a brand story. If the primary goal changes mid project, the layout has to change too, which is why the goal needs to be locked before design starts.

Define Success With a KPI Tree, Not a Wish List

“More leads” is too broad to guide design. A KPI tree links a business outcome to measurable website signals and gives the team a common definition of success. It can also separate outcome metrics from supporting indicators such as CTA clicks, form completion, and high-intent page actions.

A simple KPI tree approach:

• Business outcome: qualified pipeline influenced by the website
• Conversion KPIs: demo requests, booked calls, consultation submissions, high intent downloads
• Supporting KPIs: CTA click through rate, form completion rate, key landing page conversion rate
• Experience guardrails: Core Web Vitals targets so the site feels responsive and stable (web.dev)

Performance requirements should also be current. Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024 (Google Search Central). A redesign should therefore define performance ownership and test the final implementation rather than assume visual approval is enough.

• Define each KPI clearly so everyone measures the same thing.
• Set target ranges, not vague goals.
• Assign owners so the metrics don’t drift after launch.

Lock the Audience and Buying Context

Before you write copy or design layouts, agree on who the site is for and what those audiences need to understand. In B2B, that can mean several stakeholders with different questions about outcomes, cost, implementation, and risk. The workshop should map the concerns that matter to each priority audience and the evidence the site needs to provide.

This is also where brand clarity shows up. If leadership cannot explain what makes the organization different in plain language, design will not resolve the positioning gap. That is when a positioning and narrative pass matters, and why teams may involve branding services before the page system is finalized.

Define these workshop outputs:

• 2 to 3 primary ICPs and their jobs to be done
• The top objections per ICP, phrased in language sales or service teams actually hear
• Proof assets required to reduce risk: results, case studies, certifications, process transparency
• Message hierarchy: what should be clear immediately and what can be explained with more depth

If regional collaboration changes the working model, include that in the brief. A company comparing a branding agency in Chicago, for example, should still define decision-makers, business objectives, approval responsibilities, and delivery constraints rather than treating location as the strategy.

Map the Priority Journeys the Site Must Support

A strategy workshop should identify the journeys that deserve the most attention instead of treating every page and audience as equally important. Start with how users arrive, what they need to understand, what evidence reduces uncertainty, and which actions indicate meaningful intent. This is where user experience discipline matters because friction can hide in navigation labels, proof placement, forms, and interaction details.

Typical journeys for a B2B lead gen site:

• Services page to proof to contact
• Industry page to case study to booked call
• Pricing or process page to consultation request
• Blog to supporting service page to conversion

If you’re working with a UI UX design agency, this is also where you define interaction patterns that should remain consistent across the site: how CTAs appear, how proof is presented, and how forms behave across mobile and desktop.

• Choose 3 to 5 “must win” journeys.
• Define the conversion action for each journey.
• Clarify what makes the lead high quality for sales.

Decide Your Information Architecture Rules Before You Build a Sitemap

A sitemap is not simply a list of everything stakeholders want to say. It is part of a system for helping users find what they need. People often scan and decide quickly, so structure matters (Nielsen Norman Group). Define the information-architecture rules first, then build a sitemap that follows them. Where labels or groupings are uncertain, card sorting and tree testing can help validate the assumptions before design locks them in.

Rules we typically define:

• What belongs in top navigation vs what belongs as supporting pages
• Depth rules: how directly important pages should be reachable from relevant navigation and hubs
• Naming conventions: task based labels, not internal department language
• Page ownership: who is responsible for accuracy and updates

This is also where you identify “must exist” pages: core service pages, industry pages, proof pages, and conversion endpoints.

• Build navigation around user tasks and intent.
• Keep categories clean and mutually exclusive.
• Prevent dead end pages by defining next steps on every core page.

Make the Content Decisions Early: Keep, Kill, Consolidate, Rewrite

Content is where redesigns quietly derail. Teams underestimate how much has to be rewritten, how much proof needs to be created, and how migration can affect search visibility. Your workshop should decide what stays, what gets updated, and what needs net new content, especially on core services and high intent landing pages.

If organic traffic is a major growth channel, involve your SEO agency early so you don’t accidentally bury pages that currently drive leads. A content inventory with clear actions keeps the project honest.

Use a simple classification:

• Keep: accurate and aligned content that still performs
• Consolidate: overlapping pages that should become one stronger page
• Rewrite: content that’s outdated, unclear, or misaligned with positioning
• Retire: low value pages that create noise or confusion

Then create a page brief for every core page:

• Goal and primary audience
• Key message and proof required
• Primary CTA and secondary CTA
• Internal links that support the journey
• Decide how many net new proof assets you need, such as case studies and testimonials.
• Align your FAQ content with sales objections, not random questions.
• Avoid rewriting everything unless you have a clear reason.

Define Measurement, Forms, and Routing Before Design

If measurement is left until after launch, reporting can become inconsistent or incomplete. The workshop should define which actions matter, what events must be captured, and how leads route to the right owner. A practical marketing attribution framework can also clarify how campaign data, forms, analytics, and CRM fields should connect before the implementation starts.

GA4 is event-based, and actions that are particularly important to the business can be marked as key events (Google Analytics Help). Define those important actions before design so forms, CTAs, confirmation states, and reporting requirements can be implemented consistently across templates.

Define these items:

• Conversion definitions: what action counts, and what fields qualify it
• Event taxonomy: naming conventions so reporting stays clean
• Routing rules: which team gets which lead, and follow up SLA expectations
• Reporting cadence: weekly performance summary and monthly deeper review

If you run paid campaigns, you may also want to align conversion measurement rules across platforms so ad optimization is consistent. (Google Tag Platform)

• Decide your top 3 to 5 key events and track them consistently.
• Avoid capturing everything without purpose, it creates reporting noise.
• Document the measurement plan as a workshop artifact.

Write Performance and Accessibility Into the Brief

Performance and accessibility should be requirements the team can test, not optional polish. Core Web Vitals provide measurable signals for loading, responsiveness, and visual stability (web.dev). WCAG 2.2 provides the accessibility standard for requirements such as labels, instructions, and error handling (W3C). A website QA checklist can turn those requirements into launch acceptance checks alongside forms, tracking, SEO, and responsive behavior.

Two WCAG criteria are especially relevant for lead gen forms:

• Labels or instructions should be provided so users understand what to enter. (W3C)
• Errors should be identified in text so users know what went wrong and how to fix it. (W3C)

For performance, be explicit:

• Set targets for LCP, INP, and CLS, and define who owns performance budgets. (web.dev) (Google Search Central)
• Identify heavy third party tools early so they don’t surprise you in development.
• Define mobile as a first class experience, not a compressed desktop layout.
• Write acceptance criteria your QA team can validate.
• Treat accessibility as part of conversion, not just compliance.
• Treat performance as part of trust, not just engineering.

A Sample 90-Minute Workshop Agenda

A tight agenda keeps the meeting focused on decisions, documentation, and ownership. If uncertainty is high, extend the work into a broader discovery phase, but keep the purpose the same: understand users, constraints, and the problem being solved (GOV.UK Service Manual).

One 90-minute format to adapt is:

• 0 to 10: scope, constraints, and the decisions you must make today
• 10 to 30: goals, KPI tree, targets, and owners
• 30 to 55: audience clarity and priority journeys, including conversion actions
• 55 to 75: information architecture rules, sitemap draft, and core page list
• 75 to 90: content decisions, measurement plan, next steps, owners

Facilitation rules that keep it productive:

• One decision maker per domain, marketing, sales, and delivery
• Parking lot for off topic issues so the group doesn’t spiral
• Decision log updated live so nothing gets lost
• Keep the attendee list small and decision capable.
• Bring evidence, not assumptions.
• Leave with artifacts, not notes.

What Happens Next: Turning Strategy Into Design and Build

Once the workshop outputs are approved, the next phase has a clearer reference point. Wireframes can map to priority journeys, copy can map to proof requirements, and development can map to technical acceptance criteria. Stakeholders can then review the work against agreed artifacts instead of reopening strategic decisions on every screen.

If you want outside support facilitating the workshop and carrying the decisions into design and build, start with our marketing consultation services. Brand Vision can structure the session, document agreed outputs, and connect those decisions to the next phase of the website project.

• Confirm the artifact set: KPI tree, journeys, sitemap rules, content briefs, measurement plan
• Convert artifacts into wireframes with clear CTAs and page goals
• Build and QA against performance and accessibility requirements
• Launch with clean measurement so you can optimize based on real data

FAQ

What is a website strategy workshop?

It’s a focused working session that defines what your website must achieve before design begins. You lock goals, priority journeys, key pages, and measurement so design is based on decisions, not opinions.

Who should attend the workshop?

Keep it small and decision-ready: one executive sponsor, the marketing lead who owns the pipeline, someone close to sales or RevOps, and a delivery lead. Add a technical owner only if integrations, CMS, or compliance constraints will shape the build.

How long should a website strategy workshop take?

A focused 60- to 90-minute session can be enough to make an initial set of decisions when pre-work is complete and the scope is narrow. Sites with multiple audiences, complex integrations, or layered approvals may need additional sessions for goals and journeys, then information architecture, content, and measurement.

What deliverables should we leave with?

You should leave with written artifacts: a KPI tree with targets, 3 to 5 priority journeys, sitemap rules plus a draft sitemap, core page briefs, and a measurement plan for events, forms, and lead routing. If those aren’t documented, the workshop isn’t finished.

How do we know we’re ready to start design?

You’re ready when your team agrees on success metrics, priority journeys, the core page list, content actions (keep, rewrite, consolidate, retire), and your conversion tracking plan. You should also have clear performance and accessibility requirements so QA can test against standards, not taste.

Make the Decisions That Let Design Win

A redesign is visible, but much of the work that supports it happens before the first polished screen: defining goals, journeys, content responsibilities, and measurement with enough precision that the team can execute without guessing. A good strategy workshop creates a shared decision framework that can carry into design, development, and launch.

If you want a workshop facilitated end to end and then carried into wireframes, design, and development, talk to our web design agency team. The goal is to define what matters before design starts so the creative work can be evaluated against a clear brief.