Decide with context

A practical library for better digital choices.

Use these frameworks to compare common project paths, understand the trade-offs and recognize when more discovery is needed.

Build Your Project Brief

Five common decisions

Compare the paths before choosing the work.

These are planning frameworks, not universal prescriptions. Constraints, evidence and organizational readiness still determine the right scope.

Brand direction

Brand refresh or complete rebrand?

Choose according to the size of the strategic change, not how tired the current visuals feel.
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

Revisit research, positioning, naming where necessary, verbal identity, visual identity and rollout governance.

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?

Separate visible experience problems from structural platform limitations before defining scope.
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?

The right choice depends on differentiation, workflow complexity, governance and the cost of future change.
Path A

Configured foundation

The journey is conventional, launch speed matters, integrations are simple and differentiation can be achieved through content and disciplined art direction.

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?

Match the engagement to the gap between today’s site and the competitive search environment.
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 retainers should have a visible learning loop. Repeating generic reports without implementation is not a growth system.

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 defensible brief.

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. 03Choose the smallest coherent scope

    Solve the connected problem without adding unrelated workstreams.

  4. 04Define how learning continues

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

Apply the framework

Turn the decision into a structured project brief.

Open Project Planner