Coordination Crisis in Modern Tech Work
Over 50% reported spending 25–50% of their week on "work about work”. What is the root cause of it? How can we improve that? Can AI help?
Monolith to Microservices Migration — What to Expect (10 challenges + frameworks to overcome them) (Sponsored)
Transitioning to microservices is tough. It’s not just a technical shift but an organizational one too.
From defining service boundaries, to managing decentralized data and handling interservice communication, there’s a lot that can go sideways.
This 80+ page ebook breaks down common migration challenges with examples from dev teams at Uber, Spotify & Netflix, helping you understand the obstacles before you hit them.
Let’s get back to this week’s thought.
Intro
I had the pleasure of attending the event called: The Coordination Crisis Summit at the University of Maryland last week.
Steady, University of Maryland - A. James Clark School of Engineering and AlphaROC recently conducted a survey with a goal to understand what’s really slowing teams down in today’s distributed work environments.
What's been really interesting to see is that over half of the survey respondents said they spend 25–50% of their week on “work about work”.
We had sessions, breakouts and panel discussions to see what we can do to improve in this area.
I am sharing the overview of the survey and my opinion associated with the results together with the ideas for improvements in today's article!
Was really great to meet with these great professionals:
Henry Poydar, CEO Steady
John Johnson, Lead Faculty, Project Management Center for Excellence
Daniel Forrester, Chief Growth Officer and Advisor
Uma HS, Former PMI WDC President Portfolio Exec Advisor
Damien Peters, UMD Faculty, Product Managemet Expert
Kathleen Walch, Director of AI Engagement and Learning
Let’s get straight into the survey next!
1. The Coordination Crisis Survey
A survey was conducted recently with 994 tech and knowledge workers in the United States with the goal of understanding what’s really slowing teams down in today’s distributed work environments.
The finding?
Over half of survey respondents said they spend 25–50% (or more) of their week on “work about work”, such as aligning stakeholders, attending status meetings, managing tools, and chasing approvals.
The consequences of this can often be hidden, but there are 2 likely outcomes based on the survey results:
Individuals and teams having unnecessary meetings, inefficient systems, silos, delays and there is a potential for burnout.
Customers experiencing consequences from miscommunications, slower service and bigger costs.
Here are some of the important results:
37.9% of people reported that excessive meetings are the contributors to inefficiencies.
36.9% reported that slow decision-making and approvals is slowing them down.
29.4% mentioned that knowledge is scattered across disconnected tools.
30.5% of people have mentioned that coordination breakdowns lead to rework and errors.
28.3% said these costs are felt directly by customers in the form of missed deadlines, price increases or reduced experiences.
You can download the full survey report below:
Make sure to follow along the article for my opinions and comments on specific data insights.
Let’s go to specific questions and the results next.
1.1 Survey Results
State of the Coordination Crisis
As we can see from the results, over half of the people reported they spend 25–50% (or more) of their week on “work about work”.
A lot of people mentioned “Somewhat”, which in a lot of cases means they need to actively protect their focus time and find “spare” hours in their day-to-day.
As expected, challenges with coordination spiral down to employee retention and burnout. In my opinion “not being able to get things done” is one of the biggest factors for changing companies or burning out, right after bad management.
This was very interesting to see, especially the increased costs for customers. In my opinion, a lot of companies don’t share with customers all the insights on what contributed to particular costs.
But price, customer experience and quality in deliverables are very important in order to be competitive in the current market and inefficiencies in the process can contribute to competitive disadvantage.
Root Causes of the Coordination Crisis
That is aligned with my expectations. The more your organization grows, the more important systems are. It’s rarely a problem with people who do hands-on work, but processes, systems, organizational focus and overall structure.
These two quotes come to my mind:
“You do not rise to the level of your goals. You fall to the level of your systems.”
— James Clear
Organizations that design systems are constrained to produce designs that are copies of the communication structures of these organizations.
— Conway’s law
As we mentioned above in the important results section, excessive meetings, slow approvals, lack of training, outdated data and systems contribute to inefficiencies in coordination.
In today’s distributed nature of our work → hybrid/remote work is unavoidable. I don’t know any mid+ size tech company, where all of their people are on-site at the same office at all times.
So it’s a must in my opinion for organizations to support that well.
These two make sense. There are pros and cons when it comes to hybrid/remote (similar to on-site work), but I believe if any of the mid+ size organization wants to be successful, it’s really important to optimize for hybrid/remote work.
AI’s Role In The Crisis and Impacting Careers
The surprise here is the AI-Powered Automation, 35% of organizations seem to have that already to a certain extent.
And also 27~% mentioned Internally Hosted AI Models. What would be interesting to see is: Are these 27% of organizations building their own models or using existing ones - just hosted on their own infrastructure? I am assuming that most do the latter.
Summarizing meeting and preparing notes is a good use case, however, it’s getting a bit daunting when I get into a meeting and I see many AI note-takers present in the meeting.
I think that can spiral to people not being open to sharing things as what you say may get “misquoted” and you may mean a different thing.
There is a lot of positivity in opportunities that AI can bring and make a lot of things easier for us, especially repetitive tasks and automation.
You can read what 11 engineering leaders have shared on how their teams are using AI to increase Software Development productivity here:
A lot of people are a bit unsure whether it will bring benefits or not. But my take on this is:
You can’t use AI as a replacement for a bad process. You need to improve the process first and then add AI to make it better.
Expecting that AI will resolve organizational issues is just the wrong expectation to have.
These are very interesting insights. More than 30% of people have concerns regarding job security and more than 40% of people are concerned about lack of human decision-making in critical areas.
Also, 30% of people mentioned surveillance and micromanagement. I’ve addressed the topic of enforcing AI either being a good thing or a bad thing here:
This is a great sign to see that many people believe that AI will enhance rather than replace their roles and also they are confident in adapting.
And same with this chart → a lot of people are prepared for an AI-driven future, which is the right way to go. It’s important to stay up-to-date with the new things coming and look for how you can improve in this area.
1.2 Cross-Analysis and Insights
Demographic-related questions were also part of the survey, specifically:
Where do you work?
Which of the following best describes your focus within the company?
What is your organization's approach for how you build products?
What primarily drives the company's planning on 'what' to build?
What is the size of your company?
And 3 specific insights emerged when they connected the demographics with the overall survey.
These are the insights provided in the report, so I am quoting them.
Insight 1 - Leaders are more uncertain about the future of their roles than contributors in a world of AI
Leaders are nearly three times more likely than engineers to fear job loss (15.8% vs. 5.6%), suggesting that uncertainty at the top may shape the pace and tone of organizational AI strategies.
Engineers, meanwhile, appear pragmatic and prepared: while only 5.6% fear being replaced, 16.7% anticipate significant changes to their roles and are confident in their ability to adapt.
This is interesting insight and I believe it has to do with different companies adjusting the ratio of managers vs individual contributors. Starting with Amazon, I saw this trend in other companies as well.
One of the key factors I’ve mentioned in the article: Become a great engineering leader in 2025 is to increase your skillset, stay technical and embrace AI as an engineering leader.
Insight 2 - Fully in-office teams spend the most time on coordination
People working entirely in the office are the most likely to say they spend over half their week on tasks like finding information, getting approvals, or switching between tools and teams.
In fact, fully in-office workers report this level of coordination time more than twice the rate of hybrid workers (7.4%).
This has also been very interesting to read as companies who wants people to come work on-site claim that they want to increase collaboration. Funny, this report completely denies such claims of this actually being true.
Insight 3 - Familiarity with AI builds trust, absence breeds confusion
When AI is fully woven into workflows, people are more open to its help with decision-making and action. The more AI is embedded in daily work, the more people trust it to reduce chaos, not create it.
Conversely, fear of AI is highest where it’s absent. 61% of workers at companies with no AI adoption believe it creates more coordination confusion.
This makes sense, as a lot of people are not prone to change and everything that is new and unknown is harder to embrace and it’s harder to believe it will actually improve things.
2. Ideas for Improvements in Coordination in Tech Teams
Now that we covered the survey, let’s go into what we did at the Summit. We gathered at the University of Maryland and we had people present both on-site and online as well.
The main goal was to raise awareness on the topic and define key solutions and ideas on what we can do to improve the coordination in modern tech teams.
We separated into different groups and jumped on a Miro board to brainstorm
We went over different stages, which include:
The purpose
Defining the problem
Solutions and ideas
Reflections and next steps
There was a specific timeframe for every stage, where we talked and brainstormed together and filled in the notes.
Between these stages, we also had lightning talks and panel discussions. Here is a picture from the panel discussion regarding adopting AI in organizations, led by Henry Poydar and panelists: Damien Peters, Joe Mariani (online) and Kathleen Walsh.
Now let’s go straight into specific solutions and ideas that we came up with on how we can improve the coordination among tech teams.
Here are some of the ideas and solutions that you can use to improve the coordination
First, let’s start with what can Individual contributors do:
Make sure to propose solutions and ideas to the managers and people responsible for the efficiency of the process.
Learn to adapt to asynchronous work. It’s unavoidable and don’t normalize dysfunction.
Always look for ways to improve and make your job easier for you and your team.
Apply AI tools where it helps.
Document things that are important for everyone to understand, that can be: workflows, specific knowledge and agreements.
Raise awareness of problems and bottlenecks where time is wasted on coordination.
Let’s continue with People managers:
Ensure psychological safety in teams, so that everyone feels that they can propose ideas and solutions.
Empower people and teams with decision-making by delegating the problems with a clear intent.
Promote a culture of continuous learning that values experimentation and reflection.
Align business goals with the day-to-day responsibilities of people and teams
Support AI adoption the right way → by encouraging exploration and reducing fear of change.
Executives:
Ensure that everyone is aligned on strategy, priorities and ownership of particular things.
Invest in the right tools and systems, don’t embrace a new tool or a system for the wrong reasons.
Promote autonomy. With too much reliance between different teams and people → it’s hard to make progress.
Track and act on coordination costs → It’s important that you have some way to see where the wastes are or can be and then create initiatives to improve that.
Now, let’s take a look at how we can use AI to improve coordination between people and teams:
Use AI to summarize meetings → auto-generate notes, decisions and next steps.
Encourage the use of AI coding tools. This is a great article to read: Top AI coding tools for engineering teams in 2025.
An interesting idea is to use AI to eliminate low-value meetings. That can potentially be checked by going through meeting notes.
Use AI to analyze and track workflow waste → track misalignments, delays, and rework.
Prototyping is something that AI can definitely help a lot, which can speed up going from idea to execution.
Use AI to create mockups, simple designs, proof of concepts and proposals.
This helps with tighten the feedback loops between PM <> Design <> Engineering
Use an AI chatbot trained and personalized based on your organization’s knowledge base, so everyone can quickly get the answers they need.
These are some of the ideas and suggestions that you can try. If you have any additional in mind, make sure to let me know in the comments!
Last words
Special thanks to Henry Poydar for inviting me to the event. I had a great time at the University of Maryland and I’ve also spent some time sightseeing around Washington and Philadelphia.
Also thanks to John Johnson and Daniel Forrester for the great facilitation of the event. It was great meeting everyone and looking forward to more of such events.
I strongly believe that such insights from the survey and the ideas for improvements will help many teams be more productive!
We are not over yet!
How to Grow From Mid-Level to Senior Software Engineer
Check out my latest video. I have shared what makes a Senior Software Engineer for me and 5 points on what you should do in order to grow from mid-level to senior engineer.
New video every Sunday. Subscribe to not miss it here:
Liked this article? Make sure to 💙 click the like button.
Feedback or addition? Make sure to 💬 comment.
Know someone that would find this helpful? Make sure to 🔁 share this post.
Whenever you are ready, here is how I can help you further
Join the Cohort course Senior Engineer to Lead: Grow and thrive in the role here.
Interested in sponsoring this newsletter? Check the sponsorship options here.
Take a look at the cool swag in the Engineering Leadership Store here.
Want to work with me? You can see all the options here.
Get in touch
You can find me on LinkedIn, X, YouTube, Bluesky, Instagram or Threads.
If you wish to make a request on particular topic you would like to read, you can send me an email to info@gregorojstersek.com.
This newsletter is funded by paid subscriptions from readers like yourself.
If you aren’t already, consider becoming a paid subscriber to receive the full experience!
You are more than welcome to find whatever interests you here and try it out in your particular case. Let me know how it went! Topics are normally about all things engineering related, leadership, management, developing scalable products, building teams etc.
for insight 2 - what if the organization have existing inefficient coordination process that leads it leaders felt they need full WFO. on the WFH/ hybrid side, they keep it because their coordination process is efficient and can perfom well without on site necessity?