Website Redesign Discovery Questions

Outcome Summary

• Run discovery that uncovers goals, constraints, stakeholders, and “must-keep” elements before you talk visuals.
• Turn answers into a scoping-ready brief: pages, content readiness, technical constraints, and acceptance criteria.
• Use a redesign preview to validate direction early—without locking yourself into final design decisions.

What Revamp Actually Does (Truth Block)

✅ does

• Lets you paste a website URL and generate an AI website redesign preview.
• Produces a shareable live preview link you can use for internal reviews or client alignment.
• Supports optional design preferences to steer style direction (e.g., layout vibe, typography feel, brand tone).
• Can export code on paid plans.

❌ does not

• Replace discovery, requirements gathering, or stakeholder alignment.
• Guarantee SEO, performance, or conversion outcomes from a redesign preview.
• Reliably reproduce complex app behavior or specialized interactive components from every site.

The Core Problem

• Stakeholders say “modern” but mean different things (brand, conversion, speed, credibility, recruiting).
• Hidden constraints (CMS, integrations, approvals, compliance) surface late and derail scope.
• Content readiness is unclear (missing pages, weak messaging, no imagery), so design timelines slip.
• “Must-keep” elements aren’t defined (navigation, IA, URLs, components), causing rework.
• Success criteria are vague, so sign-off becomes subjective and slow.

Framework

Step: Start with outcome, not pages

Ask:

• “What decision should this website help someone make?”
• “What action do we want the primary visitor to take?”
• “What would make you call this redesign a success?”

Step: Define the primary audiences and their jobs

Ask:

• “Who are the top audiences, and what are they trying to accomplish?”
• “What objections do we need to overcome?”
• “What must visitors understand before they’re willing to act?”

Step: Identify stakeholders, approvers, and review workflow

Ask:

• “Who gives final approval—and what do they care about most?”
• “Who needs to review copy vs design vs technical details?”
• “What’s the preferred feedback format (comments, doc, ticketing)?”

Step: Lock in “must-keep” and “must-change” elements

Ask:

• “What must stay exactly the same (brand elements, legal text, navigation labels, URLs)?”
• “What is non-negotiably broken today?”
• “What features are in scope vs explicitly out of scope?”

Step: Inventory content readiness and ownership

Ask:

• “Do we have final copy, or are we rewriting?”
• “Who owns content approvals?”
• “What assets exist (logos, brand guidelines, imagery), and what needs creation?”

Step: Map the key pages and journeys

Ask:

• “Which pages are essential for launch?”
• “What are the most common paths to the primary action?”
• “Which pages are high-risk (complex layout, heavy stakeholders, compliance review)?”

Step: Capture technical constraints early

Ask:

• “What CMS or site builder are we staying on (or moving to)?”
• “What integrations must remain (forms, CRM, scheduling, analytics, payments)?”
• “Are there environments or deployment rules we have to follow?”

Step: Handle SEO, analytics, and measurement explicitly

Ask:

• “Which pages or queries matter most—and why?”
• “Do we have access to analytics and search tooling?”
• “What URL structure must be preserved, and what can change?”

Step: Validate direction with a redesign preview (before final comps)

Recommended approach:

• Generate a Revamp redesign demo from the current URL.
• Apply a small set of design preferences to test direction (tone, layout feel, brand vibe).
• Share the live preview link and ask reviewers to respond to a focused checklist (clarity, hierarchy, trust cues, primary action).

Use Cases

Use case: Agency scoping a redesign pitch

• Scenario: A prospect wants “a modern refresh,” but the team disagrees on what that means.
• Recommended approach: Use outcome + must-keep questions first, then generate a Revamp preview and collect feedback against agreed criteria (not taste).
• Common mistake: Jumping straight to moodboards—feedback becomes subjective and scope stays fuzzy.

Use case: In-house marketing team modernizing an outdated site

• Scenario: Marketing owns the site, but brand and legal must approve changes.
• Recommended approach: Run stakeholder workflow discovery early, define approval checkpoints, and use a shareable redesign preview link to reduce back-and-forth.
• Common mistake: Treating approvals as a final step—launch gets blocked by late-stage objections.

Use case: Founder-led site rebuild with limited internal time

• Scenario: The founder wants a new site but can’t provide complete copy or assets up front.
• Recommended approach: Use content readiness questions to decide what to rewrite now vs later, and use a preview to validate structure while content is drafted.
• Common mistake: Designing “final” pages with placeholder messaging—rewrites break the layout and force redesign.

Decision Checklist

• Can you clearly state the primary visitor action and the business reason it matters?
• Do you know who approves the redesign—and what each approver values?
• Have you documented must-keep items (URLs, navigation, legal, brand elements, integrations)?
• Is content ownership clear (who writes, who edits, who signs off)?
• Do you have access to analytics/search insights—or a plan if you don’t?
• Are technical constraints confirmed (CMS, hosting, forms, tracking, deployment)?
• Do you have an agreed way to give feedback (criteria-based, not preference-based)?
• Is there a defined launch scope vs post-launch improvements?

Constraints

• Discovery answers change; your scope should explicitly separate assumptions from confirmed requirements.
• A redesign preview is a direction-setting artifact, not a final spec—expect refinement and implementation work.
• The quality of any AI redesign output depends on what the source site exposes (structure, content, assets).
• If the site includes complex application behavior, plan for additional solution design beyond a marketing-page redesign.
• Code export availability and usage limits can vary by plan—confirm what your team needs before committing.

Common Mistakes

• Asking “what do you like?” before “what must this page accomplish?” leads to taste-based debate instead of measurable criteria.
• Treating content as “someone else’s problem” causes layout churn and delays when copy changes late.
• Skipping stakeholder mapping results in late-stage vetoes from brand, legal, or product.
• Not defining must-keep URLs and redirects early can create avoidable SEO risk and migration confusion.
• Letting scope remain “redesign the site” (instead of pages, journeys, and constraints) makes estimates unreliable.

FAQ

Should discovery include design direction, or only requirements?

Include direction, but anchor it to outcomes and constraints. A redesign preview can help teams react to hierarchy and messaging structure without pretending the visuals are final.

What if stakeholders can’t agree on what “modern” means?

Translate “modern” into criteria: clarity of value prop, hierarchy, trust signals, accessibility expectations, and a primary action that’s obvious. Then collect feedback against those criteria.

Do I need access to analytics and SEO tools before scoping?

It helps, but you can still scope if you’re explicit about assumptions and unknowns. If access isn’t available, add a discovery task to validate priorities and risk areas.

How do I handle “must-keep” elements without killing creativity?

Separate “must-keep” (constraints) from “preferences” (nice-to-have). Constraints protect the business; preferences can be explored through controlled variations.

Where does Revamp fit in this process?

After you’ve captured goals, audiences, and constraints, use Revamp to generate a redesign demo from the current URL, apply design preferences to test direction, and share the live preview link for structured feedback.