Here’s a question most teams never stop to ask: why do we call unfinished work an issue?
Not in the philosophical sense — in the practical one. The word you use to describe your work shapes how your team thinks about it. And if you’ve ever felt like your backlog is a never-ending pile of problems to fix rather than a purposeful plan of things to build, the language your tool uses might be part of the reason why.
This is exactly the territory that Modelithe’s take on why they have no “Issues”, “Tickets”, “Stories”, or “Titles” explores — and it’s one of the more thought-provoking reads we’ve come across in the agile space.
The Baggage Behind Familiar Words
The word issue comes from legal and medical traditions — disputes, complications, things that have gone wrong. When software teams borrowed it, they borrowed all that baggage too. Suddenly your whole backlog is framed as a series of defects, even when you’re building something brand new.
Ticket isn’t much better. It’s a word borrowed from helpdesks and customer support queues — it frames the engineer as a processor and the work as throughput to be cleared. Story has its own problems: a format designed to keep teams user-focused that, in practice, often gets cargo-culted onto infrastructure tasks and refactoring work where it simply doesn’t fit.
And title? A title just tells you what something is called. It tells you nothing about why it exists or what success looks like.
What Happens When You Change the Words
Modelithe replaces all of it with two concepts: Scope and Goal.
A Goal is a single plain sentence answering the only question that actually matters — what does done look like, and why does it matter? Compare these two backlog entries:
- Title: Fix login bug
- Goal: User authenticates with their email without receiving an error on first attempt
The first tells you something needs attention. The second tells you exactly what success looks like and who it affects. That clarity, built in at the moment of creation, changes how the work is planned, discussed, and reviewed.
Creativity and Clarity Are Both Built on Strong Foundations
That the tools and language you surround your work with have a quiet but powerful influence on the outcome. Whether it’s the way you label your supplies, structure a project, or name a track — small framing decisions accumulate into big differences in the finished product.
The same is true for your team’s workflow. When the word you click to add new work is “Increase Scope” rather than “Create Issue,” something subtle but meaningful shifts. The work stops feeling reactive and starts feeling intentional.
It’s a surprisingly compelling read — check out the full article here and see if it changes how you think about the tools your team uses every day.
Leave a Reply