This is 3.8 in a small sequence on launch decisions when building with AI.
One pattern I keep seeing is that many launch risks were already known earlier in the build but stayed as vague concerns instead of being written down.
Often a simple shared list is enough. Once risks are written down people can actually see and discuss them.
Agreed, I build something that can hopefully help alleviate these risks. I am a risk management professional by trade currently. If you're interested in checking out my QA project (open source) you can see it at agenticassure.com
That looks interesting and thanks for sharing. I’m finding I’m using YAML quite a lot lately as a bridge between human and machine readable. I’ll definitely be taking a closer look.
This is 3.8 in a small sequence on launch decisions when building with AI.
One pattern I keep seeing is that many launch risks were already known earlier in the build but stayed as vague concerns instead of being written down.
Often a simple shared list is enough. Once risks are written down people can actually see and discuss them.
Agreed, I build something that can hopefully help alleviate these risks. I am a risk management professional by trade currently. If you're interested in checking out my QA project (open source) you can see it at agenticassure.com
That looks interesting and thanks for sharing. I’m finding I’m using YAML quite a lot lately as a bridge between human and machine readable. I’ll definitely be taking a closer look.