A Purchasing Decision Framework – Balancing Values and Viability

What This Framework Is For

This framework helps you work through purchasing and resourcing decisions when values and viability appear to be in tension.

It is designed for projects, organisations, and initiatives, not just personal consumption.

Step 1: Name the Actual Decision

Start by being specific.

Ask:

Example:

Clarity prevents moral fog.

Why This Matters

Abstract decisions invite abstract guilt.

Specific decisions allow:

You cannot design viability around a feeling.

Step 2: Identify the Role of the Purchase

Ask:

Different roles require different standards.

Example: Personal vs Project Decisions

Buying ethical food for yourself and choosing a supplier for a public resource are not the same decision.

One affects you.
The other affects everyone downstream.

Treat them differently.

Step 3: Clarify the Constraints

Before judging options, name constraints clearly.

Ask:

Constraints do not negate values.
They define the design space.

Example: Hidden Constraint

A supplier may be “affordable once” but unsustainable if used regularly.

Viability is tested by repetition, not intention.

Step 4: Map Real Options

Avoid false binaries.

Ask:

If only one option is visible, zoom out.

Funding Change: Collective vs Individual

Shift from supplier identity to system effect.

Ask:

Ethical labels alone do not guarantee ecosystem impact.

Important Clarification

Buying from a worker co-op does not automatically create an ecosystem.

If there is:

then it may still be a one-way transaction.

This is not a failure.
It is a fact to design around.

Step 6: Test for Repeatability

Ask:

If not, it may be symbolic rather than structural.

Step 7: Decide on Sequencing

Now make timing explicit.

Ask:

Viability is often about order, not abandonment.

Step 8: Make the Trade-Off Explicit

Name what is happening.

Ask:

Clarity replaces guilt.

Mini Worked Example

A project wants to print educational material.

Option A:
A values-aligned printer costs six times more, with no shared structure or return flow.

Option B:
A cheaper supplier allows wider access, keeps the project solvent, and enables future scaling.

Decision:
Choose Option B now, document the reasoning, and revisit aligned options when volume or partnerships change.

This is sequencing, not contradiction.

Step 9: Decide Whether to Document

Sometimes it helps to record the reasoning.

This:

Not every decision needs broadcasting, but patterns are worth naming.

Step 10: Set a Revisit Point

Avoid permanent compromise by default.

Ask:

Values need time and structure to act.

How to Use This Framework

Use this framework:

It is not about being perfect.
It is about being deliberate.

Share this carousel