Skip to content
Blog

How much time does coordination cost in design engineering?

Collecting status, answering questions, preparing status meetings: in design departments, coordination takes up many hours a week. Two cases from special-purpose machine building and a simple method for measuring your own effort.

Yanik YeganehfarCo-Founder & COO4 min read
Quick answer

Coordination costs design departments many hours a week. In two cases from special-purpose machine building, the managers put it at around twelve hours with ten design engineers and around fifty hours with 27 people, mostly for collecting status and answering questions. How much it is in your own company can be measured with a tally sheet over one week.

Contents
  1. How much time goes into coordination?
  2. What does coordination effort consist of?
  3. How do you measure the effort in your own team?
  4. What can be improved without a new tool?
  5. How does KoAssist help?

Monday morning, head of design. Ten design engineers, fourteen projects under way. Before the actual week begins, the status of every project has to be collected: where the release is stuck, which question from the customer is still open, which drawing is waiting to be checked. A head of engineering and projects in special-purpose machine building described it in a conversation like this: "That's the first 12 hours of the week gone already."

This time does not appear in any project costing. It sits in the overhead rate, which is why it rarely stands out.

How much time goes into coordination?

Two cases from special-purpose machine building show the order of magnitude.

A manager with ten design engineers. Around twelve hours a week just for collecting data internally before decisions can be made. That is almost a third of a working week.

A design department with 27 people. The head of department reckons on one to two hours of coordination per person and week. Across the team: "That's 50 hours gone straight away." That is more than one full-time position.

These figures are what the people involved told us, not measurements. They do show, though, that coordination is not a side issue but a quantity that can and should be measured.

What does coordination effort consist of?

Collecting status. The manager goes round asking where each project stands, because the status is spread across Excel, OneNote and email. Why that takes so much time is described in the article on project status in Excel, OneNote and email.

Answering questions. Purchasing asks for the released revision of the bill of materials, assembly about a change in dimensions, sales about a date. Each question only takes minutes, but they come all day.

Status meetings. The meeting itself and its preparation. If the first half hour goes on asking everyone in turn, little time is left for decisions. How it can work differently is covered in the article on project status without status meetings.

Searching. For the current drawing revision, the email with the customer's approval, the minutes with the decision from three weeks ago.

Maintaining lists. Open issues list, change register, schedule overview. How an open issues list should be structured so that it does not go out of date is the subject of a separate article.

How do you measure the effort in your own team?

One week is enough for a reliable picture. This is how to do it without a tool:

  1. Set four categories: collecting status, answering questions, meetings, searching and maintaining lists.
  2. One tally sheet per person. Each mark stands for a quarter of an hour. On paper or in a simple spreadsheet.
  3. Pick a normal week, not the week before acceptance and not a holiday week.
  4. Add it up on Friday. Per person and for the team, split by category.
  5. Put a value on it with an hourly rate. That makes the figure tangible for management.

It is important that the measurement is not seen as a check on people. It is about the effort the system creates, not about individuals.

What can be improved without a new tool?

One place for the status of each project. People who know where to look ask less often.

Record decisions with their source. That saves searching for the email. How this works day to day is described in the article on project decisions from email. What AI can do in engineering design beyond project coordination is described in the guide AI in engineering design.

Bundle questions. Fixed times for questions from purchasing and assembly, instead of answering them one by one all day.

Keep status meetings to decisions. Read the facts beforehand, decide in the meeting.

How does KoAssist help?

Project Memory in KoAssist, the AI agent for machine and plant builders, reads the specification, emails and minutes for every project and records the status, every detail with its source. Changes arrive as proposals and only become valid once someone on the team accepts them. The knowledge assistant answers questions from the documents with file and page. Project Memory is currently in pilot operation with existing customers.

We do not promise in advance how much time this saves in your team. A pilot runs for 60 days on a real project, and on the first day and after 60 days we measure, among other things, the effort for status queries and status meetings. If you would like to see this on one of your own projects, you can book a demo.

Written by

Yanik Yeganehfar

Co-Founder & COO

On LinkedIn ↗

Frequently asked questions

Yanik Yeganehfar, co-founder of KoAssist

Find out with Yanik whether KoAssist fits your projects.

Request a demo