Design Sprint to MVP: How NovaList Prioritized Features Using Jobs-to-be-Done

Design · 4 min read

Design Sprint to MVP: How NovaList Prioritized Features Using Jobs-to-be-Done

NovaList began with a long backlog of features—shared lists, comments, analytics, templates—after launching an MVP that saw high curiosity but low retention. To focus the team, they ran a two-day JTBD workshop with customer interviews, mapping moments when users "hire" a task manager and what outcomes they actually needed.

The insights were specific: users primarily wanted quick capture for shared commitments and simple visibility into who was responsible today. NovaList prioritized a lightweight 'shared inbox' plus a daily responsibility card rather than building complex comments or analytics. The team used a five-day design sprint to prototype and validate the reduced scope with customers.

The MVP shipped in six weeks and produced a 22% lift in 30-day retention among teams. The refined scope also reduced engineering work by an estimated 40% compared to the original plan, enabling more frequent iteration. NovaList's approach shows how JTBD can be an effective lens for startups to decide what to build first and what to postpone.