Nobody builds a business the way it looks from the outside, with every step confidently planned in advance.

Mine came with real mistakes along the way. Some small, some costly, all of them useful in hindsight. These are a few of the ones that actually changed how I run Dardas Construction today.

Doing the Work Myself Instead of Leading the Crew

Early on, I found it hard to hand work over to anyone else, even when I didn’t need to be the one doing it. Having worked across nine trades myself, I understood most of what was happening on a site better than the average foreman would, and that made it tempting to jump in and fix things personally rather than trust someone else to get it right. It felt efficient at the time. It wasn’t.

Understanding a trade myself made it hard to step back and let someone else handle it, even when stepping back was the better decision for the project as a whole.

What it actually cost the project

Spreading myself across too many small tasks meant less attention on the decisions that actually needed me. I’d be sorting a minor issue on one part of the site while a scheduling problem quietly built up somewhere else, unattended, because I wasn’t watching for it.

Being capable of doing a job myself isn’t a reason to do it myself. My value on a project comes from overseeing the whole picture, not proving I could still lay bricks or run wiring if I wanted to. I still stay hands-on and walk every site personally, but I’ve learned the difference between staying close to the work and doing it instead of the people I’ve trusted to do it.

Running Sites on Instinct Instead of a Proper Plan

In the early years, I ran sites on instinct more than structure, and it cost me more than it should have. I’d learned construction through years of hands-on trade work, not formal project management, so my early approach to scheduling was closer to reacting to problems as they came up than planning to avoid them in the first place.

Where the gap in experience showed

Trade skill and project planning are two different things, and I’d only really built the first one by the time I was running sites alone .

That showed up in a few consistent ways:

• Trades arriving before the site was actually ready for them
• Work overlapping in ways that slowed two crews down at once
• Small delays stacking up into a schedule that quietly drifted off track

The cost of not planning ahead

None of it was disastrous on its own, but it added up to lost time and unnecessary friction between crews who should have been working smoothly together.

A site doesn’t run well just because everyone on it is skilled. It runs well when the sequence of work is planned properly, so trades move through cleanly rather than tripping over each other. Programming a project properly, so the team and contractors work as one, is now something I treat as seriously as any trade itself.

Saying Yes to Every Job the Business Was Offered

When the business was young and every dollar mattered, I said yes to almost everything. Turning down work felt riskier than being overstretched. In the early years, with no guaranteed income and no financial buffer, saying no to a job felt like saying no to the business’s survival.

Every job felt essential to keeping the business alive, which made it hard to see that some jobs were actually costing more than they were worth.

What overcommitting actually looked like

The result was fairly predictable. I ended up juggling far more at once than I could properly oversee, some jobs took longer than they should have, and I spent less time walking sites personally than I believed was necessary, simply because there weren’t enough hours to go around.

Taking on every available job isn’t the same as building a sustainable business. There’s a point where saying yes to more work actually costs more than the income is worth, because quality and oversight both suffer. I’m far more deliberate now about how much work the business takes on at any one time — growth matters, but not at the cost of the standard I expect from every project.

Assuming Trade Knowledge Would Be Enough to Earn Respect

As a young foreman managing subcontractors who’d been in the industry for decades longer than I had, I assumed my knowledge of the trades would be enough on its own to earn their trust. I understood the work well, having come up through nine trades myself, and I expected that understanding to speak for itself.

Where that assumption broke down

Knowing the work and earning trust from people twice my experience turned out to be two separate challenges, not one.

I didn’t fully appreciate, early on, how much respect still needed to be actively earned through the way I communicated, not just through what I knew. Some early working relationships started off tenser than they needed to, simply because I hadn’t yet learned how to lead people who had every reason to question a young foreman’s authority.

What respect is actually required?

Knowing a trade and leading the people who work in it are two different skills. Respect isn’t automatically granted because you understand the job. It’s built through:

• How you treat people, regardless of their title
• How well you listen before making a call
• Whether your decisions are backed by fair reasoning, not just assumed authority

The approach I’ve carried forward

I treat every subcontractor, regardless of their experience level compared to mine, with the same respect from day one—an approach learned the hard way and part of why so many of the same trades have worked with me for years since.

Why These Mistakes Mattered More Than Any Success

None of these mistakes were dramatic enough to make headlines. They were quieter than that—the kind of thing that only becomes obvious in hindsight, once you’ve corrected the pattern enough times to see what it was costing you.

That’s really the honest version of how I improved. Not through one turning point, but through noticing, slowly, where my own habits were working against me, and being willing to change them even when the old way had gotten the job done, just not properly.

Nineteen years and more than 1,000 projects later, the standards I run Dardas Construction on today exist largely because of the mistakes I made building it in the first place.

FAQs

What mistakes did Ibrahim George Dardas make early in his career?

He tried to do too much himself instead of trusting his crew, under-planned site scheduling, took on more work than the business could properly handle, and assumed experience alone would earn respect from subcontractors.

What caused these mistakes?

Mostly inexperience with leading people rather than just understanding trades, combined with the financial pressure of running a new business with no guaranteed income.

What were the consequences?

Inefficiencies on site, strained early working relationships, and periods where quality and oversight slipped below the standard he expected of himself.

What did he learn from these mistakes?

That capability isn’t a reason to do everything yourself, that proper site programming prevents avoidable problems, that taking on every job isn’t sustainable, and that respect has to be earned through leadership, not assumed through knowledge.

How does he run Dardas Construction differently today?

He delegates more deliberately, programmes every site properly, takes on only what the business can handle to standard, and treats every subcontractor with the same respect regardless of experience level.