Offering-as-object
Offering-as-object is the framing where the provider treats the offering itself as the valuable thing being sold. The app, platform, or product becomes the object customers are paying for access to, and product work centers on building it out: polishing features, adding capabilities, refining the interface. The offering is what the team is grading its work on.
Definition
The default framing in which providers treat the offering as the unit of value — features as what's valuable, the offering as something to sell access to — rather than as a vehicle for the user's transition.
The default substrate of product work
Offering-as-object isn't a competing framework that teams choose; it's the substrate underneath most product work, operating by default until something pulls them out of it. Roadmaps are organized as feature lists. Quarterly planning happens in persona × goal grids. Homepages lead with screenshots of the interface. None of this gets argued for — it's just how the work is set up.
If value is produced by the user's activity rather than by the offering's features, then the offering isn't where value lives, and any framing that treats it as such will misallocate attention. Stepping out of offering-as-object isn't a one-time conceptual move — the default pulls teams back whenever attention slackens, so holding the path framing requires ongoing stance-taking.
Features as the unit of value
The structural commitment of an offering-as-object perspective is that features are what carries value: the offering is a bundle of features, and improving the offering means adding or refining features. Offering-as-paths, by contrast, inverts the unit — transitions become what carries value, and features are evaluated against whether or not they support the user's transition.
The downstream consequences cascade. Object framing produces persona × goal grids — five personas with five goals each generates twenty-five goal-cells, none of which can be committed to without abandoning the others, and planning loses the resolution it needs to make decisions. Path framing groups by intent rather than persona, concentrating investment on intents the team commits to serving deeply.
Where the framing surfaces
Offering-as-object leaves traces that make it diagnosable from outside:
- Marketing collateral: dominated by screenshots of the interface — 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.
- Onboarding as facility tour: new users get walked through the product's features rather than routed to the value they came for.
- Sorting hat slide: a sorting hat that routes users into the offering's preferred paths regardless of what they came pursuing — the instrument operating as sales routing rather than intent detection.
Example
A SaaS company's onboarding takes a new user through a guided tour: here's your dashboard, here's where you manage your team, here's the settings panel, here's the integrations marketplace. The user signed up because they wanted to send their first invoice. None of the tour stops are routing them toward that — they're orienting the user to the offering's structure. Twenty minutes in, the user has been shown the whole product and hasn't sent an invoice. The onboarding was designed to introduce the offering; it wasn't designed to support the transition the user arrived in pursuit of. Object framing all the way down.