Data-Driven Solutions

Data-Driven Solutions Data Transformation & Automation for modern organisations.

Our focus is simple: reduce operational friction and unlock business value from data.

DDS helps organisations turn complex data environments into reliable, automated decision platforms.

06/11/2026

Too often in IT, the code changes before the problem is understood.

A process fails, a report produces the wrong figures or an application throws an error.

And before anyone has properly investigated what's going on, someone is already changing code.

But do we actually understand what's causing the problem?

Whatever happened to the art of troubleshooting?

Some of the most valuable lessons in IT come from experienced colleagues who take the time to teach others.

They don't necessarily give you the answer. They teach you how to find it.

How to investigate, follow the evidence, eliminate possibilities and understand why something isn't working before attempting to fix it.

Sometimes that means spending hours investigating something that turns out to have a very simple explanation.

But that's part of learning.

We do wonder whether we're losing some of that.

Under pressure to deliver, time for mentoring can easily disappear. Deadlines need meeting, projects need delivering and problems need fixing.

It's often quicker to give someone the answer or make the change yourself than spend time teaching them how to work it out.

But what are we creating in the process?

People who know how to write code, but haven't necessarily learnt how to troubleshoot it.

And there's a big difference.

Without understanding the cause, a change can hide the symptom, introduce another issue or leave the original problem waiting to happen again.

At DDS, we see troubleshooting as one of the most valuable skills in IT. It's not just about technical knowledge. It's about knowing how to think through a problem.

A course or certification can help build that skill. But it also develops through experience, making mistakes and working alongside people willing to share what they've learnt.

Making time for that is an investment in the team's ability to solve the next problem.

Are we so focused on fixing today's problems that we're forgetting to develop the people who need to solve tomorrow's?

“AI won't take your job.”How many times have we heard it?“AI won't replace people. It will free them up to focus on high...
05/11/2026

“AI won't take your job.”

How many times have we heard it?

“AI won't replace people. It will free them up to focus on higher-value work.”

It's a reassuring message. But what does it look like in practice?

This year, WiseTech announced plans to cut approximately 2,000 jobs, explicitly linking its restructuring to AI-led changes.

Atlassian announced approximately 1,600 job cuts globally, saying the decision would help fund further investment in AI and enterprise sales.

More recently, NAB announced plans to reduce its internal workforce by up to 2,500 roles as part of an operating-model restructure.

Different organisations. Different circumstances. These aren't interchangeable examples of AI replacing people.

But they do give us reason to challenge blanket assurances about what happens to employees as organisations adopt AI.

At DDS, we work with data, technology and automation. We believe in their potential to improve how businesses operate.

That doesn't mean we should accept every claim about the benefits without asking for evidence.

If AI is freeing people up for higher-value work, what work are they moving into?

What training are they receiving?

And how many are actually being given the opportunity to make that transition?

Saving time on a task doesn't automatically create a new role for the person who previously did it.

Retraining takes investment. Redeployment requires suitable opportunities. Neither happens simply because an AI tool has been introduced.

So alongside the hours saved and productivity gains, we'd like to see organisations reporting how many people they've successfully retrained, redeployed and retained.

And how many roles have disappeared through redundancies, attrition or recruitment freezes.

Those figures would tell us far more about workforce transition than another assurance that people will be able to focus on higher-value work.

If that's the promise, where is the evidence that it's happening?

04/11/2026

When did change control become a tick-box exercise?

Over the years, we have consulted for a number of organisations and seen some very different approaches to change control.

Some have had excellent, rigorous processes where production changes require proper documentation, test evidence, impact assessments, appropriate sign-offs and, where possible, deployment by someone other than the person who developed them.

And rightly so.

Unfortunately, we have also worked in organisations where change control seems to have become little more than a tick-box exercise.

The change request is raised, the mandatory fields are completed, the approvals are obtained and off we go.

But how often does anyone actually challenge what's being submitted?

Has the testing really been done? Does the evidence demonstrate that the change works as expected? Has anyone considered what else might be affected? Is there a realistic rollback plan?

Or are we simply approving the change because all the boxes have been ticked?

We have seen changes approved with questionable test evidence, vague implementation plans and rollback procedures that amount to little more than “restore the previous version”.

Without explaining how that would work, how long it would take or what happens to data changed in the meantime.

And yet, the change is approved.

We're not advocating more bureaucracy or making the process unnecessarily complicated.

We're questioning whether the controls in place are actually doing what they're supposed to do.

Because having a change management process doesn't necessarily mean you have effective change control.

An approval should mean someone has reviewed the evidence, understood the potential impact and made an informed decision about whether the change should proceed.

Otherwise, what is that approval actually worth?

𝗪𝗵𝗲𝗻 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗮𝗽𝗽𝗿𝗼𝘃𝗲𝘀 𝗮 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝗰𝗵𝗮𝗻𝗴𝗲, 𝗮𝗿𝗲 𝘁𝗵𝗲𝘆 𝗺𝗮𝗸𝗶𝗻𝗴 𝗮𝗻 𝗶𝗻𝗳𝗼𝗿𝗺𝗲𝗱 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝗿𝗶𝘀𝗸, 𝗼𝗿 𝘀𝗶𝗺𝗽𝗹𝘆 𝗰𝗼𝗻𝗳𝗶𝗿𝗺𝗶𝗻𝗴 𝘁𝗵𝗮𝘁 𝘀𝗼𝗺𝗲𝗯𝗼𝗱𝘆 𝗵𝗮𝘀 𝗳𝗶𝗹𝗹𝗲𝗱 𝗶𝗻 𝘁𝗵𝗲 𝗳𝗼𝗿𝗺?

03/11/2026

Too often in IT, the code changes before the problem is understood.

DDS founder Delio Nobrega reflects on the value of troubleshooting and passing that skill on.

A process fails, a report produces the wrong figures or an application throws an error.

And before anyone has properly investigated what's going on, someone is already changing code.

But do we actually understand what's causing the problem?

Whatever happened to the art of troubleshooting?

When I started my career, I was fortunate enough to work alongside more experienced people who took the time to teach me.

They didn't necessarily give me the answer. They taught me how to find it.

How to investigate, follow the evidence, eliminate possibilities and understand why something wasn't working before attempting to fix it.

And sometimes that meant spending hours investigating something that turned out to have a very simple explanation.

But that was part of learning.

I do wonder whether we're losing some of that.

Mentoring and learning from experienced colleagues were a big part of developing your skills. You learnt not just how to do something, but why you were doing it.

Under pressure to deliver, time for that kind of mentoring can easily disappear. Deadlines need meeting, projects need delivering and problems need fixing.

It's often quicker to give someone the answer or make the change yourself than spend time teaching them how to work it out.

But what are we creating in the process?

People who know how to write code, but haven't necessarily learnt how to troubleshoot it.

And there's a big difference.

Without understanding the cause, a change can hide the symptom, introduce another issue or leave the original problem waiting to happen again.

To me, troubleshooting is one of the most valuable skills you can have in IT. It's not just about technical knowledge, it's about knowing how to think through a problem.

And that's something you don't necessarily learn from a course or a certification.

You learn it through experience, making mistakes and, perhaps most importantly, from people willing to share what they've learnt.

Are we so focused on fixing today's problems that we're forgetting to develop the people who need to solve tomorrow's?

We still find it incredible how many database changes are made without proper source control.And by source control, we d...
02/11/2026

We still find it incredible how many database changes are made without proper source control.

And by source control, we don’t mean having a Git repository somewhere that contains some SQL scripts.

Redgate research found that only 58% of SQL Server professionals were using version control for database development, compared with 81% for application code.

But I actually wonder how many of that 58% use it with real rigour.

A stored procedure gets changed directly in production.

A view gets a quick fix.

Someone adds an index.

“It’s only one change. I’ll put it back into source control later.”

And then they don’t.

Six months later somebody deploys the version from source control and quietly wipes the production change out.

Or worse, nobody even knows which version is actually correct anymore.

We wouldn’t accept developers casually changing application code in production and not committing it back to the repository.

So why do we still accept it with databases?

Source control should be the source of truth.

Every change.
Every time.
No exceptions.

Having source control is the easy bit.

Having the discipline to use it properly is what actually protects you.

We still find it astonishing how often we test our code without properly understanding the data it's going to process.We...
02/11/2026

We still find it astonishing how often we test our code without properly understanding the data it's going to process.

We write some beautiful code that we're proud of. Create the test cases, validate everything in development and then move it through UAT.

All good. No issues.

Then we deploy it into production and suddenly something breaks.

The problem?

Dev and UAT often contain nice, predictable test data.

Production doesn't.

Production has the record created 12 years ago. The unexpected NULL. The 35 characters in a field everyone thought would never exceed 20. The value that according to every specification shouldn't even exist.

And invariably that's the data that finds the weakness in our code.

We spend a lot of time testing whether the code does what we expect it to do.

Yet we seem to spend considerably less time understanding the data that the code is actually going to process.

Because passing every test case means very little if those test cases don't represent the data the code is actually going to encounter.

The code change takes an hour.The change does not take an hour.Recently, we were asked to make a relatively simple chang...
15/10/2026

The code change takes an hour.

The change does not take an hour.

Recently, we were asked to make a relatively simple change to a data feed going to an external supplier.

“How long will it take?”

“About an hour to make the change. A day to test it.”

That answer wasn't particularly well received.

The field was already in the feed for one category. We simply needed to populate it for another.

So why would that take a day to test?

Because changing the code is the easy bit.

We need to prove the extract file is correct, that the new category is populated correctly and that the supplier consumes it in the way we expect.

And importantly, we need to make sure we haven't broken what was already working.

We stood our ground. The change needed a day of testing.

And it highlights something we see regularly in technology delivery.

The effort required to implement a change is not necessarily representative of the effort required to validate it.

At Data-Driven Solutions, we believe testing isn't the bit we squeeze in if there's time left.

It's part of the change.

If we make a change, we need to test the touch points, the different permutations and the things we might have affected to the best of our knowledge.

“It already works over there” isn't a test.

We cannot assume anything in this field.

hashtag hashtag hashtag hashtag

14/10/2026

Standards seem to matter right up until things get busy.

Then suddenly they're optional.

Deadlines are tight.
Resources are stretched.
Something has to give.

And standards are often the easiest thing to compromise.

"It works."
"We'll come back and fix it."
"We just need to get this over the line."

The problem is that we rarely come back.

And what looked like a shortcut becomes the new standard.

A few months later, organisations are dealing with inconsistent implementations, technical debt, additional support overhead and controls that are much harder to assure.

At Data-Driven Solutions, we believe engineering standards shouldn't be compromised simply because delivery pressures increase.

Standards aren't there for when we have plenty of time.

Arguably, they're most important when we don't.

Database access should be driven by business requirements, not convenience.Yet we continue to see requests such as:“Can ...
13/10/2026

Database access should be driven by business requirements, not convenience.

Yet we continue to see requests such as:

“Can you give this person read-only access to the database?”

Or:

“We have someone starting in a new role. Can you give them the same permissions as the rest of the team?”

Both seem reasonable on the surface.

But they raise important questions.

What data does the individual actually need to access?

What business function are they performing?

Does their role require access to the entire database, or only specific datasets?

And why should someone in a new role automatically inherit another person's permissions?

Read-only access is not a business role. It simply restricts the ability to modify data. It doesn't necessarily restrict what information someone can see.

Similarly, copying another user's permissions may be convenient, but it risks perpetuating excessive access privileges.

At Data-Driven Solutions, we believe access should be defined by business need, supported by clear roles and governed by the principle of least privilege.

Good data governance starts with understanding the requirement, not simply fulfilling the request.

Perhaps the question shouldn't be:

“What access can we give them?”

But rather:

**“What do they actually need to do?”**

hashtag hashtag hashtag hashtag

We think we may have created a problem with the way we are measuring technology delivery.Speed has become a measure of s...
12/10/2026

We think we may have created a problem with the way we are measuring technology delivery.

Speed has become a measure of success.

So has quantity.

How quickly did we deliver?
How many features?
How many pipelines?
How many releases?
How many processes did we automate?

All very easy to measure.

Quality is harder.

Did we build the right thing?
Is the data complete?
Can we prove it?
What controls did we build around it?
What risk did we introduce while moving faster?

Those things are much harder to measure.

And that's where we think we have a problem.

We've become very good at measuring how much we deliver and how quickly we deliver it.

We're not convinced we put the same effort into proving that what we delivered is actually correct.

Speed matters.

Quantity matters.

But without quality and assurance, aren't we just getting better at producing more risk, faster?

hashtag hashtag hashtag hashtag

Address

Gold Coast, QLD
4214

Alerts

Be the first to know and let us send you an email when Data-Driven Solutions posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Data-Driven Solutions:

Shortcuts

Share