Stop building products nobody adopts

Run the POLE audit to surface which value layer — acquisition, liberation, or retention — is missing or misaligned

Separate what looks impressive in a demo from what users actually perceive as valuable before signing up

Identify the single missing layer blocking adoption, retention, or pricing power — before you invest further.

Use the Obvious & Immediate (O) framework to design value a prospect grasps before experiencing the product — no explanation needed.

Build Embedded (E) value that rewards users for staying — the kind that drives long-term retention without constant re-acquisition spend.

Mixing the two is the most reliable way to build a product that neither acquires nor retains. POLE makes the distinction structural.

Map the real switching costs — financial, relational, habitual — invisible forces keeping users from your product even when they want it.

Design specific hooks: risk reversal, convenience bridges, incentives — built for the specific lock-in your users face, not generic offers.

Without L, even the best O fails. Users are interested but never convert. POLE names this gap and shows you how to close it.

Define the enduring benefit users want over time. This is P — the north star that prevents roadmap drift and keeps brand positioning honest.

Use the P stress test to prevent the most common failure: drifting into mission-statement language that sounds good but predicts nothing.

Leadership alignment becomes easier when the roadmap is grounded in a Persistent VP — not a feature list or a quarterly theme.

Classify any AI feature across POLE: is it an acquisition tool (O), a switching bridge (L), or a retention driver (E)?

The most common AI product failure is leading with intelligence — an Embedded value — when users need something Apparent before sign-up.

Design AI features that are explainable and trustworthy. 'Smart' is not a value proposition. POLE shows you what actually is.

Use the 30-Second POLE Check before shipping any feature, writing any copy, or prioritising any roadmap initiative.

Run the O/L/E classifier in real-time product reviews — no slides, no frameworks document required

When your team starts saying 'strong E, weak O' in standups, the framework has become a shared language. That is the goal.