By now, you’ve probably gone through the basics and understanding not only the first few principles but how outcomes, contexts and events all work together. Which is great; you’re on the right path to making your life easier by using BBT. This next principle is one we’ve probably all heard at some point in our lives, the KISS rule. In the BBT world, this translates to Keeping it Stupid Simple. Sounds pretty basic right? That’s because it is, but just because it sounds basic doesn’t mean its easy or second nature to everyone.
When creating your BBT graphs, it’s very easy to overdo it. Whether it’s to many contexts and outcomes thrown into one graph or if there is just too much behavior for a single feature. Never be afraid to start breaking things up. The majority of cases where things get out of hand are because a few different behaviors are clumped together in a single graph. You have to resist this common trap. For example, a new feature was just developed that touch not only logging into an account but creating one as well. Just because they are handled in the same story or ticket, doesn’t mean they have to be done in the same graph. When you have simpler graphs they become easier to read, not only by the user (i.e. you), but the product owner as well. And because they are easier to read, making any adjustments becomes easier as well.
BBT is all about testing the behavior of each feature, but if you don’t utilize it in a clean and easy to read way, some behavior can get lost in the clutter. Once again the KISS rule is applied and it keeps everyone happy. But remember it is very easy to fall into traps of over complicating things. You have to resist, “future you” will thank you for it. I encourage you to keep learning more about BBT and the other principals involved with making its usage easier.