Field note

Wood-Shedding the Value Proposition

A value proposition does not need only to be written. It has to be rehearsed against the objections, caveats, proof gaps, and internal disagreements that make it break in market.

Most companies do not have a value proposition problem because nobody has written a sentence.

They have written many sentences.

They have a homepage sentence, a sales-deck sentence, a founder sentence, a customer-success sentence, an investor sentence, and a sentence that only appears when the biggest prospect in the pipeline asks why they should choose this company instead of the cheaper one.

The problem is not shortage. It is rehearsal.

In music, wood-shedding is the private work before the performance. You go to the shed because the thing cannot yet survive being played in public. The phrase is old and plain and useful: you take the part that fails, isolate it, slow it down, repeat it, find the seam, and stay there until your hands can do under pressure what your head already understands.

That is a better model for settling a value proposition than the workshop model most companies keep repeating.

A workshop produces language. Wood-shedding produces reliability.

The sentence that sounds right in the meeting is not the test

A leadership team can make a sentence sound good in a meeting.

That is understandable. Put capable people together, give them a whiteboard, and they can usually produce something plausible. The sentence will include the customer, the outcome, a claim about difference, and perhaps a word that everyone recognizes from the category. It will feel better than what they had before.

That feeling is dangerous because it can arrive before the organization has answered the buying question together.

The test is not whether the meeting likes it. The test is whether the sentence still works when the pressure changes.

Can sales use it when the buyer says the competitor is cheaper?

Can the founder use it without adding three caveats?

Can delivery recognize it as true?

Can marketing build from it without turning it into a cloud of adjacent claims?

Can the leadership team say it the same way two weeks later, when nobody is performing alignment for the facilitator?

Most value proposition language fails there because the organization has moved downstream before the foundational answer is shared clearly enough. The unique value proposition is supposed to carry that answer: why customers buy, stated in a form the business can actually use.

Consistency is not memorization

This is the part people usually misunderstand.

Consistency does not mean everyone recites the same script. That would be brittle and strange, and a good buyer can hear it immediately. The goal is not chorus work.

Consistency means the same decision is visible underneath different explanations.

The CEO may say it one way. The sales lead may say it another. The product or delivery lead may use different examples entirely. That is fine. It may even be necessary. But the buyer should be able to hear the same underlying answer each time: who this is for, what problem it solves, what alternatives it is being weighed against, what outcome matters, and why this company can claim the difference.

If those answers change depending on who is speaking, the company does not have a messaging problem. It has an agreement problem.

Wood-shedding is how that becomes visible before the market punishes it.

The weak spots show up only when the team repeats the claim

The first version of a value proposition often hides its weakest part.

Everyone can say “we save time.” Fewer can say what kind of time, for whom, against which alternative, and how the buyer would know before they buy.

Everyone can say “we are easier to work with.” Fewer can point to the mechanism that makes that true.

Everyone can say “we combine strategy and execution.” Fewer can explain why that is a reason to choose them rather than a reason to worry they are unfocused.

The weak spot appears when the claim is repeated and pressed. Someone reaches for a proof point and finds an anecdote. Someone names the buyer and then quietly expands the audience. Someone describes the outcome in a way the delivery team cannot support. Someone says the old version because it is the one they actually believe.

That is useful information. It is not failure. It is the shed doing its job.

The mistake is to treat the first stumble as a copy problem and reach for better phrasing. Better phrasing can make an unresolved claim sound finished. It cannot make it true.

A value proposition has to be practiced against objections

The reason musicians rehearse is not that they expect ideal conditions.

They rehearse because they do not.

The same is true here. A value proposition that only works when the buyer is already nodding is ornamental. The useful one has to survive the objections that actually appear in the sales conversation.

Why you instead of the cheaper firm?

Why now?

Why not keep doing this internally?

Why not hire the agency we already use?

Why does this matter if we are still growing?

Why should the CEO spend a focused day on it?

Those are not interruptions to the value proposition. They are the places where the value proposition either becomes real or collapses into assertion.

If the team cannot answer them from the same spine, the sentence is not ready.

This is why the working session matters

The wood-shedding metaphor has a limit.

A musician can go to the shed alone. A leadership team cannot. The value proposition belongs to the business, which means the people who hold the business decisions have to rehearse the argument together.

Sales has to hear delivery say what can actually be claimed.

Delivery has to hear sales describe what buyers are really pushing back on.

The founder has to hear where the old story no longer works.

The decider has to rule when the sentence tries to keep everyone comfortable by becoming too broad.

That is the work. Not wordsmithing. Not naming. Not branding. Not the performance of clever language. The work is forcing the claim to survive contact with the people who will later have to use it.

When that happens, the final sentence is almost anticlimactic. It is not magic. It is the record of what the team could keep saying after the easier claims failed.

The practical test

Here is the simple version.

Take the value proposition you think you have and ask five leaders to answer these questions without looking at the website:

  • Who is this most for?
  • What problem are we solving that the buyer already recognizes?
  • What does the buyer choose instead?
  • What outcome makes the difference worth paying for?
  • What proof can we point to without embellishing?
  • Who are we not for?

Then compare the answers.

If the answers are different in language but the same in substance, you may have a usable spine.

If the answers are polite variations on different strategies, the sentence on the homepage is not the issue. The team has not finished the argument.

And if nobody wants to run the test because it will be uncomfortable, that is also an answer.

What the Fit Check can and cannot tell you

The Fit Check will not write the answer for you. It should not. A value proposition produced without the decision-makers would create the same problem in cleaner clothing: language without agreement.

What it can do is read the materials you already use and tell you where the current story is clear, where it is unsupported, and where it starts to contradict itself.

That is enough to decide whether the problem is live.

If the materials already hold, you may not need the session. If they do not, the next useful question is not “what should the words be?” It is whether the people who can decide the answer are ready to sit together and wood-shed it until it holds.

Start there.

Test whether your current materials can survive pressure.

The Fit Check reviews your homepage, supporting pages, and PDFs for clarity, proof, contradiction, and message drift. It will not write your value proposition for you. It will show whether the argument is ready for the working session.

← Field notes