Problem Creep: Breathe and Solve

Previously, I wrote about technical debt difference when solving the local development on-boarding is a problem.

As a technical leader, avoiding technical debt that becomes problem creep is difficult as:

• there’s no one on the business side to “blame”
• results are still expected, even with the problem
• the problem can be so bad it is a cultural issue
• fixing can become a challenge - either by knowing what the you & the team wants or even seeing the final solution while delivering.

In such challenges, like with local development on-boarding, it’s important to remember to breathe. The problem sucks now and you do have the power to fix it.

Just remember to find a solution that is:

• consistent with team values
• sustainable
• get buy in from partners

In a way, this make the technical challenge even more interesting than just a business problem.

Next, I talk about solution creep.