As we head towards the end of another financial year, most businesses in construction and property start doing what they always do. They review pipeline, budgets, resourcing, recruitment plans, risk, growth targets, and generally try to work out whether the next twelve months look exciting, terrifying, or some healthy combination of both.

Employees are usually doing their own version of the same exercise. Should I stay? Should I go? Am I learning enough? Am I being paid fairly? Am I still enjoying this role, or have I just become very good at looking calm while internally questioning my life choices on the drive home?

Normal end-of-financial-year behaviour, really.

A few weeks ago, I was reflecting on all the guests I have had on The Building Talks Podcast over the years. I have been lucky enough to speak with developers, builders, architects, engineers, project managers, consultants, lawyers, HR leaders, business owners and plenty of others operating across different parts of the built environment.

What struck me was that many of them, despite coming from very different angles, seem to keep touching on the same idea. Sometimes, they probably do not even realise they are saying the same thing. But after nearly 100 conversations, one lesson keeps surfacing.

The quality of our outcomes is heavily influenced by the quality of the things we choose to say yes to.

It sounds simple, which is annoying, because the simple ideas are usually the ones we all nod along to and then immediately ignore when things get busy. Saying yes is easy when the opportunity looks good. The harder part is stopping long enough to ask whether it is actually right.

One conversation that stuck with me was with Nathan Theos (GM at Dowse Projects). Nathan spoke about procurement and collaboration, and made the point that before a five or six-week tender process even begins, there may already have been five, six or even twelve months of work and decisions shaping the project.

That matters, because the industry often focuses on the tender period itself. Nathan was highlighting everything that happens before it. By the time the market properly sees the job, many of the key decisions may already have been made.

The lesson applies well beyond procurement. Many of the problems we experience on projects do not start when things visibly go wrong. They often start months earlier, when a risk gets accepted, a programme gets squeezed, a relationship gets overlooked, or a compromise gets justified because, at the time, it seemed manageable.

Eventually, those early decisions show up somewhere. They become margin pressure, programme pressure, stress, long hours and, quite often, recruitment problems.

People rarely call me and say, “Martin, I am looking for a new opportunity because of poor procurement decisions made twelve months ago.” Usually, the conversation is a little more direct, and occasionally more colourful, because apparently “structurally poor risk allocation” is not how most people describe having had enough.

But often, when you keep digging, that is exactly where the problem started.

Badly chosen work eventually becomes badly felt work.

Another comment that stood out came from Jason Folino (now Director at Saint James Construction), who said, “We do not just go and grab any old work.”

Simple statement, but a big lesson.

The best businesses I come across are usually very disciplined about what they say no to. Not every project suits the business. Not every client suits the culture. Not every opportunity is worth pursuing, even if the revenue looks attractive on a spreadsheet, which, as we know, has never lied to anyone before.

The temptation in any market is to chase turnover, fill the pipeline, keep people busy and keep growing. None of that is wrong, but growth at any cost usually comes with a cost. The businesses that seem to perform best long term tend to understand who they are, what they do well and what type of work genuinely suits their people.

That raises a pretty useful end-of-financial-year question for construction and property businesses:

Because if the work does not suit the business, eventually your people will feel that gap. And when they do, recruiters like me tend to get the phone call.

The same discipline applies to employees and candidates. One of the most common conversations I have starts with something along the lines of, “Martin, I think it is time for a change.”

Sometimes they are absolutely right. Sometimes moving is exactly the right decision. But not always.

Liam Casey (who is now the Pre-Construction Manager at South Rd) touched on this when discussing people moving too frequently between employers. His point was that if people move every six or twelve months, they often do not build the trust, capability and internal opportunities that come from staying somewhere long enough to grow.

That is not an argument for loyalty at all costs. I am a recruiter, not a hostage negotiator. Sometimes, leaving is the smartest thing you can do. But it is an argument for being deliberate.

There is a big difference between progress and movement. A bigger salary is not always progress. A shinier logo is not always progress. A more impressive job title is not always progress. Sometimes it is just movement, with a new email signature and the same old problems waiting for you in a different office.

Before saying yes to a new role, candidates should be asking better questions:

Salary matters, of course. Anyone pretending otherwise is either lying or has recently won Powerball. But salary should sit alongside the other factors, not replace them entirely.

Another recurring theme across several podcast conversations has been sustainability, not in the environmental sense, but in the human sense.

Dr Natalie Galea made a comment that has stayed with me: “I do not think we should get too fixated on the five-day work week. I think the real fixation should be on work hours.”

That line matters because the five-day week debate is not really just about Saturdays. It is about whether the industry has built delivery models that depend on people running too hot for too long.

Aaron McEwan touched on something similar when he spoke about autonomy. Not just where people work, but when they work, how they work, who they work with and what they work on.

For employers, this is becoming increasingly important. Flexibility is not just a nice little perk to chuck in a job ad, wedged somewhere between “great culture” and “competitive salary”, which usually means “we will tell you when we know what you are currently on.” It is part of how businesses compete for good people.

Of course, site-based work has constraints. Nobody is suggesting you pour concrete from the kitchen table. But the businesses that think more creatively about hours, autonomy, planning and recovery will have an advantage.

For employees, the question is whether your current role is sustainable for the season of life you are in. Some roles are intense and worth it. Some are intense and teach you a lot. Some are simply intense because someone upstream made poor decisions and everyone downstream is now pretending it is character building.

It is worth knowing the difference.

Perhaps the biggest lesson I have taken from these podcast conversations is that every yes comes with a no attached to it.

Say yes to a project, and you are saying no to something else. Say yes to a job, and you are saying no to another opportunity. Say yes to rapid growth, and you may be saying no to some level of certainty. Say yes to more money, and you might be saying no to a great mentor. Say yes to a promotion, and you might be saying no to balance for a period of time.

The best leaders, businesses and professionals I have spoken to seem to understand this. They do not avoid trade-offs, they acknowledge them. The worst decisions often happen when people convince themselves there are no trade-offs at all.

That is where poor decisions creep in. A business convinces itself the project is worth taking even though the risk feels wrong. A candidate convinces themselves the job is right because the salary is higher. A hiring manager rushes a decision because the project is screaming for help. Everyone is doing the best they can, but the question underneath is often the same.

What are we really saying yes to?

As we head into a new financial year, most businesses will ask, “What should we do next?” Most employees will ask, “What is my next move?” Both are reasonable questions, but I am not sure they are the most important ones.

After over 100 conversations on The Building Talks Podcast, I think the better question is this:

What are we saying yes to, and what should we finally start saying no to?

Because every successful project, business and career I have observed usually started with somebody making a good decision early. And, in many cases, the train wrecks started the same way, with somebody saying yes to something they probably should have walked away from.

That might be the most consistent lesson I have heard across the podcast.

Better outcomes usually start earlier than we think. They start when we decide what deserves our time, energy, attention and commitment.

And what does not.