An idea without a name: separating the assessment from its author's reputation
Decide what reviewers need to know before an idea is attributed. Preserve context, assess the concept separately from delivery, and check the information submitted for review.
Article language: English

In this article
Two concepts arrive for review. One carries the name of a respected partner; the other comes from someone who has only just joined the company. Before describing the differences between the solutions, the team begins discussing whom it trusts. Information about the authors may be needed later. First, it is worth asking exactly what it is supposed to explain in an initial assessment of the ideas.
Suppose a company that provides product training for shops wants to change how participants prepare for a session. A well-known consultant proposes a short pack of material before the training. A new member of the customer service team proposes collecting one example from each shop in advance. The company first wants to assess how both directions address the problem. It will discuss the provider's experience and the cost of taking the work further at the next stage.
Removing the names can be one way to organise the first reading. It does not by itself guarantee a better decision. You need to decide what information to retain, what to assess and when to return to the question of authorship. Taking a name off the cover does not make two unevenly described ideas comparable.
Name the assessment you want to make
Recognising a concept's potential and choosing who will carry it out are different decisions. The first asks how the solution relates to the problem and what needs to be checked. The second also involves skills, availability and the terms of a particular collaboration. The team should know which task it is performing before deciding whether to hide information.
In our example, the company wants to spend less training time explaining the basics. It does not yet know whether the problem comes from a lack of material or from overlooking the shops' questions. Both concepts may be useful directions. The consultant's name does not establish which uncertainty matters more to the session.
Prepare the same scope of description for each proposal. What is the participant meant to do before the training? What does the trainer receive? What conditions must be met to test this direction? Do not demand identical solutions or the same number of slides. You need comparable information about the task, not a contest in filling out boxes.
Clarify the criteria as well. If you are assessing the chance to understand the shops' questions, say so before reading. If the priority is preparing a participant for a particular part of the session, that is a different assessment. A broad label such as "quality of the idea" can hide several different questions that only emerge when ratings disagree.
You can have this discussion after brainstorming and developing alternatives (in Polish). It is no longer about the number of new ideas. It is about how the material is read. Developing proposals independently and removing names during assessment are separate choices. You may need either one, both or neither.
In an open competition to solve a problem (in Polish), the distinction becomes especially clear. A first reading may concern the proposal; a later stage may require information about a team's capacity to do the work. Do not quietly change the criterion from the merit of the solution to the provider's reputation while keeping the old name for the assessment.
Research offers no single promise of anonymity
In a 2023 experiment by Dahlander and colleagues, managers at a technology company evaluated early ideas with or without information about the proposer. For the studied differences involving gender, organisational unit and location, the expected improvement from hiding that information was not found. An additional online experiment supported the main result. Removing a name should therefore not be sold as a guaranteed effect.
A different context appears in a 2022 study by Huber and colleagues. In an experiment reviewing the same academic paper, the visible author information was changed: a prominent author, a little-known author or an anonymous version. Assessments differed between those conditions. This concerns a particular paper and scientific peer review, not a measurement of how Polish companies select concepts.
Together, the studies show why a company should name its own problem. Perhaps the team reaches for a name before an argument. Perhaps it separates the idea from its author well, but the descriptions are too thin. Changing signatures will not supply missing information about the task. The first assessment also needs to examine the quality of the material submitted.
In their discussion of the findings, Dahlander and colleagues distinguish evaluation of early ideas from their final selection when resources are limited. Their company experiment concerned the initial stage. That is an important boundary for your own use: a good first assessment does not settle the decision to implement an idea.
At the training company, one proposal might score highly for its connection to the problem and still need a capability the current team lacks. Another might be easier to prepare but fail to address an important question. Record both facts separately. There is no need to revise the first assessment retrospectively just to justify a later choice.
Remove the name, keep the necessary context
When preparing the first reading, retain the description of the intended use and assumptions. If the new employee knows recurring shop questions from daily customer service, the list of those questions may itself be useful. It need not disappear with the name of their department. Reviewers should know what observation supports the concept, even when they do not know its author.

Agree on a common level of preparation too. The consultant might provide a polished presentation while the employee offers a few sentences in a message. Whoever prepares the review material should preserve the meaning of both ideas. They may organise the descriptions, but should not secretly develop one and reduce the other to a slogan. Before the first assessment, check with the authors that the material still represents their proposals.
For example, the consultant's presentation has fourteen slides and the employee's message has 180 words. The person coordinating the comparison selects a description of the participant's activity and the benefit expected by the trainer from each. The first proposal answers both questions. The second does not say who will collect the shops' answers. Rather than assign the employee an extra task, the coordinator sends that specific question back to them.
The author may turn out to be assuming use of an existing form the consultant does not know about. If both concepts could use it, the information should enter the comparison as an available company resource. It should not remain a secret advantage for the person inside the organisation. At the same time, do not attribute an intention to use the form to the consultant if they did not propose it. Separate the conditions of the task from the description of the chosen solution.
Keep the original material separate from the version prepared for reading. That lets a later question refer back to the correct content. If someone added a condition while editing the common comparison, its origin should be known. Do not assess as the author's idea a solution that appeared only while the comparison was being edited.
Concealing information also has a particular scope in a tool. Miro's private mode documentation distinguishes temporarily hiding content from an option to keep authors' names hidden after notes are revealed. It also warns that the mode is not a data protection feature. Establish which behaviour was selected instead of relying on the word "private" alone.
Do not promise participants that a name will return later until you have checked the chosen mechanism. In an ordinary file, information about origin may also remain in a heading, a note or the text itself. In a small team, style and familiarity with a project may point to the author. A first reading without a name is a particular way of presenting material, not a guarantee that the person cannot be recognised.
When using AI, inspect the instruction as well. If it still says "this is a proposal from our most respected partner", removing the name from the attached description does not remove that information from the entire input. Decide what material the tool should assess and who will read its reasoning. An "anonymous" label above a task does not describe the data actually submitted for evaluation.
Aeneia Audit can trace that flow: where the material comes from, what a person sees and what reaches the AI tool. The work concerns the particular assessment process and checks on the result. Organising the input does not replace the company's decision about criteria and selection.
Authorship returns when the next decision needs it
After the first reading, you can reveal the authors and ask separate questions about delivery. The consultant may have material ready and time to prepare a trial. The employee may need the trainer's involvement and data from the shops. Those facts matter when organising the work. You do not need to ignore them to make the earlier assessment of the direction fair.
The company chooses first to test the idea based on the shops' questions, even though it rated the consultant's material as more ready. The reason is the chance to understand the cause of recurring questions, not an assumption that the new employee will run the training alone. The trainer helps prepare the trial. Both findings remain in the decision record: the proposal may provide missing knowledge, and support is needed to carry it out.
If someone changes their assessment of the concept's connection to the problem after names are revealed, ask what new information supports the change. Learning that the author has access to data may justify changing a feasibility assessment. Merely recognising a familiar name does not yet explain why participants will be better prepared for the session. Recording the reason helps distinguish new information from a return to the first reaction. It does not require pretending that experience and trust are irrelevant.
When considering team composition and combining skills (in Polish), establish what capability the author brings and what the proposal requires. An idea alone does not prove readiness to perform every stage. Equally, lack of experience running a training session need not eliminate a useful observation from someone in customer service. The company can develop that observation with the right people.
When moving on to assessing scope and choosing a provider (in Polish), prepare that assessment with appropriate information about the entity. A first reading of the concept without a name does not replace checking skills, availability or the terms of collaboration. It should be clear when the process moves to that decision and what will support it.
Record feedback against a specific passage and question, as in giving critical feedback on an expert's work (in Polish). Once the author is known, you can clarify their intention, but the discussion need not become a defence of reputation. "What should the participant prepare?" remains a question about the solution, whoever proposed it.
At the end, keep two answers: how the direction was assessed on the material presented, and why a particular next step was chosen after the conditions for delivery became known. They may differ without either being wrong. The company should be able to explain the difference. The author's name can then return to its proper role, instead of choosing the winner first and waiting patiently for arguments afterward.






