Making Better Technology Decisions

Making Better Technology Decisions

All organizations are on a journey from where they are today, to where leadership envisions the organization should be in the future. A vision of the future is (hopefully) defined by goals and objectives, and (hopefully) includes a strategy of how to get there. In today's digital world, information technology is a critical enabler for any organization, so there will be countless technology decisions between here and there and each will bring the organization closer to or further from the envisioned future. Hence the importance of making better technology decisions.

No alt text provided for this image

What is a Technology Decision?

Before going any further, let's establish some working definitions:

Information Technology. The Gartner Glossary defines Information Technology (IT) as follows:

“IT” is the common term for the entire spectrum of technologies for information processing, including software, hardware, communications technologies and related services.
Gartner Glossary

In layman's terms, Information Technology is all the stuff typically used to electronically store, retrieve, view, move, or manipulate information. In this article, we refer to this as “technology” to avoid conflating it with the Information Technology department.

Decision. Oxford defines decision as 

The action, fact, or process of arriving at a conclusion regarding a matter under consideration; the action or fact of making up one's mind as to an opinion, course of action, etc.;
Oxford English Dictionary

After consideration, we concluded that this definition works for us!

technology decision, therefore, is a conclusion related to technology reached after consideration!

People use the word decision to refer to both the pre-consideration challenge (“we need to make a decision”) and the conclusion arrived at (“this was the decision”). 

What is “Better?”

We define “better” in this case to be a conclusion that provides better support than other possible conclusions for the following:

  1. Business Need. What is the specific business driver of this technology decision? In a well-managed organization, this business need will align with the organizational vision, but ensuring such is outside the scope of this article. While we advocate strongly for always considering the more organization-wide implications of technology decisions, the specific business need requiring the decision must always be front and center.
  2. Organizational vision. What is the organization's vision for the future as embodied in its mission, principles, values, goals, objectives, and strategy? In a well-managed organization, management will communicate this organization-wide. If not well-articulated, or if aspects of the vision are confidential and not widely shared, then extrapolate from marketing materials, executive messaging, and organizational lore.
  3. IT Vision. What is the IT vision or technology strategy? This vision may be well described in published materials – vision, principles, values, strategy, goals, and objectives or it can be extrapolated from existing IT guardrails – processes, standards, reference architectures, etc. It is IT management's response to the Organizational Vision, which answers the question of what the organization's technology needs to enable. IT Vision answers the question of how it will do it.
  4. Risk. What is the organization's risk appetite? Will the delivery or operational impacts resulting from this decision align with that risk appetite? 
  5. Operations. What will technology cost to build, install, operate, and support? What runs well in the organization's technology environment? Organizational technology standards and non-functional requirements (NFRs) provide the blueprint for what runs well. 

Technology Decisions are Inevitable

“In any moment of decision, the best thing you can do is the right thing. The worst thing you can do is nothing.”
Theodore Roosevelt

The thing about technology decisions is that there is no avoiding them. If you don't make a decision, it makes itself, often reaching a conclusion that wasn't even one of the options under consideration. There is no such outcome as “no decision,” just unexpected and sometimes detrimental default decisions. Minimize the number of technology decisions that make themselves and make better technology decisions by having a process in place for making these decisions.

Process for Better Technology Decisions

No alt text provided for this image

The subject of cognitive bias in decision-making is a topic unto itself, but it refers to the errors in thinking that can irrationally influence how we make decisions. We have all witnessed a decision-maker make a technology decision for reasons having nothing to do with sound analysis, e.g. he or she has used and liked a product in a prior organization. Having a well-defined decision process can introduce objectivity into decisions to offset the impact of cognitive bias. Here are some of the elements of an effective technology decision process:

  1. It scales up and down. The amount of process and rigor used to make a technology decision should correlate to the magnitude of impact the decision will have on the organization. You can measure the impact of a decision by evaluating different facets: financial (cost or revenue), disruption to people (organizational change), or risk, to name a few.
  2. It fits the organization's culture. Organizations make technology decisions differently depending on organizational culture. For example, some organizations centralize decision-making, while others use a more distributed approach. Unless you plan to change your organization's culture to match your decision process, you need to have a decision process that works for your organization.
  3. It results in an artifact. A good decision process includes an effective approach to share and discuss both the consideration and the conclusion. A document of record is crucial when there are numerous parties involved in the decision. But it is also invaluable for an individual decision-maker to gather thoughts to make a decision as well as have a way to recall the reasoning behind prior decisions.
No alt text provided for this image

It is also critical that decision-makers have the information they need to make better technology decisions. We can infer the necessary information from the section above, where we defined what was meant by “better technology decision.” The required information is:

  • What is the business need?
  • What is the organizational vision?
  • What is the IT vision?
  • What is the organization's risk appetite?
  • What works well in the organization's environment?

Navigating the Journey

No alt text provided for this image

The road for your organization's journey from where it is now, to where leadership would like it to be is paved with technology decisions of all sizes. Your technology decisions will take your organization somewhere. Making better technology decisions will take the organization where you want it to go.

If you think you could use some support to improve the way your organization makes technology decisions, please contact us! We have helped other organizations design the right “navigation systems,” and would love to help you!


This article was cross-posted from https://www.wittij.com/making-better-technology-decisions.

Matthew Daniels

VP, Chief Architect at Lincoln Financial Group

3 年

Great thoughts here, Dan. I also think there is something to “longevity” that relates to the long term implications of an IT decision. Often there are short term drivers to decisions that might be suboptimal if the decision in question has longer term potential impacts. Taking a longer lens pays off!

要查看或添加评论,请登录

Dan Hughes的更多文章

  • Nurturing Excellence in the Workplace

    Nurturing Excellence in the Workplace

    So, you’ve hired great people, now what? Finding and hiring the right people is only step one in the journey to a…

    1 条评论
  • Solution User Diagram for Rapid Scoping

    Solution User Diagram for Rapid Scoping

    All solution design is contextual. It is impossible to know the right design unless you know why you are designing.

    3 条评论
  • The Problem with Platform-Specific Architecture Diagrams

    The Problem with Platform-Specific Architecture Diagrams

    The emergence of cloud architecture has spawned some new and trending platform-specific solution architecture diagrams.…

  • Wittij Consulting Slogan Bloopers

    Wittij Consulting Slogan Bloopers

    After the Wittij Consulting name was established, it was time for a slogan. After coming up dry using internal…

  • How to Hire Great People

    How to Hire Great People

    We frequently have clients make very positive statements about the people who work for Wittij Consulting. I have a…

    2 条评论
  • The Wittij Consulting Name

    The Wittij Consulting Name

    A common question people ask me is how I came up with the name “Wittij Consulting.” Probably second only to “how do you…

    4 条评论
  • Non-Functional Requirement Examples

    Non-Functional Requirement Examples

    I always find having some examples can be helpful when trying to understand something, so as a follow-on to my articles…

  • Writing Non-Functional Requirements: A How-To

    Writing Non-Functional Requirements: A How-To

    I recently introduced the what, why, and how non-functional requirements, a specific technology guardrail for making…

  • Non-Functional Requirements: What, Why, and How

    Non-Functional Requirements: What, Why, and How

    Let’s continue our journey to make better technology decisions! We introduced the topic of technology guardrails, then…

    2 条评论
  • Leading Through a Crisis

    Leading Through a Crisis

    For me, leadership covers a lot of ground. If you make decisions that impact other people, you are a leader.

社区洞察

其他会员也浏览了