Software engineering / strategy

Technical credit,
treated like a first-class asset.

A clear language for engineering decisions that create future optionality, maintainability, resilience, and speed.

Concept Evidence Events Network
In one line
Technical credit names the future capacity created by deliberate software engineering work.
Current focus
Research collaboration, workshops, industrial evidence, and practice-oriented consulting.
Concept

What technical credit makes visible.

Technical credit is a way to talk about the future capacity created by deliberate software engineering work. It gives teams language for investments that are easy to overlook: architecture, automation, testability, observability, documentation, and shared understanding.

Where technical debt warns about accumulated drag, technical credit helps explain what a team should protect, amplify, and invest in before value only becomes visible under pressure.

Read the concept
Debt

Names future cost, friction, and fragility created by technical choices.

Credit

Names future capacity, optionality, and resilience created by engineering discipline.

Decision

Turns invisible engineering value into something teams can discuss, prioritize, and defend.

Research

A concept being tested through evidence.

Communications of the ACM

Technical Credit

Ian Gorton, Alessio Bucaioni, Patrizio Pelliccione

The foundational article defines Technical Credit as an investment lens for system features and engineering practices that reduce future development friction.

Read publication
ICSE 2026 SEIP Distinguished Paper Award
IEEE/ACM International Conference on Software Engineering 2026, Software Engineering in Practice

Technical Credit: Industry Views on Benefits and Barriers

Alessio Bucaioni, Ian Gorton, Patrizio Pelliccione

The industry-facing study reports survey evidence from 31 experienced software professionals and six interviews on benefits, barriers, and adoption.

Read publication
Events

Where the language becomes shared.

Talks, workshops, and roundtables create the room to compare experiences, refine examples, and translate Technical Credit into formats that researchers and practitioners can use together.

See the events
Future

IWTC 2027: 1st International Workshop on Technical Credit

Accepted as a workshop at the IEEE International Conference on Software Architecture 2027, IWTC creates a focused venue for research, evidence, methods, and practice around Technical Credit.

Collaboration

Collaboration opportunities.

The initiative is open to teams and organizations that want to apply Technical Credit in real engineering decisions, explore advisory work, or contribute evidence through research.

Collaborate with us
Practice

Use Technical Credit to frame architecture, maintainability, and long-term engineering value.

Consulting

Explore workshops, assessments, pilots, or advisory conversations with engineering leaders.

Research

Join empirical studies, develop theory, or co-author research outputs.

Network

The researchers behind the concept and first works.

The early Technical Credit work was shaped through publications by Alessio Bucaioni, Ian Gorton, and Patrizio Pelliccione. The initiative is now a place for a broader community to refine, challenge, and apply the concept.

Open the network
Alessio Bucaioni
Associate Professor of Computer Science, Mälardalen University

Alessio Bucaioni

Software engineering researcher working across software architecture, model-driven engineering, AI engineering, and industrial software systems.

Ian Gorton
Professor of the Practice and Director of Mobility Programs, Khoury College of Computer Sciences, Northeastern University

Ian Gorton

Software architecture and distributed systems researcher focused on complex, high-performance systems and architecture methods for practice.

Patrizio Pelliccione
Professor in Software Engineering and Computer Science, Gran Sasso Science Institute; Adjunct Professor, University of Bergen

Patrizio Pelliccione

Research leader in software architecture, trustworthy AI, robotics, and high-impact software-intensive systems.