Technology, People, and Business

A few thoughts on technology, the people who depend on it, and the decisions that make it worthwhile.

I've spent a good part of my working life trying to understand how things work, why they work the way they do, and what could be done to make them better. Technology provides an extraordinary number of ways to accomplish that, but I've come to appreciate that the most important part of any system isn't necessarily the equipment or software. It's the people who depend on it.

1. Understanding the Problem

I've never been one to shy away from a problem simply because it's difficult, but I also don't believe in rushing to fix something before I understand what's really happening. If I don't have enough information, I'd rather ask more questions, look at the circumstances, and reconsider what I originally thought I knew. Sometimes that leads to a complicated solution, and sometimes it turns out the problem isn't quite what everyone thought it was.

2. Enterprise Technology Strategy

A company can spend an extraordinary amount of money on technology without necessarily making things any better. Before recommending a significant investment, I want to understand where the business is trying to go, what's standing in the way, and how the proposed technology is actually going to help the people involved. Sometimes the right decision is to make a substantial investment, and sometimes it's to recognize that what we already have is doing the job just fine.

3. Enterprise Architecture

I've always enjoyed understanding how different things fit together, whether it's a mechanical assembly or a collection of business systems. In an organization, people rarely think about how many different systems are involved in something as ordinary as processing an order, paying an employee, or helping a customer. When those systems work together properly, people can concentrate on their responsibilities rather than figuring out how to compensate for the things that don't.

4. Infrastructure & Systems

Most people don't particularly care where an application runs or what equipment supports it, and I don't think they should have to. They care that it works when they need it, performs reasonably well, and doesn't create unnecessary obstacles during their day. I don't expect any technology to be perfect, but I do believe in understanding its limitations and making realistic decisions about the reliability the business actually requires.

5. Networks & Communications

It's remarkable how much of a working day depends on people being able to communicate and access information. Something as simple as an unreliable network connection can interrupt a conversation, delay a customer, or bring an otherwise productive afternoon to a halt. I've always considered dependable communications one of those foundations that people shouldn't have to think about very often, because when they're working properly, everything else becomes a little easier.

6. Cloud & Hybrid Computing

Cloud computing has created opportunities that would have been difficult or prohibitively expensive for many organizations years ago, and I appreciate the flexibility it provides. But moving a system to the cloud doesn't automatically make it better, less expensive, or easier to manage. I'd rather evaluate what the system needs to accomplish, what it costs to operate, and which environment makes the most practical sense than commit to a particular approach simply because it's popular.

7. The Modern Workplace

People don't all work the same way, and increasingly they don't work from the same place. I appreciate technology that allows someone to contribute effectively whether they're sitting in an office, working from home, or traveling between locations. To me, the important part isn't where somebody happens to be sitting, but whether they have the tools, access, communication, and support needed to do their work well.

8. IT Support & Service Delivery

When someone contacts IT because they can't do their job, they're usually not interested in hearing about the complexity of the problem. They want to know that somebody understands what's happening, takes their situation seriously, and is going to help them get back to work. Sometimes that means a quick correction, sometimes it takes considerable investigation, and occasionally the most useful thing you can do is explain clearly what can and cannot be accomplished.

9. Identity & Access Management

Having the right access to information and applications seems like such a simple thing until somebody needs it and can't get it. I've seen how frustrating unnecessary barriers can become, but I also understand the importance of making sure people only have access to what they're authorized to use. I think a well-designed approach should make ordinary access straightforward while providing the controls necessary to protect the information and systems involved.

10. Cybersecurity

Nobody wants to discover that their personal information, their employer's records, or the work they've spent months developing has been compromised. I take security seriously, but I also recognize that every additional restriction has the potential to affect somebody trying to do legitimate work. The challenge is understanding the actual risks, applying appropriate protections, and recognizing that making a system more difficult to use doesn't necessarily make it more secure.

11. Privacy & Information Protection

People provide information to businesses with an expectation that it will be handled responsibly. That becomes especially important when the information concerns someone's finances, health, employment, or personal life. I've always felt that protecting that trust deserves more consideration than simply asking whether a particular practice satisfies the minimum technical or regulatory requirements.

12. Enterprise Applications

An accounting system, a customer management platform, or an employee records application might seem like separate pieces of software, but each supports people doing work that matters. When those systems are cumbersome or poorly suited to their purpose, people often develop their own workarounds just to get through the day. I've found that understanding why someone created a workaround can tell you quite a bit about whether the real problem is the software, the business process, or something else entirely.

13. Systems Integration

I've never understood why someone should have to enter the same information into several different systems just because those systems don't communicate with one another. Besides being tedious, every repetition introduces another opportunity for a mistake, and correcting those mistakes can consume even more time. When integration makes sense, getting systems to exchange reliable information can eliminate a surprising amount of unnecessary work, although I think it's worth understanding the process before simply automating the way it's currently done.

14. Automation

There's not much satisfaction in asking a capable person to spend hours performing the same repetitive task. I'd rather see that person's time and abilities put toward something that requires judgment, experience, or creativity, but I also don't believe everything should be automated just because it can be. Sometimes a process needs to be reconsidered before automating it, and sometimes the human involvement is exactly what makes it work well.

15. Data Quality & Governance

I've always been a little skeptical of decisions made from information nobody has taken the time to verify. A beautifully presented report doesn't help much if the information behind it is incomplete, inconsistent, or simply wrong. I'd rather work with a smaller amount of dependable information, understand what might be missing, and adjust my conclusions as better information becomes available.

16. Enterprise Data Warehouses

Different departments often have their own understanding of what's happening inside the same company, partly because they're looking at different information. Bringing that information together can give people a much clearer picture of how their work relates to everyone else's, but only if there's enough consistency and understanding of where the information came from to make the comparisons meaningful. I think the real value is helping people see the organization as a whole instead of having everyone make decisions from their own small piece of it.

17. Business Intelligence & Analytics

I think most people have experienced the frustration of knowing something isn't working quite right but not having enough information to understand why. Good reporting and analytics can help bring those problems into focus, but I don't believe more charts and measurements automatically lead to better decisions. The useful information is the information that helps somebody understand what's happening, recognize what matters, and decide whether anything actually needs to change.

18. Artificial Intelligence

I'm fascinated by what artificial intelligence is making possible, particularly its ability to help people work through complex information and accomplish things that previously required considerable time or specialized knowledge. At the same time, I've seen enough of what technology can and cannot do to recognize the importance of questioning its conclusions, understanding its limitations, and maintaining appropriate oversight. I think some of the most promising opportunities come from combining these capabilities with human experience and judgment, rather than assuming either one should do everything independently.

19. Monitoring & Operational Awareness

It's much better to discover that something is beginning to fail before somebody calls to report that their work has stopped. That's one of the reasons I've always valued having a clear view of what's happening inside an environment, rather than simply waiting for problems to announce themselves. But monitoring should help people recognize and act on meaningful conditions, not bury them in so many alerts that the important ones become difficult to distinguish.

20. Business Continuity

When technology becomes unavailable, the consequences don't stop at the server room or the network equipment. Someone may be unable to fill an order, complete a report, serve a customer, or carry out a responsibility that others are depending on. I think continuity planning should begin by understanding which activities people genuinely need to keep running, how long they can reasonably be interrupted, and what it takes to protect those activities without creating unnecessary expense.

21. Backup & Disaster Recovery

I don't think there's much comfort in being told that everything is backed up if nobody knows whether it can actually be recovered. When important information is lost or systems become unavailable, people need more than assurances that a procedure exists. They need confidence that recovery has been properly considered, tested, and can be accomplished within a timeframe that makes sense for the work being supported.

22. Compliance & Regulated Environments

Some organizations carry responsibilities that reach well beyond their own business operations, particularly when people's health, safety, or sensitive information is involved. In those environments, doing something properly isn't simply a matter of avoiding penalties or satisfying an audit, although those obligations certainly matter. I think it's important to understand why the requirements exist, who they're intended to protect, and how to meet them without unnecessarily complicating the work people are responsible for performing.

23. Technology Budgets & Investments

I've never been especially impressed by spending money simply because a budget happens to be available, and I don't believe the most expensive solution is necessarily the best one. I want to understand what an investment will accomplish, what it will cost to maintain, what risks it introduces, and whether there's a simpler way to achieve the same result. Sometimes the most responsible recommendation is to spend more, sometimes it's to spend less, and occasionally it's to leave a perfectly serviceable system alone.

24. Vendors & Technology Partnerships

I've worked with enough different people over the years to appreciate how much the quality of a working relationship matters. A supplier can have an excellent product and still be a poor fit if they don't understand the organization, recognize its limitations, or respond when things become difficult. I truly value a vendor representative who takes the time to understand the problem before offering a solution, and who is willing to tell me when their product may not be the right answer.

25. Technical Debt & Modernization

There's a difference between keeping something because it still serves its purpose and keeping it simply because nobody wants to deal with replacing it. Older technology isn't automatically bad, and I've never thought that a system should be replaced just because something newer is available, but maintenance costs, security risks, limitations, and growing dependencies all deserve consideration. Sometimes the existing solution remains the most sensible option, and recognizing that is just as important as recognizing when it's time to move on.

26. Growth & Scalability

Growth is usually something a business welcomes, but it can introduce challenges people didn't have when the organization was smaller. Systems that worked perfectly well for a dozen employees may become increasingly difficult to manage when there are hundreds or thousands, and the people supporting those systems can find themselves spending more time maintaining them than helping the business move forward. I think thoughtful planning means recognizing where those limits are likely to appear and making improvements when they're justified, rather than trying to build everything for an imagined future that may never arrive.

27. Change Management

People are generally more willing to accept change when they understand why it's happening and how it will affect them, although I also recognize that some changes are simply going to be unpopular. Even a worthwhile improvement can create frustration when people aren't prepared for it, especially if they're being asked to give up a process they've grown comfortable using. I've always appreciated a well-structured rollout that provides clear communication, opportunities to ask questions, practical training, and enough support for people to become confident with something new.

28. Technology Leadership & Developing People

One of the things I've come to appreciate as my career has progressed is that I don't need to be the person with every answer, and I don't think anyone benefits when one person is expected to have them all. There's a great deal of satisfaction in helping somebody develop the knowledge, confidence, and judgment to work through a problem independently, even when their approach turns out to be different from mine. As that knowledge becomes shared and interconnected throughout an organization, people become less dependent on any one individual, and the organization becomes stronger and more capable of dealing with whatever comes along.

29. Communication & Business Relationships

I enjoy technical conversations, but I also recognize that not everyone wants or needs the same level of detail. Someone responsible for running a department may be far more interested in when a problem will be resolved and what it means for their people than in the underlying technical explanation, while an engineer may need to understand exactly what's happening and why. I think being able to have either conversation, without talking down to one person or oversimplifying things for the other, is an important part of working effectively with people.

30. Measuring Success

Technology teams can produce a remarkable number of reports showing system availability, response times, completed projects, and other measurements. Those things certainly matter, but I think it's worth asking whether the people depending on those systems are actually having a better experience and whether the organization is receiving meaningful value from the resources it's investing. A technically successful project that doesn't improve anything for the people or the business isn't necessarily much of a success.

A Closing Thought

After working in several different occupations and spending much of my career in technology, I've come to believe that the most useful solutions usually begin with understanding people and the problems they're trying to solve.

I still enjoy the technical details, and I probably always will. But I've also learned that good judgment sometimes means questioning the problem itself, reconsidering an assumption, or recognizing that the best course of action is to leave something alone.

I don't believe every difficult situation has an easy answer, or even that every problem has a solution worth pursuing. What matters to me is approaching those situations thoughtfully, being willing to deal with the realities involved, and making decisions that genuinely help the people depending on them.