Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

Evidence-based decision-making: A framework for IT

Solicit a proposal from your average consultant and you’re likely to unearth in the ensuing PowerPoint a slide that extols the virtues of the consulting firm’s “frameworks and methodologies.”

You — and, for that matter, the consultants as well — probably chalked up the phrase to the realm of redundancy-driven concept amplification, where saying the same thing twice using different words lends a certain profundity to the proceedings.

But frameworks and methodologies aren’t the same thing. They’re both important when you’re trying to organize a change effort, but they’re fundamentally different.

A framework shows how the relevant bits and pieces fit together. A technical architecture framework, for example, explains how applications, platforms, infrastructure, and so on can be assembled into a functioning technical environment.

A methodology describes the work that must get done to assemble the frameworks’ various components into a working whole.

Fail to settle on a framework and you’ll have the equivalent of a pile of lumber and other construction stuff. Lack a methodology and nobody knows which 2×4 to pick up and nail into place, and when to pick it up.

A rational approach to IT decisions

Which takes us to your desire to incorporate evidence-based decision-making into your organization’s business culture, and the need you didn’t know you had for a framework to facilitate it.

Fortunately for you, your tax dollars (okay, my tax dollars) have led Minnesota Management and Budget to develop a framework for defining evidence in a practical way.

While developed to help Minnesota government agencies make evidence-based policy and service-design decisions, you and your organization might find it useful, too. To get you started, here’s a quick summary of MMB’s six-level framework:

  • Proven effective: A service or practice that’s been Proven Effective offers a high level of research on effectiveness for at least one outcome of interest. Qualifying evaluations use rigorously implemented experimental or quasi-experimental designs.
  • Promising: A Promising service or practice has some research demonstrating effectiveness for at least one outcome of interest. Qualifying evaluations use rigorously implemented experimental or quasi-experimental designs.
  • Theory Based: A Theory Based service or practice has either no research on effectiveness or research designs that do not meet standards. These services and practices may have a well-constructed logic model or theory of change but, at the risk of being redundant, aren’t supported by evidence.
  • Mixed Effects: A Mixed Effects service or practice offers a high level of research on the effectiveness of multiple outcomes. However, the outcomes have contradictory effects.
  • No effect: A service or practice rated No Effect has no impact on the measured outcome or outcomes of interest.
  • Proven Harmful: A service or practice that’s Proven Harmful offers a high level of research that shows program participation adversely affects outcomes of interest.

Weighing risk vs. reward

A framework like MMB’s can be immensely valuable, especially when contrasted with meaningless catch-phrases like “best practice” or advocacy based on a key decision-maker “trusting their gut.”

But it does have a serious limitation: While decision-makers can be confident that approaches rated proven or promising will result in a positive outcome, that doesn’t mean they’ll deliver as good an outcome as you might get from one or more untried alternatives.

And in fact, MMB’s framework could, due to its chicken-and-egg-ish nature, stifle promising alternatives that have never been tried.

So if your goal is to minimize the risk of failure, limit your choices to what has been proven effective or are promising. And certainly, avoid those that are proven harmful.

But limiting your choices like this also means filtering out alternatives that might turn out to be spectacular successes — when, that is, there’s reason to think the value returned from an untried, theory-based approach exceeds the risk of failure.

Because (okay, call me Captain Obvious) until you and a bunch of others have tried a bunch of stuff that hasn’t yet been proved effective, it can never be proved effective.

A theory-based conclusion

The moral of this story is that choosing a course of action based on evidence-based decision-making should, for most business managers, be the default way of making decisions. But that doesn’t mean you shouldn’t ever try alternatives that might not work out.

Especially, if you find the theory supporting a course of action to be convincing and you can manage the risk that comes with something untried.

And that’s where progress comes from.

P.S. I know you’re wondering if MMB’s framework is, in fact, proven, or even promising.

Me too. So I’m counting it as a Theory-Based approach, which probably makes it as good as any alternative you’re likely to encounter.

See also:

  • 8 venial sins of IT management
  • ‘Chronodebt’: The lose/lose situation few CIOs can escape
  • AI benefits don’t scale
  • Political engineering 101: The biz-savvy IT leader’s survival guide


Read More from This Article: Evidence-based decision-making: A framework for IT
Source: News

Category: NewsSeptember 18, 2025
Tags: art

Post navigation

PreviousPrevious post:Qué estrategias de talento establecen los CIO para preparar su plantilla de TI de cara al futuroNextNext post:AI 개발 시장 주도권, 앤트로픽으로?···MS, VS코드에 클로드 우선 노출

Related posts

「健康情報」はなぜ特別扱いなのか――個人情報保護法から見た医療データ
December 14, 2025
インド・フィンテックの2025年を振り返る
December 14, 2025
ソフトウェアサプライチェーンの透明化が問い直す企業の信頼――SBOM世界標準化の現在地と日本企業が講ずべき生存戦略
December 14, 2025
フェデレーション技術が拓く「集めないデータ活用」の新地平――企業ITが直面する分散型アーキテクチャへの転換点
December 14, 2025
オプトインからオプトアウトへ―次世代医療基盤法が変えた医療データのルール
December 13, 2025
AI ROI: How to measure the true value of AI
December 13, 2025
Recent Posts
  • 「健康情報」はなぜ特別扱いなのか――個人情報保護法から見た医療データ
  • インド・フィンテックの2025年を振り返る
  • ソフトウェアサプライチェーンの透明化が問い直す企業の信頼――SBOM世界標準化の現在地と日本企業が講ずべき生存戦略
  • フェデレーション技術が拓く「集めないデータ活用」の新地平――企業ITが直面する分散型アーキテクチャへの転換点
  • オプトインからオプトアウトへ―次世代医療基盤法が変えた医療データのルール
Recent Comments
    Archives
    • December 2025
    • November 2025
    • October 2025
    • September 2025
    • August 2025
    • July 2025
    • June 2025
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.