3 Questions Every New Design Engineer Asks. And Nobody Can Answer Quickly.
A new design engineer joins the team. Day one. Motivation high, knowledge low. And then come the questions.
Why was that decision made back then? Which standard applies here? Has someone built this before?
Three questions. Every day. From every new team member. And the answers? They're buried somewhere in project folders, in the minds of experienced colleagues, or in SharePoint structures that nobody has touched since 2017.
The problem isn't missing knowledge. The problem is that nobody can find it fast enough.
The Onboarding Problem in Engineering Design
In hardly any department is experiential knowledge as valuable as in engineering design. Every decision builds on previous projects. Every tolerance, every material choice, every standards reference has a history.
New employees know this. That's why they ask. But the answers cost time. Not their own, but that of experienced colleagues who are actually working on ongoing projects.
Every question from a new engineer costs a senior colleague an average of 15 to 30 minutes. With three questions per day, that's over 300 lost hours per year. Per new employee.
Most companies accept this as a given. Onboarding just takes time. Six months, sometimes twelve, until someone is truly productive. But does it have to be this way?
Why Traditional Solutions Don't Work
Everyone knows the usual approaches. Set up a wiki. Maintain a folder structure. Write a handbook.
The problem: These systems only work if someone maintains them. And if the new employee knows where to search. In practice, both rarely happen.
Wikis become outdated after three months. Folder structures grow uncontrollably. And nobody reads the handbook because it doesn't answer the specific question about the current project.
What's missing isn't a better filing system. What's missing is a system that understands questions and delivers matching answers from existing documents.
The Three Core Questions in Detail
"Why was that decision made back then?"
Behind every design decision lies context. Perhaps a customer requirement. Perhaps a manufacturing restriction or a supplier failure. This context is rarely documented. It lives in emails, meeting notes, and the memory of individual people.
When these people leave the company, the knowledge disappears. Irretrievably. What remains is a CAD model without explanation.
"Which standard applies here?"
DIN, ISO, EN. The standards framework in mechanical engineering is enormous. New engineers often don't even know which standard might be relevant. Let alone what the current version says.
Searching for the right standard doesn't cost minutes, but often hours. And if the wrong standard is applied in the end, it costs significantly more.
"Has someone built this before?"
The most valuable resource in an engineering department is completed projects. Every solved problem, every proven solution saves time and errors next time. But only if you know about it.
In reality, new engineers often start from scratch because they have no access to relevant predecessor projects. Not because the data is missing. But because it can't be found.
How KoAssist Solves These Questions
KoAssist by Soneo AI does exactly that: It searches existing project documentation, standards, and internal knowledge bases. An answer arrives in seconds. With source references.
No new system that needs maintenance. No complex data migration. KoAssist works with the documents that already exist. PDFs, technical drawings, data sheets, internal standards.
The crucial point: Every answer is traceable. The engineer sees where the information comes from and can decide for themselves whether to trust it. No black box, no hallucinations without context.
The fastest way to build new knowledge isn't reading more. It's asking better questions.
What This Means for Engineering Managers
The math is simple. When new employees become productive three months earlier, it doesn't just save onboarding costs. It relieves experienced colleagues who no longer have to serve as a walking wiki.
At the same time, the risk of knowledge loss decreases. KoAssist makes implicit knowledge searchable. What only the colleague with 20 years of experience knew before is now available to the entire team.
For companies facing a skilled worker shortage, this isn't a nice-to-have. It's the foundation for new employees to work efficiently at all.
Conclusion
Three questions. Every day. From every new engineer. The knowledge for the answers exists in every company. It's just not accessible.
KoAssist changes that. Not by inventing new knowledge, but by making existing knowledge accessible. Fast, traceable, with source references.
Onboarding in engineering design doesn't have to take six months. It just needs a system that answers questions as well as the most experienced colleague on the team.
Learn how KoAssist accelerates onboarding in your engineering department.
Book a free consultationFAQ
How long does onboarding new design engineers typically take?
In most companies, it takes six to twelve months until a new design engineer is fully productive. The main reason is the lack of access to experiential knowledge from past projects. With an AI-powered knowledge management system like KoAssist, this onboarding time can be significantly reduced.
Why don't wikis and handbooks work in engineering design?
Wikis and handbooks fail in practice for two reasons: they need to be actively maintained, and the new employee needs to know where to search. In engineering design, projects, standards, and specifications change constantly, causing static documentation to become outdated quickly. An AI system like KoAssist works directly on existing documents and delivers context-specific answers.
What is KoAssist and how does it support knowledge management?
KoAssist is an AI-powered design engineering assistant by Soneo AI. It searches existing project documentation, standards, data sheets, and internal knowledge bases, delivering traceable answers with source references in seconds. No new data storage is needed — KoAssist works with the documents that already exist.
How much time do experienced engineers lose answering new employees' questions?
Every question from a new engineer costs an experienced colleague an average of 15 to 30 minutes. With three questions per day, that adds up to over 300 lost hours per year per new employee. This time is missing from ongoing projects and slows down the entire department.
Can KoAssist also search DIN and ISO standards?
Yes, KoAssist can search standards and guidelines such as DIN, ISO, and EN, and suggest the relevant standard for the engineer's specific use case. Every answer includes a source reference so the engineer can verify the information independently.
What happens to experiential knowledge when long-term employees leave the company?
Without a structured knowledge management system, implicit knowledge is irretrievably lost when experienced employees leave the company. KoAssist makes this knowledge searchable and accessible by indexing existing documentation, emails, and project files, making them available to the entire team.
