Skip to content

Shipping vs Talking — How to Tell If You're Actually Building Something

Department of Product and Project Management | Level: Beginner | Duration: 20 minutes

After this lesson, you will be able to:

  • Apply the BS Test to any product pitch, roadmap, or strategy document
  • Distinguish real communication from buzzword padding
  • Write a clear one-pager that a stranger could act on
  • Separate metrics that matter from vanity metrics

Here is a sentence from a real product document (names changed):

“We are leveraging our synergistic platform capabilities to create a best-in-class, AI-driven solution that empowers stakeholders through transformative digital innovation.”

Quick quiz: What does this company actually do?

If your answer is “I have no idea,” congratulations — your BS detector is working. That sentence says absolutely nothing. It contains zero information. You could paste it into any company’s website and it would fit, which is exactly the problem.

Most product work does not fail because people are stupid. It fails because people talk instead of ship, and nobody notices because the talking sounds productive.

This course is about telling the difference.


Every claim, plan, or strategy can be evaluated on four dimensions:

Does it name concrete things? Names, numbers, dates, features, users.

  • Failing: “We’re improving the user experience.”
  • Passing: “We’re reducing checkout page load time from 4.2s to under 1.5s by March 15.”

Could you prove it wrong? If a statement cannot possibly be false, it contains no information.

  • Failing: “We’re committed to excellence.” (What would non-excellence look like? How would you know?)
  • Passing: “We’ll ship the MVP to 50 beta users by Friday.” (Either you did or you didn’t.)

What is the ratio of information to words? Every word should earn its place.

  • Failing: “In order to facilitate the ongoing process of continuous improvement in our product development lifecycle…” (18 words, zero information)
  • Passing: “We ship weekly.” (3 words, clear commitment)

Does it bind someone to something? Vague intentions are free. Commitments have consequences.

  • Failing: “We should probably look into that at some point.”
  • Passing: “I’ll have the spec reviewed by Thursday. If it’s not ready, we push the sprint.”

Find the last email, Slack message, or document you wrote about a project. Run it through all four dimensions. Be honest. If it fails two or more, rewrite it.


These words and phrases are not inherently bad, but they are almost always used to avoid saying something concrete. When you catch yourself writing them, stop and ask: “What do I actually mean?”

Buzzword What People Usually Mean What to Say Instead
Leverage Use “Use”
Synergy Two things work together Name the two things and how
Transformative It changes stuff Say what changes, for whom
Best-in-class Good, allegedly Compared to what? By which metric?
Empower Give someone the ability Name the ability and the someone
Holistic We considered more than one thing List the things you considered
Align Agree “We agreed that…”
Deep dive Look at carefully “We analyzed X and found Y”
Move the needle Improve a metric Name the metric and the target
Ecosystem A group of related things Name the things

The rule is simple: if you can replace a word with a more specific one and lose nothing, do it. If you cannot think of a more specific word, you might not know what you are talking about yet — and that is fine, but say that.


A one-pager is the minimum viable document for any product decision. If you cannot fit it on one page, you either do not understand the problem or you are solving too many problems at once.

Title: [What you are building, in plain language]

Problem: [1-2 sentences. Who has this problem? How bad is it? How do you know?]

Solution: [1-2 sentences. What you will build. Not how — what.]

Success metric: [One number that tells you if it worked. Be specific.]

Scope: [What is IN. What is explicitly OUT.]

Timeline: [When it ships. Not “Q3” — a date.]

Open questions: [What you don’t know yet. This is the most honest section.]

Hand your one-pager to someone who has never heard of your project. Can they answer these questions after reading it?

  1. What problem does this solve?
  2. For whom?
  3. How will you know if it worked?
  4. When will it be done?

If the answer to any of these is “unclear,” revise.

Pick something you are currently working on. Write a one-pager using the template above. Time yourself — it should take 15 minutes or less. If it takes longer, that is diagnostic: you may not have clarity on the problem yet.


A vanity metric makes you feel good. A real metric helps you make decisions.

Ask: “If this metric changes, will I do something different?”

If yes, it is a real metric. If no, it is vanity.

Vanity Metric Why It’s Vanity Real Alternative
Total registered users Only goes up. Never tells you if people actually use the product. Weekly active users (WAU)
Page views High traffic means nothing if nobody converts. Conversion rate
Lines of code More code is not better code. Defect rate per feature
Number of features shipped Shipping garbage quickly is not an achievement. Feature adoption rate (% of users who use it)
Social media followers Followers do not pay bills. Revenue per customer
Meetings held Activity is not progress. Decisions made and implemented

Look at your team’s dashboard. For each metric, ask:

  1. When was the last time this number changed a decision?
  2. If this number doubled overnight, what would you do differently?
  3. If this number dropped to zero, would anyone notice within a week?

If you cannot answer these, the metric is decoration.


Talkers optimize for sounding smart. Shippers optimize for learning fast.

Talker Pattern Shipper Pattern
“Let’s schedule a meeting to discuss the roadmap.” “Here’s the spec. Comments by Thursday, shipping Monday.”
“We need to do more research.” “We’ll ship a v1 to 10 users and see what happens.”
“This needs to be perfect before we launch.” “What’s the smallest thing we can ship that teaches us something?”
“I have concerns about the approach.” “Here are three specific risks and my proposed mitigations.”
“Let’s align on the vision.” “Here’s the one-pager. Do you agree or disagree with the success metric?”

The difference is not intelligence or effort. It is the willingness to be specific, to commit, and to be proven wrong.


Term Definition
BS Test Four-dimension evaluation: specificity, falsifiability, density, commitment
One-pager A single-page document that captures problem, solution, metric, scope, and timeline
Vanity metric A number that feels good but does not inform decisions
Falsifiability The property of a claim that makes it possible to prove wrong
Shipping Delivering working product to real users (not demoing, not presenting, not planning)

1. A colleague says “We need to leverage our platform to drive synergistic outcomes.” What do you do?

Ask: “What specifically are we building, for whom, and how will we know it worked?” Do not accept an answer that fails the BS Test.

2. Your dashboard shows “Total Users: 50,000” and it has gone up every month. Is this a good sign?

Not necessarily. Total users only goes up (people rarely un-register). It tells you nothing about engagement, retention, or value. Ask for weekly active users or retention rate instead.

3. You have a great product idea but your one-pager is three pages long. What does this suggest?

You are probably solving more than one problem, or you do not yet have clarity on which problem matters most. Split it up or sharpen your focus.

Pass criteria: Can apply the BS Test to a real document, write a one-pager under 15 minutes, and explain why at least two vanity metrics are misleading.


  • Falsifiability framework draws on Karl Popper’s philosophy of science, applied to product thinking
  • Vanity metrics concept popularized by Eric Ries, The Lean Startup (2011)
  • One-pager format influenced by Amazon’s “Working Backwards” document culture
  • Information density principles from George Orwell’s “Politics and the English Language” (1946)
  • Belief state: T(0.80) F(0.03) U(0.14) C(0.03)