Design It!

Let Risk Be Your Guide

Shortly after the first stakeholder meeting on a new software project, I always feel a giant pit grow in my stomach. If I didn’t have that feeling, then I would be worried. Software worth building always has risks. You should feel a bit uncomfortable at the start of a new project. After all, if you knew everything at the outset and had no questions about what you were going to build, then why would an architect be needed?

We can use that slight sinking feeling in our guts to our advantage. Risk is an excellent indicator of what might prevent us from succeeding. To harness the power of our guts, write down all the things that worry you about the software system. Next, prioritize the items on your list so that the things ...