Category: RD3 Tech - RD3 Tech

RD3 Tech

Your Technology Support Journey Starts Here!

Building a Better Way for Clients to Ask for IT Help

You Don’t Need to Know the Technical Problem

One of the things I’ve been working on recently is making it easier for people to explain what they need help with.

That might sound like a small thing, but it’s actually quite important.

When something goes wrong with technology, most people don’t necessarily know what the technical problem is.

They know what they were trying to do.

They know what happened.

And they know that it isn’t working.

That’s enough to get started.

Start With What You’re Trying to Do

Rather than asking someone to choose from a long list of technical problems, I prefer to start with simple questions about what they’re trying to achieve and what sort of help they need.

From there, the information can be organised so that the next step is clearer.

This also makes it easier to identify what sort of help is actually required, rather than trying to fit someone’s situation into a technical category before we’ve understood the problem.

Not Everything Is a “Computer Problem”

This is particularly useful when the problem isn’t really a “computer problem” at all.

It might be:

  • Something that’s broken
  • Something that could work better
  • A question about workplace technology
  • Help managing existing IT
  • A technology decision that needs some thought
  • Simply not knowing where to start

Those are all different situations, even though they might initially look like the same thing.

Technology Can Be Complicated. Asking for Help Shouldn’t Be.

The technology behind the scenes can be quite sophisticated, but the experience for the person asking for help shouldn’t be.

You shouldn’t need to understand IT before you can ask an IT professional for help.

That’s something I’m continuing to work on with RD3 Tech — making that first step as straightforward as possible.

Not Sure Where to Start?

If you’re not sure what the problem is, that’s okay.

You don’t need to know the name of the problem, understand the technical terminology, or already know what solution you need.

Tell me what you’re trying to achieve and what isn’t working.

Getting started with a conversation is often enough to work out what needs to happen next.

RD3 Tech – Helping people and organisations make technology work better.

Why JSON Files Are So Useful — And Why I’m Using Them in RD3 Tech

Why JSON Matters When Building Better Systems

JSON is one of those things you can easily ignore if you’re not a developer.

It looks a little strange at first, but at its core, JSON is simply a structured way of storing information.

Keeping Information Separate From the Code

I’ve been using JSON as part of some RD3 Tech development because it provides a useful separation between the information a system uses and the code that operates the system.

That’s an important distinction.

Instead of putting every setting, label, or option directly into the code, some of that information can be stored separately in a JSON file.

This means the system can read that information when it needs it, rather than having every detail built directly into the program itself.

Why Is That Useful?

There are several practical advantages to this approach:

  • Easier to maintain – If something changes, you may only need to update the data rather than change the underlying program.
  • Less duplication – Information can have one central source rather than being repeated throughout different parts of a system.
  • Easier automation – Software can read structured information and use it to make decisions about what it should do.
  • Easier to expand – Adding another option doesn’t necessarily mean rewriting the whole application.

It’s About Good System Design

The important point isn’t that JSON is somehow better simply because it’s modern or technical.

It’s that using a sensible structure can make a system easier to understand, maintain, and change.

That’s something I think about quite a lot when building systems for RD3 Tech.

A system shouldn’t just work today. It should also be possible to understand what it is doing and make changes later without creating a bigger problem.

Building for the Future

Getting something working is only the first step. You also want to be able to change it six months from now without creating a bigger problem.

That applies whether you’re building a small automation, a website, a business system, or something much more complicated.

Good technology isn’t just about making something work. It’s about making it maintainable, adaptable, and appropriate for the problem you’re trying to solve.

If you’re looking at automating a business process or connecting different systems together, RD3 Tech can help look at the problem first and work out what sort of solution makes sense.

Behind the Scenes: The Technology Stack Behind the RD3 Tech Website

How the RD3 Tech Website Works Behind the Scenes

A website can look quite simple from the outside.

You see the pages, menus, images and contact forms. What you don’t see is the collection of different technologies and services working behind them.

The RD3 Tech website is built using WordPress as its content management system, with a custom RD3 Starter Theme providing the foundation for the site’s design, layout and structure.

There is also custom PHP, CSS and JavaScript where they provide something useful, rather than adding another plugin simply because one happens to exist.

The site uses custom functionality for things such as forms, content management and other parts of the website. External services are then used where they make sense, rather than trying to make the website do everything itself.

Keeping Development Under Control

GitHub is also part of the development workflow. This allows changes to the website code to be managed, tracked and reviewed rather than simply editing files and hoping everything continues to work afterwards.

This becomes particularly useful as a website grows. When something changes, there is a clearer record of what was changed and why. It also makes it easier to work on improvements without losing track of previous versions.

More Than Just the Website

There are also systems outside the website itself.

Google Workspace handles business email and related services. Google Forms and Apps Script are used for parts of the enquiry process, while structured configuration such as JSON helps keep some application logic separate from the data it uses.

This means the website isn’t operating in isolation. It is part of a wider system where different services have different jobs.

The Infrastructure You Don’t Normally See

Then there is the infrastructure that most visitors never see — hosting, DNS, email authentication, security and the connections between the different services.

These systems can be invisible when everything is working properly. When something goes wrong, however, they can suddenly become very important.

An email might not arrive because of an authentication problem. A form might fail because two systems can no longer communicate correctly. A website might be working perfectly while a DNS problem prevents someone from reaching it.

Good technology is often about making sure these individual pieces work together reliably.

Technology Should Have a Purpose

None of these technologies are particularly useful simply because they are technically interesting.

They are useful when they help the website achieve something.

That might mean making it easier for someone to contact RD3 Tech, making the site easier to maintain, improving reliability, reducing unnecessary complexity or allowing the system to grow without needing to rebuild everything from scratch.

The same principle applies to technology in a business. The goal shouldn’t be to use the most complicated or newest technology available. It should be to use the right technology for the job.

A Website Is More Than What You See

A good website isn’t just about how it looks. It’s about how well all the pieces work together.

If your business website has become difficult to maintain, your online services have grown complicated, or you’re simply not sure how the different pieces of your technology setup fit together, RD3 Tech can help you look at the bigger picture.

Sometimes the best solution isn’t another plugin or another piece of technology. Sometimes it’s simply understanding what you already have and making it work better.

© 2026 RD3 Tech. All rights reserved.