---
title: "Not every engineer can deliver every project"
description: "Software delivery improves when leaders match people’s strengths and working styles to the demands of each project."
date: "2025-11-11"
updated: "2026-05-22"
type: essay
topics:
  - "Engineering"
  - "Delivery & Organisations"
canonical: "https://dalugoda.com/writing/not-every-engineer-can-deliver-every-project"
sources:
  - "https://www.linkedin.com/pulse/every-engineer-can-deliver-project-asiri-dalugoda-yhywc/"
---

## The common myth

One of the biggest misconceptions in software delivery is the belief that **“any good engineer can work on any project.”**

It sounds efficient and fits neatly into resource-planning spreadsheets. In reality, it is one of the fastest ways to burn people out, miss deadlines, and stall delivery momentum.

The truth is that not every project needs the same kind of engineer, and not every engineer thrives under every kind of pressure.

## Why skill is not the same as fit

I have seen brilliant engineers (people who can architect scalable systems or write flawless code) struggle when placed on projects with significant ambiguity, undefined requirements, or time-sensitive delivery.

It is not a question of competence. It is about *fit*.

Some engineers excel in greenfield builds: creative, open-ended, and exploratory. Others shine in structured, high-accountability environments where clarity and timelines are strict.

Being technically gifted does not mean someone can or should thrive in every delivery context.

As delivery leaders, **our job is not simply to allocate resources; it is to design fit.**

## The delivery dilemma

Here is where the real tension lies: leaders are under pressure to balance workload, meet delivery dates, and keep utilisation high.

So when someone says, “Can’t James pick this up? He’s a great developer,” it can feel logical.

But assigning work based only on availability or technical depth misses a critical variable: **delivery adaptability.**

Every project has a *delivery personality*:

* Some need patience and deep problem-solving.
* Some need speed and structured chaos.
* Some need collaboration in the face of ambiguity.
* Some need independence and precision.

When those personalities do not align, teams do not flow. You get high effort and low progress.

## Fit is not favouritism

Choosing who should work on what is not bias; it is delivery design. It is the practice of matching people’s working styles, pressure tolerance, and communication patterns to the project’s needs.

A mature delivery leader looks beyond:

> “Who’s available?” to ask, “Who’s built for *this* kind of problem?”

That is not about seniority or popularity. It is about understanding **human rhythm**: how people think, collaborate, and execute under specific constraints.

## How I approach project-person fit

* **Understand the project’s tempo before assigning people.** Is it fast-paced or exploratory? Predictable or volatile? The tempo helps determine the mindset you need.
* **Classify engineers by more than their skill set.** Some are “builders”, some are “fixers”, and some are “navigators”. Understand their rhythm before assigning them.
* **Rotate for growth, not chaos.** Give people stretch projects, but not all at once and not at the cost of delivery.
* **Have honest conversations.** Some engineers do not like ambiguity. Some do not thrive under client-facing pressure. That is not weakness; it is awareness.

## Closing thought

Delivery is not about plugging names into a spreadsheet. It is about understanding **who can thrive in what kind of problem**.

When you get that right, projects can move faster, teams stay healthier, and outcomes become more predictable.

Not every engineer can deliver every project. That is perfectly okay, as long as you, as a leader, know **who should**.

## References

* “Engineering Resource Planning: Best Practices for Engineering Leaders” by Lauren Hamberg, Jellyfish, 4 February 2025. [Jellyfish](https://jellyfish.co/blog/engineering-resource-planning/)
* “How to Reserve Engineering Capacity and Deliver Projects on Time” by Vinay Raghu, LeadDev, 4 September 2024. [LeadDev](https://leaddev.com/management/how-reserve-engineering-capacity-and-deliver-projects-time)
* “Matching Devs to Projects,” Upstack blog. [Upstack](https://upstackhq.com/blog/software-development/matching-devs-to-projects)

## Sources and attribution

- [Original publication on LinkedIn](https://www.linkedin.com/pulse/every-engineer-can-deliver-project-asiri-dalugoda-yhywc/) (original publication date: 2025-11-11)