Decide with context

A practical library for better digital choices.

Compare common project options, understand the compromises and see when more research would help you decide.

Build your project brief

Five common decisions

Compare the paths before choosing the work.

These comparisons are a starting point, not a fixed answer. The right scope depends on the evidence, your constraints and what your organization is ready to do.

Brand direction

Brand refresh or complete rebrand?

Base the decision on what has changed in the business, not just whether the visuals feel dated.
Path A

Refresh

The offer and audience remain relevant, recognition has value, and the main problem is inconsistency or dated execution.

Likely scope

Refine identity rules, typography, colour, templates, messaging hierarchy and digital application.

Path B

Rebrand

The business model, audience, positioning or reputation has materially changed and the existing identity reinforces the wrong meaning.

Likely scope

Review the research, positioning, name where necessary, language and visual identity. Agree who will manage the introduction of the new brand.

Decision caution: Do not discard existing recognition merely to look new. Equally, visual polish cannot repair an unclear proposition.

Explore the relevant service

Website investment

Website redesign or technical rebuild?

Work out whether the problem is how the site looks and works for visitors or a limitation of the platform itself.
Path A

Focused redesign

The platform is secure and maintainable, content models still fit, and the main issues are clarity, visual hierarchy or conversion flow.

Likely scope

Improve information architecture, page composition, interaction patterns, accessibility and conversion paths on the existing foundation.

Path B

Technical rebuild

The site is difficult to maintain, structurally inflexible, slow because of its architecture, or unable to support required integrations.

Likely scope

Redefine content models, templates, performance architecture, integrations, migration and release quality controls.

Decision caution: A rebuild should solve verified platform constraints. It should not be used as an expensive substitute for content decisions.

Explore the relevant service

Delivery model

Template website or custom development?

Consider what makes your business different, how the site needs to work, who will manage it and the cost of future changes.
Path A

Configured foundation

A standard website structure meets your needs, a quick launch matters and integrations are straightforward. Content and visual design can provide the distinction you need.

Likely scope

Use a carefully selected foundation with controlled customization, performance review and clear ownership.

Path B

Custom system

The experience, content model or operational workflow is central to the proposition and cannot be expressed responsibly with a standard structure.

Likely scope

Design components and content architecture around the real user journey, with maintainable code and documented behaviour.

Decision caution: Custom code is not automatically better. It earns its cost only when it supports a requirement the simpler route cannot meet well.

Explore the relevant service

Search investment

SEO foundation project or ongoing SEO?

Choose the level of support according to your site’s current condition and the competition for relevant searches.
Path A

Foundation project

The site needs technical cleanup, clear page targeting, measurement, internal linking and a credible initial content map.

Likely scope

Establish crawlability, page purpose, metadata, structured data, measurement and a prioritized implementation roadmap.

Path B

Ongoing programme

Search demand, competition and customer questions change continuously, and the team can publish, improve and promote useful material over time.

Likely scope

Combine technical monitoring, content improvement, new authority assets, digital PR and evidence-led iteration.

Decision caution: Ongoing support should turn findings into improvements. Repeating generic reports without acting on them does not help the site grow.

Explore the relevant service

Project readiness

Is the project ready to begin?

A short definition phase is often more valuable than forcing an uncertain brief directly into design and development.
Path A

Ready for delivery

The decision owner, audience, priority outcome, required capabilities, content responsibilities and approval process are understood.

Likely scope

Confirm assumptions, success signals, scope boundaries, delivery sequence and ownership before production begins.

Path B

Start with discovery

Stakeholders disagree on the goal, the audience is broad, content ownership is unclear or requested features are not connected to a customer need.

Likely scope

Run focused interviews, journey mapping, evidence review and prioritization to produce a brief supported by evidence.

Decision caution: Discovery should reduce uncertainty and end with decisions. It should not become an open-ended research phase without ownership.

Explore the relevant service

A better decision process

Four checks before committing budget.

  1. 01Name the customer decision

    Define what someone should understand or do differently.

  2. 02Separate evidence from assumptions

    Record what is known, what is inferred and what still needs testing.

  3. 03Keep the scope focused

    Include the work needed to solve the problem without adding unrelated tasks.

  4. 04Plan what happens after launch

    Agree what will be measured, reviewed and improved after launch.

Apply the framework

Turn the decision into a structured project brief.

Open Project Planner