← Latest papers
💻 computer science

Documentless Assessments Using Nominal Group Interviews

This paper introduces a collaborative group interview technique that replaces traditional document-heavy audits with agile-inspired methods, such as user stories and Planning Poker, to facilitate efficient and consensus-driven process assessments.

Original authors: Eduardo Miranda

Published 2026-04-27
📖 4 min read☕ Coffee break read

Original authors: Eduardo Miranda

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The "No-Paperwork" Health Check: A New Way to Fix Broken Teams

Imagine you are part of a professional kitchen. For years, the chefs have been working in chaos. Some use fancy knives, others use dull ones; some follow recipes, while others just "wing it." The kitchen is messy, the food is inconsistent, and the chefs are constantly arguing about whose way is better.

Suddenly, a "Kitchen Inspector" arrives. Usually, an inspector is a nightmare: they walk in with a massive clipboard, demand to see every single written recipe, check every receipt, and grill every chef like they’re in a police interrogation. Most chefs would hate this—they’d hide their mistakes, get defensive, and feel like the inspector is just a bureaucratic nuisance getting in the way of actual cooking.

This paper describes a much better way to do that inspection.

Instead of a "Clipboard Inspector," Eduardo Miranda proposes a "Conversation Coach." Here is how his method works, broken down into three simple ideas:


1. The "User Story" (Turning Boring Rules into Real Life)

In traditional assessments, the inspector uses "Corporate Speak." They might ask, "Do you maintain bidirectional traceability between requirements and work products?"

To a tired developer, that sounds like gibberish. It’s like an inspector asking, "Do you utilize thermal energy to achieve Maillard reactions on your proteins?" You’d just stare at them blankly.

Miranda’s method translates these boring rules into User Stories. Instead of the corporate jargon, he asks: "As a chef, I want to see how a recipe has changed over time so that I don't accidentally add salt when the customer asked for sugar."

Suddenly, everyone understands exactly what is being discussed because it’s about real work, not just rules in a book.

2. The "Planning Poker" (The Secret Ballot)

In a typical meeting, if the Head Chef says, "We follow the cleaning schedule perfectly!" the junior cooks might be too intimidated to say, "Actually, we haven't cleaned the ovens in a month." This is called "groupthink"—everyone just agrees with the loudest person in the room.

To fix this, Miranda uses Planning Poker. Imagine every chef has a set of cards with different faces on them (like "Always," "Sometimes," or "Never").

The inspector asks a question, and everyone picks a card in secret. Then, on the count of three, everyone flips their cards at once. This "Showdown" prevents people from being bullied into agreeing. It allows the quietest person in the room to have as much power as the loudest person.

3. The "Nominal Group Technique" (The Round Robin)

Once the cards are flipped, the "Conversation Coach" doesn't just move on. He uses a structured way to let people talk. He goes around the table—one by one—and asks each person to explain why they picked their card.

It’s like a polite, organized version of a dinner party debate. Because everyone knows they will get their turn to speak, the "loud" people learn to listen, and the "shy" people feel safe to share their wisdom.


The Result: From Fighting to Fixing

The magic of this method isn't just that it finds problems; it’s that it heals the team.

In the case study mentioned in the paper, the developers were skeptical and even angry about being "assessed." But because the process felt like a collaborative game rather than a scary audit, they actually started talking to each other. They stopped arguing about who was right and started agreeing on what the actual problems were.

The Bottom Line:
Instead of using a magnifying glass to find faults, this method uses a mirror to help the team see themselves clearly. It turns a scary "inspection" into a productive "team huddle," helping organizations fix their processes without the headache of endless paperwork.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →