Idea Catalogue

Ideas for better demand-driven commerce

A growing set of practical ideas for specification journeys, product information, capability, constraints and commercial improvement.

Each entry states a commercial problem, how to address it, what could go wrong, and what you would have to measure to know whether it worked. These are published in full. They are a selection: ideas made specific to one customer, and what we keep internal, are not published here.

Nothing here is presented as a proven result. Every idea carries a label saying how well supported it actually is, and the strongest of those labels is not currently in use by anything.

What is published here

This is a selection, not the whole catalogue

The ideas below are published in full and are meant to be usable exactly as written. An idea can sit at one of three levels, and only this one is public.

  1. Published

    What is on this page. Chosen because it holds up without knowing anything about your business, and because publishing it costs nothing we are not willing to give away.

  2. Shared with customers

    An idea made specific to one business during an engagement, worked against its own catalogue, capability model or constraints. It belongs to that business and is shared only with it.

  3. Internal

    What we keep back: commercially sensitive work, ideas that are really product direction, and open questions we have not resolved well enough to hand to anybody.

An idea only moves toward this page by being rewritten as a general pattern. The details of the business it was made for stay with that business.

How to read these

Every idea says how well supported it is

The label is the most important field on each entry. It is also the one most catalogues leave out, which is why they all read as equally confident.

Established practice
Widely and independently practised across commerce. Nothing here is a Specify discovery; these are the ideas most likely to be uncontroversial and least likely to be exciting.
Context-dependent
The reasoning is sound and the outcome genuinely depends on your business, your customers and your production. Worth testing rather than adopting wholesale.
Hypothesis
Specify's argument, untested by us or anyone else we can cite. Treat it as a position somebody should try to falsify.

Difficulty is an initial editorial assessment of how much work an idea usually takes, not a guaranteed estimate for your systems. A change that is small in one storefront can be significant in another because of where the data lives.

12 ideas

Showing 12 ideas.

Established practice Specification journeys

Ask the next missing question

When a request cannot yet be evaluated, ask for the specific missing information instead of returning a generic rejection.

Difficulty Moderate

Established practice Customer intent

Capture no-result demand

Record what the customer was trying to find when search, filters or configuration produced no valid result.

Difficulty Small

Established practice Delivery

Explain which options affect delivery

Expose the dimensions, materials or choices that materially change the lead time, at the point the choice is made.

Difficulty Moderate

Context-dependent Constraints and approval

Separate possible from approved

Make it explicit when an outcome is technically plausible but still requires human review or commercial approval.

Difficulty Moderate

Context-dependent Specification journeys

Show acceptable alternatives

When an exact result is impossible, explain which requirement could change and what becomes available if it does.

Difficulty Moderate

Hypothesis Constraints and approval

Record the reason for rejection

When a request is refused, record the governing constraint, so repeated unmet demand becomes visible instead of anecdotal.

Difficulty Moderate

Context-dependent Experimentation

Prepare experiments from audit findings

Convert an observed problem into a hypothesis, a proposed change, a metric and a review, before anybody builds anything.

Difficulty Moderate

Established practice Specification journeys

Design for specification abandonment

Find the question or stage where customers stop, and establish whether it is unclear, premature, intrusive or simply unnecessary.

Difficulty Small

Context-dependent Product information

Make product imagery answer a question

Choose and commission images based on what customers need to understand, rather than on what photographs well.

Difficulty Depends on systems

Context-dependent Constraints and approval

Bring constraints into the customer journey

Communicate meaningful limitations early enough to prevent a false expectation, without burying the customer in caveats.

Difficulty Moderate

Where the ideas come from

An idea is not the end of the process

The catalogue is the written output of a cycle that runs continuously, and entries change as the later stages produce evidence.

An idea
A merchant's actual context
Consulting or implementation
An experiment or an observation
Recorded learning
A refined idea, or a platform standard

An entry that has been through the whole cycle would carry a stronger evidence label and a citation. None of them have yet, which is why none of them do.

From idea to implementation

An idea is not a plan for your business

Everything above is written to be general, which is exactly what makes it insufficient on its own. What an idea is worth depends on your catalogue, your production constraints, who has authority to approve what, and which of these problems you actually have. Consulting is where an idea is tested against those facts and turned into something specific: an investigation, a capability model, a built component or integration, a governance decision, or the conclusion that it does not apply to you.

Start with evidence

Or see it running first

The demo store runs on this site. A customer describes what they need, and the store answers. It costs nothing to try.