What problem does it solve? Vendor and technology comparisons often collapse into feature matrices that describe what each option is rather than what customers hire it to do. This Skill reframes such comparisons around the customer's Job to be Done, producing solution-free job statements, measurable desired outcomes, competing solutions including non-consumption, and the struggling moment that triggers the search. ## Core Features & Use Cases - Job and outcome statements: Writes solution-free job statements (verb + object + contextual clarifier) and desired-outcome statements (minimize/increase + metric + object of control) following Ulwick's Outcome-Driven Innovation grammar. - Competitive framing with non-consumption: Lists the solutions a customer could hire, including the no-tool status quo, and captures a labeled struggling moment of 30 words or fewer. - Copy-ready output template and verification checklist: Emits one structured block per technology with mandatory fields, plus a checklist that rejects solution language, vague struggling moments, and identical jobs across options. - Use Case: A team choosing between an internal-mobility platform, LinkedIn Recruiter, and a manual agency process uses this Skill to state the job ("fill an open engineering requisition with a qualified internal candidate"), name non-consumption as a competitor, and show that the options serve different jobs rather than ranking them on one feature list. ## Quick Start Use the jtbd-framing skill to reframe my vendor comparison around the customer's job to be done, with desired outcomes, competing solutions including non-consumption, and a labeled struggling moment.
