Uncover the hidden decisions shaping your team's future and performance.

In the presentation "Hidden Decisions You Don’t Know You’re Making," Dan Fike and Shawna Martell delve into the often-overlooked choices that shape software architecture and engineering culture.

3 min readInfoQ
Uncover the hidden decisions shaping your team's future and performance.

Every team has decisions it knows it made. The ones that shape your future, though, are often the ones nobody noticed at the time. Dan Fike and Shawna Martell have done the field a real service by pulling those invisible choices into the light.

Their central insight is simple and powerful: what looks like a neutral default, a CI/CD pipeline configuration, a metric choice, a platform dependency, is actually a decision that encodes values. When your build pipeline bottlenecks, that is not a technical problem. It is the accumulated weight of past choices about what speed mattered, who could approve changes, and how risk was defined. When your engineering culture feels misaligned with your stated goals, the culprit is almost never bad intentions. It is the set of invisible defaults that reward the wrong behaviors. Martell and Fike call this the "decision behind the decision," and the phrase earns its keep.

For leaders, the practical implication is uncomfortable but freeing. You cannot fix a culture by writing a new mission statement. You can fix it by auditing the systems that silently incentivize your team every day. Is your platform so complex that only senior engineers can deploy? That is a decision about inclusion and velocity, whether you meant to make it or not. Are your metrics focused on output rather than outcomes? That decision shapes career growth, risk tolerance, and collaboration. The framework Martell and Fike offer is a lens for seeing these structures clearly, and that clarity is the prerequisite for intentional change.

The real test of this work is not whether you agree with their examples. It is whether you can apply the lens to your own context. Start with one bottleneck that frustrates your team. Ask what default created it. Ask what decision that default replaced. Then ask whether you would make that same choice today. That is the work. It is not glamorous, and it does not require a transformation initiative. It requires the discipline to stop treating inherited systems as neutral and start treating them as choices you can remake.

From InfoQ

Dan Fike and Shawna Martell explain how "hidden decisions" silently shape software architecture and engineering culture. By examining the invisible defaults behind CI/CD bottlenecks, platform complexity, and misaligned metrics, they share frameworks for leading with intentionality. Learn to identify the "decision behind the decision" to better incentivize high-performing teams and careers.

Read the original at InfoQ