Making Software Greener helps organizations understand the hidden consequences of software decisions before those consequences become expensive problems.
We work at the intersection of software architecture, engineering intelligence, operational resilience, cost, sustainability, and systems thinking.
Our focus is not only whether software works today.
It is whether that software can continue delivering value as growth, complexity, cost pressure, organizational change, and new technologies increase.
Why We Exist
Software systems rarely fail because of one catastrophic decision.
More often, problems accumulate quietly.
A shortcut that seemed harmless becomes difficult to change. A dependency becomes critical. A retry policy amplifies load. A cloud architecture becomes increasingly expensive. Knowledge becomes concentrated in too few people. AI-generated code accelerates delivery faster than teams can evaluate the consequences.
Individually, these decisions may be reasonable.
Together, they can create fragility.
Making Software Greener exists to help organizations see those conditions earlier, while they still have choices.
Our Mission
Our mission is to help organizations understand and improve the survivability of their software systems.
We do that by identifying architectural weaknesses, operational risks, hidden waste, scaling constraints, and other conditions that may prevent software from continuing to deliver value as pressure increases.
Our goal is not to eliminate every imperfection.
It is to help teams understand which conditions matter, which risks can safely remain, and which decisions are likely to become expensive or dangerous later.
Our Vision
We believe engineering teams should be able to understand the consequences of software decisions before those consequences become failures.
As software becomes easier and faster to create, especially with AI-assisted development, engineering judgment becomes even more important.
Our long-term vision is to make software survivability something organizations can understand, measure, and improve continuously.
That means making the relationships among architecture, operations, cost, maintainability, organizational capacity, reliability, and sustainability more visible.
How We Think
Waste is a Bug
Waste is not only an environmental issue. It can appear as unnecessary compute, unnecessary complexity, repeated work, avoidable infrastructure cost, engineering time, operational friction, or lost organizational capacity.
Architecture Matters
Architecture is not simply boxes and arrows. It is the accumulated set of decisions that determine how a system behaves when conditions change.
Every Solution is a Commitment
Every technical decision creates future constraints, dependencies, opportunities, and consequences. Some are obvious immediately. Others emerge only under pressure.
Performance, cost, reliability, and sustainability are connected.
They are often different symptoms of the same underlying system decisions.
Proximity Dulls Perception
People closest to a system naturally inherit its assumptions. Sometimes an independent perspective is necessary to see what familiarity makes invisible.
Software should survive change.
The important question is not simply, “Does it work?”
It is:
Can this software continue delivering value as pressure increases?
We call that software survivability.
What We Do
Our flagship offering is the Survivability Review, a structured examination of the conditions that may threaten a software system as pressure increases.
We look across architecture, dependencies, operations, technical decisions, organizational realities, cost, maintainability, and other relevant evidence.
The goal is not to produce a pile of findings.
The goal is to provide a survivability judgment, explain the reasoning behind it, and help organizations understand what matters most.
We also provide focused services around cloud efficiency, software waste, AI-generated code, and related engineering risks.
About the Founder
Making Software Greener was founded by Matt “Kelly” Williams, a software and systems professional with more than three decades of experience across development, systems administration, infrastructure, cloud, DevOps/SRE, architecture, consulting, technical governance, and education.
His work has spanned startups, software companies, consulting organizations, multinational nonprofits, and large-enterprise environments.
Across those roles, a recurring pattern emerged: major failures are often described as sudden, even though their causes accumulated quietly over time.
Making Software Greener grew out of that observation and the belief that better engineering intelligence can help organizations recognize those conditions earlier.
About Our Ecosystem
Making Software Greener is part of a broader ecosystem of work around sustainable and resilient technology.
The Sustainable IT Manifesto Foundation is a separate nonprofit initiative focused on advancing sustainable IT practices and publishing shared resources, including the Eco Rules Catalog.
Making Software Greener draws on that public body of knowledge as one input into its proprietary analysis methods and technology.
Matt also serves on the advisory board of the Green Computing Foundation, contributing to broader conversations around sustainable computing and responsible technology.
Where We’re Going
Making Software Greener is evolving from expert-led analysis toward scalable engineering intelligence.
The long-term goal is to help organizations identify hidden risks and systemic consequences earlier and more continuously, before growth, complexity, cost, turnover, or other pressures turn them into failures.
Software is becoming easier to create.
Understanding what it will become is the harder problem.
That is the problem Making Software Greener is working to solve.