Offering-as-paths
Offering-as-paths treats the product as paths users take on the way to something they want in their own lives, rather than as an object the company sells access to. Whatever a user is doing inside the product, they're using it to get somewhere else. The product is what they're moving through, not where they're going.
Definition
The provider framing that takes the user's transition as the unit of value, with the offering as a vehicle the user moves through to produce that transition.
Transitions as the unit of value
If users produce value through their own activity and the offering is one of the vehicles that supports that activity, then the offering can't be the unit of value. The user's transition is.
The contrast that gives the framing its bite is offering-as-object — the default in most product work, where features are treated as the unit being sold and the offering as the unit of analysis. Offering-as-paths operates as an active stance the team maintains against that default, which reasserts itself constantly in product work. The framing has to be held, not adopted once.
Planning by intent
Object framing produces persona × goal grids. Five personas with five goals each generates twenty-five cells, none of which can be committed to without abandoning the others, and the planning conversation loses the resolution it needs to make decisions.
Path framing groups by intent instead. A designer and a developer pursuing the same sought state are on the same path; their demographic differences are secondary. One person can hold multiple intents at different moments. The planning unit becomes the intent the offering is built to serve, and the strategic move is deep commitment to a few intents the team is positioned to serve well.
The marketing diagnostic
A reliable surface signal of which framing a team operates from is what their marketing collateral shows. Object-framed marketing is dominated by screenshots — the offering as the thing being depicted. Path-framed marketing depicts users in their transition, with the offering as one element in a larger scene. The shorthand is "what users look at while using the offering" versus "what users look like while using the offering." The ratio between these in a company's marketing tracks which framing the team operates from, largely independent of what the copy otherwise claims.
Example
A project management SaaS operating offering-as-object builds around its features. Gantt charts, dashboards, integrations. The website hero is a product screenshot. Roadmap planning happens across a persona × goal grid: founder, PM, engineering manager, each crossed with goals like "track work," "report status," "plan sprints." Marketing copy talks about what the product does.
The same team operating offering-as-paths builds around what users are trying to accomplish. A PM delivering a project on time across a distributed team; an engineering manager keeping stakeholders informed without writing five status updates a week. Roadmap planning commits deeply to specific intents the team is positioned to serve. The website hero shows a PM at work, with the product visible on a laptop next to a calendar, a Slack thread, and a printed sprint board. The offering is one element the user assembles, and the team plans accordingly.