The task-technology fit problem
In 1995, researchers Dale Goodhue and Ronald Thompson published a landmark study on task-technology fit—the idea that technology performs best when its capabilities match the requirements of the task at hand. Their research, published in MIS Quarterly, found that mismatched tools don’t just underperform; they actively frustrate users and reduce task completion.
”Performance impacts occur when a technology provides features that fit the requirements of a task.”
Goodhue & Thompson, MIS Quarterly (1995)
This framework explains why the Splitwise-at-dinner moment feels so frustrating. Splitwise is designed for ongoing expense ledgers—tracking who paid for groceries last Tuesday, who covered the electric bill, who owes whom after a week-long vacation. Its architecture assumes you’ll add expenses over days and weeks, settling up periodically.
But at a restaurant, you have a different task entirely: split this specific receipt, right now, before everyone leaves. You need item-by-item assignment (Sarah had the salad, Mike had the steak). You need proportional tax and tip distribution. You need to send payment requests in the next 90 seconds.
Splitwise’s design doesn’t match this task. It doesn’t support item-by-item assignment at all—even with receipt scanning, it only captures the total. And its expense-logging workflow assumes you have time to navigate menus, select groups, and categorize spending.
Source: Goodhue & Thompson, “Task-Technology Fit and Individual Performance,” MIS Quarterly (1995).