Four Actions Framework (ERRC Grid): A Practical Guide

The Four Actions Framework is a strategy tool for redesigning the factors on which an industry competes. It asks four questions: what should be eliminated, reduced, raised, and created? The answers form an eliminate-reduce-raise-create grid, usually shortened to ERRC Grid.

W. Chan Kim and Renée Mauborgne developed the framework as part of Blue Ocean Strategy. Their official Four Actions Framework guide describes its purpose as reconstructing buyer value while challenging an industry's strategic logic. It is not a generic brainstorming matrix or a guarantee that a company has found an uncontested market.

For founders, the ERRC Grid is most useful when it converts customer evidence into a deliberately different offer—and when every change can be tested.

The four actions, precisely defined

The sequence matters less than the tradeoffs. “Raise quality, create innovation, reduce costs” is not a strategy because it avoids naming what changes. A useful grid identifies specific competitive factors such as setup time, product range, expert support, contract length, customization, status signaling, or buyer effort.

The ERRC Grid complements a Blue Ocean Strategy examples review, which can help you see the broader concept. This page owns the practical query: how to complete and test the grid.

Build the current value curve first

Do not begin with your preferred product. List the factors that shape a real buying decision in the current category.

Use four evidence sources:

1. Recent customer interviews about an actual purchase or workaround.
2. Competitor pricing pages, onboarding, contracts, support, and product limits.
3. Reviews and loss notes that reveal why buyers choose, leave, or do nothing.
4. Delivery economics showing which factors consume money or time.

Create a simple comparison table. Score each factor from low to high only after defining what the scale means.

This is not market research by spreadsheet. The table should point back to customer behavior and source material.

Complete the ERRC worksheet

Write at least one candidate in every box. Then force each candidate into a measurable change.

Eliminate

Ask:

• Which feature exists mainly because competitors have it?
• Which step creates effort without changing the customer's outcome?
• Which promise attracts poor-fit buyers or expensive exceptions?

Test statement: “Remove custom monthly PDFs from the standard package and observe renewal, support, and sales objections among the target segment.”

Reduce

Ask:

• Where does the category over-serve?
• Which choices create complexity buyers rarely use?
• Which service level costs more than the customer values?

Test statement: “Reduce configuration from 20 options to five defaults and measure completion time, corrections, and requested exceptions.”

Raise

Ask:

• Which failure causes the largest customer consequence?
• Which part of the experience determines trust?
• Where are alternatives consistently inadequate?

Test statement: “Raise first-response clarity by giving every alert an owner, source record, and recommended next action; measure resolution without support.”

Create

Ask:

• What job do noncustomers solve outside this category?
• Which new combination removes a tradeoff?
• What would make the offer usable by a previously excluded buyer?

Test statement: “Create a fixed-scope weekly review for customers who cannot staff an internal analyst; test paid uptake and delivery margin.”

A worked startup example

Imagine a small company that sells analytics reporting to independent agencies. Traditional alternatives emphasize broad dashboards, custom reports, many integrations, and annual contracts. Interviews show that the target customer mainly needs to find delivery risks before a Monday client meeting.

Its draft ERRC Grid becomes:

The grid does not prove that the offer will work. It generates a sharper hypothesis: agencies may value an exception-to-action workflow more than a broad reporting platform.

The founder can now test a manual version with five relevant agencies. Customers submit one export, receive an exception list, assign next actions, and decide whether to repeat the workflow. That experiment connects strategy to the product ideation process rather than treating the grid as a presentation artifact.

Score each proposed action

Use a 0–2 score on five criteria:

High scores deserve experiments, not immediate roadmap status. A “create” idea can add more cost than value; an “eliminate” decision can destroy a reason customers buy. Prewrite what evidence would make you keep, revise, or reverse each action.

Turn the grid into a strategy statement

Summarize the choices in one paragraph:

For [specific customer] after [trigger], we will eliminate [factor] and reduce [factor] so the offer costs less or asks less of the buyer. We will raise [factor] and create [factor] to deliver [observable outcome]. We will test this through [experiment] and decide using [evidence].

Then compare that statement with your positioning, operations, and price. If the website says “simple” while delivery remains highly customized, the grid has not reached the business model.

Common ERRC Grid mistakes

Treating every box as “improve”

Eliminate and reduce require real subtraction. Without it, the framework becomes a feature wish list and cannot challenge the cost structure.

Copying famous examples without checking the mechanism

An example may illustrate the framework without matching your customer, regulation, channel, or economics. Use sourced examples to learn the pattern, not to claim that your idea is a blue ocean.

Asking only current power users

Current customers may value the category's complexity. Include noncustomers, lost deals, churned users, and people who rely on substitutes.

Ignoring delivery cost

Buyer value and provider economics must change together. Estimate direct labor, support, failure cost, and implementation work for every proposed action.

Publishing the grid as proof

The grid is a decision hypothesis. Customer commitments, completed workflows, repeat use, and viable delivery provide evidence.

ERRC review checklist

• Competitive factors come from current customer and market evidence.
• Every action names a specific factor and direction.
• Eliminate and reduce choices create meaningful subtraction.
• Raise and create choices connect to an observable customer outcome.
• Cost and operational consequences are explicit.
• Noncustomers and contradictory evidence are represented.
• Each major choice has a small test and reversal rule.
• The resulting value curve differs as a system, not just in one feature.

The Four Actions Framework earns its value when it forces tradeoffs. Build the current curve honestly, make subtraction as concrete as creation, and let a real market test—not the elegance of the grid—decide whether the new value proposition deserves investment.