Chris Sterling goes over some of the things they discussed and shares his account of the workshop with us.

Technical debt is an interesting topic because we do not necissarily have a succinct measurement of it. Generally speaking things like mechanical engineering and electrical engineering have been blessed (or cursed) with standards that give them a common terminology or view of what 'good' engineering practices are.

In the world of software development we have a time-honored tradition to measure success on revenue and deadlines and sacrifice quality to get there.

Talk with your team about what technical debt is to them and come to a consensus and stick to your guns as technical people because non-technical people really need you to tell them when quality is being sacrificed and technical debt is being accrued.