The competitive set is bounded by the job, not the category

What it is

The competitor sheet for an expense tool lists other expense tools. What was actually compared that time may have been a shared spreadsheet, asking an assistant to fill it, or slipping it to next quarter. A job-defined competitive set includes every means that was seriously considered in the same hiring, whether or not it belongs to the product category, whether it is software, whether it is “do nothing.” What is being set here is a boundary, not a method for tearing down one rival’s interface.

Why it happens

Category is the seller’s shelf language, handy for spec and price comparison. Hiring happens in the buyer’s moment, and means off the shelf can move the same progress. Nail the set to the category and the strongest substitutes drop out systematically: nonconsumption, another person, a kludge from another category. After the drop-out, the product polishes fields inside the category and still loses to “have the assistant do it,” a zero-UI rival. Once the boundary is cut by job, the list looks undignified—milk and a banana as competitors for the same breakfast job. The undignified look is the point: it is correcting a shelf illusion.

Studying it

In each hiring event, list means the person considered, tried, or later wished they had chosen, and cluster by job rather than by industry code. Measure overlap between the in-category list and the job list; low overlap means category benchmarking is punching air. Track the share of abandonments that went to “do nothing,” “ask a person,” or a cross-category kludge. Outcomes: length of the job list, and the fraction of competitors that sit outside the category.

Where it stops holding

Procurement and tenders may have to compare three vendors inside a named category; that is an institutional set, not a hiring set—keep two lists. Brand strategy may still watch category share; it must not let share stand in for job competition. If the job is drawn too wide (“get work done”), everything competes and the boundary stops being operable; tighten it to observable progress. This entry does not say how to dissect a rival’s information architecture or visuals; that is a different analysis.

Applying it

• Write the progress that had to move that time, then ask the person to enumerate every means they thought of, including people, sheets, and delay.
• Split the competitor table: in-category / same job. Decision material must include the second column, or it is category benchmarking, not job competition.
• If abandonment went to “a person” or “nothing,” write those as formal competitors and give them the same analytic space as a software rival.
• When reviewing a feature list, ask which job-competitor this feature is trying to un-hire. If no off-category name can be given, the set is still nailed to the shelf.

Related

• Same group: Q4.08.1 Attend to what the user hires the product to do · Q4.08.3 The wording slides easily into after-the-fact explanation
• Adjacent: Q2.17 Competitive and benchmark analysis · Q4.09 Opportunity ranking
• Search terms: job-defined competitive set · nonconsumption · jobs to be done competition