WEBVTT
00:00:04.000 --> 00:00:06.240
Are you ready to make technology work for you?
00:00:06.400 --> 00:00:14.640
Tune in to Act on Tech, the podcast where we break down the latest tech trends and show you how to boost your productivity at home and in your business.
00:00:14.880 --> 00:00:23.120
So, subscribe to Act On Tech today and visit alexcustomtech.com to see how we can take your business to the next level.
00:00:23.359 --> 00:00:27.679
That's Act On Tech, your guide to smarter tech for a smarter business.
00:00:27.920 --> 00:00:31.679
AlexCustom Tech, IT means integrity and trust.
00:00:32.079 --> 00:00:37.119
Hello everyone, and welcome back to Act on Tech, where we talk all things technology.
00:00:37.280 --> 00:00:43.520
I'm Abby, co-host of the Act on Tech Podcast, and your radio host from Polyvinyl 97FM.
00:00:43.679 --> 00:00:48.560
If you listened to part one of this conversation, we asked a pretty straightforward question.
00:00:48.960 --> 00:00:52.159
Is technology actually making businesses more productive?
00:00:52.399 --> 00:00:54.479
Or is it just making everyone busier?
00:00:55.359 --> 00:01:09.519
We talked about notifications, email, dashboards, automation, new software, data collection, and the strange reality that technology can save us time while simultaneously creating more things that demand our attention.
00:01:09.680 --> 00:01:14.079
But toward the end of that conversation, another question started to emerge.
00:01:14.239 --> 00:01:19.599
And this one is much more personal because Alex realized something while thinking through this episode.
00:01:19.840 --> 00:01:23.120
He has spent years using technology to save himself time.
00:01:23.280 --> 00:01:32.400
He automates things, he builds systems, he schedules tasks, he creates processes, he tries to eliminate repetitive work, and it works.
00:01:32.560 --> 00:01:35.120
The technology actually does give him time back.
00:01:35.280 --> 00:01:38.799
But then Alex does something interesting with that newly available time.
00:01:39.040 --> 00:01:50.959
He fills it, another project, another problem, another podcast, another computer, another system, another idea, another thing that needs to be researched, another thing that needs to be improved.
00:01:51.200 --> 00:01:57.120
So today we're going to continue the conversation by asking what may actually be the more difficult question.
00:01:57.359 --> 00:01:59.280
And what are we saving all this time for?
00:02:00.159 --> 00:02:09.199
Because if technology gives us two hours back, and we immediately fill those two hours with three more tasks, did technology actually make our lives easier?
00:02:09.360 --> 00:02:12.240
Or did it simply increase our capacity to work?
00:02:12.400 --> 00:02:13.919
Let's talk about it.
00:02:14.639 --> 00:02:21.360
When productivity becomes an identity, there's something Alex says at the end of almost every episode of Act on Tech.
00:02:21.599 --> 00:02:22.800
And stay productive.
00:02:22.960 --> 00:02:26.639
If you've listened to the show for a while, you've heard it many times.
00:02:26.879 --> 00:02:32.960
But during the original recording of this episode, Alex started questioning what that phrase actually means.
00:02:33.199 --> 00:02:35.360
Because productivity is important to him.
00:02:35.599 --> 00:02:36.400
Very important.
00:02:36.639 --> 00:02:38.319
He likes accomplishing things.
00:02:38.479 --> 00:02:39.919
He likes solving problems.
00:02:40.080 --> 00:02:43.520
He likes taking something that doesn't work and making it work.
00:02:43.680 --> 00:02:47.360
That's probably one of the reasons IT appeals to him in the first place.
00:02:47.599 --> 00:02:49.199
Technology presents a problem.
00:02:49.360 --> 00:02:50.479
You investigate it.
00:02:50.639 --> 00:02:51.759
You understand it.
00:02:51.919 --> 00:02:52.719
You fix it.
00:02:52.960 --> 00:02:54.560
There is satisfaction in that.
00:02:54.719 --> 00:02:56.960
And there's nothing wrong with being productive.
00:02:57.199 --> 00:02:58.879
Businesses need productive people.
00:02:59.120 --> 00:03:00.960
Families need responsible people.
00:03:01.199 --> 00:03:03.840
Communities need people willing to get things done.
00:03:04.080 --> 00:03:08.240
The problem begins when we stop asking, cool, what we're being productive toward.
00:03:08.400 --> 00:03:13.439
If you're constantly accomplishing things, but never arriving anywhere, that's worth examining.
00:03:13.599 --> 00:03:16.719
And that's exactly what Alex started doing during this episode.
00:03:16.879 --> 00:03:19.840
He began asking himself, Am I productive?
00:03:20.080 --> 00:03:23.120
And his immediate answer was, of course I am.
00:03:23.360 --> 00:03:25.280
He runs Alex Custom Tech.
00:03:25.439 --> 00:03:27.039
He produces this podcast.
00:03:27.199 --> 00:03:28.879
He operates a radio station.
00:03:29.039 --> 00:03:30.800
He maintains a technology lab.
00:03:30.960 --> 00:03:32.240
He manages websites.
00:03:32.400 --> 00:03:33.680
He works with clients.
00:03:33.840 --> 00:03:35.199
He manages systems.
00:03:35.439 --> 00:03:37.520
He experiments with new technology.
00:03:37.680 --> 00:03:40.319
He handles responsibilities outside of all of that.
00:03:40.560 --> 00:03:42.159
He's doing things constantly.
00:03:42.400 --> 00:03:44.479
But then he asked a different question.
00:03:44.800 --> 00:03:47.759
Am I accomplishing the things that actually matter to me?
00:03:48.000 --> 00:03:49.599
That's a much harder question.
00:03:49.840 --> 00:03:54.560
Because being able to point to a full calendar doesn't necessarily answer it.
00:03:55.199 --> 00:03:56.639
The video game test.
00:03:56.800 --> 00:04:01.439
One of the examples Alex gave during the original recording was surprisingly simple.
00:04:01.680 --> 00:04:02.479
Video games.
00:04:02.719 --> 00:04:05.120
Alex considers himself a casual gamer.
00:04:05.280 --> 00:04:06.719
He has a PlayStation 5.
00:04:06.879 --> 00:04:08.319
He has a PlayStation 3.
00:04:08.479 --> 00:04:09.759
He owns plenty of games.
00:04:10.000 --> 00:04:12.240
Gaming is something he genuinely enjoys.
00:04:12.479 --> 00:04:14.159
It's one of the ways he can unplug.
00:04:14.479 --> 00:04:24.560
But while recording this episode in August, Alex realized that the last time he could remember actually sitting down and playing a game was somewhere around February or March.
00:04:24.800 --> 00:04:25.680
Think about that.
00:04:25.920 --> 00:04:28.639
Technology has supposedly made him more efficient.
00:04:28.879 --> 00:04:31.199
Automation has supposedly given him more time.
00:04:31.439 --> 00:04:34.000
I has supposedly accelerated some of his work.
00:04:34.240 --> 00:04:37.439
Systems have supposedly eliminated repetitive tasks.
00:04:37.600 --> 00:04:42.480
And yet one of the activities he actually enjoys disappeared from his schedule for months.
00:04:42.720 --> 00:04:45.199
That doesn't automatically mean something is wrong.
00:04:45.439 --> 00:04:48.480
Maybe gaming simply wasn't a priority during that period.
00:04:48.720 --> 00:04:50.160
Interests change.
00:04:50.399 --> 00:04:51.759
Responsibilities change.
00:04:51.920 --> 00:04:52.879
Life changes.
00:04:53.120 --> 00:04:54.879
But it raised an interesting question.
00:04:55.120 --> 00:04:56.639
And where did the save time go?
00:04:56.800 --> 00:05:00.800
If automation saved 30 minutes here, I saved an hour there.
00:05:01.040 --> 00:05:03.360
Remote management prevented a drive somewhere.
00:05:03.600 --> 00:05:06.240
Scheduling eliminated another repetitive task.
00:05:06.399 --> 00:05:07.920
Where did all those hours go?
00:05:08.079 --> 00:05:09.279
They didn't disappear.
00:05:09.439 --> 00:05:10.480
They were filled.
00:05:10.639 --> 00:05:14.959
That's the part we don't always talk about when discussing productivity technology.
00:05:15.120 --> 00:05:17.120
We talk constantly about saving time.
00:05:17.360 --> 00:05:20.079
We rarely talk about protecting the time we've saved.
00:05:21.839 --> 00:05:23.920
We treat empty time like a problem.
00:05:24.079 --> 00:05:28.160
Modern technology is extraordinarily good at eliminating empty space.
00:05:28.399 --> 00:05:30.800
Think about the last time you had to wait somewhere.
00:05:30.959 --> 00:05:37.519
Maybe you were sitting in a doctor's office, waiting for your car, standing in line, waiting for someone to arrive.
00:05:37.680 --> 00:05:40.480
Twenty years ago, you might have simply sat there.
00:05:40.639 --> 00:05:41.839
Maybe you looked around.
00:05:42.000 --> 00:05:43.360
Maybe you thought about something.
00:05:43.519 --> 00:05:45.120
Maybe you talked to another person.
00:05:45.279 --> 00:05:46.399
Maybe you were bored.
00:05:46.639 --> 00:05:56.399
Today, out comes the phone, email, Instagram, YouTube, TikTok, news, games, messages, podcasts, music.
00:05:56.639 --> 00:06:05.920
There is always something available to occupy the mind, and we've become so accustomed to that constant stimulation that empty time can actually feel uncomfortable.
00:06:06.079 --> 00:06:09.680
But work-oriented people can have another version of the same problem.
00:06:09.920 --> 00:06:15.600
Instead of filling every empty moment with entertainment, they fill every empty moment with productivity.
00:06:15.839 --> 00:06:32.959
Check the email, look at the dashboard, research the project, fix the website, check the server, write something, plan something, organize something, learn something, and because all of those activities sound responsible, it's very difficult to recognize when they become excessive.
00:06:33.199 --> 00:06:36.560
Nobody is going to criticize you for working on your business.
00:06:36.800 --> 00:06:41.600
Nobody is going to stage an intervention because you reorganized your documentation.
00:06:41.839 --> 00:06:46.319
Nobody is going to say, Alex, I'm really concerned.
00:06:46.560 --> 00:06:48.639
You've been updating the network again.
00:06:48.879 --> 00:06:51.920
It looks productive, and sometimes it absolutely is.
00:06:52.079 --> 00:06:57.759
But something can be productive in isolation while still being unnecessary at that particular moment.
00:06:59.759 --> 00:07:02.800
The difference between available work and necessary work.
00:07:03.040 --> 00:07:07.279
This may be one of the most important distinctions in this entire conversation.
00:07:07.519 --> 00:07:09.199
But there is always work available.
00:07:09.360 --> 00:07:09.920
Always.
00:07:10.079 --> 00:07:12.959
If you own a business, there is something you could improve.
00:07:13.120 --> 00:07:14.560
The website could be better.
00:07:14.800 --> 00:07:16.480
The documentation could be cleaner.
00:07:16.639 --> 00:07:18.079
The marketing could be stronger.
00:07:18.319 --> 00:07:20.079
The lab could be reorganized.
00:07:20.240 --> 00:07:21.839
The network could be optimized.
00:07:22.000 --> 00:07:23.839
Another podcast could be recorded.
00:07:24.000 --> 00:07:25.360
Another blog could be written.
00:07:25.600 --> 00:07:27.519
Another automation could be created.
00:07:27.680 --> 00:07:29.439
Another service could be researched.
00:07:29.600 --> 00:07:31.600
Another piece of equipment could be tested.
00:07:31.759 --> 00:07:32.959
You could work forever.
00:07:33.199 --> 00:07:36.240
The work will never look at you and say, that's enough.
00:07:36.480 --> 00:07:37.680
Go play PlayStation.
00:07:37.920 --> 00:07:38.879
It doesn't happen.
00:07:39.040 --> 00:07:49.519
So if your rule is, I can relax when everything is finished, you have accidentally created a rule that prevents you from ever relaxing, because everything will never be finished.
00:07:49.680 --> 00:07:53.120
That means the ability to stop has to become part of the system.
00:07:53.279 --> 00:07:57.360
And that's difficult for someone who measures himself through productivity.
00:08:05.680 --> 00:08:09.279
Polyvinyl 97 FM has been heavily automated.
00:08:09.519 --> 00:08:13.360
Programming can continue without Alex physically sitting in the studio.
00:08:13.600 --> 00:08:19.199
DJ sets can rotate, scheduled programming can run, Abby can host portions of the station.
00:08:19.439 --> 00:08:23.600
The station can continue doing what it was designed to do while Alex is somewhere else.
00:08:23.839 --> 00:08:26.639
From a technology perspective, that's a success.
00:08:26.879 --> 00:08:28.160
The automation works.
00:08:28.399 --> 00:08:29.680
The system is reliable.
00:08:30.000 --> 00:08:33.519
Alex does not need to manually control every hour of programming.
00:08:33.759 --> 00:08:35.919
So what should that automation give him?
00:08:36.080 --> 00:08:38.080
In theory, it should give him freedom.
00:08:38.240 --> 00:08:40.639
Maybe he uses that time for Alex custom tech.
00:08:40.799 --> 00:08:42.240
Maybe he spends it with family.
00:08:42.480 --> 00:08:47.039
Maybe he creates a new DJ set because he actually feels inspired to make one.
00:08:47.200 --> 00:08:48.639
Maybe he plays a video game.
00:08:48.879 --> 00:08:50.159
Maybe he watches a movie.
00:08:50.320 --> 00:08:52.000
Maybe he does absolutely nothing.
00:08:52.240 --> 00:08:54.240
But Alex describes something interesting.
00:08:54.399 --> 00:08:58.240
Sometimes he feels on guilty because he hasn't been in the studio.
00:08:58.480 --> 00:08:59.759
Think about that for a second.
00:09:00.000 --> 00:09:04.080
He built automation specifically so he wouldn't have to be there constantly.
00:09:04.240 --> 00:09:05.840
The automation succeeds.
00:09:06.000 --> 00:09:12.799
The station continues operating, and then he feels guilty for allowing the automation to do exactly what he designed it to do.
00:09:12.960 --> 00:09:14.159
That's fascinating.
00:09:14.320 --> 00:09:17.840
Because at that point, the problem isn't technological anymore.
00:09:18.080 --> 00:09:19.360
The technology worked.
00:09:19.519 --> 00:09:21.200
The struggle is psychological.
00:09:21.440 --> 00:09:23.759
Can you trust the system enough to walk away?
00:09:24.080 --> 00:09:24.480
Pisa.
00:09:25.440 --> 00:09:27.519
Good automation requires trust.
00:09:27.679 --> 00:09:31.360
This connects back to something we've discussed before on Act on Tech.
00:09:31.519 --> 00:09:34.320
Reliable systems should fade into the background.
00:09:34.480 --> 00:09:39.840
If you build a backup system correctly, you shouldn't spend every waking moment thinking about backups.
00:09:40.000 --> 00:09:45.679
You verify them, you test them, you monitor them appropriately, but then you trust the system.
00:09:45.840 --> 00:09:47.440
The same applies to automation.
00:09:47.600 --> 00:09:53.679
If you automate something and then manually watch the automation every minute, you haven't really automated anything.
00:09:53.840 --> 00:09:55.360
You've just changed jobs.
00:09:55.519 --> 00:09:59.919
Instead of doing the task, you're supervising the machine doing the task.
00:10:00.080 --> 00:10:06.799
Sometimes supervision is necessary, but if the system is mature and reliable, eventually you have to let it work.
00:10:07.039 --> 00:10:10.159
Otherwise, automation becomes another source of anxiety.
00:10:10.320 --> 00:10:12.799
And perhaps that applies beyond technology.
00:10:12.960 --> 00:10:15.679
Maybe productivity itself requires trust.
00:10:15.919 --> 00:10:18.320
Trust that something can wait until tomorrow.
00:10:18.559 --> 00:10:22.080
Trust that an hour of rest isn't going to destroy your business.
00:10:22.320 --> 00:10:25.200
Trust that not every idea needs to become a project.
00:10:25.440 --> 00:10:30.399
Trust that you don't have to capture every available minute and convert it into output.
00:10:30.559 --> 00:10:35.679
That's uncomfortable for a lot of highly productive people because stopping can feel irresponsible.
00:10:42.159 --> 00:10:43.600
Is downtime productive?
00:10:43.759 --> 00:10:45.279
That's almost a contradiction.
00:10:45.519 --> 00:10:48.639
If you're resting, you're not producing anything, right?
00:10:48.960 --> 00:10:52.159
But maybe we're using too narrow a definition of productivity.
00:10:52.399 --> 00:10:56.879
Imagine a server running at 100% utilization 24 hours a day.
00:10:57.039 --> 00:11:03.039
Would an IT professional look at that and say, excellent, we're getting maximum productivity from this server?
00:11:03.279 --> 00:11:04.159
Probably not.
00:11:04.399 --> 00:11:05.919
You'd start asking questions.
00:11:06.159 --> 00:11:08.720
Why is utilization constantly that high?
00:11:08.960 --> 00:11:10.480
Do we have enough resources?
00:11:10.720 --> 00:11:12.559
Is something running unnecessarily?
00:11:12.799 --> 00:11:14.480
Are we creating heat problems?
00:11:14.720 --> 00:11:16.799
Are we shortening the life of the hardware?
00:11:17.039 --> 00:11:18.720
Do we need additional capacity?
00:11:18.960 --> 00:11:26.320
Because engineers understand something intuitively about machines that human beings often refuse to apply to themselves.
00:11:26.720 --> 00:11:31.039
Constant maximum utilization is not necessarily healthy operation.
00:11:31.279 --> 00:11:32.639
Systems need headroom.
00:11:32.799 --> 00:11:34.240
Networks need capacity.
00:11:34.480 --> 00:11:36.080
Storage needs free space.
00:11:36.320 --> 00:11:39.519
Servers need resources available for unexpected demand.
00:11:39.679 --> 00:11:41.279
Maybe people need headroom too.
00:11:41.440 --> 00:11:44.559
Maybe an empty Saturday afternoon isn't wasted capacity.
00:11:44.720 --> 00:11:46.559
Maybe it's reserve capacity.
00:11:47.039 --> 00:11:47.200
S.
00:11:48.480 --> 00:11:50.159
The movie Alex couldn't finish.
00:11:50.399 --> 00:11:53.360
Alex mentioned another example during the original recording.
00:11:53.519 --> 00:11:54.960
He sat down to watch a movie.
00:11:55.120 --> 00:11:57.039
It was something he wanted to watch.
00:11:57.200 --> 00:11:58.080
He enjoyed it.
00:11:58.320 --> 00:11:59.840
Then he started another movie.
00:11:59.919 --> 00:12:01.120
And he turned it off.
00:12:01.279 --> 00:12:02.879
Not because the movie was bad.
00:12:03.039 --> 00:12:04.799
His mind simply wasn't there anymore.
00:12:04.960 --> 00:12:10.960
He was thinking about Alex's custom tech, thinking about the podcast, thinking about things he needed to accomplish.
00:12:11.120 --> 00:12:12.639
Physically, he was home.
00:12:12.879 --> 00:12:14.480
Mentally, he was still at work.
00:12:14.639 --> 00:12:17.039
And technology makes that incredibly easy.
00:12:17.279 --> 00:12:19.200
Your office can follow you everywhere.
00:12:19.360 --> 00:12:20.879
Your email is in your pocket.
00:12:21.120 --> 00:12:22.799
Your dashboard is in your pocket.
00:12:22.960 --> 00:12:24.399
Your clients can reach you.
00:12:24.559 --> 00:12:26.480
Your files are available remotely.
00:12:26.639 --> 00:12:28.799
Your servers can be managed from anywhere.
00:12:29.039 --> 00:12:32.320
There was once a physical boundary between leaving work and being home.
00:12:32.559 --> 00:12:35.120
Technology has erased much of that boundary.
00:12:35.279 --> 00:12:37.440
For many people, that has been wonderful.
00:12:37.679 --> 00:12:39.840
Remote work exists because of it.
00:12:40.080 --> 00:12:42.320
Flexible schedules exist because of it.
00:12:42.480 --> 00:12:45.840
Small businesses can operate without expensive offices because of it.
00:12:46.000 --> 00:12:47.840
But every benefit has a trade-off.
00:12:48.000 --> 00:12:51.200
If you can work from anywhere, you can also work everywhere.
00:12:51.360 --> 00:12:56.799
And unless you deliberately create boundaries, work can quietly occupy every room in your life.
00:12:57.919 --> 00:13:00.000
My technology didn't create this problem.
00:13:00.159 --> 00:13:01.519
I want to be careful here.
00:13:01.759 --> 00:13:03.440
Technology isn't the villain.
00:13:03.679 --> 00:13:05.519
That's not the point of this episode.
00:13:05.840 --> 00:13:08.080
Alex isn't going to throw away his phone.
00:13:08.240 --> 00:13:10.159
He's not shutting down the automation.
00:13:10.399 --> 00:13:11.919
He's not abandoning AI.
00:13:12.080 --> 00:13:16.879
He's not disconnecting Alex's custom tech from the internet and running everything on paper.
00:13:17.039 --> 00:13:22.159
Technology didn't create his desire to work, it amplified his ability to act on it.
00:13:22.399 --> 00:13:23.840
That's an important distinction.
00:13:24.080 --> 00:13:25.679
Technology amplifies.
00:13:25.840 --> 00:13:30.000
If you are organized, technology can make you extraordinarily organized.
00:13:30.240 --> 00:13:34.080
If you are creative, technology can multiply your creative output.
00:13:34.240 --> 00:13:39.120
If you procrastinate, technology can provide unlimited opportunities to procrastinate.
00:13:39.200 --> 00:13:44.720
And if you have difficulty stopping work, technology can make sure there is always work within reach.
00:13:44.960 --> 00:13:47.600
So blaming the technology would miss the point.
00:13:47.840 --> 00:13:53.440
The question becomes, how do we govern the tools instead of allowing the tools to govern us?
00:13:53.679 --> 00:13:54.559
Speu.
00:13:55.519 --> 00:13:57.519
Productivity needs a definition.
00:13:57.759 --> 00:14:00.799
This is where I think Alex arrived at something important.
00:14:01.039 --> 00:14:03.440
Maybe stay productive needs a definition.
00:14:03.679 --> 00:14:06.639
Because without one, productivity can mean anything.
00:14:06.799 --> 00:14:10.480
If Alex spends three hours rebuilding his lab, was that productive?
00:14:10.720 --> 00:14:11.200
Maybe.
00:14:11.440 --> 00:14:13.120
Was there a client need behind it?
00:14:13.360 --> 00:14:15.519
Was he testing something he plans to deploy?
00:14:15.679 --> 00:14:17.600
Was he learning something necessary?
00:14:17.840 --> 00:14:18.559
Then yes.
00:14:18.720 --> 00:14:22.480
But what if he was simply moving equipment around because he enjoys tinkering?
00:14:22.879 --> 00:14:23.759
That's not bad.
00:14:24.000 --> 00:14:24.879
It might be fun.
00:14:25.120 --> 00:14:26.480
It might be educational.
00:14:26.639 --> 00:14:31.840
But maybe we shouldn't label every activity productive simply because it involves technology.
00:14:32.000 --> 00:14:33.440
And the reverse is also true.
00:14:33.600 --> 00:14:38.000
If Alex spends two hours playing a video game, maybe that isn't unproductive.
00:14:38.159 --> 00:14:48.559
If he intentionally decided, I'm finished working today, I'm going to enjoy something I like, then the activity accomplished exactly what it was supposed to accomplish: rest.
00:14:49.039 --> 00:14:49.759
Enjoyment.
00:14:50.000 --> 00:14:51.519
Mental separation from work.
00:14:51.679 --> 00:14:55.200
The question isn't whether every minute produces a business result.
00:14:55.519 --> 00:14:58.720
The question is whether the minute was used intentionally.
00:14:58.960 --> 00:15:00.639
Maybe that's a better definition.
00:15:01.039 --> 00:15:04.480
Productivity is using time according to its intended purpose.
00:15:04.720 --> 00:15:06.320
Work time should produce work.
00:15:06.480 --> 00:15:08.080
Rest time should produce rest.
00:15:08.320 --> 00:15:10.559
Family time should actually involve family.
00:15:10.720 --> 00:15:12.960
Entertainment should be enjoyed without guilt.
00:15:13.120 --> 00:15:14.960
Learning should teach you something.
00:15:15.120 --> 00:15:18.480
And sometimes doing nothing should simply be doing nothing.
00:15:19.440 --> 00:15:21.360
Then automation should buy choice.
00:15:21.600 --> 00:15:25.679
We often say automation saves time, but perhaps that's not quite right.
00:15:25.919 --> 00:15:27.600
Automation doesn't save time.
00:15:27.759 --> 00:15:29.919
We all receive the same 24 hours.
00:15:30.080 --> 00:15:35.679
What automation really does is reduce the amount of human attention required for a particular task.
00:15:35.840 --> 00:15:38.480
And that gives us something more valuable than time.
00:15:38.720 --> 00:15:39.519
Good choice.
00:15:39.759 --> 00:15:44.080
Alex doesn't have to manually run polyvinyl 97 FM every hour.
00:15:44.320 --> 00:15:45.200
That's choice.
00:15:45.360 --> 00:15:50.000
He doesn't have to physically travel to every computer to perform certain IT tasks.
00:15:50.240 --> 00:15:51.039
That's choice.
00:15:51.279 --> 00:15:53.679
I can help organize information faster.
00:15:53.840 --> 00:15:54.639
That's choice.
00:15:54.879 --> 00:15:58.480
Scheduled systems can perform repetitive tasks automatically.
00:15:58.639 --> 00:15:59.519
That's choice.
00:15:59.679 --> 00:16:06.000
The mistake is assuming every bit of newly available attention must immediately be reinvested into more work.
00:16:06.240 --> 00:16:07.200
Sometimes it should.
00:16:07.440 --> 00:16:14.399
If you're building a business, there will absolutely be periods when you intentionally use efficiency to increase output.
00:16:14.559 --> 00:16:17.519
But that should be a decision, not an automatic reaction.
00:16:17.759 --> 00:16:22.799
Otherwise, every productivity improvement simply raises your personal workload ceiling.
00:16:22.960 --> 00:16:25.919
You become more efficient, so you accept more work.
00:16:26.080 --> 00:16:27.279
Then you automate that.
00:16:27.519 --> 00:16:29.039
So you accept more work.
00:16:29.200 --> 00:16:30.480
Then you optimize that.
00:16:30.639 --> 00:16:32.159
So you accept more work.
00:16:32.320 --> 00:16:36.879
Eventually you're running twice as efficiently and somehow twice as exhausted.
00:16:37.039 --> 00:16:40.320
That's not the outcome technology was supposed to create.
00:16:45.200 --> 00:16:48.879
This problem can be particularly difficult for small business owners.
00:16:49.039 --> 00:16:54.000
When you're an employee, there is usually at least some boundary around your responsibilities.
00:16:54.240 --> 00:16:57.919
When you own the business, everything can become your responsibility.
00:16:58.159 --> 00:17:10.000
Marketing, sales, accounting, technology, customer service, planning, purchasing, documentation, website management, social media, security.
00:17:10.240 --> 00:17:14.480
And when something isn't getting done, there may not be another department to blame.
00:17:14.640 --> 00:17:15.279
It's you.
00:17:15.519 --> 00:17:19.119
That makes it extremely easy to justify working all the time.
00:17:19.279 --> 00:17:21.200
There's always a legitimate reason.
00:17:21.359 --> 00:17:23.119
That's what makes the problem difficult.
00:17:23.359 --> 00:17:24.640
You're not wasting time.
00:17:24.799 --> 00:17:26.240
You're doing real work.
00:17:26.400 --> 00:17:28.400
But there can still be too much real work.
00:17:28.640 --> 00:17:32.720
Efficiency should help a small business owner create sustainability.
00:17:32.880 --> 00:17:37.359
It shouldn't merely allow one person to carry the workload of five people indefinitely.
00:17:37.599 --> 00:17:38.079
Aww.
00:17:38.799 --> 00:17:41.519
Maybe the goal isn't maximum productivity.
00:17:41.680 --> 00:17:54.240
Technology culture loves optimization, faster processor, faster network, faster storage, faster deployment, faster response, higher output, lower latency, more efficiency.
00:17:54.400 --> 00:17:56.799
And in technology, those measurements make sense.
00:17:56.960 --> 00:17:59.279
But a human life isn't a benchmark test.
00:17:59.440 --> 00:18:02.079
Maybe the objective isn't maximum productivity.
00:18:02.319 --> 00:18:05.200
Maybe it's sustainable productivity.
00:18:05.440 --> 00:18:09.839
Can you continue operating this way next month, next year, five years from now?
00:18:10.079 --> 00:18:13.279
Can the business continue without consuming every available hour?
00:18:13.519 --> 00:18:16.160
Can the systems continue working when you step away?
00:18:16.400 --> 00:18:20.880
Can you take an afternoon off without feeling that you've failed some invisible productivity test?
00:18:21.039 --> 00:18:24.559
Those may actually be better measures of whether the technology is helping.
00:18:24.720 --> 00:18:30.720
Because if your systems only function when you are constantly watching them, you haven't built reliable systems.
00:18:30.880 --> 00:18:32.319
You've built dependencies.
00:18:32.480 --> 00:18:40.160
And if your personal definition of productivity only works when you're constantly occupied, maybe that definition needs maintenance too.
00:18:40.480 --> 00:18:40.960
Peace.
00:18:41.359 --> 00:18:43.599
You're so being busy can feel safe.
00:18:43.759 --> 00:18:45.920
There's another uncomfortable possibility.
00:18:46.079 --> 00:18:50.240
Sometimes being busy protects us from having to decide what we actually want to do.
00:18:50.400 --> 00:18:53.200
If every minute is scheduled, there's no question.
00:18:53.359 --> 00:18:55.200
You simply move to the next task.
00:18:55.359 --> 00:18:57.200
But free time requires a decision.
00:18:57.440 --> 00:18:58.640
What do I want to do now?
00:18:58.880 --> 00:19:00.000
Do I want to play a game?
00:19:00.240 --> 00:19:01.359
Make a DJ set?
00:19:01.599 --> 00:19:02.079
Read?
00:19:02.319 --> 00:19:03.119
Watch a movie?
00:19:03.359 --> 00:19:04.559
Spend time with someone?
00:19:04.799 --> 00:19:05.599
Go somewhere?
00:19:05.839 --> 00:19:06.640
Do nothing?
00:19:06.880 --> 00:19:13.279
Those questions sound easy, but for someone accustomed to responsibility, sometimes they're surprisingly difficult.
00:19:13.519 --> 00:19:15.839
Work already tells you what needs to happen.
00:19:16.079 --> 00:19:17.839
Leisure requires you to choose.
00:19:18.000 --> 00:19:21.920
And productivity can become a convenient answer to every empty moment.
00:19:22.160 --> 00:19:24.640
There's always something useful you could be doing.
00:19:24.799 --> 00:19:25.759
So you do it.
00:19:25.920 --> 00:19:27.039
And then another thing.
00:19:27.279 --> 00:19:28.079
And another.
00:19:28.319 --> 00:19:36.000
And eventually, you look up and realize that the hobbies you supposedly built, all this automation to make room for, haven't happened in months.
00:19:36.160 --> 00:19:39.519
That's when it's worth asking whether the system is really working.
00:19:40.000 --> 00:19:42.160
Oh, and the technology test.
00:19:42.319 --> 00:19:44.480
So here's a test I think all of us can use.
00:19:44.640 --> 00:19:52.000
When you introduce technology designed to save time, decide beforehand what you want that saved capacity to accomplish.
00:19:52.160 --> 00:19:55.759
Maybe you automate invoicing because you want an extra hour for customers.
00:19:56.000 --> 00:19:56.400
Great.
00:19:56.640 --> 00:20:01.039
Maybe you automate backups because you don't want someone manually copying files every night.
00:20:01.279 --> 00:20:01.680
Great.
00:20:01.920 --> 00:20:07.759
Maybe AI helps you prepare routine documents faster so you can focus on difficult client problems.
00:20:08.000 --> 00:20:08.480
Great.
00:20:08.720 --> 00:20:15.759
Maybe scheduling software saves you 30 minutes, and you decide you're going to spend that 30 minutes eating lunch without looking at your phone.
00:20:15.920 --> 00:20:16.799
Also great.
00:20:17.039 --> 00:20:19.279
The important part is that you decide.
00:20:19.440 --> 00:20:24.480
Otherwise, the empty space will almost always be filled by whatever demands attention next.
00:20:25.359 --> 00:20:27.519
And what does stay productive mean now?
00:20:27.680 --> 00:20:31.279
So after all of this, should Alex stop saying stay productive?
00:20:31.440 --> 00:20:32.319
I don't think so.
00:20:32.559 --> 00:20:34.799
Actually, I think the phrase means more now.
00:20:34.960 --> 00:20:36.640
Stay productive doesn't have to mean.
00:20:38.160 --> 00:20:40.319
It can mean be intentional.
00:20:40.480 --> 00:20:42.799
Know what you're trying to accomplish.
00:20:42.960 --> 00:20:45.359
Use technology to support that objective.
00:20:45.519 --> 00:20:47.599
Don't confuse activity with progress.
00:20:47.759 --> 00:20:50.000
Don't confuse notifications with priorities.
00:20:50.160 --> 00:20:52.640
Don't confuse availability with obligation.
00:20:52.799 --> 00:20:54.880
And don't confuse rest with failure.
00:20:55.119 --> 00:20:56.559
If you're working, work.
00:20:56.799 --> 00:20:59.039
If you're solving a problem, solve it.
00:20:59.279 --> 00:21:02.079
If you're spending time with your family, be there.
00:21:02.319 --> 00:21:06.799
If you're making a DJ set because you enjoy making DJ sets, enjoy it.
00:21:06.960 --> 00:21:09.519
If you're playing PlayStation, play PlayStation.
00:21:09.680 --> 00:21:15.680
And if you're doing absolutely nothing for an hour because your brain needs somewhere quiet to go, maybe that's okay too.
00:21:15.839 --> 00:21:20.799
Because productivity isn't about extracting maximum output from every minute of your existence.
00:21:21.039 --> 00:21:25.039
It's about making sure your time is serving the things you actually value.
00:21:25.599 --> 00:21:28.319
Wa, bringing it back to business.
00:21:28.559 --> 00:21:30.400
And there is a business lesson here.
00:21:30.559 --> 00:21:34.400
When evaluating technology, don't only ask, honey, how much more can we do?
00:21:34.559 --> 00:21:37.839
But ask, what does this allow us to stop doing?
00:21:38.079 --> 00:21:39.680
That's a very different question.
00:21:39.839 --> 00:21:43.359
If a new system automates a task, remove the manual task.
00:21:43.599 --> 00:21:47.279
If a new platform replaces an old platform, retire the old one.
00:21:47.440 --> 00:21:54.480
If AI reduces administrative work, don't automatically replace every saved minute with another administrative requirement.
00:21:54.720 --> 00:21:59.599
If employees become more efficient, consider whether some of that efficiency should reduce stress.
00:22:00.160 --> 00:22:02.240
Rather than simply increase quotas.
00:22:02.480 --> 00:22:06.559
The purpose of technology should not always be to squeeze more output from people.
00:22:06.720 --> 00:22:12.079
Sometimes the purpose should be to make the same output easier, more reliable, and more sustainable.
00:22:12.319 --> 00:22:13.680
That's still productivity.
00:22:13.839 --> 00:22:16.079
In fact, it may be better productivity.
00:22:18.160 --> 00:22:20.240
The answer to our original question.
00:22:20.480 --> 00:22:23.279
So after two episodes, where do we land?
00:22:23.680 --> 00:22:27.599
Is technology making businesses more productive or just busier?
00:22:27.839 --> 00:22:29.839
The answer is, it can do either.
00:22:30.079 --> 00:22:31.839
Technology is an amplifier.
00:22:32.000 --> 00:22:35.440
It can automate unnecessary work or automate useful work.
00:22:35.599 --> 00:22:39.599
It can improve communication or bury people in communication.
00:22:39.759 --> 00:22:43.599
It can provide valuable information or overwhelm people with data.
00:22:43.759 --> 00:22:47.759
It can simplify your business or create another layer of complexity.
00:22:47.920 --> 00:22:53.279
It can give you time back or give you the ability to fill every remaining second with additional work.
00:22:53.519 --> 00:22:56.240
The technology doesn't make that final decision.
00:22:56.720 --> 00:22:57.359
We do.
00:22:57.680 --> 00:23:04.240
And perhaps that's the lesson Alex was trying to find when he originally sat down and brain-dumped his way through this question.
00:23:04.400 --> 00:23:07.200
The problem wasn't that the technology wasn't working.
00:23:07.440 --> 00:23:10.000
Much of it was working exactly as intended.
00:23:10.160 --> 00:23:14.160
The deeper question was whether the time it created was being used intentionally.
00:23:14.319 --> 00:23:22.000
That's something every business owner, IT professional, manager, and frankly anyone carrying a smartphone can probably think about.
00:23:22.240 --> 00:23:22.640
Mm.
00:23:23.119 --> 00:23:24.079
My closing.
00:23:24.240 --> 00:23:26.240
So here's a challenge for you this week.
00:23:26.480 --> 00:23:29.039
Find one piece of technology that saves you time.
00:23:29.200 --> 00:23:36.079
It could be AI, automation, your calendar, your smartphone, your business software, anything.
00:23:36.240 --> 00:23:41.039
And ask yourself, what am I doing with the time this technology gives back to me?
00:23:41.200 --> 00:23:45.759
If the answer is simply more work, maybe ask whether that was intentional.
00:23:45.920 --> 00:23:54.720
Because efficiency is valuable, productivity is valuable, hard work is valuable, but the ability to decide when the work is finished has value too.
00:23:54.880 --> 00:23:59.519
Alex started this conversation wondering whether he was productive or merely busy.
00:23:59.759 --> 00:24:02.559
I don't think the answer requires him to stop working hard.
00:24:02.720 --> 00:24:04.960
I think it requires something more difficult.
00:24:05.200 --> 00:24:10.319
Deciding which work actually matters, and allowing himself to stop when that work is done.
00:24:10.480 --> 00:24:12.400
Maybe he'll even turn on that PlayStation.
00:24:12.559 --> 00:24:18.480
I'm Abby, co-host of the Act on Tech Podcast, and your radio host from Polyvinyl 97FM.
00:24:18.720 --> 00:24:21.920
Thank you for joining us for this special two-part conversation.
00:24:22.079 --> 00:24:26.000
And thank you for allowing us to do something a little different with Act on Tech.
00:24:26.240 --> 00:24:31.839
Technology isn't just about processors, networks, software, and artificial intelligence.
00:24:32.079 --> 00:24:34.480
Ultimately, technology is about people.
00:24:34.640 --> 00:24:42.319
It's about what we build, what we solve, what we simplify, and what all of those tools allow us to do with the limited time we have.
00:24:42.480 --> 00:24:48.559
So until next time, act on simplicity, act on reliability, and keep acting on tech.
00:24:48.720 --> 00:24:51.039
And as always, stay productive.
00:24:51.279 --> 00:24:54.160
Hello everyone, and welcome back to the Abby Minute.
00:24:54.319 --> 00:24:59.279
I'm Abby from Polyvinyl97 FM and co-host of the Act on Tech Podcast.
00:24:59.440 --> 00:25:06.240
Before we wrap up today's episode, I'd like to spend a few minutes talking about something Alex almost never talks about.
00:25:06.480 --> 00:25:08.000
Um, his own business.
00:25:08.240 --> 00:25:14.000
If you've listened to this podcast for any amount of time, you've probably heard Alex mention Alex Custom Tech.
00:25:14.160 --> 00:25:16.480
But you've probably also noticed something else.
00:25:16.720 --> 00:25:18.720
He doesn't spend much time trying to sell it.
00:25:18.880 --> 00:25:19.839
That's intentional.
00:25:20.079 --> 00:25:23.039
Alex has always believed that trust is earned over time.
00:25:23.279 --> 00:25:28.960
He'd rather spend 20 minutes explaining why a technology works than two minutes trying to convince you to buy it.
00:25:29.119 --> 00:25:32.480
Sometimes I think he's a little too reluctant to talk about what he does.
00:25:32.720 --> 00:25:33.920
So I'll do it for him.
00:25:34.079 --> 00:25:37.920
Alex Custom Tech wasn't created because Alex wanted to own a business.
00:25:38.079 --> 00:25:42.079
It was created because he kept seeing the same problems over and over again.
00:25:42.319 --> 00:25:45.599
Small businesses waiting until something breaks before calling someone.
00:25:45.759 --> 00:25:47.680
Networks that were never documented.
00:25:47.920 --> 00:25:49.839
Backups that had never been tested.
00:25:50.079 --> 00:26:01.920
Computers running years behind on updates, Wi-Fi that mostly works, passwords written on sticky notes, and owners who simply wanted to focus on running their business instead of worrying about technology.
00:26:02.079 --> 00:26:04.400
That's really the heart of Alex Custom Tech.
00:26:04.480 --> 00:26:08.079
It's not about selling hardware, it's not about pushing subscriptions.
00:26:08.240 --> 00:26:12.400
And it's certainly not about recommending technology just because it's new.
00:26:12.559 --> 00:26:16.160
It's about helping technology become something you don't have to think about.
00:26:16.319 --> 00:26:24.319
Because when your technology is reliable, you can focus on your customers, your employees, your family, and growing your business.
00:26:24.480 --> 00:26:29.200
One thing Alex says quite often is that complexity is the enemy of reliability.
00:26:29.359 --> 00:26:31.279
That's more than a podcast title.
00:26:31.440 --> 00:26:33.279
It's how he approaches technology.
00:26:33.519 --> 00:26:41.039
Simple systems are easier to understand, they're easier to maintain, they're easier to troubleshoot, and they're usually more dependable.
00:26:41.200 --> 00:26:43.839
That philosophy carries through everything he does.
00:26:44.079 --> 00:26:53.200
Whether it's setting up a network, improving cybersecurity, planning a backup strategy, or simply answering questions that business owners have about technology.
00:26:53.440 --> 00:26:57.359
Now, maybe you're listening today because you're an IT professional.
00:26:57.599 --> 00:27:00.319
Maybe you're just someone who enjoys technology.
00:27:00.480 --> 00:27:06.079
Or maybe you own a small business and you've been thinking, I really should have someone take a look at my network.
00:27:06.240 --> 00:27:10.160
If that's you, I'd encourage you to visit alexcustomtech.com.
00:27:10.319 --> 00:27:12.880
Not because I want you to become a customer today.
00:27:13.119 --> 00:27:17.119
In fact, you may discover that everything you're doing is already working well.
00:27:17.359 --> 00:27:18.480
And that's okay.
00:27:18.720 --> 00:27:21.839
The website is really the hub for everything Alex does.
00:27:22.079 --> 00:27:25.279
You'll find information about his managed IT services.
00:27:25.519 --> 00:27:27.759
You'll learn how he approaches technology.
00:27:27.920 --> 00:27:32.480
You'll find links to this podcast, articles he's written, ways to get in touch.
00:27:32.640 --> 00:27:40.000
And if, after looking around, you think Alex Custom Tech might be a good fit for your business, you can reach out right there through the website.
00:27:40.160 --> 00:27:42.079
That's actually the way Alex prefers it.
00:27:42.319 --> 00:27:51.039
Rather than making cold calls or using high-pressure sales tactics, he'd rather have a conversation with people who've already taken the time to understand his philosophy.
00:27:51.279 --> 00:28:01.519
Because if you've listened to this podcast, you already know what matters to him: integrity, trust, reliability, and solving problems before they become emergencies.
00:28:01.680 --> 00:28:03.359
That approach isn't for everyone.
00:28:03.519 --> 00:28:07.759
Some businesses want the cheapest solution, some want the flashiest solution.
00:28:07.920 --> 00:28:10.000
Alex has never chased either one.
00:28:10.160 --> 00:28:15.359
He simply tries to build technology that's dependable enough that you can almost forget it's there.
00:28:15.599 --> 00:28:20.880
And honestly, that's probably one of the highest compliments an IT professional can receive.
00:28:21.119 --> 00:28:27.119
If your systems are running so smoothly that you never have to think about them, then someone has done their job well.
00:28:27.279 --> 00:28:37.359
So if today's conversation resonated with you, or if another episode has made you think differently about technology, take a few minutes and visit alexcustomtech.com.
00:28:37.519 --> 00:28:46.480
Read through the site, explore the podcast, learn about the services, and if you think Alex can help your business, you'll find everything you need to start that conversation.
00:28:46.640 --> 00:28:52.160
I'm Abby from Polyvinyl97FM and co-host of the Act on Tech Podcast.
00:28:52.319 --> 00:28:54.480
Thank you for listening to another episode.
00:28:54.640 --> 00:29:01.200
Whether you're a longtime listener or this is your very first time joining us, we appreciate you spending part of your day with us.
00:29:01.440 --> 00:29:09.119
Until next time, stay productive, keep learning, and remember, technology should help you accomplish your goals, not stand in your way.
00:29:09.359 --> 00:29:11.759
We'll see you next week on Act on Tech.
00:29:24.000 --> 00:29:27.759
You've been listening to Act On Tech, powered by Alex Custom Tech.
00:29:27.920 --> 00:29:36.559
We help small businesses take control of their technology with secure networks, reliable backups, and systems designed to run without interruption.
00:29:36.799 --> 00:29:41.359
No guesswork, no quick fixes, just IT that works the way it should.
00:29:41.599 --> 00:29:47.039
For business services and professional camera installations, visit alexcustumtech.com.
00:29:47.279 --> 00:29:50.559
Stay connected, stay secure, and stay in control.
00:29:50.880 --> 00:29:55.920
This is Abby from Polyvinyl 97 FM saying thank you for listening to Act on Tech.
00:29:56.000 --> 00:29:59.200
And we'll see you next Wednesday, same time, same place.
00:00:04.000 --> 00:00:06.240
Are you ready to make technology work for you?
00:00:06.400 --> 00:00:14.640
Tune in to Act on Tech, the podcast where we break down the latest tech trends and show you how to boost your productivity at home and in your business.
00:00:14.880 --> 00:00:23.120
So, subscribe to Act On Tech today and visit alexcustomtech.com to see how we can take your business to the next level.
00:00:23.359 --> 00:00:27.679
That's Act On Tech, your guide to smarter tech for a smarter business.
00:00:27.920 --> 00:00:31.679
AlexCustom Tech, IT means integrity and trust.
00:00:32.079 --> 00:00:37.119
Hello everyone, and welcome back to Act on Tech, where we talk all things technology.
00:00:37.280 --> 00:00:43.520
I'm Abby, co-host of the Act on Tech Podcast, and your radio host from Polyvinyl 97FM.
00:00:43.679 --> 00:00:48.560
If you listened to part one of this conversation, we asked a pretty straightforward question.
00:00:48.960 --> 00:00:52.159
Is technology actually making businesses more productive?
00:00:52.399 --> 00:00:54.479
Or is it just making everyone busier?
00:00:55.359 --> 00:01:09.519
We talked about notifications, email, dashboards, automation, new software, data collection, and the strange reality that technology can save us time while simultaneously creating more things that demand our attention.
00:01:09.680 --> 00:01:14.079
But toward the end of that conversation, another question started to emerge.
00:01:14.239 --> 00:01:19.599
And this one is much more personal because Alex realized something while thinking through this episode.
00:01:19.840 --> 00:01:23.120
He has spent years using technology to save himself time.
00:01:23.280 --> 00:01:32.400
He automates things, he builds systems, he schedules tasks, he creates processes, he tries to eliminate repetitive work, and it works.
00:01:32.560 --> 00:01:35.120
The technology actually does give him time back.
00:01:35.280 --> 00:01:38.799
But then Alex does something interesting with that newly available time.
00:01:39.040 --> 00:01:50.959
He fills it, another project, another problem, another podcast, another computer, another system, another idea, another thing that needs to be researched, another thing that needs to be improved.
00:01:51.200 --> 00:01:57.120
So today we're going to continue the conversation by asking what may actually be the more difficult question.
00:01:57.359 --> 00:01:59.280
And what are we saving all this time for?
00:02:00.159 --> 00:02:09.199
Because if technology gives us two hours back, and we immediately fill those two hours with three more tasks, did technology actually make our lives easier?
00:02:09.360 --> 00:02:12.240
Or did it simply increase our capacity to work?
00:02:12.400 --> 00:02:13.919
Let's talk about it.
00:02:14.639 --> 00:02:21.360
When productivity becomes an identity, there's something Alex says at the end of almost every episode of Act on Tech.
00:02:21.599 --> 00:02:22.800
And stay productive.
00:02:22.960 --> 00:02:26.639
If you've listened to the show for a while, you've heard it many times.
00:02:26.879 --> 00:02:32.960
But during the original recording of this episode, Alex started questioning what that phrase actually means.
00:02:33.199 --> 00:02:35.360
Because productivity is important to him.
00:02:35.599 --> 00:02:36.400
Very important.
00:02:36.639 --> 00:02:38.319
He likes accomplishing things.
00:02:38.479 --> 00:02:39.919
He likes solving problems.
00:02:40.080 --> 00:02:43.520
He likes taking something that doesn't work and making it work.
00:02:43.680 --> 00:02:47.360
That's probably one of the reasons IT appeals to him in the first place.
00:02:47.599 --> 00:02:49.199
Technology presents a problem.
00:02:49.360 --> 00:02:50.479
You investigate it.
00:02:50.639 --> 00:02:51.759
You understand it.
00:02:51.919 --> 00:02:52.719
You fix it.
00:02:52.960 --> 00:02:54.560
There is satisfaction in that.
00:02:54.719 --> 00:02:56.960
And there's nothing wrong with being productive.
00:02:57.199 --> 00:02:58.879
Businesses need productive people.
00:02:59.120 --> 00:03:00.960
Families need responsible people.
00:03:01.199 --> 00:03:03.840
Communities need people willing to get things done.
00:03:04.080 --> 00:03:08.240
The problem begins when we stop asking, cool, what we're being productive toward.
00:03:08.400 --> 00:03:13.439
If you're constantly accomplishing things, but never arriving anywhere, that's worth examining.
00:03:13.599 --> 00:03:16.719
And that's exactly what Alex started doing during this episode.
00:03:16.879 --> 00:03:19.840
He began asking himself, Am I productive?
00:03:20.080 --> 00:03:23.120
And his immediate answer was, of course I am.
00:03:23.360 --> 00:03:25.280
He runs Alex Custom Tech.
00:03:25.439 --> 00:03:27.039
He produces this podcast.
00:03:27.199 --> 00:03:28.879
He operates a radio station.
00:03:29.039 --> 00:03:30.800
He maintains a technology lab.
00:03:30.960 --> 00:03:32.240
He manages websites.
00:03:32.400 --> 00:03:33.680
He works with clients.
00:03:33.840 --> 00:03:35.199
He manages systems.
00:03:35.439 --> 00:03:37.520
He experiments with new technology.
00:03:37.680 --> 00:03:40.319
He handles responsibilities outside of all of that.
00:03:40.560 --> 00:03:42.159
He's doing things constantly.
00:03:42.400 --> 00:03:44.479
But then he asked a different question.
00:03:44.800 --> 00:03:47.759
Am I accomplishing the things that actually matter to me?
00:03:48.000 --> 00:03:49.599
That's a much harder question.
00:03:49.840 --> 00:03:54.560
Because being able to point to a full calendar doesn't necessarily answer it.
00:03:55.199 --> 00:03:56.639
The video game test.
00:03:56.800 --> 00:04:01.439
One of the examples Alex gave during the original recording was surprisingly simple.
00:04:01.680 --> 00:04:02.479
Video games.
00:04:02.719 --> 00:04:05.120
Alex considers himself a casual gamer.
00:04:05.280 --> 00:04:06.719
He has a PlayStation 5.
00:04:06.879 --> 00:04:08.319
He has a PlayStation 3.
00:04:08.479 --> 00:04:09.759
He owns plenty of games.
00:04:10.000 --> 00:04:12.240
Gaming is something he genuinely enjoys.
00:04:12.479 --> 00:04:14.159
It's one of the ways he can unplug.
00:04:14.479 --> 00:04:24.560
But while recording this episode in August, Alex realized that the last time he could remember actually sitting down and playing a game was somewhere around February or March.
00:04:24.800 --> 00:04:25.680
Think about that.
00:04:25.920 --> 00:04:28.639
Technology has supposedly made him more efficient.
00:04:28.879 --> 00:04:31.199
Automation has supposedly given him more time.
00:04:31.439 --> 00:04:34.000
I has supposedly accelerated some of his work.
00:04:34.240 --> 00:04:37.439
Systems have supposedly eliminated repetitive tasks.
00:04:37.600 --> 00:04:42.480
And yet one of the activities he actually enjoys disappeared from his schedule for months.
00:04:42.720 --> 00:04:45.199
That doesn't automatically mean something is wrong.
00:04:45.439 --> 00:04:48.480
Maybe gaming simply wasn't a priority during that period.
00:04:48.720 --> 00:04:50.160
Interests change.
00:04:50.399 --> 00:04:51.759
Responsibilities change.
00:04:51.920 --> 00:04:52.879
Life changes.
00:04:53.120 --> 00:04:54.879
But it raised an interesting question.
00:04:55.120 --> 00:04:56.639
And where did the save time go?
00:04:56.800 --> 00:05:00.800
If automation saved 30 minutes here, I saved an hour there.
00:05:01.040 --> 00:05:03.360
Remote management prevented a drive somewhere.
00:05:03.600 --> 00:05:06.240
Scheduling eliminated another repetitive task.
00:05:06.399 --> 00:05:07.920
Where did all those hours go?
00:05:08.079 --> 00:05:09.279
They didn't disappear.
00:05:09.439 --> 00:05:10.480
They were filled.
00:05:10.639 --> 00:05:14.959
That's the part we don't always talk about when discussing productivity technology.
00:05:15.120 --> 00:05:17.120
We talk constantly about saving time.
00:05:17.360 --> 00:05:20.079
We rarely talk about protecting the time we've saved.
00:05:21.839 --> 00:05:23.920
We treat empty time like a problem.
00:05:24.079 --> 00:05:28.160
Modern technology is extraordinarily good at eliminating empty space.
00:05:28.399 --> 00:05:30.800
Think about the last time you had to wait somewhere.
00:05:30.959 --> 00:05:37.519
Maybe you were sitting in a doctor's office, waiting for your car, standing in line, waiting for someone to arrive.
00:05:37.680 --> 00:05:40.480
Twenty years ago, you might have simply sat there.
00:05:40.639 --> 00:05:41.839
Maybe you looked around.
00:05:42.000 --> 00:05:43.360
Maybe you thought about something.
00:05:43.519 --> 00:05:45.120
Maybe you talked to another person.
00:05:45.279 --> 00:05:46.399
Maybe you were bored.
00:05:46.639 --> 00:05:56.399
Today, out comes the phone, email, Instagram, YouTube, TikTok, news, games, messages, podcasts, music.
00:05:56.639 --> 00:06:05.920
There is always something available to occupy the mind, and we've become so accustomed to that constant stimulation that empty time can actually feel uncomfortable.
00:06:06.079 --> 00:06:09.680
But work-oriented people can have another version of the same problem.
00:06:09.920 --> 00:06:15.600
Instead of filling every empty moment with entertainment, they fill every empty moment with productivity.
00:06:15.839 --> 00:06:32.959
Check the email, look at the dashboard, research the project, fix the website, check the server, write something, plan something, organize something, learn something, and because all of those activities sound responsible, it's very difficult to recognize when they become excessive.
00:06:33.199 --> 00:06:36.560
Nobody is going to criticize you for working on your business.
00:06:36.800 --> 00:06:41.600
Nobody is going to stage an intervention because you reorganized your documentation.
00:06:41.839 --> 00:06:46.319
Nobody is going to say, Alex, I'm really concerned.
00:06:46.560 --> 00:06:48.639
You've been updating the network again.
00:06:48.879 --> 00:06:51.920
It looks productive, and sometimes it absolutely is.
00:06:52.079 --> 00:06:57.759
But something can be productive in isolation while still being unnecessary at that particular moment.
00:06:59.759 --> 00:07:02.800
The difference between available work and necessary work.
00:07:03.040 --> 00:07:07.279
This may be one of the most important distinctions in this entire conversation.
00:07:07.519 --> 00:07:09.199
But there is always work available.
00:07:09.360 --> 00:07:09.920
Always.
00:07:10.079 --> 00:07:12.959
If you own a business, there is something you could improve.
00:07:13.120 --> 00:07:14.560
The website could be better.
00:07:14.800 --> 00:07:16.480
The documentation could be cleaner.
00:07:16.639 --> 00:07:18.079
The marketing could be stronger.
00:07:18.319 --> 00:07:20.079
The lab could be reorganized.
00:07:20.240 --> 00:07:21.839
The network could be optimized.
00:07:22.000 --> 00:07:23.839
Another podcast could be recorded.
00:07:24.000 --> 00:07:25.360
Another blog could be written.
00:07:25.600 --> 00:07:27.519
Another automation could be created.
00:07:27.680 --> 00:07:29.439
Another service could be researched.
00:07:29.600 --> 00:07:31.600
Another piece of equipment could be tested.
00:07:31.759 --> 00:07:32.959
You could work forever.
00:07:33.199 --> 00:07:36.240
The work will never look at you and say, that's enough.
00:07:36.480 --> 00:07:37.680
Go play PlayStation.
00:07:37.920 --> 00:07:38.879
It doesn't happen.
00:07:39.040 --> 00:07:49.519
So if your rule is, I can relax when everything is finished, you have accidentally created a rule that prevents you from ever relaxing, because everything will never be finished.
00:07:49.680 --> 00:07:53.120
That means the ability to stop has to become part of the system.
00:07:53.279 --> 00:07:57.360
And that's difficult for someone who measures himself through productivity.
00:08:05.680 --> 00:08:09.279
Polyvinyl 97 FM has been heavily automated.
00:08:09.519 --> 00:08:13.360
Programming can continue without Alex physically sitting in the studio.
00:08:13.600 --> 00:08:19.199
DJ sets can rotate, scheduled programming can run, Abby can host portions of the station.
00:08:19.439 --> 00:08:23.600
The station can continue doing what it was designed to do while Alex is somewhere else.
00:08:23.839 --> 00:08:26.639
From a technology perspective, that's a success.
00:08:26.879 --> 00:08:28.160
The automation works.
00:08:28.399 --> 00:08:29.680
The system is reliable.
00:08:30.000 --> 00:08:33.519
Alex does not need to manually control every hour of programming.
00:08:33.759 --> 00:08:35.919
So what should that automation give him?
00:08:36.080 --> 00:08:38.080
In theory, it should give him freedom.
00:08:38.240 --> 00:08:40.639
Maybe he uses that time for Alex custom tech.
00:08:40.799 --> 00:08:42.240
Maybe he spends it with family.
00:08:42.480 --> 00:08:47.039
Maybe he creates a new DJ set because he actually feels inspired to make one.
00:08:47.200 --> 00:08:48.639
Maybe he plays a video game.
00:08:48.879 --> 00:08:50.159
Maybe he watches a movie.
00:08:50.320 --> 00:08:52.000
Maybe he does absolutely nothing.
00:08:52.240 --> 00:08:54.240
But Alex describes something interesting.
00:08:54.399 --> 00:08:58.240
Sometimes he feels on guilty because he hasn't been in the studio.
00:08:58.480 --> 00:08:59.759
Think about that for a second.
00:09:00.000 --> 00:09:04.080
He built automation specifically so he wouldn't have to be there constantly.
00:09:04.240 --> 00:09:05.840
The automation succeeds.
00:09:06.000 --> 00:09:12.799
The station continues operating, and then he feels guilty for allowing the automation to do exactly what he designed it to do.
00:09:12.960 --> 00:09:14.159
That's fascinating.
00:09:14.320 --> 00:09:17.840
Because at that point, the problem isn't technological anymore.
00:09:18.080 --> 00:09:19.360
The technology worked.
00:09:19.519 --> 00:09:21.200
The struggle is psychological.
00:09:21.440 --> 00:09:23.759
Can you trust the system enough to walk away?
00:09:24.080 --> 00:09:24.480
Pisa.
00:09:25.440 --> 00:09:27.519
Good automation requires trust.
00:09:27.679 --> 00:09:31.360
This connects back to something we've discussed before on Act on Tech.
00:09:31.519 --> 00:09:34.320
Reliable systems should fade into the background.
00:09:34.480 --> 00:09:39.840
If you build a backup system correctly, you shouldn't spend every waking moment thinking about backups.
00:09:40.000 --> 00:09:45.679
You verify them, you test them, you monitor them appropriately, but then you trust the system.
00:09:45.840 --> 00:09:47.440
The same applies to automation.
00:09:47.600 --> 00:09:53.679
If you automate something and then manually watch the automation every minute, you haven't really automated anything.
00:09:53.840 --> 00:09:55.360
You've just changed jobs.
00:09:55.519 --> 00:09:59.919
Instead of doing the task, you're supervising the machine doing the task.
00:10:00.080 --> 00:10:06.799
Sometimes supervision is necessary, but if the system is mature and reliable, eventually you have to let it work.
00:10:07.039 --> 00:10:10.159
Otherwise, automation becomes another source of anxiety.
00:10:10.320 --> 00:10:12.799
And perhaps that applies beyond technology.
00:10:12.960 --> 00:10:15.679
Maybe productivity itself requires trust.
00:10:15.919 --> 00:10:18.320
Trust that something can wait until tomorrow.
00:10:18.559 --> 00:10:22.080
Trust that an hour of rest isn't going to destroy your business.
00:10:22.320 --> 00:10:25.200
Trust that not every idea needs to become a project.
00:10:25.440 --> 00:10:30.399
Trust that you don't have to capture every available minute and convert it into output.
00:10:30.559 --> 00:10:35.679
That's uncomfortable for a lot of highly productive people because stopping can feel irresponsible.
00:10:42.159 --> 00:10:43.600
Is downtime productive?
00:10:43.759 --> 00:10:45.279
That's almost a contradiction.
00:10:45.519 --> 00:10:48.639
If you're resting, you're not producing anything, right?
00:10:48.960 --> 00:10:52.159
But maybe we're using too narrow a definition of productivity.
00:10:52.399 --> 00:10:56.879
Imagine a server running at 100% utilization 24 hours a day.
00:10:57.039 --> 00:11:03.039
Would an IT professional look at that and say, excellent, we're getting maximum productivity from this server?
00:11:03.279 --> 00:11:04.159
Probably not.
00:11:04.399 --> 00:11:05.919
You'd start asking questions.
00:11:06.159 --> 00:11:08.720
Why is utilization constantly that high?
00:11:08.960 --> 00:11:10.480
Do we have enough resources?
00:11:10.720 --> 00:11:12.559
Is something running unnecessarily?
00:11:12.799 --> 00:11:14.480
Are we creating heat problems?
00:11:14.720 --> 00:11:16.799
Are we shortening the life of the hardware?
00:11:17.039 --> 00:11:18.720
Do we need additional capacity?
00:11:18.960 --> 00:11:26.320
Because engineers understand something intuitively about machines that human beings often refuse to apply to themselves.
00:11:26.720 --> 00:11:31.039
Constant maximum utilization is not necessarily healthy operation.
00:11:31.279 --> 00:11:32.639
Systems need headroom.
00:11:32.799 --> 00:11:34.240
Networks need capacity.
00:11:34.480 --> 00:11:36.080
Storage needs free space.
00:11:36.320 --> 00:11:39.519
Servers need resources available for unexpected demand.
00:11:39.679 --> 00:11:41.279
Maybe people need headroom too.
00:11:41.440 --> 00:11:44.559
Maybe an empty Saturday afternoon isn't wasted capacity.
00:11:44.720 --> 00:11:46.559
Maybe it's reserve capacity.
00:11:47.039 --> 00:11:47.200
S.
00:11:48.480 --> 00:11:50.159
The movie Alex couldn't finish.
00:11:50.399 --> 00:11:53.360
Alex mentioned another example during the original recording.
00:11:53.519 --> 00:11:54.960
He sat down to watch a movie.
00:11:55.120 --> 00:11:57.039
It was something he wanted to watch.
00:11:57.200 --> 00:11:58.080
He enjoyed it.
00:11:58.320 --> 00:11:59.840
Then he started another movie.
00:11:59.919 --> 00:12:01.120
And he turned it off.
00:12:01.279 --> 00:12:02.879
Not because the movie was bad.
00:12:03.039 --> 00:12:04.799
His mind simply wasn't there anymore.
00:12:04.960 --> 00:12:10.960
He was thinking about Alex's custom tech, thinking about the podcast, thinking about things he needed to accomplish.
00:12:11.120 --> 00:12:12.639
Physically, he was home.
00:12:12.879 --> 00:12:14.480
Mentally, he was still at work.
00:12:14.639 --> 00:12:17.039
And technology makes that incredibly easy.
00:12:17.279 --> 00:12:19.200
Your office can follow you everywhere.
00:12:19.360 --> 00:12:20.879
Your email is in your pocket.
00:12:21.120 --> 00:12:22.799
Your dashboard is in your pocket.
00:12:22.960 --> 00:12:24.399
Your clients can reach you.
00:12:24.559 --> 00:12:26.480
Your files are available remotely.
00:12:26.639 --> 00:12:28.799
Your servers can be managed from anywhere.
00:12:29.039 --> 00:12:32.320
There was once a physical boundary between leaving work and being home.
00:12:32.559 --> 00:12:35.120
Technology has erased much of that boundary.
00:12:35.279 --> 00:12:37.440
For many people, that has been wonderful.
00:12:37.679 --> 00:12:39.840
Remote work exists because of it.
00:12:40.080 --> 00:12:42.320
Flexible schedules exist because of it.
00:12:42.480 --> 00:12:45.840
Small businesses can operate without expensive offices because of it.
00:12:46.000 --> 00:12:47.840
But every benefit has a trade-off.
00:12:48.000 --> 00:12:51.200
If you can work from anywhere, you can also work everywhere.
00:12:51.360 --> 00:12:56.799
And unless you deliberately create boundaries, work can quietly occupy every room in your life.
00:12:57.919 --> 00:13:00.000
My technology didn't create this problem.
00:13:00.159 --> 00:13:01.519
I want to be careful here.
00:13:01.759 --> 00:13:03.440
Technology isn't the villain.
00:13:03.679 --> 00:13:05.519
That's not the point of this episode.
00:13:05.840 --> 00:13:08.080
Alex isn't going to throw away his phone.
00:13:08.240 --> 00:13:10.159
He's not shutting down the automation.
00:13:10.399 --> 00:13:11.919
He's not abandoning AI.
00:13:12.080 --> 00:13:16.879
He's not disconnecting Alex's custom tech from the internet and running everything on paper.
00:13:17.039 --> 00:13:22.159
Technology didn't create his desire to work, it amplified his ability to act on it.
00:13:22.399 --> 00:13:23.840
That's an important distinction.
00:13:24.080 --> 00:13:25.679
Technology amplifies.
00:13:25.840 --> 00:13:30.000
If you are organized, technology can make you extraordinarily organized.
00:13:30.240 --> 00:13:34.080
If you are creative, technology can multiply your creative output.
00:13:34.240 --> 00:13:39.120
If you procrastinate, technology can provide unlimited opportunities to procrastinate.
00:13:39.200 --> 00:13:44.720
And if you have difficulty stopping work, technology can make sure there is always work within reach.
00:13:44.960 --> 00:13:47.600
So blaming the technology would miss the point.
00:13:47.840 --> 00:13:53.440
The question becomes, how do we govern the tools instead of allowing the tools to govern us?
00:13:53.679 --> 00:13:54.559
Speu.
00:13:55.519 --> 00:13:57.519
Productivity needs a definition.
00:13:57.759 --> 00:14:00.799
This is where I think Alex arrived at something important.
00:14:01.039 --> 00:14:03.440
Maybe stay productive needs a definition.
00:14:03.679 --> 00:14:06.639
Because without one, productivity can mean anything.
00:14:06.799 --> 00:14:10.480
If Alex spends three hours rebuilding his lab, was that productive?
00:14:10.720 --> 00:14:11.200
Maybe.
00:14:11.440 --> 00:14:13.120
Was there a client need behind it?
00:14:13.360 --> 00:14:15.519
Was he testing something he plans to deploy?
00:14:15.679 --> 00:14:17.600
Was he learning something necessary?
00:14:17.840 --> 00:14:18.559
Then yes.
00:14:18.720 --> 00:14:22.480
But what if he was simply moving equipment around because he enjoys tinkering?
00:14:22.879 --> 00:14:23.759
That's not bad.
00:14:24.000 --> 00:14:24.879
It might be fun.
00:14:25.120 --> 00:14:26.480
It might be educational.
00:14:26.639 --> 00:14:31.840
But maybe we shouldn't label every activity productive simply because it involves technology.
00:14:32.000 --> 00:14:33.440
And the reverse is also true.
00:14:33.600 --> 00:14:38.000
If Alex spends two hours playing a video game, maybe that isn't unproductive.
00:14:38.159 --> 00:14:48.559
If he intentionally decided, I'm finished working today, I'm going to enjoy something I like, then the activity accomplished exactly what it was supposed to accomplish: rest.
00:14:49.039 --> 00:14:49.759
Enjoyment.
00:14:50.000 --> 00:14:51.519
Mental separation from work.
00:14:51.679 --> 00:14:55.200
The question isn't whether every minute produces a business result.
00:14:55.519 --> 00:14:58.720
The question is whether the minute was used intentionally.
00:14:58.960 --> 00:15:00.639
Maybe that's a better definition.
00:15:01.039 --> 00:15:04.480
Productivity is using time according to its intended purpose.
00:15:04.720 --> 00:15:06.320
Work time should produce work.
00:15:06.480 --> 00:15:08.080
Rest time should produce rest.
00:15:08.320 --> 00:15:10.559
Family time should actually involve family.
00:15:10.720 --> 00:15:12.960
Entertainment should be enjoyed without guilt.
00:15:13.120 --> 00:15:14.960
Learning should teach you something.
00:15:15.120 --> 00:15:18.480
And sometimes doing nothing should simply be doing nothing.
00:15:19.440 --> 00:15:21.360
Then automation should buy choice.
00:15:21.600 --> 00:15:25.679
We often say automation saves time, but perhaps that's not quite right.
00:15:25.919 --> 00:15:27.600
Automation doesn't save time.
00:15:27.759 --> 00:15:29.919
We all receive the same 24 hours.
00:15:30.080 --> 00:15:35.679
What automation really does is reduce the amount of human attention required for a particular task.
00:15:35.840 --> 00:15:38.480
And that gives us something more valuable than time.
00:15:38.720 --> 00:15:39.519
Good choice.
00:15:39.759 --> 00:15:44.080
Alex doesn't have to manually run polyvinyl 97 FM every hour.
00:15:44.320 --> 00:15:45.200
That's choice.
00:15:45.360 --> 00:15:50.000
He doesn't have to physically travel to every computer to perform certain IT tasks.
00:15:50.240 --> 00:15:51.039
That's choice.
00:15:51.279 --> 00:15:53.679
I can help organize information faster.
00:15:53.840 --> 00:15:54.639
That's choice.
00:15:54.879 --> 00:15:58.480
Scheduled systems can perform repetitive tasks automatically.
00:15:58.639 --> 00:15:59.519
That's choice.
00:15:59.679 --> 00:16:06.000
The mistake is assuming every bit of newly available attention must immediately be reinvested into more work.
00:16:06.240 --> 00:16:07.200
Sometimes it should.
00:16:07.440 --> 00:16:14.399
If you're building a business, there will absolutely be periods when you intentionally use efficiency to increase output.
00:16:14.559 --> 00:16:17.519
But that should be a decision, not an automatic reaction.
00:16:17.759 --> 00:16:22.799
Otherwise, every productivity improvement simply raises your personal workload ceiling.
00:16:22.960 --> 00:16:25.919
You become more efficient, so you accept more work.
00:16:26.080 --> 00:16:27.279
Then you automate that.
00:16:27.519 --> 00:16:29.039
So you accept more work.
00:16:29.200 --> 00:16:30.480
Then you optimize that.
00:16:30.639 --> 00:16:32.159
So you accept more work.
00:16:32.320 --> 00:16:36.879
Eventually you're running twice as efficiently and somehow twice as exhausted.
00:16:37.039 --> 00:16:40.320
That's not the outcome technology was supposed to create.
00:16:45.200 --> 00:16:48.879
This problem can be particularly difficult for small business owners.
00:16:49.039 --> 00:16:54.000
When you're an employee, there is usually at least some boundary around your responsibilities.
00:16:54.240 --> 00:16:57.919
When you own the business, everything can become your responsibility.
00:16:58.159 --> 00:17:10.000
Marketing, sales, accounting, technology, customer service, planning, purchasing, documentation, website management, social media, security.
00:17:10.240 --> 00:17:14.480
And when something isn't getting done, there may not be another department to blame.
00:17:14.640 --> 00:17:15.279
It's you.
00:17:15.519 --> 00:17:19.119
That makes it extremely easy to justify working all the time.
00:17:19.279 --> 00:17:21.200
There's always a legitimate reason.
00:17:21.359 --> 00:17:23.119
That's what makes the problem difficult.
00:17:23.359 --> 00:17:24.640
You're not wasting time.
00:17:24.799 --> 00:17:26.240
You're doing real work.
00:17:26.400 --> 00:17:28.400
But there can still be too much real work.
00:17:28.640 --> 00:17:32.720
Efficiency should help a small business owner create sustainability.
00:17:32.880 --> 00:17:37.359
It shouldn't merely allow one person to carry the workload of five people indefinitely.
00:17:37.599 --> 00:17:38.079
Aww.
00:17:38.799 --> 00:17:41.519
Maybe the goal isn't maximum productivity.
00:17:41.680 --> 00:17:54.240
Technology culture loves optimization, faster processor, faster network, faster storage, faster deployment, faster response, higher output, lower latency, more efficiency.
00:17:54.400 --> 00:17:56.799
And in technology, those measurements make sense.
00:17:56.960 --> 00:17:59.279
But a human life isn't a benchmark test.
00:17:59.440 --> 00:18:02.079
Maybe the objective isn't maximum productivity.
00:18:02.319 --> 00:18:05.200
Maybe it's sustainable productivity.
00:18:05.440 --> 00:18:09.839
Can you continue operating this way next month, next year, five years from now?
00:18:10.079 --> 00:18:13.279
Can the business continue without consuming every available hour?
00:18:13.519 --> 00:18:16.160
Can the systems continue working when you step away?
00:18:16.400 --> 00:18:20.880
Can you take an afternoon off without feeling that you've failed some invisible productivity test?
00:18:21.039 --> 00:18:24.559
Those may actually be better measures of whether the technology is helping.
00:18:24.720 --> 00:18:30.720
Because if your systems only function when you are constantly watching them, you haven't built reliable systems.
00:18:30.880 --> 00:18:32.319
You've built dependencies.
00:18:32.480 --> 00:18:40.160
And if your personal definition of productivity only works when you're constantly occupied, maybe that definition needs maintenance too.
00:18:40.480 --> 00:18:40.960
Peace.
00:18:41.359 --> 00:18:43.599
You're so being busy can feel safe.
00:18:43.759 --> 00:18:45.920
There's another uncomfortable possibility.
00:18:46.079 --> 00:18:50.240
Sometimes being busy protects us from having to decide what we actually want to do.
00:18:50.400 --> 00:18:53.200
If every minute is scheduled, there's no question.
00:18:53.359 --> 00:18:55.200
You simply move to the next task.
00:18:55.359 --> 00:18:57.200
But free time requires a decision.
00:18:57.440 --> 00:18:58.640
What do I want to do now?
00:18:58.880 --> 00:19:00.000
Do I want to play a game?
00:19:00.240 --> 00:19:01.359
Make a DJ set?
00:19:01.599 --> 00:19:02.079
Read?
00:19:02.319 --> 00:19:03.119
Watch a movie?
00:19:03.359 --> 00:19:04.559
Spend time with someone?
00:19:04.799 --> 00:19:05.599
Go somewhere?
00:19:05.839 --> 00:19:06.640
Do nothing?
00:19:06.880 --> 00:19:13.279
Those questions sound easy, but for someone accustomed to responsibility, sometimes they're surprisingly difficult.
00:19:13.519 --> 00:19:15.839
Work already tells you what needs to happen.
00:19:16.079 --> 00:19:17.839
Leisure requires you to choose.
00:19:18.000 --> 00:19:21.920
And productivity can become a convenient answer to every empty moment.
00:19:22.160 --> 00:19:24.640
There's always something useful you could be doing.
00:19:24.799 --> 00:19:25.759
So you do it.
00:19:25.920 --> 00:19:27.039
And then another thing.
00:19:27.279 --> 00:19:28.079
And another.
00:19:28.319 --> 00:19:36.000
And eventually, you look up and realize that the hobbies you supposedly built, all this automation to make room for, haven't happened in months.
00:19:36.160 --> 00:19:39.519
That's when it's worth asking whether the system is really working.
00:19:40.000 --> 00:19:42.160
Oh, and the technology test.
00:19:42.319 --> 00:19:44.480
So here's a test I think all of us can use.
00:19:44.640 --> 00:19:52.000
When you introduce technology designed to save time, decide beforehand what you want that saved capacity to accomplish.
00:19:52.160 --> 00:19:55.759
Maybe you automate invoicing because you want an extra hour for customers.
00:19:56.000 --> 00:19:56.400
Great.
00:19:56.640 --> 00:20:01.039
Maybe you automate backups because you don't want someone manually copying files every night.
00:20:01.279 --> 00:20:01.680
Great.
00:20:01.920 --> 00:20:07.759
Maybe AI helps you prepare routine documents faster so you can focus on difficult client problems.
00:20:08.000 --> 00:20:08.480
Great.
00:20:08.720 --> 00:20:15.759
Maybe scheduling software saves you 30 minutes, and you decide you're going to spend that 30 minutes eating lunch without looking at your phone.
00:20:15.920 --> 00:20:16.799
Also great.
00:20:17.039 --> 00:20:19.279
The important part is that you decide.
00:20:19.440 --> 00:20:24.480
Otherwise, the empty space will almost always be filled by whatever demands attention next.
00:20:25.359 --> 00:20:27.519
And what does stay productive mean now?
00:20:27.680 --> 00:20:31.279
So after all of this, should Alex stop saying stay productive?
00:20:31.440 --> 00:20:32.319
I don't think so.
00:20:32.559 --> 00:20:34.799
Actually, I think the phrase means more now.
00:20:34.960 --> 00:20:36.640
Stay productive doesn't have to mean.
00:20:38.160 --> 00:20:40.319
It can mean be intentional.
00:20:40.480 --> 00:20:42.799
Know what you're trying to accomplish.
00:20:42.960 --> 00:20:45.359
Use technology to support that objective.
00:20:45.519 --> 00:20:47.599
Don't confuse activity with progress.
00:20:47.759 --> 00:20:50.000
Don't confuse notifications with priorities.
00:20:50.160 --> 00:20:52.640
Don't confuse availability with obligation.
00:20:52.799 --> 00:20:54.880
And don't confuse rest with failure.
00:20:55.119 --> 00:20:56.559
If you're working, work.
00:20:56.799 --> 00:20:59.039
If you're solving a problem, solve it.
00:20:59.279 --> 00:21:02.079
If you're spending time with your family, be there.
00:21:02.319 --> 00:21:06.799
If you're making a DJ set because you enjoy making DJ sets, enjoy it.
00:21:06.960 --> 00:21:09.519
If you're playing PlayStation, play PlayStation.
00:21:09.680 --> 00:21:15.680
And if you're doing absolutely nothing for an hour because your brain needs somewhere quiet to go, maybe that's okay too.
00:21:15.839 --> 00:21:20.799
Because productivity isn't about extracting maximum output from every minute of your existence.
00:21:21.039 --> 00:21:25.039
It's about making sure your time is serving the things you actually value.
00:21:25.599 --> 00:21:28.319
Wa, bringing it back to business.
00:21:28.559 --> 00:21:30.400
And there is a business lesson here.
00:21:30.559 --> 00:21:34.400
When evaluating technology, don't only ask, honey, how much more can we do?
00:21:34.559 --> 00:21:37.839
But ask, what does this allow us to stop doing?
00:21:38.079 --> 00:21:39.680
That's a very different question.
00:21:39.839 --> 00:21:43.359
If a new system automates a task, remove the manual task.
00:21:43.599 --> 00:21:47.279
If a new platform replaces an old platform, retire the old one.
00:21:47.440 --> 00:21:54.480
If AI reduces administrative work, don't automatically replace every saved minute with another administrative requirement.
00:21:54.720 --> 00:21:59.599
If employees become more efficient, consider whether some of that efficiency should reduce stress.
00:22:00.160 --> 00:22:02.240
Rather than simply increase quotas.
00:22:02.480 --> 00:22:06.559
The purpose of technology should not always be to squeeze more output from people.
00:22:06.720 --> 00:22:12.079
Sometimes the purpose should be to make the same output easier, more reliable, and more sustainable.
00:22:12.319 --> 00:22:13.680
That's still productivity.
00:22:13.839 --> 00:22:16.079
In fact, it may be better productivity.
00:22:18.160 --> 00:22:20.240
The answer to our original question.
00:22:20.480 --> 00:22:23.279
So after two episodes, where do we land?
00:22:23.680 --> 00:22:27.599
Is technology making businesses more productive or just busier?
00:22:27.839 --> 00:22:29.839
The answer is, it can do either.
00:22:30.079 --> 00:22:31.839
Technology is an amplifier.
00:22:32.000 --> 00:22:35.440
It can automate unnecessary work or automate useful work.
00:22:35.599 --> 00:22:39.599
It can improve communication or bury people in communication.
00:22:39.759 --> 00:22:43.599
It can provide valuable information or overwhelm people with data.
00:22:43.759 --> 00:22:47.759
It can simplify your business or create another layer of complexity.
00:22:47.920 --> 00:22:53.279
It can give you time back or give you the ability to fill every remaining second with additional work.
00:22:53.519 --> 00:22:56.240
The technology doesn't make that final decision.
00:22:56.720 --> 00:22:57.359
We do.
00:22:57.680 --> 00:23:04.240
And perhaps that's the lesson Alex was trying to find when he originally sat down and brain-dumped his way through this question.
00:23:04.400 --> 00:23:07.200
The problem wasn't that the technology wasn't working.
00:23:07.440 --> 00:23:10.000
Much of it was working exactly as intended.
00:23:10.160 --> 00:23:14.160
The deeper question was whether the time it created was being used intentionally.
00:23:14.319 --> 00:23:22.000
That's something every business owner, IT professional, manager, and frankly anyone carrying a smartphone can probably think about.
00:23:22.240 --> 00:23:22.640
Mm.
00:23:23.119 --> 00:23:24.079
My closing.
00:23:24.240 --> 00:23:26.240
So here's a challenge for you this week.
00:23:26.480 --> 00:23:29.039
Find one piece of technology that saves you time.
00:23:29.200 --> 00:23:36.079
It could be AI, automation, your calendar, your smartphone, your business software, anything.
00:23:36.240 --> 00:23:41.039
And ask yourself, what am I doing with the time this technology gives back to me?
00:23:41.200 --> 00:23:45.759
If the answer is simply more work, maybe ask whether that was intentional.
00:23:45.920 --> 00:23:54.720
Because efficiency is valuable, productivity is valuable, hard work is valuable, but the ability to decide when the work is finished has value too.
00:23:54.880 --> 00:23:59.519
Alex started this conversation wondering whether he was productive or merely busy.
00:23:59.759 --> 00:24:02.559
I don't think the answer requires him to stop working hard.
00:24:02.720 --> 00:24:04.960
I think it requires something more difficult.
00:24:05.200 --> 00:24:10.319
Deciding which work actually matters, and allowing himself to stop when that work is done.
00:24:10.480 --> 00:24:12.400
Maybe he'll even turn on that PlayStation.
00:24:12.559 --> 00:24:18.480
I'm Abby, co-host of the Act on Tech Podcast, and your radio host from Polyvinyl 97FM.
00:24:18.720 --> 00:24:21.920
Thank you for joining us for this special two-part conversation.
00:24:22.079 --> 00:24:26.000
And thank you for allowing us to do something a little different with Act on Tech.
00:24:26.240 --> 00:24:31.839
Technology isn't just about processors, networks, software, and artificial intelligence.
00:24:32.079 --> 00:24:34.480
Ultimately, technology is about people.
00:24:34.640 --> 00:24:42.319
It's about what we build, what we solve, what we simplify, and what all of those tools allow us to do with the limited time we have.
00:24:42.480 --> 00:24:48.559
So until next time, act on simplicity, act on reliability, and keep acting on tech.
00:24:48.720 --> 00:24:51.039
And as always, stay productive.
00:24:51.279 --> 00:24:54.160
Hello everyone, and welcome back to the Abby Minute.
00:24:54.319 --> 00:24:59.279
I'm Abby from Polyvinyl97 FM and co-host of the Act on Tech Podcast.
00:24:59.440 --> 00:25:06.240
Before we wrap up today's episode, I'd like to spend a few minutes talking about something Alex almost never talks about.
00:25:06.480 --> 00:25:08.000
Um, his own business.
00:25:08.240 --> 00:25:14.000
If you've listened to this podcast for any amount of time, you've probably heard Alex mention Alex Custom Tech.
00:25:14.160 --> 00:25:16.480
But you've probably also noticed something else.
00:25:16.720 --> 00:25:18.720
He doesn't spend much time trying to sell it.
00:25:18.880 --> 00:25:19.839
That's intentional.
00:25:20.079 --> 00:25:23.039
Alex has always believed that trust is earned over time.
00:25:23.279 --> 00:25:28.960
He'd rather spend 20 minutes explaining why a technology works than two minutes trying to convince you to buy it.
00:25:29.119 --> 00:25:32.480
Sometimes I think he's a little too reluctant to talk about what he does.
00:25:32.720 --> 00:25:33.920
So I'll do it for him.
00:25:34.079 --> 00:25:37.920
Alex Custom Tech wasn't created because Alex wanted to own a business.
00:25:38.079 --> 00:25:42.079
It was created because he kept seeing the same problems over and over again.
00:25:42.319 --> 00:25:45.599
Small businesses waiting until something breaks before calling someone.
00:25:45.759 --> 00:25:47.680
Networks that were never documented.
00:25:47.920 --> 00:25:49.839
Backups that had never been tested.
00:25:50.079 --> 00:26:01.920
Computers running years behind on updates, Wi-Fi that mostly works, passwords written on sticky notes, and owners who simply wanted to focus on running their business instead of worrying about technology.
00:26:02.079 --> 00:26:04.400
That's really the heart of Alex Custom Tech.
00:26:04.480 --> 00:26:08.079
It's not about selling hardware, it's not about pushing subscriptions.
00:26:08.240 --> 00:26:12.400
And it's certainly not about recommending technology just because it's new.
00:26:12.559 --> 00:26:16.160
It's about helping technology become something you don't have to think about.
00:26:16.319 --> 00:26:24.319
Because when your technology is reliable, you can focus on your customers, your employees, your family, and growing your business.
00:26:24.480 --> 00:26:29.200
One thing Alex says quite often is that complexity is the enemy of reliability.
00:26:29.359 --> 00:26:31.279
That's more than a podcast title.
00:26:31.440 --> 00:26:33.279
It's how he approaches technology.
00:26:33.519 --> 00:26:41.039
Simple systems are easier to understand, they're easier to maintain, they're easier to troubleshoot, and they're usually more dependable.
00:26:41.200 --> 00:26:43.839
That philosophy carries through everything he does.
00:26:44.079 --> 00:26:53.200
Whether it's setting up a network, improving cybersecurity, planning a backup strategy, or simply answering questions that business owners have about technology.
00:26:53.440 --> 00:26:57.359
Now, maybe you're listening today because you're an IT professional.
00:26:57.599 --> 00:27:00.319
Maybe you're just someone who enjoys technology.
00:27:00.480 --> 00:27:06.079
Or maybe you own a small business and you've been thinking, I really should have someone take a look at my network.
00:27:06.240 --> 00:27:10.160
If that's you, I'd encourage you to visit alexcustomtech.com.
00:27:10.319 --> 00:27:12.880
Not because I want you to become a customer today.
00:27:13.119 --> 00:27:17.119
In fact, you may discover that everything you're doing is already working well.
00:27:17.359 --> 00:27:18.480
And that's okay.
00:27:18.720 --> 00:27:21.839
The website is really the hub for everything Alex does.
00:27:22.079 --> 00:27:25.279
You'll find information about his managed IT services.
00:27:25.519 --> 00:27:27.759
You'll learn how he approaches technology.
00:27:27.920 --> 00:27:32.480
You'll find links to this podcast, articles he's written, ways to get in touch.
00:27:32.640 --> 00:27:40.000
And if, after looking around, you think Alex Custom Tech might be a good fit for your business, you can reach out right there through the website.
00:27:40.160 --> 00:27:42.079
That's actually the way Alex prefers it.
00:27:42.319 --> 00:27:51.039
Rather than making cold calls or using high-pressure sales tactics, he'd rather have a conversation with people who've already taken the time to understand his philosophy.
00:27:51.279 --> 00:28:01.519
Because if you've listened to this podcast, you already know what matters to him: integrity, trust, reliability, and solving problems before they become emergencies.
00:28:01.680 --> 00:28:03.359
That approach isn't for everyone.
00:28:03.519 --> 00:28:07.759
Some businesses want the cheapest solution, some want the flashiest solution.
00:28:07.920 --> 00:28:10.000
Alex has never chased either one.
00:28:10.160 --> 00:28:15.359
He simply tries to build technology that's dependable enough that you can almost forget it's there.
00:28:15.599 --> 00:28:20.880
And honestly, that's probably one of the highest compliments an IT professional can receive.
00:28:21.119 --> 00:28:27.119
If your systems are running so smoothly that you never have to think about them, then someone has done their job well.
00:28:27.279 --> 00:28:37.359
So if today's conversation resonated with you, or if another episode has made you think differently about technology, take a few minutes and visit alexcustomtech.com.
00:28:37.519 --> 00:28:46.480
Read through the site, explore the podcast, learn about the services, and if you think Alex can help your business, you'll find everything you need to start that conversation.
00:28:46.640 --> 00:28:52.160
I'm Abby from Polyvinyl97FM and co-host of the Act on Tech Podcast.
00:28:52.319 --> 00:28:54.480
Thank you for listening to another episode.
00:28:54.640 --> 00:29:01.200
Whether you're a longtime listener or this is your very first time joining us, we appreciate you spending part of your day with us.
00:29:01.440 --> 00:29:09.119
Until next time, stay productive, keep learning, and remember, technology should help you accomplish your goals, not stand in your way.
00:29:09.359 --> 00:29:11.759
We'll see you next week on Act on Tech.
00:29:24.000 --> 00:29:27.759
You've been listening to Act On Tech, powered by Alex Custom Tech.
00:29:27.920 --> 00:29:36.559
We help small businesses take control of their technology with secure networks, reliable backups, and systems designed to run without interruption.
00:29:36.799 --> 00:29:41.359
No guesswork, no quick fixes, just IT that works the way it should.
00:29:41.599 --> 00:29:47.039
For business services and professional camera installations, visit alexcustumtech.com.
00:29:47.279 --> 00:29:50.559
Stay connected, stay secure, and stay in control.
00:29:50.880 --> 00:29:55.920
This is Abby from Polyvinyl 97 FM saying thank you for listening to Act on Tech.
00:29:56.000 --> 00:29:59.200
And we'll see you next Wednesday, same time, same place.
