Young Manager/Team Leader! Get a Grip!

Table of Contents

History tends to repeat itself, and this is a common tale among young managers and team leaders. A recurring, tragic mistake is the commitment to unrealistic deadlines.

Why Do We Commit to Unrealistic Deadlines?

This mistake happens for several reasons:

  • External Pressure: From clients, managers, directors, etc.
  • Internal Pressure: A desire to prove how good our team is.
  • Lack of Knowledge: Sometimes there’s a complete lack of understanding about the project’s requirements.
  • Other reasons? Feel free to add your thoughts!

Handling External and Internal Pressure

For the first two points, the solution seems simple: assertiveness and honesty with oneself and with superiors or clients. It often requires stepping out of one’s comfort zone to say, “It’s not possible in this timeframe.”

You might encounter resistance, but it often showcases professionalism, defined here as “not committing to vague or unrealistic deadlines.”

Negotiating Realistic Timelines

I am often asked how to handle projects when there’s already a lack of time, resources, and clarity of requirements. The answer is simple: “Don’t agree to it; rather, negotiate.” Demonstrate why the deadline is unrealistic. Break down the work and estimate it. Highlight the risks. Don’t agree to compromise on quality (“We’ll manage somehow — we’ll skip testing, acceptance criteria, as long as it works”).

Negotiated deadlines are not set in stone, and you can often adjust them if you have convincing arguments. As a manager, I’ve sometimes mentioned deadlines off the cuff, without much thought. Occasionally, my team gets attached to these deadlines, sometimes forgetting that they can negotiate them. Often, a brief discussion is enough to resolve it. Almost everything is negotiable in this world! But it often requires courage! One of the core values of Agile is Courage. Do you know why? :)

Embrace Methodologies with Mentorship

For lack of knowledge, start using some methodology :) Seek help from an experienced mentor.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

The Big Lie About Clean Code and Unit Testing

Introduction

Many people are convinced that waking up early, say at 5:00 AM, is an unrealistic fantasy for them. They believe that their nature and their body are constructed in such a way that it’s impossible. I used to belong to this group of people.

Read More

Technical Leader Worries: I Have Too Many Things to Do

Technical Leader Worries: I Have Too Many Things to Do

Those wonderful days when the only thing you did was writing code are gone. Now you are a leader. You are doing everything: attending or conducting meetings, removing impediments, mediating between team members and the rest of the organization, reading or writing some kind of reports (and you deceive yourself that spending two hours in Excel counts as programming because of some smartly used formulas) and so on. You are in a hurry all the time, and it never ends.

Read More

A Few New Concepts - Architectonic Mantra, Design Retrospective, Shared Context, Natural Order of Refactoring

Recently, several named concepts have evolved in my mind, or maybe I just understood them well. Here are a few notes that I consider an alpha draft ;-)

Read More