Skip to content
October 30, 2026

Before You Build: A Prototype Decision Card for Marketing Ideas

Before You Build: A Prototype Decision Card for Marketing IdeasAIM ENGINECREATE · AUTOMATE · AMPLIFYCONTENT DEVELOPMENTBefore You Build: APrototype Decision Card for…EVIDENCE · IDEAS · RESULTSAIM ENGINE JOURNAL38

Before commissioning a plugin, drafting a landing page or automating a workflow, write down the decision the prototype needs to support. Identify the problem, the evidence still missing and the conditions under which you would choose not to build. A short, reviewable brief is a practical starting point; it does not need to become another software project.

The supplied excerpt from AIM Engine’s Prototype Lab describes a controlled space for exploring ideas before changing a live website. It covers pages, blog posts, plugin concepts and workflows. The decision card below is a proposed way to apply that principle—not a description of verified Prototype Lab functionality.

Start with a decision, not a feature list

A feature list describes a possible solution. A prototype brief should first explain why that solution deserves investigation. For marketing leads, editors and website operators—the likely audience, whose responsibilities still need validating—the useful question is: what must we learn before approving more work?

For example, a request for an approval dashboard might conceal several different problems: unclear ownership, missing evidence or uncertainty about who can publish. Each could require a different response. Start by naming the operational difficulty without committing to software.

Then reverse the usual planning sequence. Ask what would justify rejecting the idea. An existing process may already solve the problem, a necessary input may be unavailable, or nobody may be able to own the resulting workflow. These are questions to investigate, not reasons to assume the idea will fail.

Use a compact Prototype Decision Card

The proposed card combines guided questions with explicit space for unknowns. Its purpose is to make an idea reviewable, not to make incomplete evidence look complete. A document or text template is sufficient for an initial trial.

  • Problem and users: What is difficult today, who encounters it and what evidence supports that description?
  • Decision required: What should a reviewer be able to approve, reject or request next?
  • Inputs and outputs: What information is needed, and what should the prototype produce?
  • Hypothesis and evidence gaps: What do you expect to happen, and what remains unknown?
  • Smallest test: What limited activity could challenge the hypothesis without changing production?
  • Acceptance and rejection criteria: What would justify proceeding, revising or stopping?
  • Ownership and approval: Who owns the brief, who reviews it and what is its current approval status?
  • Scope boundaries: What is explicitly excluded, including live-site changes?

Allow answers such as “unknown—requires user review.” Requiring certainty too early can encourage guesses. However, give each important unknown an owner or a next evidence-gathering step so it does not disappear into the brief.

Choose a starting path that matches the work

The Prototype Lab excerpt identifies four types of work. A proposed intake could preserve those distinctions while keeping the core decision card consistent:

  • New page: Outline the audience need, message hierarchy, sections and review requirements.
  • New blog post: Define the reader’s question, evidence plan, draft direction and editorial responsibility.
  • Plugin concept: Describe the operational job before selecting technology or commissioning code.
  • Workflow or app: Map roles, data, states, decisions and approvals.

Provide an example output for each path. If an interactive intake is developed, test whether people can choose the appropriate path and complete it using a keyboard. The supplied excerpt does not establish the current interface’s accessibility or navigation quality.

Hypothetical example: test an editorial handoff before automating it

Hypothetical example: An editor proposes an automated handoff from article planning to review. No such implementation or result is established here.

The decision card might describe the suspected problem as uncertainty about whether a draft has enough evidence for review. Its hypothesis could be that a shared brief containing evidence gaps, an owner and an approval status makes the handoff clearer.

The smallest test would be a manually completed card used during a limited editorial exercise—not an integration with the live website. Reviewers would check whether they can identify the next decision and the person responsible. A rejection condition might be that the existing editorial checklist already provides the same information and the additional card duplicates work.

The approval boundary would remain explicit: permission to test the brief does not authorise publication, automation or production access.

Measure the pilot without treating targets as results

Before testing the card, record how comparable briefs are currently produced. Useful baseline measures include completion time, missing required information and clarification rounds. Keep task scope comparable when interpreting differences.

A proposed pilot could involve five representative users. Observe whether they complete the card unaided, identify confusing prompts and audit each output for ownership, evidence gaps, acceptance criteria and approval status. Four of five completing unaided could serve as an initial usability target; every card retaining its approval boundary should be a separate requirement.

These are proposed thresholds, not observed outcomes. A small pilot can reveal practical problems, but it cannot establish broad demand or guarantee less rework. Review whether shorter completion times come at the expense of useful detail.

Connect systems only after the brief proves useful

Begin with a portable text export rather than assuming integrations exist. If briefing or task capabilities are later verified, investigate whether they can reuse the same information without duplicate entry. Check that ownership, unresolved assumptions and approval status survive any transfer.

An approved brief could also be adapted for supplier comparison by adding scope, exclusions and acceptance tests. That is a proposed secondary use; supplier usefulness still needs testing. Avoid early stack selection and production credentials unless an approved next stage genuinely requires them.

The immediate next step is modest: trial one decision-card template, review the ambiguities it exposes and revise it before building an interface. The goal is a clearer basis for deciding what deserves production work—and what should remain an idea.

JOIN THE EVIDENCE

Add an example, conclusion or question.

Short, specific responses help AIM Community improve future articles and product decisions.

Your response